Own mediawiki/wikipedia naming convention for pages
up vote
1
down vote
favorite
I recently installed a mediawiki at home and I'm looking for a way to name pages.
Let's say I have the following structure :
- Main - Dev - C# - Tips
- Main - Cooking - Mexixan Cooking - Tips
- Main - Annoying my girlfriend - Tips
Each final page is a different Tips page. Naming them only "tips" won't work because I need three different pages.
Now, I could name each of my tips page with its "path" (ex: main_cooking_mexican_cooking_tips) but it looks cumbersome and the problem is that, whenever I'll change the structure of my mediawiki, some pages will need to change their name in order to be corrects.
Does it exist some convention to follow regarding this ?
Thanks for your help !
mediawiki wiki
add a comment |
up vote
1
down vote
favorite
I recently installed a mediawiki at home and I'm looking for a way to name pages.
Let's say I have the following structure :
- Main - Dev - C# - Tips
- Main - Cooking - Mexixan Cooking - Tips
- Main - Annoying my girlfriend - Tips
Each final page is a different Tips page. Naming them only "tips" won't work because I need three different pages.
Now, I could name each of my tips page with its "path" (ex: main_cooking_mexican_cooking_tips) but it looks cumbersome and the problem is that, whenever I'll change the structure of my mediawiki, some pages will need to change their name in order to be corrects.
Does it exist some convention to follow regarding this ?
Thanks for your help !
mediawiki wiki
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I recently installed a mediawiki at home and I'm looking for a way to name pages.
Let's say I have the following structure :
- Main - Dev - C# - Tips
- Main - Cooking - Mexixan Cooking - Tips
- Main - Annoying my girlfriend - Tips
Each final page is a different Tips page. Naming them only "tips" won't work because I need three different pages.
Now, I could name each of my tips page with its "path" (ex: main_cooking_mexican_cooking_tips) but it looks cumbersome and the problem is that, whenever I'll change the structure of my mediawiki, some pages will need to change their name in order to be corrects.
Does it exist some convention to follow regarding this ?
Thanks for your help !
mediawiki wiki
I recently installed a mediawiki at home and I'm looking for a way to name pages.
Let's say I have the following structure :
- Main - Dev - C# - Tips
- Main - Cooking - Mexixan Cooking - Tips
- Main - Annoying my girlfriend - Tips
Each final page is a different Tips page. Naming them only "tips" won't work because I need three different pages.
Now, I could name each of my tips page with its "path" (ex: main_cooking_mexican_cooking_tips) but it looks cumbersome and the problem is that, whenever I'll change the structure of my mediawiki, some pages will need to change their name in order to be corrects.
Does it exist some convention to follow regarding this ?
Thanks for your help !
mediawiki wiki
mediawiki wiki
edited Dec 4 at 20:37
fixer1234
17.7k144581
17.7k144581
asked Aug 31 '12 at 9:03
Andy M
120119
120119
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
If you could think of a unique name for each subpage (e.g. something like Mexican cooking tips
?), I think the best way would be to use categories. So, you would have category Main
, which would contain subcategory Cooking
, which would contain subcategory Mexican cooking
, which would contain article Mexican cooking tips
. If you want to rename a category, you would need to change all articles (and subcategories) in that category, but there are tools to automate that (e.g. AWB).
Another option is to use subpages. This way, you would have pages named like Cooking/Mexican cooking/Tips
. Renaming a part of the hierarchy can be done automatically, as long as there is at most 100 subpages (you can raise this number by setting $wgMaximumMovedPages
).
Also, subpages are disabled by default in the main namespace. To enable them, you need to set $wgNamespacesWithSubpages[NS_MAIN] = true
.
Another option is to combine the two approaches: Use subpages for the last level (or possibly last few levels) and categories for the rest. This way, you would have a page named Mexican cooking/Tips
, and the page Mexican cooking
would be in the category Cooking
.
I'll have a look at the categories since it's enabled by default. If it's not enough, I'll consider going to the subpages... I'll keep you updated with my final choice, thanks a lot for your help !
– Andy M
Aug 31 '12 at 20:12
secure.wikimedia.org/wikipedia/en/w/…
– Eroen
Sep 17 '12 at 14:16
@Eroen I'm not sure why you linked to a Wikipedia guideline page from 2004, but that's specific to Wikipedia. On your own wiki, you can do whatever you want.
– svick
Sep 17 '12 at 14:32
Yes. The page describes a lot of non-obvious cons to using subpages, which the WP crowd discovered the hard way, and how categories scale better. This could be useful for mr. Andy, as it provides a counter-point to the apparent simplicity of subpages. Note how most of it is a pro and con list.
– Eroen
Sep 17 '12 at 14:37
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f468558%2fown-mediawiki-wikipedia-naming-convention-for-pages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
If you could think of a unique name for each subpage (e.g. something like Mexican cooking tips
?), I think the best way would be to use categories. So, you would have category Main
, which would contain subcategory Cooking
, which would contain subcategory Mexican cooking
, which would contain article Mexican cooking tips
. If you want to rename a category, you would need to change all articles (and subcategories) in that category, but there are tools to automate that (e.g. AWB).
Another option is to use subpages. This way, you would have pages named like Cooking/Mexican cooking/Tips
. Renaming a part of the hierarchy can be done automatically, as long as there is at most 100 subpages (you can raise this number by setting $wgMaximumMovedPages
).
Also, subpages are disabled by default in the main namespace. To enable them, you need to set $wgNamespacesWithSubpages[NS_MAIN] = true
.
Another option is to combine the two approaches: Use subpages for the last level (or possibly last few levels) and categories for the rest. This way, you would have a page named Mexican cooking/Tips
, and the page Mexican cooking
would be in the category Cooking
.
I'll have a look at the categories since it's enabled by default. If it's not enough, I'll consider going to the subpages... I'll keep you updated with my final choice, thanks a lot for your help !
– Andy M
Aug 31 '12 at 20:12
secure.wikimedia.org/wikipedia/en/w/…
– Eroen
Sep 17 '12 at 14:16
@Eroen I'm not sure why you linked to a Wikipedia guideline page from 2004, but that's specific to Wikipedia. On your own wiki, you can do whatever you want.
– svick
Sep 17 '12 at 14:32
Yes. The page describes a lot of non-obvious cons to using subpages, which the WP crowd discovered the hard way, and how categories scale better. This could be useful for mr. Andy, as it provides a counter-point to the apparent simplicity of subpages. Note how most of it is a pro and con list.
– Eroen
Sep 17 '12 at 14:37
add a comment |
up vote
2
down vote
accepted
If you could think of a unique name for each subpage (e.g. something like Mexican cooking tips
?), I think the best way would be to use categories. So, you would have category Main
, which would contain subcategory Cooking
, which would contain subcategory Mexican cooking
, which would contain article Mexican cooking tips
. If you want to rename a category, you would need to change all articles (and subcategories) in that category, but there are tools to automate that (e.g. AWB).
Another option is to use subpages. This way, you would have pages named like Cooking/Mexican cooking/Tips
. Renaming a part of the hierarchy can be done automatically, as long as there is at most 100 subpages (you can raise this number by setting $wgMaximumMovedPages
).
Also, subpages are disabled by default in the main namespace. To enable them, you need to set $wgNamespacesWithSubpages[NS_MAIN] = true
.
Another option is to combine the two approaches: Use subpages for the last level (or possibly last few levels) and categories for the rest. This way, you would have a page named Mexican cooking/Tips
, and the page Mexican cooking
would be in the category Cooking
.
I'll have a look at the categories since it's enabled by default. If it's not enough, I'll consider going to the subpages... I'll keep you updated with my final choice, thanks a lot for your help !
– Andy M
Aug 31 '12 at 20:12
secure.wikimedia.org/wikipedia/en/w/…
– Eroen
Sep 17 '12 at 14:16
@Eroen I'm not sure why you linked to a Wikipedia guideline page from 2004, but that's specific to Wikipedia. On your own wiki, you can do whatever you want.
– svick
Sep 17 '12 at 14:32
Yes. The page describes a lot of non-obvious cons to using subpages, which the WP crowd discovered the hard way, and how categories scale better. This could be useful for mr. Andy, as it provides a counter-point to the apparent simplicity of subpages. Note how most of it is a pro and con list.
– Eroen
Sep 17 '12 at 14:37
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
If you could think of a unique name for each subpage (e.g. something like Mexican cooking tips
?), I think the best way would be to use categories. So, you would have category Main
, which would contain subcategory Cooking
, which would contain subcategory Mexican cooking
, which would contain article Mexican cooking tips
. If you want to rename a category, you would need to change all articles (and subcategories) in that category, but there are tools to automate that (e.g. AWB).
Another option is to use subpages. This way, you would have pages named like Cooking/Mexican cooking/Tips
. Renaming a part of the hierarchy can be done automatically, as long as there is at most 100 subpages (you can raise this number by setting $wgMaximumMovedPages
).
Also, subpages are disabled by default in the main namespace. To enable them, you need to set $wgNamespacesWithSubpages[NS_MAIN] = true
.
Another option is to combine the two approaches: Use subpages for the last level (or possibly last few levels) and categories for the rest. This way, you would have a page named Mexican cooking/Tips
, and the page Mexican cooking
would be in the category Cooking
.
If you could think of a unique name for each subpage (e.g. something like Mexican cooking tips
?), I think the best way would be to use categories. So, you would have category Main
, which would contain subcategory Cooking
, which would contain subcategory Mexican cooking
, which would contain article Mexican cooking tips
. If you want to rename a category, you would need to change all articles (and subcategories) in that category, but there are tools to automate that (e.g. AWB).
Another option is to use subpages. This way, you would have pages named like Cooking/Mexican cooking/Tips
. Renaming a part of the hierarchy can be done automatically, as long as there is at most 100 subpages (you can raise this number by setting $wgMaximumMovedPages
).
Also, subpages are disabled by default in the main namespace. To enable them, you need to set $wgNamespacesWithSubpages[NS_MAIN] = true
.
Another option is to combine the two approaches: Use subpages for the last level (or possibly last few levels) and categories for the rest. This way, you would have a page named Mexican cooking/Tips
, and the page Mexican cooking
would be in the category Cooking
.
answered Aug 31 '12 at 11:52
svick
6741626
6741626
I'll have a look at the categories since it's enabled by default. If it's not enough, I'll consider going to the subpages... I'll keep you updated with my final choice, thanks a lot for your help !
– Andy M
Aug 31 '12 at 20:12
secure.wikimedia.org/wikipedia/en/w/…
– Eroen
Sep 17 '12 at 14:16
@Eroen I'm not sure why you linked to a Wikipedia guideline page from 2004, but that's specific to Wikipedia. On your own wiki, you can do whatever you want.
– svick
Sep 17 '12 at 14:32
Yes. The page describes a lot of non-obvious cons to using subpages, which the WP crowd discovered the hard way, and how categories scale better. This could be useful for mr. Andy, as it provides a counter-point to the apparent simplicity of subpages. Note how most of it is a pro and con list.
– Eroen
Sep 17 '12 at 14:37
add a comment |
I'll have a look at the categories since it's enabled by default. If it's not enough, I'll consider going to the subpages... I'll keep you updated with my final choice, thanks a lot for your help !
– Andy M
Aug 31 '12 at 20:12
secure.wikimedia.org/wikipedia/en/w/…
– Eroen
Sep 17 '12 at 14:16
@Eroen I'm not sure why you linked to a Wikipedia guideline page from 2004, but that's specific to Wikipedia. On your own wiki, you can do whatever you want.
– svick
Sep 17 '12 at 14:32
Yes. The page describes a lot of non-obvious cons to using subpages, which the WP crowd discovered the hard way, and how categories scale better. This could be useful for mr. Andy, as it provides a counter-point to the apparent simplicity of subpages. Note how most of it is a pro and con list.
– Eroen
Sep 17 '12 at 14:37
I'll have a look at the categories since it's enabled by default. If it's not enough, I'll consider going to the subpages... I'll keep you updated with my final choice, thanks a lot for your help !
– Andy M
Aug 31 '12 at 20:12
I'll have a look at the categories since it's enabled by default. If it's not enough, I'll consider going to the subpages... I'll keep you updated with my final choice, thanks a lot for your help !
– Andy M
Aug 31 '12 at 20:12
secure.wikimedia.org/wikipedia/en/w/…
– Eroen
Sep 17 '12 at 14:16
secure.wikimedia.org/wikipedia/en/w/…
– Eroen
Sep 17 '12 at 14:16
@Eroen I'm not sure why you linked to a Wikipedia guideline page from 2004, but that's specific to Wikipedia. On your own wiki, you can do whatever you want.
– svick
Sep 17 '12 at 14:32
@Eroen I'm not sure why you linked to a Wikipedia guideline page from 2004, but that's specific to Wikipedia. On your own wiki, you can do whatever you want.
– svick
Sep 17 '12 at 14:32
Yes. The page describes a lot of non-obvious cons to using subpages, which the WP crowd discovered the hard way, and how categories scale better. This could be useful for mr. Andy, as it provides a counter-point to the apparent simplicity of subpages. Note how most of it is a pro and con list.
– Eroen
Sep 17 '12 at 14:37
Yes. The page describes a lot of non-obvious cons to using subpages, which the WP crowd discovered the hard way, and how categories scale better. This could be useful for mr. Andy, as it provides a counter-point to the apparent simplicity of subpages. Note how most of it is a pro and con list.
– Eroen
Sep 17 '12 at 14:37
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f468558%2fown-mediawiki-wikipedia-naming-convention-for-pages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown