Hello! It's time to think about updating syncevolution.org to cover 1.0 and current features. Before I actually go ahead, let me outline what I have in mind. I'm hoping that people perusing the information there will provide feedback so that the site remains (or becomes...) useful. Here's roughly what I intend to do: * Introduce a Wiki as part of the main Drupal engine. More on that below. The goal is that this setup should make it easier to gather user-contributed documentation (howtos, information about compatible phones or HTTP SyncML servers). * Improve the description of what SyncEvolution is and does. There's a draft in http://syncevolution.org/wiki/features which will end up "/documentation/features" and partly replace "/documentation" itself. * Make it as clear as possible when a certain feature was introduced, so that we can avoid creating different copies of the pages for different releases. * Split up "Compatibility" and move most of the content into the Wiki. * Same with "Known Issues". * Add information about sync-ui. * Move "Development" content entirely into Wiki, with tags to find it. * Make more information from the source code (API, config properties) available online (long term goal and long overdue, I fear). There was a offer to help with translating syncevolution.org into Japanese. I replied back to that person that in principle I appreciate the offer, but I'm a bit afraid of the translated content getting stale. What do others think? About the Wiki at http://syncevolution.org/wiki/ - right now, it is very similar to editing normal Drupal pages, with less restrictions for creating and editing pages. New pages all show up under "/wiki/". Mike looked into creating overview pages based on tags. I didn't see a need immediately, but now I think this would be useful to mark pages as "Development", for example. Markdown+plain HTML is the main markup method. There are no dedicated Wiki features, like camel casing a word to create a link and then create that page. The advantage of this approach is that content can be copied back and forth between the "main" site and the Wiki. The disadvantage is that linking, markup and organization is a bit more limited compared to full-blown Wikis. I myself would have found reStructuredText useful. Even extended Markup was a bit limited for tables, whereas HTML is very verbose for that purpose. But there doesn't seem to be good support for it in Drupal, so we don't have it at the moment. Nothing is set in stone here. Feedback welcome... -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.