[
https://issues.apache.org/jira/browse/JENA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748446#comment-13748446
]
Ian Dickinson commented on JENA-482:
------------------------------------
Hi Samuel,
I like the breadcrumbs. I think keeping it on top is the right thing. It
occurred to me that there's another use case that this supports, which is users
arriving at the page via a search engine. They now have a much clearer idea
where they are in terms of the project's information collection.
I'd support Leigh's suggestion of having the version number easily visible on
the web site. The use case this supports is: "I'm using Jena, or thinking of
doing so, and I'd like to quickly check what the latest version is". Currently,
you have to go to the download link, navigate to the right folder, see which is
the latest archive file and parse the version number out of the file name.
Which breaks the "don't make me think" rule, and then some! We can easily make
updating the published version number part of the release process.
For similar reasons, I'd also support putting the prominent download link back
in. For people who have already "got started", and just need the latest version
or to do a new install on another machine, the call-to-action we want is to
download the software.
Those comments aside, good job! I'm happy to see this go live when we roll the
next Jena release.
Ian
> 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
> Assignee: Rob Vesse
> Priority: Minor
> Labels: documentation
> Attachments: new_website.diff
>
>
> 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
