Phase out Scratch Wiki nomenclature

So Scratch Wiki also documents every single one of its blocks. Then you notice, every single one of their block pages has (block) appended to the end of it, no matter how distinctive the title it is. This is really unnecessary and eats up time when writing links and titles. We should probably avoid this practice. There is no reason to add an extra portion of text when writing pages about blocks with unique titles (especially ones that have input markers ()). The only reason why we should do that is that if the title is ambiguous, such as that size could refer to either the block or the sprite property.

There are also other minor nitpicks I would like to change:

  • The capitalisation of titles arbitrarily don't match how the block appears. Which newcomer to the wiki is gonna type Encode Blocks () to Text () Pretty? Not only that, without changing the capitalisation, you can reduce the amount of your energy wasted off for truly needless redirects (some people tried to emulate the Scratch Wiki scheme)
  • Template naming, conversely, gets too ambiguous without these title fragments that distinguish. Without categories, it can get difficult to tell if it's an infobox or navbox. For the former, there was no category at all and template documentation of infoboxes wouldn't say it was an infobox in common. Nor there was a general template for infoboxes. "Wait. Does that mean that Template:Block will render a block? At least I don't have to design a category table myself! It's already there at Template:Block Categories so I can place it in a section readers demand the most!"

@r4356th, how do you think of that? That would create a minor principle that the Snap! Wiki has better nomenclature than theirs.

Edit: Forgot to search for Infobox in Scratch Wiki first. However, they used that term to refer to an unrelated floating container that has nothing to do with Wikipedia infoboxes or the kind of containers used in templates such as Template:Block. The infobox I refer to so far is something that is like a Wikipedia infobox. Template:Infobox - Wikipedia

It shouldn't matter how titles are capitalized; search should be case independent. Similarly, it shouldn't matter how Snap! block title text is capitalized. In documentation, you should be able to start a sentence with the name of a block, capitalized as all English beginnings of sentences are capitalized. And in forum posts I should be able to talk about the SET block without people telling me there's no such block.

I normally just use scratchblocks (now snapblocks) to avoid the capitalization dilemma

What if it's a sample of machinery data (or in this case, file names)? readme.txt for example. This will not look right and would not reflect what it is, so if a file system uses case-sensitive names, that will be inconvenient for users. Why don't we treat blocks the same way? What makes Scratch Wiki invent this system?

We could just avoid starting sentences with block names. Also, not to mention we could use {{DISPLAYTITLE:block name in lowercase}} to remove the unwanted capitalisation.

Using Title Case, Sentence case or whatever could also brew unwanted niche disputes over the capitalisation of conjuctions or connectives such as then and or.

It doesn't matter in the forums or other regions of the wiki (such as the user pages, talk pages, etc), what it matters is the way titles are named.

Yeah, well, operating systems should use case-independent filenames. I know that's not in your control.

This is where I came in. It shouldn't matter how titles are cased. If there are cases in which only capitalization distinguishes the titles of two articles (not one redirecting to the other; that should just be redundant), then one of them should have its title changed. Really changed, to use different words, maybe in parentheses the way Wikipedia distinguishes articles that would otherwise have the same title.

but still case-preserving--if i name a file "AbcEdJK.Txt" it should be "AbcEdJK.Txt" not "abcedjk.txt" (which is the one thing i dislike about the Snap! username system--it isn't case-preserving)

Edit: ok apparently there's this person who I ended up talking about case sensitivity with, and he disagrees with you

I don't know... there should be a consistent naming scheme for block articles so that when you want to link to it from elsewhere, you know what to put.

Again, it shouldn't matter what you put.

I agree that it all looks more professional if there are uniform conventions, but it shouldn't matter if once in a while somebody miscapitalizes something in a title or a link.

Actually, I'm pretty sure the wiki allows miscapitalizations in links already.

Oh yeah, capitalization shouldn't matter. I was thinking about the original post :smile:

I don't think it does, aside from the first character. For example, if there's a page located at Foobar, the following links will lead to the page:

  • [[Foobar]]
  • [[foobar]]

But [[FooBar]] will not lead to the same page, and instead lead to a similarly named page called FooBar.

MediaWiki titles, as you can see, are often case-sensitive except for the first letter.