Difference between revisions of "Linux Categories try 4"

From wiki.emacinc.com
Jump to: navigation, search
(added some recommendations)
m (Test for Mikey)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{todo|Test|Mike Dean|project=oe 4,oe 5,md,InProgress}}
+
{{todo|Rejected Big Time|Mike Dean|project=oe 4,oe 5,md,Rejected}}
 
__NOTOC__
 
__NOTOC__
 
[[File:Tux.svg|upright|frameless|right]]
 
[[File:Tux.svg|upright|frameless|right]]
 +
 +
==NOT CHOSEN SITE VERSION==
  
 
{| border="10px" width="60%"
 
{| border="10px" width="60%"
Line 32: Line 34:
 
------
 
------
  
I, and this excellent Schlafly Winter ESB that I am consuming, would recommend using the methods discussed here: http://www.mediawiki.org/wiki/Manual:Collapsible_elements to create collapsible navigation boxes. Could also use NavFrame as used by wikipedia (also described on the link above). This would be very easy to do and just requires a few modifications to the CSS created for the masonry items.
+
I would recommend using the methods discussed here: http://www.mediawiki.org/wiki/Manual:Collapsible_elements to create collapsible navigation boxes. Could also use NavFrame as used by wikipedia (also described on the link above). This would be very easy to do and just requires a few modifications to the CSS created for the masonry items.
  
In addition, you might consider making each of these navigation boxes into a template so that you can easily insert the same navigation content on multiple pages (that was the Schlafly's idea). For example, Linux_Main would have all navigation links using templates, and the header for each section would link to the intro page for that section of the documentation. Each intro page which would also include the <nowiki>{{System Operation Nav}}</nowiki> template link to show the navigation block for that section of documentation.
+
In addition, you might consider making each of these navigation boxes into a template so that you can easily insert the same navigation content on multiple pages. For example, Linux_Main would have all navigation links using templates, and the header for each section would link to the intro page for that section of the documentation. Each intro page which would also include the <nowiki>{{System Operation Nav}}</nowiki> template link to show the navigation block for that section of documentation.
  
--[[User:Tstratman|Tstratman]] ([[User talk:Tstratman|talk]]) 23:27, 27 December 2013 (UTC) (AKA Tstrizzle)
+
--[[User:Tstratman|Tstratman]] ([[User talk:Tstratman|talk]]) 23:27, 27 December 2013 (UTC)

Latest revision as of 17:12, 6 January 2014

TODO: {{#todo:Rejected Big Time|Mike Dean|oe 4,oe 5,md,Rejected}}
Tux.svg

NOT CHOSEN SITE VERSION

General Information

System Configuration

Software Development

System Operation

Graphics

Working with Filesystem Images

Bootloaders

Support


Use this: http://jqueryui.com/accordion/

With top level categories in the Examples area on the right, and the 2nd level categories as accordion section headings.


I would recommend using the methods discussed here: http://www.mediawiki.org/wiki/Manual:Collapsible_elements to create collapsible navigation boxes. Could also use NavFrame as used by wikipedia (also described on the link above). This would be very easy to do and just requires a few modifications to the CSS created for the masonry items.

In addition, you might consider making each of these navigation boxes into a template so that you can easily insert the same navigation content on multiple pages. For example, Linux_Main would have all navigation links using templates, and the header for each section would link to the intro page for that section of the documentation. Each intro page which would also include the {{System Operation Nav}} template link to show the navigation block for that section of documentation.

--Tstratman (talk) 23:27, 27 December 2013 (UTC)