LinuxMCE Forums

General => Developers => Wiki => Topic started by: purps on August 31, 2011, 04:28:43 pm

Title: Task | Draft Page Status
Post by: purps on August 31, 2011, 04:28:43 pm
http://wiki.linuxmce.org/index.php/Draft_Page_Status

Any comments/discussion welcome, please feel free to add your ideas under mine on this draft page.

Cheers,
Matt.
Title: Re: Draft Page Status
Post by: bongowongo on August 31, 2011, 04:33:28 pm
Cool

You could also make boxes with

this page is......
(part of) manual
tutorial
best practice

And put it in the proper catogery, like the wikigroup, I do not know by heart which catagory I made up.
Title: Re: Draft Page Status
Post by: purps on August 31, 2011, 04:43:37 pm
Sorry, what do you mean? Is this for the "this page is" bit?
Title: Re: Draft Page Status
Post by: bongowongo on August 31, 2011, 04:47:42 pm
[[category:wiki workgroup]]
[[category:drafts]]

Look at the change I made to the page ;)
Title: Re: Draft Page Status
Post by: bongowongo on August 31, 2011, 04:50:28 pm
Sorry, what do you mean? Is this for the "this page is" bit?

Yes. I edited my post, hopefully it clarifys
Title: Re: Draft Page Status
Post by: bongowongo on August 31, 2011, 04:52:09 pm
You should also have an option in your version tables. Not working / not supported?
Title: Re: Draft Page Status
Post by: bongowongo on August 31, 2011, 04:54:40 pm
I see when you are using the colouring in this draft page you use htmlcodes
What if a newbie will update this page, he has to have reference how to use which colour. What if everything was N/A and he discovered it works in 1004. How does he know which colour of green he should use?
Title: Re: Draft Page Status
Post by: tschak909 on August 31, 2011, 06:59:16 pm
This is why templates come in handy, and particularly, template parameters. ;)

-Thom
Title: Re: Draft Page Status
Post by: brononius on September 01, 2011, 08:24:33 am
Or maybe just a small image on the top right of each document?
This way, the message is there, but doesn't interfere with the article itself.


Something like this? The icons could/should be a bit little smaller:

