Bjori example's seems easier to figure out what's going to happen. I vote Markdown ratter than Wiki, because you can learn just reading another person's work.
Um abraço, :: Rafael Jaques (phpit.com.br <http://www.phpit.com.br>) :: Cristão - Professor - Evangelista PHP :: "Se confessarmos os nossos pecados, ele é fiel e justo para nos perdoar os pecados, e nos purificar de toda a injustiça." (1 João 1:9) 2013/8/13 Nikola Smolenski <smole...@eunet.rs> > On 10/08/13 07:34, Hannes Magnusson wrote: > >> I've been thinking lately about how we can make it easier for people >> to contribute to the project.. >> >> The OE was a great improvement and made it whole lot simpler to get >> going for users and did its job pretty well. >> >> Editing xml however isn't something the general public seems to be >> willing to do, not to mention they have no idea what docbook is at >> all. >> Other pain points are how long it takes to validate and build the >> documentation - and the cheesy tricks we've had to deploy to squeeze >> every performance drop out of both PHP and XML. >> >> >> If you guys remember our story.. >> DSSSL rendering took _days_ to build. >> XSLT took _hours_. >> PhD takes _minutes_. >> I think we can do better. >> I want it down to _seconds_. >> > > Have you people considered simply moving the documentation to a wiki? For > example, MediaWiki? > > * Build time in seconds. > * Wikitext syntax is as simple as any other presented so far. > * Has templating system that is needed. > * Has RTL support. > * Has PHP code formatting for code examples. >
