Web Site specific road map

The following is the current roadmap for FidoCadJ web site. We are going to work in two big areas: help and new ideas are welcome!

1. general website polishing and improvement
2. internationalization of website

General website polishing and improvement, proposals:

• Change the menu item label "about" in a more immediate and traditional "home" [DONE !]
• Keep a hierarchical organization for storing resources such as images, currently at the same level of pages [DONE !]
• Delete the current "download" link in the menu and add a big Download button with the most popular version. One might choose alternative versions from a selector menu. The download page will however remain useful for providing additional information. See issue 13
• The former Download button will be "Development" or "Contribute", a brand new page with information for good men that want to help us!
• The image's name all around the website will be Search Engine Optimized.
• CSS code will be minified through an external free web service. The native code will be preserved in a no-indexed folder.
• A robots.txt file will be provided.
• The CSS style selectors will be polished and the current use of classes, where not needed, edited.
• The FAQ page will have an index on top of content, when is visited with a mobile device [DONE !]
• Google Analytics js script will be added. (DarwinNE, you need to open a free analytics account with big G)
• I will add meta-description tags on all pages (MightyThor) [DONE !]
• I will try to make tables more responsive (MightyThor).
• A footer will be added on all pages. See issue 10

The internationalization of website

• We will need a classic language-folder tree for content storing and organization.
• It will be useful to have a language selection buttons set or menu.
• A good cookie system will be added for language preferences preservation.
• I will translate the website content in Italian by myself (MightyThor).
• All the pages will be PHP coded. We will run it locally, since the server on GitHub does not support PHP. From that moment, we will save the generated HTML code, localized in different languages and made it available on the site. But if we will move the web site on a server that can run PHP, or GitHub changes its policy about server-side script execution, we will have a dynamic PHP web site ready to go.

If you want to partecipate in website development, open a new issue with a "website" label.