Organizing Documentation with MediaWiki
-
Wow, yeah, tons of good info here: https://cmsreport.com/articles/tutorial-organizing-wiki-content-using-mediawiki-3793
-
Categories might work like the tags that I want. Check these out:
https://www.mediawiki.org/wiki/Help:Categories
So, if a page is about support for "Exchange at Andy's House of Flapjacks" we could mark that page as being in the Exchange and Andy's House of Flapjacks Categories.
-
Yep, exactly. The name spaces and the categories are for similar things, to get more detailed the more you search.
Using just categories will really leave you wanting though.
-
So what you'd likely want to do is make names spaces for the things you support.
Using Exchange as a name spaces will then allow you to sort everything related to exchange. And under that you'd have Andy's flap jack house as a category.
-
@DustinB3403 said in Organizing Documentation with MediaWiki:
Using Exchange as a name spaces will then allow you to sort everything related to exchange. And understand you'd have Andy's flap jack house
As an MSP, that doesn't work, though, because we aren't producing general documentation for Exchange, but for a customer's implementation of it. So seeing all customer's Exchange stuff in the same name space would be essentially useless and nearly nothing would apply in the same situation. But what belongs to a customer would always be that customer. So a customer name space would likely make sense.
Namespaces are like folders, the group things together in "hard" ways.
-
@scottalanmiller said in Organizing Documentation with MediaWiki:
@DustinB3403 said in Organizing Documentation with MediaWiki:
Using Exchange as a name spaces will then allow you to sort everything related to exchange. And understand you'd have Andy's flap jack house
As an MSP, that doesn't work, though, because we aren't producing general documentation for Exchange, but for a customer's implementation of it. So seeing all customer's Exchange stuff in the same name space would be essentially useless and nearly nothing would apply in the same situation. But what belongs to a customer would always be that customer. So a customer name space would likely make sense.
Namespaces are like folders, the group things together in "hard" ways.
Well ignore the exchange example, using your customer name would work well.
But do you not see the value in sorting the content based on the implemented solution as well?
IE Andy's flap jack house as a main names space and then exchange for Andy's flap jack house...
-
@DustinB3403 said in Organizing Documentation with MediaWiki:
But do you not see the value in sorting the content based on the implemented solution as well?
That's what the category is for.
-
@scottalanmiller said in Organizing Documentation with MediaWiki:
@DustinB3403 said in Organizing Documentation with MediaWiki:
But do you not see the value in sorting the content based on the implemented solution as well?
That's what the category is for.
They can be, but using namespaces means you have to add custom entries (something I'm sure you're not afraid to do) but still extra work.
Categories are much easier to make, and do allow you to focus in on a specific subject matter. Namespaces are strictly for Andy's Flap Jacks.
So while this might be a worthwhile effort, I think it would be a lot to maintain...
-
Here "brianna.laugher at gmail" has a good description of the uses of each. 3rd post down.
-
...And we've already abandoned MediaWiki for DokuWiki for page security reasons.
-
Here's my $5-6/month/user account with OneNote online
-
-
https://i.imgur.com/Gq1cJCV.png
I appear to have full access OneNote from my browser in my $5-6/m/u account.
-
Here's the free OneNote on my android with my Business account added showing both of the OneNote things in the list.
-
Yeah, but we can't access that. It's $20 for us. That's just the price, can't get around it.
-
@scottalanmiller said in Organizing Documentation with MediaWiki:
Yeah, but we can't access that. It's $20 for us. That's just the price, can't get around it.
If you're really planning on dropping all the way to the $4/u/m exchange only plan, then you can probably move to the $5/month plan (you have less than 250 users, right? and get what I have today.
-
@Dashrender said in Organizing Documentation with MediaWiki:
@scottalanmiller said in Organizing Documentation with MediaWiki:
Yeah, but we can't access that. It's $20 for us. That's just the price, can't get around it.
If you're really planning on dropping all the way to the $4/u/m exchange only plan, then you can probably move to the $5/month plan (you have less than 250 users, right? and get what I have today.
MSP, doesn't work that way. We need our E3 plans. Seriously, we don't have any option for the $5 stuff.
-
If we were a normal company that could use the $5 plans, we'd already be on them and using that. But even when we had OneNote, we were not too impressed with it. It was just "good enough." Now we are looking for something actually good.
-
@scottalanmiller said in Organizing Documentation with MediaWiki:
@Dashrender said in Organizing Documentation with MediaWiki:
@scottalanmiller said in Organizing Documentation with MediaWiki:
Yeah, but we can't access that. It's $20 for us. That's just the price, can't get around it.
If you're really planning on dropping all the way to the $4/u/m exchange only plan, then you can probably move to the $5/month plan (you have less than 250 users, right? and get what I have today.
MSP, doesn't work that way. We need our E3 plans. Seriously, we don't have any option for the $5 stuff.
then you're paying $20 already - so what difference does it make?
-
@scottalanmiller said in Organizing Documentation with MediaWiki:
If we were a normal company that could use the $5 plans, we'd already be on them and using that. But even when we had OneNote, we were not too impressed with it. It was just "good enough." Now we are looking for something actually good.
See, that's a whole different story then. But pricing was the original reason given for moving away from it.. not the desire to find a better solution.
