[
https://issues.apache.org/jira/browse/JENA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700096#comment-13700096
]
Andy Seaborne commented on JENA-482:
------------------------------------
I'm still liking it! And that license is just fine :-)
1/ Good to know that the current markdown can be used because it much less of a
bump in the road that way.
2/ I see it differently in Firefox and Chrome. Chrome is correct. FF is not.
There is gap at the top, then "Apache Jena" band - but it only has that and
not the Home/Download/Learn/Ask/Get Involved items.
3/ The use of "learn" and a drop down, as opposed to the side bar navigation
area is a change I think we need to discuss. People finding stuff is better
than getting user@ email. Obviously, this is a style thing, not a technology
thing.
4/ The root is "/" for hrefs.
The site does to:
http://jena.staging.apache.org/ (as the name suggests - staging and checking
the markdown)
There is a stalker buildbot that looks for SVN commits and automatically
rebuilds the staging site.
Staging is copied to the publish site
http://jena.apache.org/
by a process (we run a script if large e..g all the javadoc has changed, or
press "publish" in CMS).
5/ ia.txt is the description produced for site design - it's the
(meta)documentation.
> Website re-organisation and facelift
> ------------------------------------
>
> Key: JENA-482
> URL: https://issues.apache.org/jira/browse/JENA-482
> Project: Apache Jena
> Issue Type: Documentation
> Components: Web site
> Reporter: Samuel Croset
> Priority: Minor
> Labels: documentation
>
> I've been experimenting a bit in the last couple of days over the Jena
> website and documentation. You can see a live demo version of the result
> here: http://loopasam.github.io/jena-doc/index.html
> My motivation was to try to make the overall browsing experience a bit
> clearer and nicer looking without disrupting too much what's already in place.
> I have refactored some of the skeleton and CSS using Twitter Bootstrap. I
> haven't changed any of the build mechanism (ASF-CMS), so pretty much all the
> documents and pages are working just as before out of the box.
> Before doing more work on this I wanted to know what the community thinks of
> it and whether it could be integrated with the current code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
