MX Linux Forum

We have created a new document collection whose concept is to be a sort of drill-down companion to the Users Manual and general resource.

http://mepiscommunity.org/wiki

It contains at the moment the following items:

• Everything that was in the Manual Section 8 (Appendix), with one exception that was moved to the Help documents
• All the material out of the MEPIS Wiki that was being linked to in the Manual
• additional relevant material from the MEPIS Wiki that provides good technical support
• a database of our in-house applications

That material has been edited for the new context, but may well still have unwanted leftovers and certainly still needs better formatting.

Everyone has read access to the Wiki, but only the Dev Team can write and edit. Any Community member who has a suggestion, correction, contribution, etc., should post in this Documentation forum. We would welcome suitable draft documents for inclusion--as long as there are no copyright concerns, of course.

We hope that you will explore and enjoy this Wiki, and help us as we develop it further toward antiX/MX 15 and beyond.

For those not inclined to go look for themselves, here is the list (pasted as code so the entire URL is visible) of everything in the Wiki ATM:
All reviews welcome!

Jerry3904 wrote:For those not inclined to go look for themselves, here is the list (pasted as code so the entire URL is visible) of everything in the Wiki ATM: ...

Here they are as clickable links. (used url tags so they wouldn't get shortened)

http://mepiscommunity.org/wiki/about/da ... plications
http://mepiscommunity.org/wiki/applicat ... stem/alien
http://mepiscommunity.org/wiki/applicat ... m/aptitude
http://mepiscommunity.org/wiki/applicat ... g-software
http://mepiscommunity.org/wiki/applicat ... diswrapper
http://mepiscommunity.org/wiki/applicat ... ding-guide
http://mepiscommunity.org/wiki/applications/pdf
http://mepiscommunity.org/wiki/hardware ... m-wireless
http://mepiscommunity.org/wiki/sound-not-working
http://mepiscommunity.org/wiki/system/boot-parameters
http://mepiscommunity.org/wiki/system/compiling
http://mepiscommunity.org/wiki/system/dosemu
http://mepiscommunity.org/wiki/system/f ... stallation
http://mepiscommunity.org/wiki/applicat ... g-software
http://mepiscommunity.org/wiki/system/kde-on-mx-linux
http://mepiscommunity.org/wiki/system/greeter
http://mepiscommunity.org/wiki/applicat ... ding-guide
http://mepiscommunity.org/wiki/system/permissions
http://mepiscommunity.org/wiki/system/repos-mx-14
http://mepiscommunity.org/wiki/system/time-settings
http://mepiscommunity.org/wiki/system/wine

quick question: can any old how-to be put into the wiki or is there some guideline for inclusion?

Sure, as long as it is relevant to (a current?) version of MX and/or antiX.

As soon as you do it, a policy and precedent will have been set!

Update: the "WIKI" tab at the top of each page now points to the MX/antiX Wiki home page (h/t to Peregrine), where a link to the old MEPIS Wiki can be found.

OK going with D.O. and howtos.
Will Documentation / help files for our in house programs also be acceptable in the wiki?
also along with the above:
Will the links be static in that we can have an in iso document and this document setup in the mx / antix help windows?

Great questions--but really directed to the Dev Team as a whole that owns and is responsible for this Wiki. My role is just "mission and mouth," working with Karen to establish the structure but not determine the content.

I personally think it's a great idea to have the in-house Documentation/Help files there, b/c I have the MX ones currently sitting in a directory that few could find much less edit. Unless Dev Team members think this is a terrible idea, we will create a new Help category for the Wiki, and I will begin to move the MX Help files over there.

Karen can address the link question, but we sure don't want them moving around once we get everything pointing to them.

I ran a test this morning, moving over a couple of MX Help files. The only problem is that if our links go there they will show the text and the frame (unless there is a way to get around that). See contrast below.

I still think we should have the Help files (and Licenses too, BTW) in there, just not yet sure we want to point to that for Help buttons.

I am not sure I understand what you are asking, or mean. But anyway , well first looking at the "home page" http://mepiscommunity.org and then "looking at the wiki,
http://mepiscommunity.org/wiki which I find on the "support" button, along with the link to the forum, and then on the wiki,in the "table of contents", the help file, licenses, etc, are all easy to find,..in a nut shell, I am trying to say, that like it is , I find it pretty easy to move around and find things, the only thing I can think of, but don't know if it would be appropriate, if the manual is not part of the wiki, but it might be helpfull to some people, if there was a link to the manual , also in the table of contents ? Like right above the "help files" , or if you want to keep it alphabetical, right after "licenes", ..it is no big deal , since the "support" button still appears at the top of the page, and that shows a link to the wiki. Then of course, there is the "Other" option, in menu, which I see at this point is empty.
So far, it seems pretty clear and easy to browse, or look for a specific subject , to me. Or in other words , it is easy to follow, looks good.
Hope this makes sense. thanks from Garry
Edied: I am not seeing the "frames" as shown in Jerries post, maybe they all ready worked out a "way around it", ?

Your image shows the Wiki panel to the left and header above, currently not present when the Help link is clicked (the other image I attached).

This thread has become something that really belongs in the Development Forum, so some of the argument may not make much sense.

This thread has become something that really belongs in the Development Forum, so some of the argument may not make much sense.

After some thought, on my part, I was able to understand better, ( I think),
Since the manual is "outside" of the wiki, that is why it appaers as it is, the "help" files you moved, into the wiki, actually still have the "menu" or "table of contents" on the left side. Any way, to me it looks pretty good so far.

that is why it appaers as it is, the "help" files you moved, into the wiki, actually still have the "menu" or "table of contents" on the left side.

Nope. The files are simply html files that we store currently in a directory on the mepiscommunity.org server. When I put them into the Wiki, they will be displayed within the frame of the Wiki, which we don't want to see.

Jerry3904 wrote:I ran a test this morning, moving over a couple of MX Help files. The only problem is that if our links go there they will show the text and the frame (unless there is a way to get around that). See contrast below.

I still think we should have the Help files (and Licenses too, BTW) in there, just not yet sure we want to point to that for Help buttons.

Maybe this is not the problem I first imagined. What do people actually think of seeing the Wiki frame around the help file and associated license?

That is what I was trying to say, I liked that! : Of course, I don't know how others feel about it.
I thought you were saying the problem is, that the "Manual" did not have the frame,

they will be displayed within the frame of the Wiki, which we don't want to see.

Which leads to , if you don't want to see the frame, yes, that is more complicated, and deffinately "developement" perhaps knows a way around it, but I am not sure.
It would be interesting to see how others feel on that,

Will the links be static in that we can have an in iso document and this document setup in the mx / antix help windows?

No problem with the links.

The links are set up so that when someone creates a new page the website creates the url using mepiscommunity.org/wiki/[node:field_section]/[node:title]

If sometime in the future they needed to change for some reason, Drupal has a redirect module we could use so the old link would still take you to the correct location.

frame, Schmame. I like it because I can actually find stuff in it.