Re: [hibernate-dev] Hibernate.org
I think content wise the current sub project approach will work. Looking
at search.hibernate.org and validator.hibernate.org one can see that there
is
not so much content for this content pages. The bulk of information is
really in
the wiki which is a different thing (Clearspace). Btw, what's going to
happen
with the domains search.hibernate.org and validator.hibernate.org? Will
they forward
to the corresponding sub project page on JBoss.org?
Will EM and Annotations still be listed as sub projects though. I guess
from a current
point of view we could combine them into Core. Not sure whether we have to
consider
long time users though who might be looking for these projects.
We also have to consider the new Static Metamodel Generator. Currently it
does not have its
own project page. Will we just add it to Core or will it be its own
standalone
sub project?
Maybe we should even consider moving the actual source code into a maven
module. If I remember
right the main issue stopping us from doing so were build problems, right?
Shards I know nothing about. I am not even sure who does. Seems the best
we can do there
is to move the current content from shards.hibernate.org.
--Hardy
On Mon, 22 Feb 2010 21:53:37 -0300, Steve Ebersole <steve(a)hibernate.org>
wrote:
After months of sitting in limbo it looks like there may finally be
movement on getting hibernate.org content moved over to the
magnolia/clearspace setup.
We need to figure out what all still needs to be done in terms of
content. For core (+ annotations/em) I have a good idea of the work
still to do. But in terms of search, validator, shards and tools
(nhibernate?) I have no idea.
This will not happen until next week at the earliest as I have a meet up
scheduled with the JBoss design team here in Austin to go over LnF,
navigation, etc later this week.
Like one specific thing I know we have to iron out is navigation and
side bar content for the various subprojects. Will the various
subprojects "be under" hibernate? The infrastructure is really built so
that all projects are at the same level. I think it comes down to how
much content (pages) we see for each sub project and how y'all want the
nav and menus to work. If a unified set of nav and menus along with a
minimal set of content pages is acceptable then its probably doable to
just create sub content pages under the main set of hibernate pages. If
y'all want something more elaborate or separate nav/menus than we are
going to have to split these up I think (I'll verify to make sure this
is still the case).