Overview

Currently, the openATTIC project web site is hosted on a Typo3 CMS, which is somewhat cumbersome to use and pretty much overkill for a small project web site like ours. It also raises the bar for making improvements to the web site, as it requires a login account.

Instead, we'd like to migrate and update the content to a static web site. Using a static web site has several benefits (e.g. fewer resource needed, more secure) and it allows participation and contributions using tools familiar to a developer (e.g. a text editor and revision control)

What needs to be done?

As we're already using Nikola for the openATTIC blog, we've decided to stick to using Nikola for the rest of the web site as well (to minimize the amount of tools and to have a single build process).

The basic structure and content of the web site has already been created and is available from a dedicated website branch in the openatticblog git repository on BitBucket.

The key remaining work is making the web site more visually appealing and polishing the content. The web site uses a theme based on Bootstrap. Once the content and layout have been finished, we'll replace the current live instance with the static site.

The current state of development can be previewed here: http://openatticblog.netlify.com/

References:

• Creating a Site (Not a Blog) with Nikola
• README.md that describes how to check out and build the blog / web site
• Contact