I like this skin as well.
Regarding QDox, the new architecture of 2.0 allows custom Model writers,
so it shouldn't be too hard to make a json output.
thanks,
Robert
Op Wed, 15 Apr 2015 16:14:07 +0200 schreef Marek Romanowski
<[email protected]>:
2015-04-14 8:11 GMT+02:00 Hervé BOUTEMY <[email protected]>:
wow, impressive!
Thank you! I wasn't sure is it ok to post this message here...
what I don't like is that it does not use my wide screen, which is not
great
on some key pages like http://maven.matsuo-it.com/#/plugins/index.html
I've added full window button for you! It's in lower right corner, next
to
"scroll to top" button.
It's possible to configure this as default. But in my oppinion reading
text
is easier if line is not too long. I was thinking that main content
column
should be even shorter. But at the end tables looked messy in shorter
column.
but there are a lot of great ideas that proves people can create great
skins!
Regarding Jekyll and asciidoctor, I have in my todo list to draw a
picture
of
how maven-site-plugin currently uses reports, Doxia and Doxia SiteTools
to
render a site with a skin
I'm convinced we can replace Doxia SiteTools without wreaking havoc
What I still don't know is if Jekyll and/or asciidoctor know about a
notion of
skin, ie reusable template
Working with maven generated pages showed me some possible helpful
improvements:
* It would be fantastic if maven report plugins could save reports in
JSON
format too. I'm pretty sure some kind of data model exists in every
plugin.
Maybe it's possible to use tool like Jackson to serialize this model to
JSON. This way views could be changed or improved without infering in
report generation.
* Same for java sources. Probably it would be hard to serialize something
like QDox model to JSON. But this kind of data would be breakthrough in
creating new possibilities for view generation.
* If not QDox, then even raw java files provided for download on page
would
be useful. I was thinking about adding readonly code editor like Code
Mirror to page. Maybe it could be possible to add simple functions like
find usages in page. It would be usefull for me, so probably for somebody
else too.
Generally web page splits in three parts:
* data, pure information
* view structure (HTML)
* style (CSS)
Maven site plugin mixes all this things and that makes it hard to improve
maven sites. But I understand it is hard problem to fix.
I will be offline for somthing like 3 weeks: I hope to draw a first
draft
of the
picture to let time thinking about its improvement during my vacation :)
Then for the current skins r&d, I won't be available at the moment
But definitely, it's something really interesting: I don't know if we
have
something like a skins-community to share skins
Nothing at http://maven.apache.org/skins/index.html
But
http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html
links "Examples of Existing Skins" to
http://docs.codehaus.org/display/MAVENUSER/Maven+Skins
Notice this is a Codehaus MAVENUSER Confluence content, that will
disappear
when Codehaus shuts down: seems like we'll need to migrate at least
part of
it, I don't know how, to ASF...
And I hope we can have external contributors on ASF Confluence: once
again
I
don't know
I'll try to see what I can do before going offline...
Regards,
Hervé
Thank you for your response. If you'll find that I could help improving
maven site, I'll be glad to do it.
Kind Regards,
Marek.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
