Re: [opensuse-wiki] Concept Proposal for the openSUSE wiki
Hi.
I feel that this is a good way to go, the wiki needs to be cleaned up.
One thing I feel that needs to be addressed here to is the case sensitivity issue on the page names, as it is today you can have multiple pages with same name by just changing a letter to say uppercase, this is confusing in my eyes and for a ordinary user this is chaos.
The page names should be case insensitive to minimize the risk of confusion and misinformation.
This is as I feel. :-)
/ Marcus Uddenhed
15 okt 2009 kl. 14.48 skrev Rupert Horstkötter
Welcome to the opensuse-wiki mail list Marcus. On Thursday 15 October 2009 08:47:22 Marcus Uddenhed wrote:
One thing I feel that needs to be addressed here to is the case sensitivity issue on the page names, as it is today you can have multiple pages with same name by just changing a letter to say uppercase, this is confusing in my eyes and for a ordinary user this is chaos.
That is how every wiki treats titles. There is need for that to be able to make distinction between names and ordinary nouns, which can make distinction between different topics. The other thing influenced with case sensitivity is search, but our is not case sensitive. One approach to solve problem is to instruct authors to use Wikipedia style guide for article and section title capitalization, that require 1st word of title and any proper nouns within a title to be capitalized. That makes life much easier, from creating links within sentence like [[this is one link]], and not [[This Is One Link | this is one link]], to compensate for capital letters that don't belong in the middle of the sentence. Besides above, it has at least one more advantage, few pages of instructions lesser to read. -- Regards, Rajko OpenSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Op vrijdag 16 oktober 2009 03:23:30 schreef Rajko M.:
One approach to solve problem is to instruct authors to use Wikipedia style guide for article and section title capitalization, that require 1st word of title and any proper nouns within a title to be capitalized.
This is against language rules in Dutch where capitalisation is minimised. Even Internet is not to be written with a capital, because writing it with a lower case i is not confusing the meaning of the word. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
As an occasional wiki contributor, I find it very difficult to follow the style guide for the syntactical details of links and such. And hence I'm probably one of the most guilty. I'm not disputing the style guide is needed and should be followed :) Its just the wiki synax is anything but friendly and when one is focussed on getting the technical support content correct, its hard to switch horses and then look at the more administrative but still necessary format aspects to improve the presentation (to match the well thought out style guide). Its unfortunate there is not an application editor front end to help with those style guide details. Lee aka oldcpu Rajko M. wrote:
One approach to solve problem is to instruct authors to use Wikipedia style guide for article and section title capitalization, that require 1st word of title and any proper nouns within a title to be capitalized.
That makes life much easier, from creating links within sentence like [[this is one link]], and not [[This Is One Link | this is one link]], to compensate for capital letters that don't belong in the middle of the sentence. Besides above, it has at least one more advantage, few pages of instructions lesser to read.
-- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
oldcpu wrote:
As an occasional wiki contributor, I find it very difficult to follow the style guide for the syntactical details of links and such. And hence I'm probably one of the most guilty.
I'm not disputing the style guide is needed and should be followed :)
...
Rajko M. wrote:
One approach to solve problem is to instruct authors to use Wikipedia style guide for article and section title capitalization, that require 1st word of title and any proper nouns within a title to be capitalized.
I've just joined this group, so I don't know how things are done or what goes on here, so please forgive any missteps, such as proposing the obvious or already present. Many organizations provide templates for these purposes. Writing style, it's true, is hard to capture in a template, but standardized formats, required links and their formats, layouts, all can be encapsulated easily into a single document, or a small set of documents, each with a specific function that could be described in a master documentation page. These documents could be used as a container for any new or updated pages. Never having seen (or even having previously heard of) a wiki design language, which I infer is being referred to in some of the messages I've read during the past few days of watching this list, it also seems a few layout scripts could be used as a resource for prospective editors. Speaking of which, I subscribed because I'd like to participate. How do I go about getting involved? Not being knowledgeable in either linux or suse's variations on linux, I doubt that I could contribute much in the technical areas, but I could help out in regularizing the pages' layouts, style, and so forth. John Perry -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
John, Welcome to mail list dedicated to communication about openSUSE wiki. For the rest see below. On Friday 16 October 2009 21:39:42 John E. Perry wrote:
oldcpu wrote:
As an occasional wiki contributor, I find it very difficult to follow the style guide for the syntactical details of links and such. And hence I'm probably one of the most guilty.
I'm not disputing the style guide is needed and should be followed :)
...
Rajko M. wrote:
One approach to solve problem is to instruct authors to use Wikipedia style guide for article and section title capitalization, that require 1st word of title and any proper nouns within a title to be capitalized.
I've just joined this group, so I don't know how things are done or what goes on here, so please forgive any missteps, such as proposing the obvious or already present.
Many organizations provide templates for these purposes. Writing style, it's true, is hard to capture in a template, but standardized formats, required links and their formats, layouts, all can be encapsulated easily into a single document, or a small set of documents, each with a specific function that could be described in a master documentation page. These documents could be used as a container for any new or updated pages.
I see the same thoughts that I have. The only difference is that I have no experience in practical steps that has to be taken to make this happen. Other that work on documentation are usually very busy this close to release, have additional duties and have no time to create such template articles.
Never having seen (or even having previously heard of) a wiki design language, which I infer is being referred to in some of the messages I've read during the past few days of watching this list, it also seems a few layout scripts could be used as a resource for prospective editors.
There is no special scripting language, it is markup language used in source text of wiki articles, that will be converted by MediaWiki software in final page layout. For instance: == Section title == is converted in html tags: <h2> Section title </h2> which is understandable for common web browsers. It is another story why MediaWiki authors created set of tags that differ from standard html. IMHO, they tried to make basic editing simple, instead of hitting 4 different keys to type <h2> and 5 to close that tag, user has to hit 2 times same key to open and same to close tag that mark start and end of section header (title). For those familiar with html this seems not necessary, but for those that are not I can see advantage of special wiki markup. More time spent creating content, lesser learning how to format article. The most basic text with headers and links can be created knowing: == is section title (up to 4x'=' makes sense) [[ ]] are link delimiters for articles located on the same wiki one empty line is end of paragraph space at the begin of the line gives all output in fixed font For just a bit more learning there is: '' '' is italic delimiter ''' ''' is bold text : indentation ; bold until end of the line ---- will draw the line across the page Playing with multiple formatting tags one can discover how they influence final layout, and the most important thing, while direct usage of html is discouraged, you can have the same effect if you use <h2> and == .
Speaking of which, I subscribed because I'd like to participate. How do I go about getting involved? Not being knowledgeable in either linux or suse's variations on linux, I doubt that I could contribute much in the technical areas, but I could help out in regularizing the pages' layouts, style, and so forth.
We need someone with experience in above mentioned, as that is important part of overall wiki appearance and user experience. As you can see, there is no real TODO list that I can point you to. Some directions are written in http://en.opensuse.org/Wiki_team , and a bit more in a http://en.opensuse.org/Wiki_Team/Current_Actions , but you can find that insufficient. We are just starting discussion how to make wiki more appealing and useful place, so comments and questions from your prospective are valuable feedback for everybody involved. Maybe you can recommend some targeted reading for the rest of us that have interest in documentation organization and not so much luck with general Google search.
John Perry
-- Regards, Rajko OpenSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Rajko M. wrote:
We are just starting discussion how to make wiki more appealing and useful place, so comments and questions from your prospective are valuable feedback for everybody involved.
Some issue and suggestion that i had with current wiki, - Writing Numbered/Ordered List is not easy. Most of the wiki page contains step by step instruction. Using numbered list will make wiki reader know which step is (s)he will doing first and what will do next. Writing instruction in numbered list in wiki is hard, especially numbered list with template in it. Another alternative is using unordered (bullet) list. But sometime when one step required another sub-step and since sub-step is using bullet too it's become messy, all bullets looks same. - It's just me or default wiki font is too large ? To be honest, i, personally, does not like the default font either. Font is the first thing come up in a page and primary interface in wiki and any other web pages. A Good font will make a reader enjoy the reading. - Automatic logout. When i am editing some page, i need to double check several page/link for clarification, and sometime i got distracted by others things. When i am finished and click the preview button and directed to page that says "You need login" i will answer "Forget it". What is a harm to disable automatic logout ? because every one can create opensuse account and do any damage to any page without need to steal other account, right ? - Send me an email on page changes. i am really sure i check that option in "Preferences", but still does not know how to make it works. This option is really useful for peer-reviewed, after some one edit a page that another editor is "watched". Most active editor use "My watchlist" but many of wiki editor i think not that active. -- shuLhan -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Saturday 17 October 2009 01:10:24 m.shulhan wrote:
Rajko M. wrote:
We are just starting discussion how to make wiki more appealing and useful place, so comments and questions from your prospective are valuable feedback for everybody involved.
Some issue and suggestion that i had with current wiki,
- Writing Numbered/Ordered List is not easy.
Most of the wiki page contains step by step instruction. Using numbered list will make wiki reader know which step is (s)he will doing first and what will do next. Writing instruction in numbered list in wiki is hard, especially numbered list with template in it. Another alternative is using unordered (bullet) list. But sometime when one step required another sub-step and since sub-step is using bullet too it's become messy, all bullets looks same.
The text flow is information on steps and their order. The numbering is needed only if you create instructions that contain something like "if condition A then skip to point D", or backwards "if condition C then go back to point A". It is also needed if you want to list some items that are needed for procedure and later in article refer to them as item No. 1 and 2. instead of their longer names. In general instructions that look like computer program should be used as little as possible. They save place on a disk, but, in the same time, they make instructions readable only for small number of people that are used to read computer code, and that is the kind of users that, more often then not, don't need hand holding.
- It's just me or default wiki font is too large ?
To be honest, i, personally, does not like the default font either. Font is the first thing come up in a page and primary interface in wiki and any other web pages. A Good font will make a reader enjoy the reading.
The default font (size, font face, color) could depend on web page, but I guess that are your browser settings that you can tune to get font size that you like. This is valid for any web page, not only our wiki. Some web pages require certain font with all details, but if there is none of required available, browser will use defaults anyway.
- Automatic logout.
When i am editing some page, i need to double check several page/link for clarification, and sometime i got distracted by others things. When i am finished and click the preview button and directed to page that says "You need login" i will answer "Forget it".
Better just log in and then go back to the edit page using browser back button, not a link on a login page. Then use preview and it will work. Besides automatic logout should be set to 8 hours, so any problem with shorter time should be reported as a bug. Although, I'm not sure about proper place where to report it.
What is a harm to disable automatic logout ? because every one can create opensuse account and do any damage to any page without need to steal other account, right ?
No, but to damage your reputation, using your account to do silly edits, one has to take over your account, so it is nothing worry about spam, it is about yourself.
- Send me an email on page changes.
This doesn't work currently. It was disabled for some reason long ago. We will see how that works after wiki software update, and then it could be enabled again.
shuLhan
I'll use this opportunity to say thank you for your contributions to the wiki. -- Regards, Rajko OpenSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Rajko M. wrote:
John,
Welcome to mail list dedicated to communication about openSUSE wiki. For the rest see below. ...
There is no special scripting language, it is markup language used in source text of wiki articles, ...
It is another story why MediaWiki authors created set of tags that differ from standard html.
Well, looking over the MediaWiki history page, I see it simplifies a lot more than just the short list you gave; so even though I usually dislike duplication of resources at whim, (such as the proliferation of object-oriented scripting languages), I can see benefit in much of MediaWiki. Like you, I disdain the silly duplication of (x)html tags.
Speaking of which, I subscribed because I'd like to participate. How do I go about getting involved? Not being knowledgeable in either linux or suse's variations on linux, I doubt that I could contribute much in the technical areas, but I could help out in regularizing the pages' layouts, style, and so forth.
We need someone with experience in above mentioned, as that is important part of overall wiki appearance and user experience.
You've inferred more than I tried to imply :-). I have experience _using_, not _creating_, templates. I'm looking at it, and I'll give it a shot, but... Indeed, I see that there's already some kind of framework for creating wiki pages, since all the pages I've seen have the same title graphic and the same menu on the left. These do not appear to be frames, since they move with the content when I scroll. This I would have considered the minimum for a template, and seems to be already in place. Looking at several pages, I see missing some things such as a Table of Contents section, even on some really long pages. The idea someone proposed of subdividing long pages into a set of shorter pages would be less attractive if we had a template that provided not only the title graphic and the left-hand menu, but also a set of section blocks that automatically generates a set of hyperlinks at the top of the page to each subheading. This would promote organized development of a page, and help contributors such as oldcpu to think about organization without worrying about how to lay out his organized text. I don't object necessarily to division by pages, but frequently, it also makes better sense to have all on one page. Rather than deal with separation of his ideas, then giving them a heading, then adding an address tag, then adding a link to that tag, then finally organizing those links, a contributor could simply edit the template, putting in a subheading and adding the text for that subheading for each subdivision of his article. Then MediaWiki (I suppose?) would automatically put the headers into the wiki's standard format, add the wiki's standard subheading hyperlink to the wiki's standard table of contents, and insert appropriate wiki-standard divisions between sections. The templates would include wiki-standard cross-references, wiki-standard further readings and resources, all in wiki-standard locations on the page, so that after viewing just a couple of pages, users would know where to find everything, and what it looks like, with very little need for searching around. Be aware that I have no idea yet how to accomplish all this; I'll study the problem, but if anyone else has already done or learned this, they can do it with my blessing, or point me toward resources for learning it. In fact, I'd like to learn it anyway, so if anyone already knows it and can short-cut my learning, I'd be happy to be their helper, and work at their direction. John Perry -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Sunday 18 October 2009 16:16:24 John E. Perry wrote:
Rajko M. wrote:
John,
Welcome to mail list dedicated to communication about openSUSE wiki. For the rest see below. ...
There is no special scripting language, it is markup language used in source text of wiki articles, ...
It is another story why MediaWiki authors created set of tags that differ from standard html.
Well, looking over the MediaWiki history page, I see it simplifies a lot more than just the short list you gave; so even though I usually dislike duplication of resources at whim, (such as the proliferation of object-oriented scripting languages), I can see benefit in much of MediaWiki. Like you, I disdain the silly duplication of (x)html tags.
Speaking of which, I subscribed because I'd like to participate. How do I go about getting involved? Not being knowledgeable in either linux or suse's variations on linux, I doubt that I could contribute much in the technical areas, but I could help out in regularizing the pages' layouts, style, and so forth.
We need someone with experience in above mentioned, as that is important part of overall wiki appearance and user experience.
You've inferred more than I tried to imply :-). I have experience _using_, not _creating_, templates. I'm looking at it, and I'll give it a shot, but...
Indeed, I see that there's already some kind of framework for creating wiki pages, since all the pages I've seen have the same title graphic and the same menu on the left. These do not appear to be frames, since they move with the content when I scroll. This I would have considered the minimum for a template, and seems to be already in place.
The top of the page right of logo, and left side under the logo are server side template that only server admins can change. The same is valid for look and feel defined by CSS. We can make changes to the rest of the page. I'll call that user editable area, and that area is what I refer to when talking about editing. Having example article for certain topic that author can copy and edit to suite his needs will help to have consistent look and feel in that user editable area. Wiki editors will benefit by having defined default layout when they have to fix existing articles, or giving recommendations for improvement. The list of benefits doesn't end with that.
Looking at several pages, I see missing some things such as a Table of Contents section, even on some really long pages.
That can happen if there is no sections, or intentionally by including __NOTOC__ in a wiki source text.
The idea someone proposed of subdividing long pages into a set of shorter pages would be less attractive if we had a template that provided not only the title graphic and the left-hand menu, but also a set of section blocks that automatically generates a set of hyperlinks at the top of the page to each subheading.
That I understand as a TOC a Table Of Content, and it is really automatically generated when page contains at least 3 section titles. For instance: http://en.opensuse.org/Documentation
This would promote organized development of a page, and help contributors such as oldcpu to think about organization without worrying about how to lay out his organized text. I don't object necessarily to division by pages, but frequently, it also makes better sense to have all on one page.
The separation on more pages is the one idea that can help separate content by user skills. Simple main page with links to advanced parts, related pages that explain used words and procedures, troubleshooting etc. The other way is use of sections, but that generates very long pages, like: http://en.opensuse.org/Testing:Features_11.1 That page that should be edited by testers to add test results is so long that is hard to navigate without search function, not to mention how it is to edit. More sample you can see on http://en.opensuse.org/Special:Longpages ...
The templates would include wiki-standard cross-references, wiki-standard further readings and resources, all in wiki-standard locations on the page, so that after viewing just a couple of pages, users would know where to find everything, and what it looks like, with very little need for searching around.
The standard sections cross reference, further reading, resources, external links and so on, is something that has to be in example article as reminder to author that this kind of information has to be included. I guess Weekly News guys have something like that. Please check their dashboard page: http://en.opensuse.org/OpenSUSE_Weekly_News/Dashboard That is actually general idea of article templates applied on Weekly News. Browsing from their main page http://en.opensuse.org/OpenSUSE_Weekly_News I can see more things that can be applied to whole wiki.
Be aware that I have no idea yet how to accomplish all this; I'll study the problem, but if anyone else has already done or learned this, they can do it with my blessing, or point me toward resources for learning it. In fact, I'd like to learn it anyway, so if anyone already knows it and can short-cut my learning, I'd be happy to be their helper, and work at their direction.
To address above I'll have to take time and collect links that I find useful for myself and post that on http://en.opensuse.org/Wiki_team .
John Perry
-- Regards, Rajko OpenSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
John E. Perry wrote:
I've just joined this group, so I don't know how things are done or what goes on here, so please forgive any missteps, such as proposing the obvious or already present.
Many organizations provide templates for these purposes. Writing style, it's true, is hard to capture in a template, but standardized formats, required links and their formats, layouts, all can be encapsulated easily into a single document, or a small set of documents, each with a specific function that could be described in a master documentation page. These documents could be used as a container for any new or updated pages.
Never having seen (or even having previously heard of) a wiki design language, which I infer is being referred to in some of the messages I've read during the past few days of watching this list, it also seems a few layout scripts could be used as a resource for prospective editors.
Speaking of which, I subscribed because I'd like to participate. How do I go about getting involved? Not being knowledgeable in either linux or suse's variations on linux, I doubt that I could contribute much in the technical areas, but I could help out in regularizing the pages' layouts, style, and so forth.
John Perry
Hello, Well i suppose there is hardly any need of templates to get to know the basic editing ideas in wiki(openSUSE) :).Initially when i started with editing i was = to a beginner or less that.The best thing which i can share with you is -http://en.wikipedia.org/wiki/How_to_edit .This can give a little hint or a brief idea on how to get started.And when you are almost thorough just keep on surfing the wiki - (http://en.opensuse.org/Special:Allpages) for minor faults and try to rectify them.And as the time advances you'll slowly and steadily get to know the things around :) Warm Regards Wwarlock(Shayon) :) -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
On Saturday 17 October 2009 00:33:09 Shayon wrote:
Well i suppose there is hardly any need of templates to get to know the basic editing ideas in wiki(openSUSE) :).
Basics not, but to ensure unified look and feel, and give authors more time to write about actual topic of their article, instead of reading instructions, applying rules, looking at other pages as template, the set of templates (not in wiki sense, as inserts in other articles) is actually not needed, but required.
Initially when i started with editing i was = to a beginner or less that.The best thing which i can share with you is -http://en.wikipedia.org/wiki/How_to_edit .This can give a little hint or a brief idea on how to get started.And when you are almost thorough just keep on surfing the wiki - (http://en.opensuse.org/Special:Allpages) for minor faults and try to rectify them.And as the time advances you'll slowly and steadily get to know the things around :)
There is difference in will to invest time in formatting experiments between you focused on the wiki alone, and one that is skilled in his field and just wants to put article on the wiki with as little side effort as possible. Such person will use template provided that it exists and its existence is well advertised. Otherwise it may happen that he just walk away instead to write something that our users need. -- Regards, Rajko OpenSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Thanks, Shayon, ... Shayon wrote:
John E. Perry wrote:
I've just joined this group, so I don't know how things are done or what goes on here, so please forgive any missteps, such as proposing the obvious or already present.
Many organizations provide templates for these purposes. Writing style, it's true, is hard to capture in a template, but standardized formats, required links and their formats, layouts, all can be encapsulated easily into a single document, or a small set of documents, each with a specific function that could be described in a master documentation page. These documents could be used as a container for any new or ^^^^^^^^^^^^^^^^^^^ updated pages. ...
Well i suppose there is hardly any need of templates to get to know the basic editing ideas in wiki(openSUSE) :).
Hmm. What I've been exposed to as templates has been documents or document snippets that form the structure for an item. For example, <p> </p> could be called a template for an html paragraph. These tags encapsulate the format of a paragraph, relieving editors of the burden of putting in EOL's and blank lines to delineate paragraphs in their text, <html> <header> </header> <body> </body> </html> could be called a template for a web page. These tags encapsulate the format of a web page, giving editors a structure for specifying formats, fonts, heading highlights, etc. in their text. Initially when i started with
editing i was = to a beginner or less that.The best thing which i can share with you is -http://en.wikipedia.org/wiki/How_to_edit .This can give a little hint or a brief idea on how to get started.And when you are almost thorough just keep on surfing the wiki - (http://en.opensuse.org/Special:Allpages) for minor faults and try to rectify them.And as the time advances you'll slowly and steadily get to know the things around :)
Yes, I see that that site is very helpful. It also supports my use of the term template (http://en.wikipedia.org/wiki/Wikipedia:Template_messages), although it uses only small snippets rather than full-blown page templates (at least I haven't run across any page-level templates yet). I wonder how they get the uniformity of appearance. I suppose opensuse does its pages the same way? I haven't tried yet to edit any opensuse pages. John Perry -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
John E. Perry wrote:
Thanks, Shayon, ...
Your Welcome!! :)
Yes, I see that that site is very helpful. It also supports my use of the term template (http://en.wikipedia.org/wiki/Wikipedia:Template_messages),
Thats Good!!
although it uses only small snippets rather than full-blown page templates (at least I haven't run across any page-level templates yet). I wonder how they get the uniformity of appearance. I suppose opensuse does its pages the same way? I haven't tried yet to edit any opensuse pages.
In openSUSE , templates are basically designed for assigning the articles to certain category.Like - ''Pages that need Expanding'' , ''Pages to Delete'',etc.Yet there isn't any full-fledged template working like an page/article.And i suppose we dont require it.Because articles which fall under the category like HOWTOs,SDB,etc and all cant be noted down under a template ,as it contains manual insertion of data and there might be a change in the article as the OS Version gets updated. Where as the templates in openSUSE are designed on a default basis. :)
John Perry
Best, Shayon -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
Shayon wrote:
John E. Perry wrote:
Thanks, Shayon, ...
Your Welcome!! :)
Yes, I see that that site is very helpful. It also supports my use of the term template (http://en.wikipedia.org/wiki/Wikipedia:Template_messages), Thats Good!!
although it uses only small snippets rather than full-blown page templates (at least I haven't run across any page-level templates yet). I wonder how they get the uniformity of appearance. I suppose opensuse does its pages the same way? I haven't tried yet to edit any opensuse pages.
Arrgh! I got all wrapped up in what I was saying and forgot to finish my point, which was that templates are for simplifying and regularizing common features of a document, or even the whole document itself, and what I was seeing in opensuse, for instance, in the page "Discover It", http://en.opensuse.org/openSUSE:Checked_Pages, was ...
In openSUSE , templates are basically designed for assigning the articles to certain category.Like - ''Pages that need Expanding'' , ''Pages to Delete'',etc.
which looks to me more like assigning them to categories or namespaces, as you say above. Yet there isn't any full-fledged template
working like an page/article.And i suppose we dont require it.Because articles which fall under the category like HOWTOs,SDB,etc and all cant be noted down under a template ,as it contains manual insertion of data and there might be a change in the article as the OS Version gets updated.
Well, no -- the template itself can contain unvarying information, as many of the MediaWiki templates do (and all the opensuse templates I've seen so far), but look at that page http://en.wikipedia.org/wiki/Wikipedia:Template_messages again. You'll see that many of them are sets of tags for either structure or format. I see that http://en.wikipedia.org/wiki/Help:Template has more to say about templates; the templates I've been thinking about are "templates with parameters".
Where as the templates in openSUSE are designed on a default basis.
Which appear to be (so far) "templates with no parameters". Yes, clearly there's a lot more that I have to learn :-). jp -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org
participants (7)
-
Freek de Kruijf -
John E. Perry -
m.shulhan -
Marcus Uddenhed -
oldcpu -
Rajko M. -
Shayon