Jetty 12.0.x document modules

[gregpoulos]

@sbordet I wanted to run a couple of potential changes by you to get your thoughts.

1. What do you think of using the module-eex-modulename.adoc naming convention when we create documentation listings for modules that have multiple different versions for different EE platforms? The main advantage here is that eex uses a common substitution convention that plays nicely with filenames. One disadvantage to this approach is that there there isn't an obvious "right" way to do alphabetical sorting. For example, module-eex-webapp.adoc get automatically sorted under "E", but there's a good argument that it should appear under "W".

2. For the ee{8,9,10}-webapp module documentation, I've used an ASCIIdoc include:: statement to directly transclude the [description] text directly from ee10-webapp.mod. My goal in doing so is to reduce duplicated content, but if you'd prefer to avoid this approach, I can stop. (For example, maybe we'd prefer to avoid cluttering the .mod files with extra markup, or perhaps the [description] field serves a sufficiently distinct purpose from the documentation that they're worth maintaining separately.)

[sbordet]

What do you think of using the module-eex-modulename.adoc

Fine by me. Maybe eeN is better than eex?

I've used an ASCIIdoc include:: statement to directly transclude the [description] text directly from ee10-webapp.mod.

Good idea too.
I think perhaps you can shorten the tags, from documentation-description to just description, and documentation-ini-template to just ini-template.

[sbordet]

@gregpoulos I would standardize to Servlet with capital S everywhere.

[gregpoulos]

All these suggestions look good to me. I'll implement them and post an update with the changes.

[sbordet]

Good job!