marcgrue
commented
13 years ago If we could switch between version and component family, like http://framework.zend.com/manual/1.11/en/ (notice the selectors in the right column) then I think it would be a big leap forward!
If a mandatory Tag for Version/ComponentFamily could be enforced on all page entries, it should be possible to filter by those. Don't know github/gollum/wiki/templates/markdown etc good enough yet to tell if that could be possible. Custom tags? Keywords automatically converted in markdown template translation?
A great added value would be the ability to "vertically" explore how a certain component family is getting used in different contexts.
It would be wonderful not to have to judge/guess if some wiki is valid for a specific version!
Cheers, Marc
When we port the old wiki content from confluence it is likely that many of the pages only relate to modules that were in wicket 1.3 and that some 1.4 modules are not going to be in wicket 1.5
I propose that if a project is at the end or for a specific version only that we create a new page name with the -wicket-version suffix.
For example, Prototype is in Wicket 1.4 but is not going to be ported to Wicket 1.5 (JSLibraries is to be used instead) so the Prototype page should be renamed to Prototype-1.4
We can use this same strategy for modules that only existed in 1.3 and for projects that materially change between wicket top level versions or even those that change materially within a single wicket release (i.e. look at the Push project where the current documentation says it is current from wicket 1.4.16)
Then once this definition exists we can reorder the home page project links to appear under wicket 1.3, wicket 1.4 and wicket 1.5 headings.
We could also add links between the different versions of a single module (i.e. the Project-1.3 version has a link to the Project-1.4 version that has a link to the current Project page).