Difference between revisions of "Testing1"

From PC-BSD Wiki
Jump to: navigation, search
(test)
Line 1: Line 1:
 
<noinclude>{{testing|back=template:testing|forward=template:testing2|custompagename=Testing1 - just an idea}}</noinclude>
 
<noinclude>{{testing|back=template:testing|forward=template:testing2|custompagename=Testing1 - just an idea}}</noinclude>
 
+
==How it once was in wiki==
=How it once was in wiki=
+
 
* [[Introduction|'''1. Introduction''']]
 
* [[Introduction|'''1. Introduction''']]
 
* [[PC-BSD's Goals and Features|1.1 PC-BSD's Goals and Features]]
 
* [[PC-BSD's Goals and Features|1.1 PC-BSD's Goals and Features]]
Line 10: Line 9:
 
* [[Migrating to PC-BSD|2.1 Migrating to PC-BSD]]
 
* [[Migrating to PC-BSD|2.1 Migrating to PC-BSD]]
  
=How it is now in wiki=
+
==How it is now in wiki==
 
{{hierB|1.|title=Introduction}}
 
{{hierB|1.|title=Introduction}}
 
{{hier|1.1|title=PC-BSD's Goals and Features}}
 
{{hier|1.1|title=PC-BSD's Goals and Features}}
Line 19: Line 18:
 
{{hier|2.1|title=Migrating to PC-BSD}}
 
{{hier|2.1|title=Migrating to PC-BSD}}
  
=How it is published deadtree (w/o page#s)=
+
==How it is published deadtree (w/o page#s)==
 
[[Introduction|1 Introduction]]
 
[[Introduction|1 Introduction]]
 
:[[PC-BSD's Goals and Features|1.1 PC-BSD's Goals and Features]]
 
:[[PC-BSD's Goals and Features|1.1 PC-BSD's Goals and Features]]
Line 33: Line 32:
 
:[[Pre-Installation Tasks#Migrating to PC-BSD|2.1 Migrating to PC-BSD]]
 
:[[Pre-Installation Tasks#Migrating to PC-BSD|2.1 Migrating to PC-BSD]]
  
=Concept: how I want it to be=
+
==Concept: how I want it to be==
 
<nowiki>{{</nowiki>table_of_contents|1<br>
 
<nowiki>{{</nowiki>table_of_contents|1<br>
 
|Introduction<br>
 
|Introduction<br>
Line 50: Line 49:
 
<nowiki>}}</nowiki><br>
 
<nowiki>}}</nowiki><br>
 
<br>
 
<br>
==test==
+
== Test space ==
 +
===Variation 1===
  
 
{{testing4|1|Introduction
 
{{testing4|1|Introduction
Line 69: Line 69:
 
|Migrating to PC-BSD}}
 
|Migrating to PC-BSD}}
  
==test2==
+
=== 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 '<nowiki>|</nowiki>' character which could possibly be sent to another template to add the numbers as shown in the prior test.<br>
 
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 '<nowiki>|</nowiki>' character which could possibly be sent to another template to add the numbers as shown in the prior test.<br>
 
Ideally, all chapter names, subchapters, and subsections could be listed and selectable, but this further complication needs to be explored/defined.
 
Ideally, all chapter names, subchapters, and subsections could be listed and selectable, but this further complication needs to be explored/defined.
Line 81: Line 81:
 
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.
 
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.
 
<br><br>
 
<br><br>
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''.
+
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.
 
<noinclude>[[category:testing]]</noinclude>
 
<noinclude>[[category:testing]]</noinclude>

Revision as of 18:36, 10 August 2012

Previous:  Error: Your NavHeader assignment is malformed. template:testing Previous: Error: Your NavHeader assignment is malformed. Return to Table of Contents Next:  Error: Your NavHeader assignment is malformed. template:testing2 Next:  Error: Your NavHeader assignment is malformed.

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

{{table_of_contents|1
|Introduction
|PC-BSD's Goals and Features
|What's New in 9.1
|PC-BSD Releases
|PC-BSD for Linux Users
|1|Filesystems
|Device Names
|Feature Names
|Commands
|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
Laptops
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.