Re: [SyncEvolution] syncevolution.org reorganization: 1.0, Wiki, translations
On Mon, 2010-04-12 at 13:32 +0100, Patrick Ohly wrote:
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.
Did not happen, so I took the liberty to move ahead with reorganizing
the site.
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).
As you've seen in the 1.0 announcement, there's now a "Phone Config
Template" Wiki page. I hope that more people will use that to share
their experience with specific devices.
Mike, is there an easier way to clone that page? Right now one has to
click on "edit", copy the content, then start a new page with it.
* 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.
Moved into the "about" page. The Wiki page is still around. I intend to
update the Wiki page, then copy it over to "about" for major releases.
* Split up "Compatibility" and move most of the
content into the
Wiki.
* Same with "Known Issues".
Done.
* Add information about sync-ui.
Still missing.
* Move "Development" content entirely into Wiki, with
tags to find
it.
Not done yet, because Mike and I still need to figure out how to make it
so that old links and the menu structure remain intact.
Mike, you mentioned problems with setting up search pages for specific
tags. I think this would be useful now.
* Make more information from the source code (API, config
properties) available online (long term goal and long overdue, I
fear).
Also still to be done.
--
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.