Great! A little background info: the site uses Jekyll (http://jekyllrb.com), a static site generator. Jekyll is supported natively by GitHub Pages, which means they'll run the generation and push the result to their CDN on every commit to the repository. That should also allow for a pretty smooth editing experience for contributors, as clicking the "edit" button on the respective page on GitHub automatically prepares a pull request - all from the web UI. For larger contributions it'll make more sense to preview locally, so I'll add some instructions how to setup Jekyll to the readme later.
The front-end uses Zurb Foundation (similar to Bootstrap). All content of the old site is in /old_site and I've migrated most of the relevant pages (well, those that seemed relevant to me) to /docs with a new structure. Some pages where I'm still not sure where to put them are in /docs/_doc_candidates. Question: does the new structure under /docs make sense? I think we'll replicate that structure on the documentation landing page in some way, e.g. links to the getting started guides etc. As others have noted, many pages are severly outdated or contain invalid links. Fixing that will be the next step, but I'd appreciate some feedback whether the structure makes sense so far. -- Alex -- View this message in context: http://mono.1490590.n4.nabble.com/Mono-Project-website-tp4663100p4663142.html Sent from the Mono - General mailing list archive at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
