Hi,
The
jboss.org Team are proud to announce the release of the JBoss Community Bootstrap theme aimed at projects wishing to host project pages using the
jboss.org domain name (e.g.
jboss.org/<project> or <project>.
jboss.org):
The theme is structured as an Awestruct project in order to act as a starting point for development of project pages, principally through the use of HAML layouts which have been confirmed to work well with the modified Bootstrap CSS and JavaScript. Although the CSS (LESS) and JavaScript source code are stored in the repo the intention is for projects to reference the compiled/hosted versions at:
This ensures that the L&F for all projects using the
jboss.org domain has some form of consistency, rather than each project having their own modifications and looking slightly different. Ideally all projects will update to subsequent releases of the JBoss Community Bootstrap theme at the same time but we recognise there may be some delay which could introduce some inconsistencies.
Full instructions for use can be found in the
README.md file including System Requirements and steps to fork the repo contents into your own GitHub organization in order to start your project.
You can find an example project site using the latest version of the JBoss Community Bootstrap theme here:
Staging and Trademarked Images
-----------------------------------------------
In addition to the www_htdocs/<project> directories on
filemgmt.jboss.org that contain the production versions of your project websites you can now upload files to a stg_htdocs/<project> directory in order to test them first on a staging domain name, e.g. <project>-
stg.jboss.org
Similarly you can now upload any Red Hat trademarked images such as project logos, banners and desktops to an images_htdocs/<project> directory which makes them accessible from
http://static.jboss.org/images/<project> as per legal requirements. These can then be referenced in your project pages.
This release was a combined effort from the
jboss.org team and Eng Ops with additional thanks going to Xavier Coulon, Jason Porter and Pete Muir for reporting issues and suggesting fixes.