Another thought, Jekyll has useful features for storing data which would be better than my config.yml suggestion. The data could be more structured then if you wanted, showing the latest release per major version or something (so 1.8 => 1.8.4 etc).

http://jekyllrb.com/docs/datafiles/ and http://jekyllrb.com/docs/collections/ have more details.

This might also be a good time to add some opt-in metrics for the project too. The request to the site could (optionally, of course) include some useful data in the headers, such as the current Foreman version, plugins in use (and versions) etc.

This would probably require something to process those headers on the website side - I've not looked at the Jekyll features Dominic mentions though, as to whether that could handle it...

Jekyll's only a templating engine, we have no capability for dynamic behaviour - it can only generate static content.

• we would probably need to provide the list of plugins and their versions, the same for the proxy and its plugins?
  • for proxies, we probably need to extend foreman to know the proxy version, atm I don't think we are storing it in the db. (maybe even per feature to include plugins).
• we would need to enable security headers to allow CORS- most likely to *.theforeman.org - similar to gravatar.
• it would be nice to query using GET with the current version numbers, this would allow us to know a bit on our installation base, but not required.