I'd like to start designing a website using Jekyll or Hugo. The plan is to publish it on GitHub or GitLab pages.
After hours of searching I'm pretty confused about all the facts. Hugo support natively a multilanguage utility while Jekyll not. There are some plugins for Jekyll but plugins are not supported on GitHub pages anyway.
With Jekyll I tried to follow this solution without any concrete solution for the translation of the layouts while with Hugo I've found the instruction pretty confused (but that's my fault).
What I'm looking for is a theme (Jekyll or Hugo it doesn't matter) that is already designed with 2 (or more) languages.
Beside the official Hugo instructions for creating a multilingual site, you also have:
multilingual examples which has been recently updated
multilingual mode
themes with multilingual already baked in as (from the Hugo themes list site):
hugo-scriptor-theme
dimension
docuapi
Plus, with Hugo 0.87 (Aug. 2021), you also have Date/time formatting layouts and localized string for the current language.
As well as the themes that VonC linked to, there is the Beautiful Hugo theme which I recently updated to work with multilingual sites.
I also recently made an example of a multilingual Hugo site in hugo-multilingual-example at Github, so you can compare that with the example in the Hugo repository that VonC linked to.
With Hugo, you should ignore the "Create a Multilingual Site" tutorial, as it was made before the native multilingual support was added, and is now outdated. Instead, you should base everything on the "multilingual mode" documentation.
Hopefully that should be enough to get you started, but let us know if you have any other problems.
I localized a Jekyll theme to output to German and Japanese here. It depends what requirements you're trying to support. We sent out translated files to a translation agency and then reimported them back into the project.
My strategy in defining the theme was to put each language in its own collection. Each collection defines default values for top nav and footer to be in that language.
Additionally, I used a different config file for each language. The language's config file defined strings for that language. File names and URLs remained in English.
Related
I have an umbraco based CMS site and I've been advised to use AMP for fast mobile performance. I have read the demo page from this gitHub link.
But I am not understanding how to set it in an already developed site. Do I need to change all tags according to AMP?
better not to mess with existing instead you build new AMP version of your site
(After doing a quick Google)
I don't think there's a an AMP-plugin for Umbraco yet, but that will probably be the way to go. I've been using the AMP-plugin for WordPress for a little while now and it made all posts on my site AMP-compatible without me having to do anything :)
Perhaps check with the Umbraco community whether there's an ETA on such a plugin for their platform?
You can have seperate AMP pages and google will handle the rest. I think that is the safest way to approach it, without having a plugin like they have for wordpress.
You can still enable the users to use the CMS functionality by creating custom data types for e.g. amp-img instead of img. The content editors will just have to be briefed on the basics of AMP.
References:
https://carolelogan.net/blog/amp-implementation-in-umbraco/
https://www.ampproject.org/docs/guides/discovery
I wrote a Javascript (jQuery) plugin. Now I want to write a documentation site for it. Is there a good tool to create such a site out of some offline file formats or works like a CMS?
I know this answer has been asked before, but the last answers are from 2011. Is there anything new that does an awesome job in writing documentation?
There are a few new tools for generating websites or blogs from code/directory.
Bootstrap v3 just switched to jekyll for documentation. jekyll knows how to process Markdown or Liquid (markdown flavours)
Grunt.js is also used for all sorts of automated task. One of these being documentation generation. Search their plugin list for doc
assemble.io is another tool for generating documentation pages
I'll extend if I bump into others. I am not sure if this is exactly what you need, but they are general purpose so I am sure a jQuery plugin can fit in.
I had an issues with some joomla api. The issue was that I was using the latest version of joomla and couldn't find where a joomla class, that was being called in my code, was derived . I searched the joomla api docs and found nothing relating to the class I was looking for.
I then stumbled across the refactoring change log for joomla and noticed that the function i was after had actually been moved from /libraries/joomla/form to libraries/cms/form.
Why would this be the case? There doesn't seem to be any reference to /libraries/cms in the api docs. How are we suppose to know that there are classes living there? Very confusing.
Since Joomla! 1.6 the code has been progressively split into the Joomla! CMS and the Joomla! Platform. You can see this separation in the github repository - a good place to also keep track of changes that are committed to both the CMS and the Platform. The simplest way is fork each repository and keep track of them.
As classes are updated they may be migrated to the /libraries/cms directory if they apply specifically to the CMS application (e.g. html forms are an application level function not a platform level).
I find the best place to hear about changes under discussion are in the respective Google Groups - Joomla! Platform Development and Joomla! CMS Development
[Edit]
Documentation of class's is the hardest thing to find for Joomla! CMS - there doesn't appear to be a current api listing for it, unlike the Platform API reference. Often it is just easier to read through the code.
It's also worth keeping a watch on the developer sub-site.
If you want to define excellence in CMS without coding, Joomla is the right option for you.Joomla the most preferred content management system among developers is an easy-to-use open source solution.If you want to define excellence in CMS without coding, Joomla is the right option for you. In this post, you will find few of its features that make the website development easy and most preferred option for developers.
I just visited the Static Website Generation on Ruby toolbox and I don't know which of applications listed there is best suited for a little blog engine. Basically I need:
an index page with 1..5 of latest articles with shortened content;
possibility to add few main pages and a menu to access them (breadcrumb optional);
show articles
show/search archives
commenting system - Disqus Ok
tag-list cloud - optional
Look&Feel via layout
Important all content will be translated in 3 languages!
I can host on my own server, so side processing is possible.
Update:
First I'll try nanoc => blog's source on github
I think nanoc worth a try it has everything you specified, even if is not the best ranked on ruby toolbox its actively developed and highly customizable.
nanoc is a tool that runs on your local computer and compiles documents written in formats such as Markdown, Textile, Haml… into a static web site consisting of simple HTML files, ready for uploading to any web server.
and thats true :) I use it for a while not specially for a blog, but it has also helpers for that...
check out jekyll, it should work well for this.
Try my own "serious" - apart from archive search and tag cloud, it has everything you specified, plus the basic install should take you something like 5 minutes on heroku (and maybe 10 on your own server via Rack). It also has syntax highlighting, Disqus comments, Google Analytics and other goodies.
http://github.com/colszowka/serious
gem install serious
Disclaimer: It does not produce static html pages you can upload to your php vhost, though. But it uses caching and is really easy to setup and works on the free plan on heroku.
I know many Ruby users are using Jekyll but I wonder what the benefits that will bring over RefineryCMS?
Could someone highlights the differences and pros/cons for each.
I'm one of the core developers on Refinery CMS.
The architecture of each project is vastly different. Here's a few things Refinery CMS has:
Web based interface (just go to /refinery to login and edit content)
Visual content editing (but also supports editing in plain HTML)
Stores it's content in a database (MySQL, SQLite, PostgreSQL - your choice)
Suitable for non technical people to edit
Supports Rails 3
Supports localisation in 11 languages (and you can add your own)
Support and docs: IRC, Google Group, Tutorials, API docs, Github repository
I can't be authoritative about Jekyll (maybe mojombo can answer) but it looks like:
Static content editing
Stores it's content in files
Developer focused, not suitable for an end user to edit
Markup based editing
Will load slightly faster as the pages are static
I hope that helps weigh it up. It all comes down to your project requirements.
Well, jekyll is 100% static. All files are generated into static HTML. Jekyll is amazing for small sites that don't really need dynamic content. With jekyll you write the content in your own text editor.
I haven't tested RefineryCMS, but it is more like what you would think of as a content management system with data stored in a database managed through a web interface. If the site is going to be managed by non-tech people, I'll say jekyll is a no-go and that refinery is a better choice.
RefineryCMS is fully Rails 3.0 compatible and they offer great support over IRC. Furthermore RefineryCMS is a fully featured CMS with a localizable interface while Jekyl is not. It all depends on your projects needs.
The best thing to do would be to install them both and play. You will soon see they both serve two completely different purposes. Refinery is a CMS and Jekyll is a static site generator . Jekyll is not built for content management.