From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Erik K." To: documentation@lists.ipfire.org Subject: Re: IPFire Wiki Workflow Date: Thu, 11 Jul 2013 19:54:40 +0200 Message-ID: In-Reply-To: <54C3C794-4F06-439A-8FD6-56104D4E5A3B@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4086540618476469696==" List-Id: --===============4086540618476469696== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sorry wrong link for the new structure, this one is it --> http://wiki.ipfire= .org/nonpublic/de/configuration/start Am 11.07.2013 um 19:30 schrieb Erik K.: > Hi all, > regarding to the ideas causing a better overview of the wiki content, i hav= e tried a more compressed layout of the configuration wiki. The actual (offic= ial) look of this section can be found in here -->http://wiki.ipfire.org/en/c= onfiguration/start .=20 > The new one is very unready and only a first try, but it should show an ide= a how it could be better overviewed.=20 > In here --> http://wiki.ipfire.org/en/configuration/start you belong to the= new structure. > Until now there is no content behind the structure but this should be done = fast by a copy and paste of the old content. <-- Better to check out some sec= tions before. Another possibility in this kind of structure can be to work mo= re precised in themes with e.g. 5-10 different sections not as before with 40= -50 (example in here --> http://wiki.ipfire.org/en/configuration/start ). >=20 > A statement to the wiki workflow: > In the last months, mostly work was done in particular articles of the wiki= , also to clean up the code cause a lot of plugins was replaced, so the gener= al structure wasn=C2=B4t touched but becomes more and more informations. I th= ink most important is for the first > * Find out a new structure which can be better overviewed (configuration a= nd installation, ???). > * Go for a checkout of the basic system articles (without addons) and find= out the worse sections to make them better and clearer. > * If old articles will be revised, the explained functions should also be = tested. > * Documentation should be a part of the development of software (and if it= is only a short developer hand out) so a possible documentation "team" have = it easier. >=20 > Also to overview the actual changes in the wiki needs to be checked. In her= e --> http://wiki.ipfire.org/start?do=3Drecent a done list can be overviewed.= If there was a change in german, it might be great to find it also in the en= glish wiki. As more people looks in there as better it is. >=20 > The native speakers: It is very important to have some people especial in e= nglish (american/english). The best might be that some people are native in t= wo languages german/english otherwise we have the same condition than before.= I tried always my best as an native german speaker to translate the wikis in= to english, but thats not enough for a good feeling by reading. So i tried al= ways to send some messages over the docu mailinglist with the please that som= eone can go for corrections (also in german). Sometimes this kind of workflow= did it very good (thanks again Rod by the way ;-), but sometimes (especially= in the last past months) there was no response. As time goes by the wiki art= icles leaves the memory that there was something to do and they where forgott= en. So it is maybe an idea to mark those articles as "uncheck, everybody is i= nvited to go for a revise" or something. >=20 > So for the first some ideas from me. >=20 >=20 > Greetings=20 >=20 >=20 > Erik --===============4086540618476469696==--