[TYPO3-dev] Ending usage of the Pending Documentation page

[Adrien Crivelli]

I agree with Kay on this, to have documentation source in the same
repository as code source is definitively the best way to keep both of them
in sync. It is also much easier to find it for developers. We don't split
code and documentation for extensions, I don't know why it should be any
different for core.

Also it is not exclusive with publicly hosting HTML output. Using standard
path ("/doc/") would easily allow for automated fetching and "compiling" of
several documentation sources, even for several versions (similar to what
was done for http://api.typo3.org/).


On 22 October 2011 16:10, Kay Strobach <typo3 at kay-strobach.de> wrote:

> But this way we could have the docu in the core, which corresponds with
> the installed version?!
>
> Regards
> Kay
>
> Am 21.10.2011 19:06, schrieb François Suter:
> > Hi,
> >
> >> Wouldn't it be best to have parts of the docu in the core, this way the
> >> change in the rest Manual can be committed with a single patch ...
> >
> > Definitely not, as it would  mean we could not update documentation
> > independently of the Core. Furthermore we are rather pursuing the
> > opposite goal: with the move to reST we aim to move the sysext manuals
> > out of the Core so that the whole Core-related documentation can be
> > handled in a common way, which is not the case now. In particular the
> > sysext manuals are nowhere available online in HTML format, which is bad.
> >
> > Cheers
> >
>
>
> --
> http://www.kay-strobach.de - Open Source Rocks
>
> TYPO3 .... inspiring people to share!
> Get involved: http://typo3.org
>
> Answere was usefull: https://flattr.com/profile/kaystrobach
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>