User Tools

Site Tools


manual_of_style:unmanageable_matrioshka_namespaces

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual_of_style:unmanageable_matrioshka_namespaces [2016/01/19 23:05]
Petike [Bad Editing Habits : Unmanageable Matrioshka namespaces]
manual_of_style:unmanageable_matrioshka_namespaces [2019/03/29 15:14] (current)
Line 1: Line 1:
 ====== Bad Editing Habits : Unmanageable "​Matrioshka"​ namespaces ====== ====== Bad Editing Habits : Unmanageable "​Matrioshka"​ namespaces ======
  
-Namespaces on DokuWiki can be stacked. For example, instead of creating just <​nowiki>​[[offtopic:​ ]]</​nowiki>,​ you can create <​nowiki>​[[offtopic:​mynamespace1:​mynamespace2:​mynamespace3]]</​nowiki>​. This stacking of namespaces means you're adding an additional namespace to an already existing namespace in a page's adress. ​+This is an article that explains often recurring issues with the method of stacking too many namespaces into one wiki page adress. 
 +==== Starting point info ==== 
 + 
 +Namespaces on DokuWiki can be (for lack of a better term) "stacked". For example, instead of creating just <​nowiki>​[[offtopic:​ ]]</​nowiki>,​ you can create <​nowiki>​[[offtopic:​mynamespace1:​mynamespace2:​mynamespace3]]</​nowiki>​. This stacking of namespaces means you're adding an additional namespace to an already existing namespace in a page's adress. ​ 
 + 
 +---- 
 + 
 +==== Explanation of the issue ====
  
 Unfortunately,​ this can be abused a little too much, rendering searching the wiki and especially linking to wiki pages a real hassle. Just imagine that this page, with its already long name, consisting of three rather long words, also included up to three, five, maybe even seven namespaces, and potentially more.  Unfortunately,​ this can be abused a little too much, rendering searching the wiki and especially linking to wiki pages a real hassle. Just imagine that this page, with its already long name, consisting of three rather long words, also included up to three, five, maybe even seven namespaces, and potentially more. 
  
-"​But... But... Aren't namespaces sort of like folders on ac omputer's operating system ?", you might ask in defence ​of the practice. Well, yes and no. Yes, they are this in theory. Unfortunately,​ in practice, this namespace stacking doesn'​t really function the same way as folder stacking would do on an OS. You're ultimately not putting a page into more and more subfolders. You're instead just expanding the number of namespaces in a wiki page's overall ​adress. The more namespaces you add, the longer and more complex a wiki page'​s ​adress ​becomes. And the more complex its link on the wiki.+"​But... But... Aren't namespaces sort of like folders on a computer's operating system?",​ you might ask in defense ​of the practice. Well, yes and no. Yes, they are this in theory. Unfortunately,​ in practice, this namespace stacking doesn'​t really function the same way as folder stacking would do on an OS. You're ultimately not putting a page into more and more subfolders. You're instead just expanding the number of namespaces in a wiki page's overall ​address. The more namespaces you add, the longer and more complex a wiki page'​s ​address ​becomes. And the more complex its link on the wiki.
  
-What you get as a result of that, especially if the number of additional namespaces gets increasingly absurd, is a sort of "​Namespace Matrioshka"​ page that has an overly long adress. This makes it difficult to type in its full adress ​when adding a link to it (you'​re often forced to resort to copying the link or adress ​every single time) +What you get as a result of that, especially if the number of additional namespaces gets increasingly absurd, is a sort of "​Namespace Matrioshka"​ page that has an overly long address. This makes it difficult to type in its full address ​when adding a link to it (you'​re often forced to resort to copying the link or address ​every single time)  
 + 
 +---- 
 + 
 +==== Why it isn't recommended as a method ====
  
 In conclusion, //less is more//. This counts doubly for namespaces on a wiki using the DokuWiki software. Rather than thinking of additional namespaces as additional folders, think of them as additional identifiers. Ones that can be helpful at times, but are usually wholly unnecessary for creating new wiki pages. In conclusion, //less is more//. This counts doubly for namespaces on a wiki using the DokuWiki software. Rather than thinking of additional namespaces as additional folders, think of them as additional identifiers. Ones that can be helpful at times, but are usually wholly unnecessary for creating new wiki pages.
 +
 +----
 +
 +==== Better alternatives to this approach ====
  
 As an alternative to using too many namespaces, try to instead use wiki page adress variations that can form logically connected main pages and subpages, all within the same namespace. For instance, you've written an AH story series about ATL developments in the New Netherlands colonies. You decide to create an info page on the series in the <​nowiki>​[[stories:​ ]]</​nowiki>​ namespace. Once you finish it, though, you suddenly remember you also want to make a separate page which features a list of characters from the series. Instead of going wild with namespaces, modify the adress of the character subpage in an appropriate way (even if the title of the page will be different). E.g. if your story is called "Tales from the New Netherlands"​ and the main page of this project has the adress <​nowiki>​[[stories:​tales from the new netherlands]]</​nowiki>,​ you could try combinations such as <​nowiki>​[[stories:​tales from the new netherlands - characters]]</​nowiki>​ or <​nowiki>​[[stories:​tales from the new netherlands characters]]</​nowiki>​. Maybe even something suitably shortened, such as <​nowiki>​[[stories:​tftnn characters]]</​nowiki>,​ etc. - though bear in mind that the more similar the adresses of a project'​s pages are, the more likely they are to be easily found by readers. As an alternative to using too many namespaces, try to instead use wiki page adress variations that can form logically connected main pages and subpages, all within the same namespace. For instance, you've written an AH story series about ATL developments in the New Netherlands colonies. You decide to create an info page on the series in the <​nowiki>​[[stories:​ ]]</​nowiki>​ namespace. Once you finish it, though, you suddenly remember you also want to make a separate page which features a list of characters from the series. Instead of going wild with namespaces, modify the adress of the character subpage in an appropriate way (even if the title of the page will be different). E.g. if your story is called "Tales from the New Netherlands"​ and the main page of this project has the adress <​nowiki>​[[stories:​tales from the new netherlands]]</​nowiki>,​ you could try combinations such as <​nowiki>​[[stories:​tales from the new netherlands - characters]]</​nowiki>​ or <​nowiki>​[[stories:​tales from the new netherlands characters]]</​nowiki>​. Maybe even something suitably shortened, such as <​nowiki>​[[stories:​tftnn characters]]</​nowiki>,​ etc. - though bear in mind that the more similar the adresses of a project'​s pages are, the more likely they are to be easily found by readers.
 +
 +----
 +
 +==== See Also ====
 +
 +**[[Too many pointless subpages]]**
  
 ---- ----
Line 17: Line 38:
 ==== Navigation ==== ==== Navigation ====
  
-**[[manual_of_style/manual_of_style#​bad_editing_habits|Bad Editing Habits]]**+**[[manual_of_style:manual_of_style#​bad_editing_habits|Bad Editing Habits]]**
  
-**[[Manual of Style/Manual of Style]]**+**[[Manual of Style:Manual of Style]]**
manual_of_style/unmanageable_matrioshka_namespaces.1453262710.txt.gz · Last modified: 2019/03/29 15:19 (external edit)