ClusterLabs,org is partially generated by jekyll. Installing jekyll requires the following dependencies:

• nodejs
• npm
• ruby
• ruby-devel
• rubygems
• rubygem-bundler
• rubygem-rdiscount

Once you have those, change to the src directory and run bundle install.

ClusterLabs.org's jekyll source is under the src directory. Jekyll will generate static content to the html directory.

To generate content in a checkout for development and testing, change to the src directory and run bundle exec jekyll build (to merely generate content) or bundle exec jekyll serve (to generate and test via a local server). To generate content on the production site, run JEKYLL_ENV=production jekyll build (which will enable such things as site analytics and asset digests).

If src/Gemfile changes, re-run bundle install afterward.

We use the jekyll-assets plugin to manage "assets" such as images, stylesheets, and JavaScript. One advantage is that digest hashes are automatically added to the generated filenames when in production mode. This allows "cache busting" when an asset changes, so we can use long cache times on the server end. Another advantage is that sources are minified when in production mode.

How CSS is managed:

• src/_assets/css/main.scss is just a list of imports
• src/_assets/css/_*.scss contain the CSS to be imported by main.scss
• jekyll will generate html/assets/main.css (or main-_HASH_.css) as the combination of all imports
• web pages can reference the stylesheet via {% css main %}

JavaScript is managed similarly:

• src/_assets/js/main.js is just a list of requires
• src/_assets/js/*.js contain the JavaScript to be required by main.js
• jekyll will copy these to html/assets
• jekyll will generate html/assets/main.js (or main-_HASH_.js) as the combination of all JavaScript
• web pages can reference the script via {% js main %}

How images are managed:

• src/_assets/images/* are our images
• web pages can add an img tag using {% img _NAME_._EXT_ %}
• web pages can reference a path to an image (e.g. in a link's href) using {% asset_path _NAME_._EXT_ %}
• CSS can reference a path to an image using url(asset_path("_NAME_._EXT_"))
• only images that are referenced in one of these ways will be deployed to the website, so _assets may contain image sources such as SVGs that do not need to be deployed
• Tip: http://compresspng.com/ can often compress PNGs extremely well

Site icons used to be easy, right? favicon.ico seems downright traditional.

Unfortunately, site icons have become an ugly mess of incompatible proprietary extensions. Even favicon.ico is just a proprietary extension (and obsolete, as well). Now, there are also apple-touch-icon[-NxN][-precomposed].png (with at least 12 different sizes!), browserconfig.xml, manifest.json, link tags with rel=(icon|shortcut icon|apple-touch-icon-*), and Windows Phone tile overlay divs.

If you want to be discouraged and confused, see:

• http://stackoverflow.com/questions/23849377/html-5-favicon-support

• https://mathiasbynens.be/notes/touch-icons

• https://css-tricks.com/favicon-quiz/

There is no way to handle the mess universally. In particular, some devices do much better when different icon sizes are provided and listed in the HTML as link tags, and will pick the size needed, whereas other devices will download every single icon listed in those link tags, crippling page performance -- not to mention the overhead that listing two dozen icon sizes adds to the HTML.

We've chosen a simple approach: provide two site icons, a 16x16 favicon.ico, and a 180x180 apple-touch-icon.png, both listed in link tags in the HTML. Most browsers/devices will choose one of these and scale it as needed.

The clusterlabs.org web server is configured to redirect certain old URLs to their new locations, so be careful about renaming files.