Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
MIME-Version: 1.0
From: Lukasz Lenart <lukaszlenart@apache.org>
Date: Sat, 28 Jan 2017 09:33:16 +0100
Message-ID: <CAMopvkPLdKYswb3PO2ds4CF9JrD8PgmxQT5-=Zs9tzfggMqcAQ@mail.gmail.com>
Subject: Documentation
To: Struts Developers List <dev@struts.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sat, 28 Jan 2017 08:33:40 -0000

Hi,

I would like to move our docs (or some part of it) to Markdown and put
them next to our website's source. Existing mechanism of exporting
docs is rather not the best approach, also it isn't possible to engage
community to improve it (as with the core and PRs via GitHub).

My first idea was to export everything from Confluence and convert to
MD but this not the best approach after all - we still need a place to
restrict access for some pages, i.e. security bulletins and so on,
also some pages are to detailed to be part of so common user guides.

So instead of migrating things I think it would be better to start
writing/copy/pasting some parts from wiki directly to website and
create a new/based on old guides. Confluence will be still used for
more detailed explanations of core elements and to manage releases and
so on.

I want to start with
https://cwiki.apache.org/confluence/display/WW/Getting+Started

or more generally with
https://cwiki.apache.org/confluence/display/WW/Tutorials

wdyt?


Regards
--=20
=C5=81ukasz
+ 48 606 323 122 http://www.lenart.org.pl/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org