Sorry for the inconvenience.  Known Navigation header breakage, its being "rebuilt" but forward nav should be ok now.
There may be other unforeseen breakage primarily in the handbook portion of the wiki.
The Table Of Contents section of each "PC-BSD® Users Handbook" page may be the best workaround.


From PC-BSD Wiki
Revision as of 17:36, 10 August 2012 by Tigersharke (Talk | contribs)

Jump to: navigation, search
Template:Word-previous/en {{:Translations:{{{1}}}/Page display title/en}} template:testing Previous: Error: Your NavHeader assignment is malformed. Placeholder.png Template:Word-next/en {{:Translations:{{{2}}}/Page display title/en}} template:testing2 Template:Word-next/en {{:Translations:{{{2}}}/Page display title/en}}

Testing1 - just an idea

How it once was in wiki

How it is now in wiki

1. Introduction

1.1 PC-BSD's Goals and Features
1.2 What's New in 9.1
1.3 PC-BSD Releases
1.4 PC-BSD for Linux Users

2. Pre-Installation Tasks

2.1 Migrating to PC-BSD

How it is published deadtree (w/o page#s)

1 Introduction

1.1 PC-BSD's Goals and Features
1.2 What's New in 9.1
1.3 PC-BSD Releases
1.4 PC-BSD for Linux Users
1.4.1 Filesystems
1.4.2 Device Names
1.4.3 Feature Names
1.4.4 Commands
1.4.5 Additional Resources

2 Pre-Installation Tasks

2.1 Migrating to PC-BSD

Concept: how I want it to be

|PC-BSD's Goals and Features
|What's New in 9.1
|PC-BSD Releases
|PC-BSD for Linux Users
|Device Names
|Feature Names
|Additional Resources
|Pre-Installation Tasks
|Migrating to PC-BSD

Test space

Variation 1

1. Introduction

1.1 PC-BSD's Goals and Features
1.2 What's New in 9.1
1.3 PC-BSD Releases
1.4 1
1.5 PC-BSD for Linux Users
1.6 Filesystems
1.7 Device Names
1.8 Feature Names
1.9 Commands
1.10 1
1.11 Additional Resources
1.12 source one
1.13 source 2
1.14 source 3
1.15 2
1.16 Pre-Installation Tasks
1.17 Migrating to PC-BSD

variation 2

This is an interesting thought also, to use subheading definitions in more than one location, by this method, it could be included on the intro page and with more work also included in the table of contents. It is possible to include the '|' character which could possibly be sent to another template to add the numbers as shown in the prior test.
Ideally, all chapter names, subchapters, and subsections could be listed and selectable, but this further complication needs to be explored/defined.

1. Introduction

PC-BSD's Goals and Features
What's New in 9.1
PC-BSD Releases
PC-BSD for Linux Users

2. Pre-Installation Tasks

Hardware Requirements
Partitioning the Hard Drive
Obtaining PC-BSD
Burning the Installation Media
PC-BSD Live Mode
Using VirtualBox

general thoughts

The main plan is to give the same or similar result as now, but with a lot less work, and hopefully the markup is more readable. However, further thought has provoked the second concept with test2 and may sacrifice readabilty for flexibility.
All of tis could be a challenge, because somehow if it is a number then it is indented and prepended to a series of numbers automatically. Such as 1. then 1.1, 1.2, 1.3, and supposing a second 1, then it would continue from 1.3, to 1.3.1, 1.3.2 etc. Turning any text into a link is easy. Formatting text is easy enough. I think there are ways to test for numerics versus alphanumeric/letters.
Also, since there is the chance that a link and the link text may be different, I need to figure out how to handle that. This is a challenging wrinkle, since I am trying not to use named variables, and a series of up to 20 seems realistic for each chapter even if it has a second level used such as 1.3.1 mentioned above.

Is it possible that the problem is already solved in the sidebar menu? It is the desired numbering pattern that does not follow, which needs to be solved. If I used tables, would that work? If I followed the decimal point would that help? How do I begin or end a sub topic without adding too much extra typing? It is the levels of sub topics that cause the difficulty, and that i did not fully illustrate as compared to dead tree. The sidebar menu has the advantage of ecma script I believe.

Personal tools