Example 1
(http://www.oniria.be/temp/linuxmce/710g.png) (http://www.oniria.be/temp/linuxmce/810g.png)(http://www.oniria.be/temp/linuxmce/1004g.png)

Lorem Ipsum is simply dummy text of the printing and typesetting industry.
Lorem Ipsum has been the industry's standard dummy text ever since the
1500s, when an unknown printer took a galley of type and scrambled it to
make a type specimen book. It has survived not only five centuries, but
also the leap into electronic typesetting, remaining essentially unchanged.
It was popularised in the 1960s with the release of Letraset sheets
containing Lorem Ipsum passages, and more recently with desktop publishing
software like Aldus PageMaker including versions of Lorem Ipsum.





Example 3
(http://www.oniria.be/temp/linuxmce/710r.png) (http://www.oniria.be/temp/linuxmce/810g.png)(http://www.oniria.be/temp/linuxmce/1004g.png)
Lorem Ipsum is simply dummy text of the printing and typesetting industry.
Lorem Ipsum has been the industry's standard dummy text ever since the
1500s, when an unknown printer took a galley of type and scrambled it to
make a type specimen book. It has survived not only five centuries, but
also the leap into electronic typesetting, remaining essentially unchanged.
It was popularised in the 1960s with the release of Letraset sheets
containing Lorem Ipsum passages, and more recently with desktop publishing
software like Aldus PageMaker including versions of Lorem Ipsum.




Example 3
(http://www.oniria.be/temp/linuxmce/710g.png) (http://www.oniria.be/temp/linuxmce/810r.png)(http://www.oniria.be/temp/linuxmce/1004r.png)
Lorem Ipsum is simply dummy text of the printing and typesetting industry.
Lorem Ipsum has been the industry's standard dummy text ever since the
1500s, when an unknown printer took a galley of type and scrambled it to
make a type specimen book. It has survived not only five centuries, but
also the leap into electronic typesetting, remaining essentially unchanged.
It was popularised in the 1960s with the release of Letraset sheets
containing Lorem Ipsum passages, and more recently with desktop publishing
software like Aldus PageMaker including versions of Lorem Ipsum.





ps i wasn't able to get the image on the wiki page, therefor i do i here...
Title: Re: Draft Page Status
Post by: bongowongo on September 04, 2011, 12:48:19 pm
This is why templates come in handy, and particularly, template parameters. ;)

-Thom

I have no clue how that works.
Argh
Does anybody have any know how about wiki templates?
Title: Re: Draft Page Status
Post by: posde on September 04, 2011, 12:57:43 pm
I am sure the wikigroup manager will be able to read some documentation about the MediaWiki  ;D
Title: Re: Draft Page Status
Post by: purps on September 04, 2011, 02:24:30 pm
I am trying to bone up on MediaWiki stuff as well, that's how the collapsible contents are going to work I think.
Title: Re: Draft Page Status
Post by: purps on September 08, 2011, 11:58:54 am
I have finished the next iteration of what I think the page status stuff should look like, comments most welcome http://wiki.linuxmce.org/index.php/Draft_Page_Status
Title: Re: Draft Page Status
Post by: bongowongo on September 17, 2011, 12:35:32 pm
Ok let's finalise this task.

The box 10.04 / 8.10 / 7.10 is very nice and we could use that straight away.
You can leave comments how to use the box in the wiki code when people edit the page.
So that there will be uniformity.
Which status will we have?
 
Applicable = works for current version
N/A = doesn't work for current version ( I would prefer that one to be red)
and unknown.
We also need maybe one that it works but you need e.g. a hack.

The box with short summary is also nice idea, but what if it is information AND an instruction?
I still agree that we should keep "this page is a hack'.

The third box can be implemented straight away.
Also all pages with review should be in the catagory group wikiworkgroup?
Title: Re: Task | Draft Page Status
Post by: purps on September 17, 2011, 02:23:42 pm
I agree on the colours for the version info, will change that shortly.

Regarding the page type, I see no reason why both can't be displayed as per the example. Doesn't make sense to split pages up just for the sake of it - if there is RELEVANT background information to an instruction, or vice versa, then fine, just have both.
Title: Re: Task | Draft Page Status
Post by: purps on September 17, 2011, 02:27:34 pm
I've just viewed this page on my netbook for the first time, and the text is wrapping in a stupid way, probably due to the stupid way in which I have done it. I will change this also.
Title: Re: Task | Draft Page Status
Post by: bongowongo on September 17, 2011, 04:36:51 pm
I agree on the colours for the version info, will change that shortly.

Regarding the page type, I see no reason why both can't be displayed as per the example. Doesn't make sense to split pages up just for the sake of it - if there is RELEVANT background information to an instruction, or vice versa, then fine, just have both.

Makes sense.
Ok, I will wait till you modified all, so we can finalise it.
Title: Re: Task | Draft Page Status
Post by: twodogs on September 17, 2011, 11:28:15 pm
A lot of our current wiki articles assume a level of knowledge that many beginning and intermediate users do not possess (i.e. change the polarity on the flux capacitor and Bob's your uncle - it works!). I find that really irritating. If I knew as much as the author, I probably wouldn't be reading his wiki article. So it might be nice to include some verbiage in the template on the preferred level of detail. Something like...

"Wiki articles should be written with beginning users in mind. Readers should be provided an overview of what they are doing before being given a laundry list of steps to perform. If the overview already has already been covered elsewhere, a link to that source would be helpful. If no overview exists, then an introductory paragraph might eliminate repeated cries for assistance in the forums."

This is a pretty simple thing that will pay off in a big way. It makes LinuxMCE less intimidating to new users, so we will increase our user-base. It will also allow users to graduate more rapidly from beginner, to intermediate, to advanced, to developer. A larger and smarter user-base is nothing but good.
Title: Re: Task | Draft Page Status
Post by: bongowongo on September 18, 2011, 02:06:39 am
A lot of our current wiki articles assume a level of knowledge that many beginning and intermediate users do not possess (i.e. change the polarity on the flux capacitor and Bob's your uncle - it works!). I find that really irritating. If I knew as much as the author, I probably wouldn't be reading his wiki article. So it might be nice to include some verbiage in the template on the preferred level of detail. Something like...

"Wiki articles should be written with beginning users in mind. Readers should be provided an overview of what they are doing before being given a laundry list of steps to perform. If the overview already has already been covered elsewhere, a link to that source would be helpful. If no overview exists, then an introductory paragraph might eliminate repeated cries for assistance in the forums."

This is a pretty simple thing that will pay off in a big way. It makes LinuxMCE less intimidating to new users, so we will increase our user-base. It will also allow users to graduate more rapidly from beginner, to intermediate, to advanced, to developer. A larger and smarter user-base is nothing but good.

It makes sense.
I just reveiced a link from the dev's that was to difficult for me.
Maybe make a class

Novice
Intermediate
Expert
Title: Re: Task | Draft Page Status
Post by: davegravy on September 18, 2011, 03:25:54 am
In addition to the 3 levels mentioned, what about a "needs simplification" tag for novice level articles that aren't simple enough.
Title: Re: Task | Draft Page Status
Post by: bongowongo on September 18, 2011, 12:11:29 pm
If a target reader is a novice it should be able to read it
 
If it is not the writer will just have to take another class.
Title: Re: Task | Draft Page Status
Post by: davegravy on September 18, 2011, 06:04:10 pm
Not sure if I described my idea very well.

I'm thinking:

3 levels of intended audience (novice, intermediate, advanced)
AND
for articles that are intended for novice/intermediate users, but are clearly not simple enough for that group, a "needs simplification" tag.



That way if a wiki editor comes across an article that is intended for novice users and it is too complicated, he can tag it as such, and then the article author knows he needs to do more work to simplify things. It's a notice system to the author.
Title: Re: Task | Draft Page Status
Post by: purps on September 19, 2011, 12:47:00 pm
I do agree that the pages should be written for the novice, and something need to be in place to ensure that this happens. What twodogs said to do is vital - I will think about creating a wiki template/standards page and start getting things like this in it.

With regards to marking the pages as novice/intermediate/advance, is that not a bit overkill? Who decides what is intermediate and what is advanced? I completely understand the need for it, but isn't there already a wiki feature in place that says "this page is a stub" and "this page requires simplification", etc? I've seen this on wikipedia before, but I have never known how one would flag this up.
Title: Re: Task | Draft Page Status
Post by: bongowongo on September 20, 2011, 08:51:24 am
http://wiki.linuxmce.org/index.php/Draft_Frequently_used_Command

Hi Purps, I tried to do the status page for this page.
Somehow the alignments do not work if you edit the status boxes specifically for the page.
Title: Re: Task | Draft Page Status
Post by: purps on October 05, 2011, 10:38:05 am
Yes I am going to lay it out in a different way, tables within tables perhaps. I've been experimenting with different browsers on different devices and the current layout is definitely no good.
Title: Re: Task | Draft Page Status
Post by: posde on October 05, 2011, 03:47:39 pm
A note of advice: When setting up templates and pages, always remember the KISS principle. Make sure that

a)  writers can easily setup pages without needing to dig around in obscure formatting
b)  make sure stuff is linked to categories as much as possible
Title: Re: Task | Draft Page Status
Post by: bongowongo on October 16, 2011, 10:18:14 pm
In my opinion, the page status should present fixed choices in a drop down menu.
But I am not sure how this will work with the wiki.