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:30:03 +0200 Message-ID: <54C3C794-4F06-439A-8FD6-56104D4E5A3B@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0424218638266092416==" List-Id: --===============0424218638266092416== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, regarding to the ideas causing a better overview of the wiki content, i have = tried a more compressed layout of the configuration wiki. The actual (officia= l) look of this section can be found in here --> http://wiki.ipfire.org/en/co= nfiguration/start .=20 The new one is very unready and only a first try, but it should show an idea = how it could be better overviewed.=20 In here --> http://wiki.ipfire.org/en/configuration/start you belong to the n= ew structure. Until now there is no content behind the structure but this should be done fa= st by a copy and paste of the old content. <-- Better to check out some secti= ons before. Another possibility in this kind of structure can be to work more= precised in themes with e.g. 5-10 different sections not as before with 40-5= 0 (example in here --> http://wiki.ipfire.org/en/configuration/start ). 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 general= structure wasn=C2=B4t touched but becomes more and more informations. I thin= k most important is for the first * Find out a new structure which can be better overviewed (configuration and= installation, ???). * Go for a checkout of the basic system articles (without addons) and find o= ut the worse sections to make them better and clearer. * If old articles will be revised, the explained functions should also be te= sted. * Documentation should be a part of the development of software (and if it i= s only a short developer hand out) so a possible documentation "team" have it= easier. Also to overview the actual changes in the wiki needs to be checked. In here = --> http://wiki.ipfire.org/start?do=3Drecent a done list can be overviewed. I= f there was a change in german, it might be great to find it also in the engl= ish wiki. As more people looks in there as better it is. The native speakers: It is very important to have some people especial in eng= lish (american/english). The best might be that some people are native in two= 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 into= english, but thats not enough for a good feeling by reading. So i tried alwa= ys to send some messages over the docu mailinglist with the please that someo= ne can go for corrections (also in german). Sometimes this kind of workflow d= id it very good (thanks again Rod by the way ;-), but sometimes (especially i= n the last past months) there was no response. As time goes by the wiki artic= les leaves the memory that there was something to do and they where forgotten= . So it is maybe an idea to mark those articles as "uncheck, everybody is inv= ited to go for a revise" or something. So for the first some ideas from me. Greetings=20 Erik --===============0424218638266092416==--