Niclas Hedhman a écrit :
- an always present link to the sources and distributions
Specifics? A "Download" section at the top? (Getting crowded)
Yep, for example, but as you say we must make some room if we want the
website to play nice with not so big screen.
- more recipes
Suggestions please!!! I have asked for this many times.
Alongside "Create a Constraint" we should have "Create a SideEffect"
and "Create a Concern" to cover the three Modifier types.
I don't have much suggestions in mind. In fact, the actual website
content is pretty complete but "how to material" is spread around
and I feel that the quick recipes format can ease the pain for
newcomers.
On the other hand, as I'm used to the Qi4j documentation I'm not sure
I have an objective point of view. That's why we need feedback. I've
asked a few people to tryout some tutorials, we'll see what they think.
- integration of the dev-status.xml file
Yes, would be nice. I guess this requires a combo of AsciiDoc output
as well as CSS styling. I think I can manage this, since I already
read the dev-status in the build system to determine if a lib/ext is
to be part of a release.
See below.
- copy/paste classpath specification for all examples and on
Generated from build system?? Wow!
Yeah!:-)
libraries/extensions page would be nice, maybe using the published groupIds
and artifactIds
Please elaborate. Not sure I get what you have in mind. A Maven
<dependency/> snippet on each lib/ext doc page would be good to have
in anyway, but I get the impression you want to have some "overview"
page for them all.
I was not thinking about an artifact overview page but it could be nice.
I was more thinking about getting the groupId/artifactId of each library,
extension, tools available in their respective documentation. Once we get
that it should not be too difficult to build a small box containing
copy/paste snippets for say, gradle, maven et al.
JavaScript could come in handy for this.
I had the same type of thinking about the dev-status.xml file. We could even
think about generating some simple json data that javascript code could
use to
enhance the pages.
As a simple example I just pushed a new commit that replace git repository
listing in Community/Codebase with nice github widgets.
However, the Tutorials and Core sections are still a bit messy.
I totally agree! But it was hard to try and organize before any
reasonable style produced a readable output. Should be a lot easier
now to experiment.
I tried to get the sub-nav TOC to go one level deeper without success
Gosh, I have spent a day on that, to no avail. Perhaps we should
contact the guy that made the XSLT in the first place.
Niclas, do you think it would even be possible?
I am sure it is possible, it is more a matter of whether one have
enough XSLT (and DocBook XSLT) sorcery skills.
I'm no DocBook XSLT Sorcerer :)
Could you take a look and contact the guy?
/Paul
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
