Hmm, interesting. Reworking the website I ensured to avoid JavaEE (BTW JEE
doesnt exist anymore ;)) cause it is not important at tomee level. I mean
if tomee covers JavaEE then it reduces mathematically tomee specific
features space which is what users search coming on tomee website in
general.
The classloader point is funny but part of the most hit issue so don't know
if hiding it a bit would be beneficial. The website has been thought as an
enabler/reference and less like a book with a progression ('getting
started"s probably) which is more or less what you propose. Wonder if we
can merge both somehow, probably with the new menu item.
I like your menu but it can need a submenu on doc - not sure how mobile
handling would be but doable.
Maybe we should drop the blog, we never used it accurately.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2017-06-26 0:40 GMT+02:00 Thomas Whitmore <[email protected]>:
> Hi Ivan, Romain,
>
> I probably support having a 'Documentation' item in the top menu. At the
> moment there are all the subtopics, but nothing at the top-level says
> Documentation! At a brief glance this is likely to give the impression
> that there isn't documentation, or that it's hard to find.
>
> From an external perspective 'Documentation', 'Getting Started' and
> possibly 'Examples' are good top-level headings.
>
> I would suggest something like:
> - Documentation
> - Getting Starting
> - Examples
> - Blog
> - Community
> - Downloads
>
> I write quite a lot of documentation so my quick thoughts -- trying to be
> constructive here.
>
> Reviewing the current 'Developer', 'Admin', 'Advanced' pages -- these are
> all lacking any overview to tell you the basics and badly empty.
> There needs to be some introductory text to start these sections and set
> the scene, TomEE for Developers needs to start with an overview of what
> TomEE is & why it's good; then have some simple guide or guides to writing
> JEE application, as the first (few) articles. These will show how to use
> TomEE's features.
>
> 'Developer' section should go something like:
> - (introductory text) TomEE is a JEE container. Advantages this gives.
> - JEE Basics -- basic outlines of how to write a JEE application & link
> to other guides
> - Eclipse, Intellij Idea, Netbeans: TomEE in and IDE (maybe: but
> there's no real content here)
> - JEE Feature Guides
> - TomEE and Testing
>
> Perhaps there could be several guides to important JEE areas:
> - JEE Guide -- CDI
> - JEE Guide -- Datasource
> - JEE Guide -- JPA
> - JEE Guide -- EJB
> - JEE Guide -- CXF & Webservices
>
> The above topics map well to the areas in Examples
> http://tomee.apache.org/examples/index-ng.html which have good coverage
> of examples.. and outlining a little bit of concrete usage should allow
> good opportunities to explain TomEE's configuration, particular details etc.
>
> (Little bit of an insight here -- perhaps the fact that we haven't been
> focusing / docing based on the JEE features, has made it hard to write doc?)
>
> I suggest 'Developer' section should not start with "All you need to know
> about TomEE classloading". This is not what new developer should need to
> get started with, and is a great way to scare people off.
>
> Busy these past couple of months, trying to offer some guidance to the
> best degree I can but don't have time available to actually do the writing.
>
>
> Regards,
> Thomas
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
