For anyone following along, I have implemented what I consider "enough"
for me for now... at least until I have useful reports to include.
Basically, I've taken the gradle website build and tweaked to include
configurable content markup based on WikiText (<- the old Textile-J
engine). This means I can use confluence/textile style mark-up when
creating my content and it gets converted to HTML like it should. It is
pretty easy to add other formats.
It seems like some of this is ripe for some kind of plug-in... probably
with a lot of tweaks. Tweak example, it partially bothers me that
content is reprocessed every time but I don't have the energy left to
look at it right now. Some kind of src -> target transform would be
best but I don't know what's involved.
If anyone is curious, the build.gradle file that builds my site can be
found here:
http://filament.svn.sourceforge.net/viewvc/filament/trunk/site/build.gradle?revision=158&view=markup
The content is nearby in that repository. Currently the index page is
the only one converted to textile/confluence mark-up.
The site it builds looks like this:
http://filament.sourceforge.net/
The one thing I'll probably miss from standard confluence markup is the
ability to logically refer to pages by title when linking... but that
would favor a multi-stage transform that I'm not prepared to do right
now. The file names are predictable enough.
Comments/criticism welcome... still just learning gradle.
-Paul
Paul Speed wrote:
Hans Dockter wrote:
but I'm looking to be able to use multiple content formats like
Doxia does and have it all assembled into a site from a logical
model. I didn't want to reinvent the wheel if someone has already
made some progress.
I'm not aware of any efforts here. It would be excellent to have such
an abstraction.
What I really miss is the ability to compose write-up in something other
than HTML (textile, atf, etc.). The docs for Doxia are a little obtuse
but it has all of the components... they may just be too hard to get at
outside of a full-up maven environment in the plexus container.
The other problem I haven't figured out an elegant approach for is
marrying the site report stuff with the "model" used to generate the site.
If I make any break-throughs relating to some sort of site plug-in, I'll
post back. I'm a CSS newb (and a Groovy newb, too) so it will probably
need a lot of clean-up. At least I can generate my new site now, though.
-Paul
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
