Re: Site documentation format choosing

[Rodrigo Ruiz]

I agree with you Lukas,






Cheers

Lukas Theussl wrote:

The APT format simpler than the rest, and this has good and bad points. Modifications at template level are applied to the whole site, and are independent from the document format, so they are not really relevant if the point is just to decide which document format to use. And macros are far more complex to create than just switching to XDoc in the few cases you need to. I generally use APT for most documents, fml for the FAQs, and XDoc only when I need to create something more complicated (usually the main page, as it usually has to be more attractive than the rest, and it is the entry point for robots and other meta-data consumers).

-Lukas


nsowatsk wrote:

I was only listing the differences/limitations of the document format itself. Whatever tools you use around it (maven, velocity) can be applied to any other document format as well.

Hi


sections of the pom.

Once they are in the pom, they also get processed by the standard Maven
report plugin and so appear in various web pages created by that plugin.


from the pom file in the text of the pages generated from the .apt files.


think about what the other Maven tools can do also.

Regards

Nathan

On 29/07/2009 11:55, "Lukas Theussl" <ltheu...@apache.org> wrote:

The list of meta data that you give below is partly addressed in different Also, by using velocity (.apt.vm) you can include the values of the variable Just to clear, APT is limited, but you have to look at it holistically, and

Stefan Seidel wrote:

On Wed, 29 Jul 2009 10:44:28 +0200
Lukas Theussl <ltheu...@apache.org> wrote:

turn it also lacks in flexibility and misses advanced functionality, eg

(from the top of my head):

- no advanced formatting and layout (eg tables)

Wrong, tables are easily possible.

Of course, I said *advanced* formatting and layout, tables was just an

frames/borders, multicolumns, tables within tables,...

example, with apt you cannot specify eg arbitrary column widths, cell padding/spacing,

- no meta-information

What do you mean? You can include date, author and document title.

what about: author coordinates (address, email,...), subject, keywords,

creationDate, modifyDate,...


by the parser.

-Lukas

description, generator, robots, copyright, language, confidential, draft, You can always include those as comments of course but it won't be recognized

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

--
-------------------------------------------------------------------
GRID SYSTEMS, S.A.             Rodrigo Ruiz
Parc Bit - Edificio 17         Analyst/Programmer
07121 Palma de Mallorca
Baleares - Spain
http://www.gridsystems.com/
-------------------------------------------------------------------

smime.p7s
Description: S/MIME Cryptographic Signature