Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geclipse-dev] geclipse documentation structure

Hi Mariusz

My proposal would be to introduce a subchapter under the "g-Eclipse User Guide" entitled "Middlwares" or "Technologies" or something along those lines. Here each individual middleware implementation could integrate documentation specific to their usage scenarios. This could lead to some duplication in documentation but it is more specific and would thereby be closer to the actual user. Specifically guides like "How to do XY" are very valuable.

For GRIA I added chapter Consepts / GRIA specific concepts

There are all functionalities, which are specific for gria and shouldn't be described in general documentation.
I agree here. You have created a special chapter containing documentation specific to your middleware. But in fact there is also some docu under "Site Administration -> Gria Site Editor". To embed the specific docu under "Concepts" does not seam to be the best spot i think. Other subchapters like "getting started", "specific links" etc would not really fit under the "GRIA specific concepts" chapter. They are not "Concepts" they are something different. Therefore a middleware specific subchapter should be introduced.

greets
Moritz


Back to the top