openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin McDonald" <>
Subject RE: [www] html instead of markdown (mdtext)?
Date Fri, 12 Aug 2011 07:41:08 GMT

> -----Original Message-----
> From: Rob Weir []
> Sent: Friday, 12 August 2011 5:45 AM
> To:
> Subject: Re: [www] html instead of markdown (mdtext)?
> On Thu, Aug 11, 2011 at 12:12 PM, Kay Schenk <>
> wrote:
> > I am proposing that we adopt plain HTML for the OOo website instead of
> > the current markdown (mdtext) implementation.
> >
> > I hesitate to make this recommendation given ALL the time and research
> > Dave and others have already spent on the current incubator website,
> > but, I feel, given that we will be migrating a rather large existing
> > site, it makes sense.
> >
> Where can I find the sources for the current website?  Not the wiki stuff, but
> the parts that you think would be difficult to migrate?
> > I also realize that doing this will "break" the ability to use the
> > webgui editing capability of the Apache CMS, forcing everyone to use
> > svn for page updates. However, I don't have a good feel right now for
> > the ultimate impact of that -- e.g. what do we expect in terms of web site
> editors.
> >
> > This would allow us to continue to use the default template system
> > (Dotiac::DTL) but eliminate the need for wrapping or intermixing
> > markdown text with normal HTML. HTML files shouldn't require any
> > "wrapping" functions at all I think, since this is the indigenous
> > format for web servers. We would have to bypass header, footer and
> > navigation items for anything that
> > *isn't* html, like js, css files.
> >
> We should also consider that the best approach might be to not do mdtext
> and not do Dotiac::DTL, but to adopt a newer framework.
> > Unfortunately, I've had a very difficult time this week trying to find
> > any information on the setup details of Dotiac::DTL (documentation not
> > available) -- the relationship of the two .pm files to the template
> > areas, etc.
> >
> > I took at look around at many the Apache web areas (svn) at:
> >
> >
> >
> > You will see, as I did, that the vast majority are not using markdown,
> > and this is NOT a requirement.
> >
> > Anyway, thoughts/comments on this proposal?
> HTML is not a panacea, of course.  It is very easy to design pages that look
> bad, are broken from portability,  internationalization and accessibility
> standpoint, introduce security issues, etc.  So having a constrained markup
> can be a good thing for a web site that you expect many people of various
> skill levels to edit.
> Just a thought:  Could you do the entire website in MediaWiki, with only
> exception cases (download page, etc.) done in HTML?

Just to put a blocker on this right away, we will not be using the wiki as the
main website or the main entrance into the OOo world. 

The website will
be housed where we house all our websites, on the main www infra
machines, with code kept in svn. How that code gets there can differ and
there are a variety of publishing tools and CMS to do the job. The preferred
CMS of course is the built in CMS - which is being used currently.
Other methods can include putting html pages directly in svn and these can
be hand written, produced with a build tool such as Maven or  Apache Forrest
or whatever.

Continue discussing but please take the wiki out of the equation as being the
main website. The wiki will be treated like the forums and like the bug tracker
etc, as a resource.


View raw message