Difference between revisions of "Talk:Flat html"

From PC-BSD Wiki
Jump to: navigation, search
m (Created page with "It looks like plenty of additional adjustments would need to be made. One thought is each location in the table of contents would have two parts: # a ''container'' page with t...")
 
(organization: by page vs generated toc: new section)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
It looks like plenty of additional adjustments would need to be made.
+
Problems solved:
  
One thought is each location in the table of contents would have two parts:
+
* A new template makes the translcusion of the pages simpler by adding the lost header.  
# a ''container'' page with the header and content added by inclusion wiki effect,
+
* Adding the missing header from each page allows sections to be referenced by the index that precedes them to a location on this page.
# text content page.  
+
* The transclusion of the unnecessary Navheaders is accomplished by wrapping them in a <nowiki><noinclude>tag set</noinclude></nowiki>
However, this may complicate matters for editors.. but perhaps not. As it is right now, any new handbook page must have the proper navheader included, as well as an entry in the table of contents page. Instead of those two steps, perhaps just a category tag that would mean "add to handbook" which is a simple thing to do: <nowiki>[[category:handbook]]</nowiki>, and a reasonable thing to add for all handbook pages.
+
 
+
The wiki inclusion effect is transparent to everything else, but as you can see by the current state of this page (Flat html) there are multiple instances of the headers and the required TOC makes things additionally messy.
+
 
----
 
----
 +
As yet, it appears no further tweaks are needed.. but perhaps another template might ease the process :)
 +
 +
== organization: by page vs generated toc ==
 +
 +
I think the only way we can auto-generate a TOC that matches the layout of the printed handbook, is to have nearly static primary pages which contain sourced content from other pages. There could still be an organization like it is now, but especially on flat_html, it would get ordered in a way that would cause proper numbering to be generated.
 +
 +
In our table of contents page, all of the bolded titles would become the primary pages. I would prefer that these primary pages not actually have content of their own, but transclude it instead. We can adjust the visible page names but I believe the auto-generated toc (in the box on the flat_html page) uses the actual page names. This is something to investigate prior to much work on v9.2 handbook.

Latest revision as of 19:43, 5 December 2012

Problems solved:

  • A new template makes the translcusion of the pages simpler by adding the lost header.
  • Adding the missing header from each page allows sections to be referenced by the index that precedes them to a location on this page.
  • The transclusion of the unnecessary Navheaders is accomplished by wrapping them in a <noinclude>tag set</noinclude>

As yet, it appears no further tweaks are needed.. but perhaps another template might ease the process :)

[edit] organization: by page vs generated toc

I think the only way we can auto-generate a TOC that matches the layout of the printed handbook, is to have nearly static primary pages which contain sourced content from other pages. There could still be an organization like it is now, but especially on flat_html, it would get ordered in a way that would cause proper numbering to be generated.

In our table of contents page, all of the bolded titles would become the primary pages. I would prefer that these primary pages not actually have content of their own, but transclude it instead. We can adjust the visible page names but I believe the auto-generated toc (in the box on the flat_html page) uses the actual page names. This is something to investigate prior to much work on v9.2 handbook.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox