The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 18: | Line 18: | ||
=== Appropedia manual of style? === | === Appropedia manual of style? === | ||
For a more well-presented Appropedia, I'd like to see some consistency in presentation - layout and formatting. These affect quite a few pages, and if I just started changing things I'd put some noses out of joint, so I'd like us to have some agreement. Here are some things I've noticed, with tentative solutions. I don't want to crack down on good people who do things differently from me; I do hope to come to an agreement, and I do want to hear other views. Here's what I'm thinking | For a more well-presented Appropedia, I'd like to see some consistency in presentation - layout and formatting. These affect quite a few pages, and if I just started changing things I'd put some noses out of joint, so I'd like us to have some agreement. Here are some things I've noticed, with tentative solutions. I don't want to crack down on good people who do things differently from me; I do hope to come to an agreement, and I do want to hear other views. Here's what I'm thinking. | ||
* Categories are usually placed at the end, but sometimes at the top. This is only an issue when editing. I like them at the bottom, because (a) it's what I'm used to (on Wikipedia and some other wikis, and it's how I've edited here); and (b) if a new editor visits the page, I think it's good if what they see at the top of the edit box matches what they see on the page, as much as possible. (Conversely, perhaps some journals place keywords at the beginning of articles, so it makes sense from an academic point of view?) | * Categories are usually placed at the end, but sometimes at the top. This is only an issue when editing. I like them at the bottom, because (a) it's what I'm used to (on Wikipedia and some other wikis, and it's how I've edited here); and (b) if a new editor visits the page, I think it's good if what they see at the top of the edit box matches what they see on the page, as much as possible. (Conversely, perhaps some journals place keywords at the beginning of articles, so it makes sense from an academic point of view?) | ||
* Capitalization of page titles and headers. We have a guide at [[Help:Page naming]], but many pages follow different formats, especially with headers, e.g. "How It Works" instead of the suggested "How it works". (I'm not upset if someone does it differently - I just want there to be agreement on whether it's ok to go and fix up the headers.) | * Capitalization of page titles and headers. We have a guide at [[Help:Page naming]], but many pages follow different formats, especially with headers, e.g. "How It Works" instead of the suggested "How it works". (I'm not upset if someone does it differently - I just want there to be agreement on whether it's ok to go and fix up the headers.) | ||
* Titles - plural or singular? I pushed for plurals in the beginning, and that's become the default for many of us, but other editors do it differently. And sometimes I think my idea of plural titles was daft - there are some words where the plural isn't obvious (E.g. is it technology, as an uncountable noun, or technologies?) There are a few issues - see [[Appropedia:Village pump #Capitals in titles - change the convention?]] Note that there will always be exceptions and we need to be very clear about them, and avoid changing inappropriately. (A few pages need to be clearer about whether they're projects or topic pages - and that affects the page name.) | * Titles - plural or singular? I pushed for plurals in the beginning, and that's become the default for many of us, but other editors do it differently. And sometimes I think my idea of plural titles was daft - there are some words where the plural isn't obvious (E.g. is it technology, as an uncountable noun, or technologies?) There are a few issues - see [[Appropedia:Village pump #Capitals in titles - change the convention?]] Note that there will always be exceptions and we need to be very clear about them, and avoid changing inappropriately. (A few pages need to be clearer about whether they're projects or topic pages - and that affects the page name.) | ||
* Headers at the beginning of articles, esp ''Introduction'', ''Background'', ''Definition'', ''Abstract'', or a header that's identical to the page title. I don't see the need for these, and it introduces confusion for anyone trying to emulate existing pages in creating a new page | * Headers at the beginning of articles, esp ''Introduction'', ''Background'', ''Definition'', ''Abstract'', or a header that's identical to the page title. I don't see the need for these, and it introduces confusion for anyone trying to emulate existing pages in creating a new page. (Exceptions: Journal papers are required to have a header for the intro, I think, so if such a paper is replicated here and the author wants to keep it, that's fine.) If we're agreed, I could run my bot and delete most of these in an hour or two's work. | ||
* Notices marking a page as the work of a particular institution - where do they go, top, bottom or side? Does it matter whether it's a topic page or a project page? | * Notices marking a page as the work of a particular institution - where do they go, top, bottom or side? Does it matter whether it's a topic page or a project page? | ||
* Categories for a particular class, especially on topic pages, could give the impression that the page is "owned". How about a template notice giving visible credit to the class, which includes the category, but make it a [https://www.mediawiki.org/wiki/Help:Categories#Hidden_categories hidden category]. | * Categories for a particular class, especially on topic pages, could give the impression that the page is "owned". How about a template notice giving visible credit to the class, which includes the category, but make it a [https://www.mediawiki.org/wiki/Help:Categories#Hidden_categories hidden category]. | ||