[TYPO3-core] ReStructured Text in the TYPO3 backend

Ernesto Baschny ernesto.baschny at typo3.org
Mon May 27 09:22:35 CEST 2013

François Suter schrieb am 27.05.2013 09:17:

>> - a dedicated module seems the way to go. It could be called
>> "documentation" or "library" (although both keys are already registered;
>> "documentation" can be found in TER, last update in 2006; "library" is
>> not public).
> I received a positive answer from the owner of the "documentation" key.
> It will be transferred to me. We'll see later about the appropriate
> account.
> BTW that's one more point to debate: should this be a system extension
> (i.e. shipped with the Core) or should it be outside of the Core?
> I have mixed feelings here, because I think it may become quite a
> crucial extension, especially if it provides an API for doing CSH or
> similar in ReST. So it would make sense to be a sysext. And the Core
> Team might be more implicated (I have fears that this is seen only as a
> Doc Team project).
> OTOH if it's outside of the Core, it may be able to evolve faster, which
> might be important, especially in the early days.
> What do you think?

I would aim for it being a sysext, maintained by the doc-team, but of
course adhering to the core coding and code quality guidelines and
policies (deprecation strategy etc).

For a quicker "kick start" I recommend to start it out as a stand alone
extension in typo3conf/ext but considering that it could be later
integrated in typo3/sysext. As soon as the first maturity level is
reached, we can get it into the core.


Ernesto Baschny
TYPO3 CMS Core Developer
Release Manager TYPO3 4.5 & 6.2 LTS

TYPO3 .... inspiring people to share!
Get involved: typo3.org

More information about the TYPO3-team-core mailing list