Scratch Wiki talk:Community Portal/Not Done

Shortcuts:
	S:CPND; S:NOTDONE;

Community Portal Archives

Archives (oldest first):
1 • 2 • 3 • 4 • 5 • 6 • 7 • 8 • 9 • 10
11 • 12 • 13 • 14 • 15 • 16 • 17 • 18 • 19 • 20
21 • 22 • 23 • 24 • 25 • 26 • 27 • 28 • 29 • 30
31 • 32 • 33 • 34 • 35 • 36 • 37 • 38 • 39 • 40
41 • 42 • 43 • 44 • 45 • 46 • 47 • 48 • 49 • 50
51 • 52 • 53 • 54 • 55 • 56 • 57 • 58 • 59 • 60
61 • 62 • 63 • 64 • 65 • 66 • 67 • 68 • 69 • 70
71 • 72 • 73 • 74 • 75 • 76 • 77 • 78 • 79 • 80
81 • 82 • 83 • 84 • 85 • 86 • 87 • 88 • 89 • 90
91 • 92 • 93 • 94 • 95 • 96 • 97 • 98 • 99 • 100
101 • 102 • 103 • 104 • 105 • 106 • 107 • 108 • 109 • 110
111 • 112 • 113 • 114 • 115
Unfinished discussions

If a topic on the community portal hasn't received a lot of replies or it's not been solved in a while, topics may be moved to this page, to keep track of incomplete discussions. Remove the original topic and move it to this page to prevent confusion.

We need your help: Apply for getting "International Scratch Wiki Coach"

MainThread #We need your help: Apply for getting "International Scratch Wiki Coach"
SubThread1 #Individual Threads with scratch-wiki-authors that want to help
SubThread2 #Forum Thread: Scratch Wiki in Your Native Language
SubThread3 #New Idea for the future of international Scratch-Wiki or even more
SubThread4 #Not Done!

Introduction

After presenting at de:Scratch2015AMS (see [1]) (and before at de:Scratch2013BCN see[2]) we have some just starting International Scratch Wikis. We found out, that there is much more work, than me de:user:Mtwoll, de:user:LiFaytheGoblin and de:user:akhof can handle.

We just started international Scratch-Wikis where we were sure, that there are Scratchers of that language that would really work hard for their Scratch-Wiki, but it seems that those people all need help, coaching and motivation, to cope with the problems of a just started Wiki: It seems that only id: is completely on the right track until now (Thanks to id:user:Rumanti, who made a great start and motivated some other Indonesian Scartchers to help). ru: is also evolving slowly but there seem to be too less active authors with just ru:user:Dimon4ezzz and ru:user:Timkoiko. With ja: we have great hopes in ja:user:Jp86143 and ja:user:Abee who just started. But hu: and nl: are still in a kind of "starting position".

In opposite to the English and German Scratch-wiki the starting Scratch-Wiki-Authors have no templates and existing articles where they can look up what is needed and mostly less experiance in Wikimedia-Syntax. Also some of them have problems with the English language: Naturally they know it, but everything lasts longer with misunderstandings and so on. (My English isn't perfect either, but where is a will there is a way ;-) Ironically the language-communities that have the biggest problems with English language need a Scratch-Wiki the most. Imagine the English Scratch-Wiki had nearly zero articles and templates and you could only see other wikis in languages that you know only a little bit. Also imagine that your Scratch community was not so big than the english-language one (see Wikipedia: World_language#Living world languages).

How would you start? Therefore I'm asking you for your help: Who of you wants to get „International Scratch Wiki Coach "? You would get an account and perhaps also admin-rights at all existing international wikis (depending on your activity). You should be an experienced Scratch-Wiki author in the English Wiki (>1 year membership and >300 edits?). We already have some de:Scratch-Wiki:Team_Mitglieder#Interwiki Autoren but that's only Interwiki, not coaching. It would really be great, if some of the English Scratch-Wiki-Admins would also apply for this job: They would immediately get Admin rights at all other international Wikis and perhaps also FTP-rights, if they are experienced with that "under the hood"-stuff. To see what goes on, we have made de:Scratch-Wiki:Watch. There are also many other ideas from the International Scratch-Wiki-Community (e.g. automized-account-application everywere, multinational-accounts like in Wikipedia, international templates, Scratch-Projects inside the Scratch-Wiki like we have it in DACH, international Blocks Plugin support, #Mobile Device Skin & Responsive Design for Scratch-Wikis ?, conecting scratch-wikis as a part of the scratch-editor-help…)...

...but let's begin with the beginning :-) Who wants to help and applies for getting "International Scratch Wiki Coach"?
MartinWollenweber (talk | contribs) 12:16, 23 September 2015 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘

Individual Threads with scratch-wiki-authors that want to help

back to top

answer of TheHockeyist

answer of KrIsMa

answer of ErnieParke

answer of jvvg

answer of Mathfreak231

answer of Rumanti

answer of Eribetra

answer of OurPrincess

Forum Thread: Scratch Wiki in Your Native Language

back to top

@All: Am I right that all of you know this Forum Thread? Diskussionsforen » Translating Scratch » Scratch Wiki in Your Native Language (New)] . user:ErnieParke created it and sort of curates it (Thank you very much Ernie!). There are some other language communities that could be ready to start with their own native wiki in the future.
MartinWollenweber (talk | contribs)

Link-Table: Authors wih multiple Scratch-Wiki-Accounts

I put a Table here that shows de:Scratch-Wiki:Watch#Authors wih multiple Scratch-Wiki-Accounts. Please feel free to correct it if there are any mistakes.
MartinWollenweber (talk | contribs) 15:49, 30 September 2015 (UTC)

New Idea for the future of international Scratch-Wiki or even more

Why is Interwiki not possible in the english community-portal?

Why is Interwiki not possible in the english community-portal? In de:Scratch-Wiki:Gemeinschafts-Portal it is no problem (but in and id:Pembicaraan_Scratch-Indo-Wiki:Portal_Komunitas it seems to be, just tried it...).
MartinWollenweber (talk | contribs) 14:00, 23 September 2015 (UTC)

Embedding of Scratch Projects

Unresolved ^{(see all...)}

Hey! :) I was thinking it'd be cool if we could embed Scratch projects into the wiki. They could be used in place of the existing example projects in the Pen Projects article, used on certain tutorial pages to demonstrate an expected result or even show a process more easily using an animation.

At the moment, you can't use the <iframe> tag required for embedding a Scratch project on the wiki. I've done a little research, and it looks like the easiest way to allow iframes would be to install this Media Wiki plugin. The good thing about this extension is that it doesn't allow the embedding of any iframe, it can be configured to only allow the embedding of Scratch projects, for example.
EH7meow (talk | contribs) 22:02, 27 June 2017 (UTC)

3.0 updating

Unresolved ^{(see all...)}

Note:

before writing please read this

As a result of Scratch 3.0 releasing, we have to update a lot of articles.

Is there anything more to update?
Is it OK to use bots?
When to update?

Updates are:

{{Pen Blocks}} to {{Pen Extension}}
Change {{block}} for 3.0 blocks (it's larger than 2.0!)
Music Extension, LEGO WeDo Extension categorize and put a new template
remove {{unreleased}}
if there's XX (1.4) and XX, XX moves to XX (2.0), and XX (3.0) moves XX
TOC remake
Tutorials remake
Upload blocks' images
Remake scratchblocks
put {{Obsolete feature}}

(everybody can edit this list, with Siggy!)

--
Apple502j Talk/Activities 2,243edit 04:58, 14 January 2018 (UTC)

We have to delete Fair Use

Unresolved ^{(see all...)}

The server is in Germany now. German copyright law doesn't allow Fair Use, so we have to delete all the fair use images. For example, screenshots of games are prohibited.
Apple502j Talk/Activities 2,243edit 08:13, 21 February 2018 (UTC)

Help:Contents Is missing some help pages

Unresolved ^{(see all...)}

There are a few help pages which aren't in Help:Contents, for some reason.
We need to fix that.
Yzyzyz (talk | contribs) 14:07, 7 October 2017 (UTC)

Account Request Notes

Unresolved ^{(see all...)}

I, when, recently doing account requests (yes, I do still use this thing) I have noticed that I am not learning much about what this user wants to edit and why they want to join the wiki. I like this system which identifies things to fix, but I feel that we should also add back some of the old application. I suggest adding the wiki experience, why they should be accepted, and an article to edit, and then have the current Find 3 Add 2 system. Opinions?
Cυƨтσмнαcκεя ( тαʟκ | cσптяıв ) 02:34, 25 January 2018 (UTC)

Take Example:

There is a capital S in the word "Screen" in the middle of a sentence that should not be capitalized. There is a dead link to the page "Oranges." There is the first person used under the paragraph called "Pineapples." It would be possible to add a section about Kiwis under the header of "Awesome Fruits." It would be possible to add a picture of an orange to the section titled "Oranges". The secret word is "Bananas"

With this example (which is totally about fruits) as long as they use complete sentences and basically fit this point:

In the request notes, does the user properly identify at least 3 flaws in the flawed article and 2 things to add?
Saying "I found a grammar error" is not clear
Users must actually make sense of what they are talking about.
If the specific examples of what they would add to the flawed article are not allowed on the Wiki (e.g. writing about their projects), fully reject if there was little effort, partially reject if it seems like you could get more ideas out of them or explain to them why it's not allowed.

Then they can be accepted into the wiki. This system, In my opinion, only tests the reading comprehension and if the user can write in complete sentences. It shows nothing about if the user can navigate the wiki or know what they want to edit. We get nothing of why they deserve to be a wikian. I belie these systems need to be combined.
Cυƨтσмнαcκεя ( тαʟκ | cσптяıв ) 02:45, 25 January 2018 (UTC)

Not Done doesn't get enough attention

Unresolved ^{(see all...)}

So I was browsing through Scratch Wiki talk:Community Portal/Not Done and realized that all of the discussions had been moved there and left to rot simply because they happened to last longer than an archive period. I suggest that we do at least one of the following things:

Don't have a separate Not Done page at all and keep the not done discussions on the main CP.: This would be effective but not feasible.
Pros: Great at keeping attention on topics.
Cons: Would likely break links and increase CP loading time.

Link to them in a more obvious way: This would be feasible but potentially not effective.
Pros: Saves space, keeps links.
Cons: Doesn't really solve the problem. Nobody wants to click an extra link just to get to topics they might not even care that much about. From my point of view, people comment on discussions because they're new and they want to get their opinion in. When a discussion takes an extra click to get to and has been rotting for so long, it no longer is attractive to comment on. Also, the Not Done page actually feels like an archive more than another discussion page - thereby discouraging new comments on it.

Have an entirely separate page for not done topics (maybe "Scratch Wiki talk:Not Done"?).: This would be partially feasible but potentially effective too.
Pros: Wouldn't break links (redirects exist, people), and would remove the feeling of an archive since it's a talk page of its own; would also save space on the actual CP because the content is literally in another page.
Cons: Still needs another click, and still seems too separate from the actual CP.

What are your thoughts? Do you have another suggestion for this problem? Do you have an opinion on or amendment to one of the current suggestions? Discuss!
kenny2scratch Talk Contribs Directory 14:12, 7 February 2018 (UTC)

Relax S:NOSP even more

Okay, so the English wiki is obviously by far the most restrictive wiki out of the nine. Especially strict is our rule against user-generated content, S:NOSP. That rule was recently relaxed, to the point where as long as there is at least one Scratch Team member involved, it is allowed.

I feel like we could write so many more articles and have so much more activity, however, if the rule was relaxed further. I propose a relaxation of the rules to the following points:

All of the following are still prohibited:
- All Scratch-prohibited things, including userscripts, iO, and the like
- Particular projects
- Certain forum topics or posts
- Specific studios
- Individual users
Advertising gets kind but firm warnings, three warnings is vandalism, twice vandalism is a block.
All user-generated content articles must have a template denoting them as such.

That means no Paper Minecraft, no Sigton's Shop, no Scratch OS Studio, no Griffpatch; articles about anything else should be allowed by default.

For a quick rule of thumb about what crosses the line under this system, basically specific things are prohibited but collections of them are okay. (Things like studios as collections of projects and forum topics being collections of posts notwithstanding.)

If you think these rules are too relaxed for mainspace articles, I have an alternate proposal. A separate namespace for articles about user-generated content, subject to the following rules:

All Scratch-prohibited things remain prohibited (follow CGs, people!).
Everything else is a go.
Advertising will be treated almost as severely as vandalism, thrice advertising is a block.
The entire namespace is treated as non-content pages (i.e. it's not indexed by default and isn't counted in the {{NUMBEROFARTICLES}} (2,155)) [this rule is open for debate].

The namespace name would be something relevant, e.g. "User Content:" or "UG:" or something.

Which idea would you prefer? What are your thoughts?
kenny2scratch Talk Contribs Directory 22:09, 5 August 2018 (UTC)

Not Done

Unresolved ^{(see all...)}

I know someone already brought it up...
Anyways, Not Done is not getting any attention. I know that Kenny2scratch already added “Things To Do” on the left sidebar, and the TOC of Not Done, yet no one seems to notice it. I think that we should release an announcement to all existing editors about ND, and all incoming users about ND on their welcome page. In fact, I’m going to add that to my welcome right now.
Any thoughts?
NYCDOT [ Talk Page | Contributions | Directory ] 23:53, 19 June 2018 (UTC)

Suggestion: Scratch Wiki:Featured Image Suggestions

Unresolved ^{(see all...)}

It's as it says on the tin.

As part of this new revival of featured images (and leading on from #An Interval for Featured Images, I propose that we create a page similar in concept to S:WWS, where users leave new section saying which image they think deserve to be featured. This will clean up the CP (just slightly). At around the same time as Wiki Wednesday, the EWs/Bureaucrats review the suggestions and pick three images which will then to onto S:FI. If necessary, we could also edit the current Wiki Wednesday suggestion forum post to incorporate Featured Images too.

What do you think?
Daring Sailor [ Talk | Contribs | More... ] 15:24, 4 August 2018 (UTC)

New page for mall simulators

Unresolved ^{(see all...)}

Should we make a new page for mall simulators? Mall simulators are sort of big with the biggest mall simulator (Palace of Points) having more than 1400 members. Should we create a page for it?
Sti_scratch (talk | contribs) 04:55, 21 November 2018 (UTC)

Split the Paint Article

Unresolved ^{(see all...)}

I was browsing the wiki and noticed that the Paint editor article (here) is really long and could possibly be split up into three different articles: History of the paint editor, 2.0 Bitmap Paint editor, and 2.0 Vector Paint Editor.
Jakel181 (talk | contribs) 20:55, 18 September 2018 (UTC)

Block Problems

Unresolved ^{(see all...)}

Not done, as blocks are still unfinished or broken
Today I started to finish up the script for How to Evaluate an Expression, and things got out of hand. When I first completed it, I realized I did some of the block loops wrong, and it like wrapped around some things that I didn't want to wrap around, while I also couldn't get this one if then else block to wrap around something else — it was all a mess. I cleaned some of it up, but I am afraid I'll make it worse and I already spent more than an hour on it. Also, I have to save it each time I want to check if it is correct, since for some reason the blocks won't load up in Show preview mode (it appears in code) but loads when the changes are saved. Can somebody please fix up the script to match the one in post #19 in this forum topic?
TenType (talk | contribs) 04:22, 22 May 2019 (UTC)

Scratch Wiki Adventure

Unresolved ^{(see all...)}

On Wikipedia, there is an option for new Wikians to complete the Wikipedia Adventure. This teaches them skills and covers all the basics of using Wikipedia. I think it'd be a good idea to create a Scratch Wiki Adventure of our own to teach new Wikians the basics of the Scratch Wiki. This would include editing tips, rules, etiquette, etc. I'm wondering what people's thoughts are on this idea and/or if anyone would like to work with me on creating this.
54329 (talk | contribs) 17:08, 20 November 2019 (UTC)

Suggestion: Mention that the Privacy Policy and Disclaimers are in German

Unresolved ^{(see all...)}

Currently, the links under the 'Legal' category do not are not mentioned that they are in German. I suggest that the footer mentions that the content under the Legal category are in German.

Without mentioning that, some people might be confused that they are in German, and not English. They also cannot be translated into English without it being inaccurate.
Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 13:21, 28 March 2020 (UTC)

Scratch Wiki YT Channel

Unresolved ^{(see all...)}

Hi everyone! I wanted to put a little feeler out there to see who was interested in participating/creating content for a possible Scratch Wiki YT Channel. We would publish wiki-like content within YT's video format. We could then link to this content from within the Wiki. You could for example create a Scratch tutorial, run-through a certain block or feature, or discuss a recent community venture you participated in. If y'all are interested in seeing this idea come to fruition, please comment to express your interest and volunteer yourself for content creation. Thanks!
Makethebrainhappy (talk | contribs) 14:51, 27 April 2020 (UTC)

Constructiveness in Community Portal - An Idea

Unresolved ^{(see all...)}

Hello there!

In case you didn't know, I'm a Forum Helper (https://scratch.mit.edu/studios/3688309/) on Scratch, which means I generally help out on the the Scratch discussion forums. One day, I headed over to the Community Portal and it seemed like a sort of "discussion forums" within the Scratch Wiki, and I understand that the concept is different, but for me it personally seemed that way.

Anyways, I mostly help around a lot on the Suggestions forum, which, yet again, redirects to the Community Portal since there are a lot of suggestions for the Scratch Wiki here. One difference is though, that the Scratch Team and some Scratchers (like me) enforce the rule of "constructiveness" while making posts, and I'm pretty sure most of you know what that means but I'll just clarify:

It means that one does not simply post "Support!", "Good idea!", or "+1!" and explain why they like the suggestion, that they provoke discussion, and look for possible issues instead of continuosly leaning on one side, like "I love this suggestion" or "I hate this suggestion"

It means that one does not simply add one sentence to act as if their post is constructive. For example, "Support, because this might be useful for many Wikians!" seems constructive but it isn't really constructive, because they're not stating how it would be useful for many Wikians or why it would be.

Now, I've been looking around in the CP, and I've been seeing a couple of responses just saying "+1!" or merely "Support!" without provoking any further discussion and merely showing your satisfaction. So I thought, maybe, we could enforce the constructive rule on the CP as well. Especially because the ideas here much more mature and complex, and not like Scratch where it's just new blocks or random new features.

I do agree that many people are already following this rule, but maybe just enforce it more? I do think it'll be incredibly helpful for the type of suggestions being given here.

wow... that's... long
Nambaseking01 (talk | contribs) 09:31, 4 July 2020 (UTC)

Merging Cloud Data Articles?

Unresolved ^{(see all...)}

I think that there are far too many articles on Cloud Data. I think these should all be merged or certain ones removed to reduce the amount of potential editing.
ContourLines (talk | contribs) 06:42, 15 July 2020 (UTC)

Suggestion: Have a dedicated page for feedback on the account request system

Unresolved ^{(see all...)}

I was browsing through some old CP archives, and one of the topics reminded me of a suggestion I thought of earlier. My suggestion may have been partly inspired by an account request I reviewed that included feedback on the account request system.

Currently, I leave users one of two messages if I accept their account request. I use this one if their request meets all the requirements already (I have preserved the external links, since this is how I post it on the Scratch website):

“

Hello, (USERNAME). Congratulations - your Scratch Wiki account request was accepted! You can log in here with the password sent to your email address: https://en.scratch-wiki.info/wiki/Special:Login Begin here: https://en.scratch-wiki.info/wiki/S:NEW Make sure to follow the guidelines, shown at https://en.scratch-wiki.info/wiki/S:GUIDES. If you have questions, visit https://en.scratch-wiki.info/wiki/S:FAQ and if they aren't answered there, feel free to ask me or any other Wikian! Have fun!

”

Now, some people inevitably miss something in S:CONTRIB. When we're reviewing account requests, and someone seems to have put in effort and has not missed too much of S:CONTRIB, we first put their request on hold. We comment on their profile and ask them further questions. If they satisfy the requirements after replying to our comment(s), we accept their request. This is all outlined in Scratch Wiki:Become a contributor/Admin Guide.

This is the comment I leave on people's profiles if I first put their request on hold and then accept it:

“

Thanks, that's all. Congratulations - your Scratch Wiki account request was accepted! You can log in here with the password sent to your email address: https://en.scratch-wiki.info/wiki/Special:Login Begin here: https://en.scratch-wiki.info/wiki/S:NEW Make sure to follow the guidelines, shown at https://en.scratch-wiki.info/wiki/S:GUIDES. If you have questions, visit https://en.scratch-wiki.info/wiki/S:FAQ and if they aren't answered there, feel free to ask me or any other Wikian! Have fun!

”

Some Experienced Wikians have a slight variation of this message, but we all link them to Special:Login, S:NEW, S:GUIDES, and S:FAQ (or other shortcuts that link to those pages). Now, why am I mentioning the messages that I use when accepting someone's account request? Well, because those may be changed if my suggestion gets implemented.

What is my suggestion? Well, in short, I think we should have a dedicated page for feedback on our account request system. As a wiki, we should always be looking to improve; and this is a way to do it. People can already give feedback on the account request system (or anything else wiki-related, for that matter) in the CP, but feedback is not actively facilitated. This is why I think we should have a dedicated page.

This page would be specifically designed to be easy-to-use for people who are new to the Scratch Wiki and wikis in general. Users would be able to click a link or button, and the "new section" interface would be filled with a form where they could insert their feedback. The user's signature would be automatically inserted at the end. It would be similar to the link users click to nominate themselves for an EW election.

However, I don't think that the page should just exist — I think we should actively make New Wikians aware of it. When someone gets accepted, the account request system is fresh in their mind, and they may have some ideas on how to improve it. However, they may not know where they can put that feedback, or may be too nervous to make us aware of it. My first thought was to add a link to the page to the messages used when accepting users. If we feel that that already has too much information, we could also add it to S:WELCOME.

Of course, all of this is subject to change. What do y'all think of this idea? Is it a good one? A bad one? Do you have any ideas to make it better? Everyone's feedback is equally valued.
bigpuppy talk ▪︎ contribs 02:16, 3 August 2020 (UTC)

Tip of the Day

Unresolved ^{(see all...)}

SWP 005 - Tip of the Day

Description	Status	Owner	Started	Links
Create a panel that will show one tip for each day of the year.	Not done	bigpuppy ahmetlii Illusion705 Groko13 Filmlover12 Jammum garnetluvcookie jakel181 Dominic305 12944qwerty TheTrillion Jackson49 Purvitekriwal CrazyBoy826	8/22/2020	Project results
				Project page
				Project discussion

I created a Tip of the Day system that will show one tip for each day of the year. It's inspired by Wikipedia's tip of the day. However, we need tips! If you would like to help, feel free to add your name to the project page.
bigpuppy talk ▪︎ contribs 02:29, 23 August 2020 (UTC)

Scratch Wiki talk:Community Portal/Archive 107#Tell users on Wiki Wednesday topics not to spam in replies continuation

Unresolved ^{(see all...)}

I am just reviving the discussion mentioned in the title above because it was archived and it did not seem to be completed. Also, on the latest Wiki Wednesday topic, no notice in the first post telling Scratchers not to spam in the topic was put in.

In the discussion linked above, I mentioned some examples of what the notice would mention as being spam. I also think posts only saying 'Hi', 'Hello' or something similar could also be mentioned as being spam.
Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 15:37, 5 September 2020 (UTC)

json Editing

Unresolved ^{(see all...)}

Many pages have similar instructions on how to access the json inside sb3 and sprite3 files:

Page	Steps Taught
Making Invisible Code	extracting, opening, editing and recompressing
Hidden Blocks	extracting, opening, editing and recompressing
JSON Tutorial	extracting, opening, editing and recompressing
Scratch Lab#Custom Fonts	extracting, opening, editing and recompressing
Layer (value)#Viewing the Specific Layer Value	extracting, opening
How to Save a Project#Uploading a Project	extracting, opening
Exporting and Importing#Scripts	extracting, opening
Scratch File Format#Project Files	extracting

This could be simplified by using templates with instructions for each step, so maybe such templates should be created.
Mlcreater (talk | contribs) 01:50, 26 February 2021 (UTC)

Hide 'Save changes' in the editor until Show Preview is clicked

Unresolved ^{(see all...)}

This might not be possible, but I think the Save Changes button in the editor should be hidden until Show preview is clicked. If this is possible, this would decrease WikiMonitor warnings for editing too many times.

Apart from the possibility of this being a major problem, some users might be confused that the button is missing.
Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 18:04, 2 March 2021 (UTC)

About the block

Unresolved ^{(see all...)}

Many articles on specific Reporter Blocks have paragraphs at the top with messages like:

This scratch wiki talk is about the block. For more information on the value this block reports, see Direction (value).

There could be an {{About the block}} template (or one with a similar name) to take a value's article's name as its argument, and create a paragraph with:

{{about|the block|more information on the value this block reports|[[{{{1}}}]]}}

Such a template could be used on the pages:

Mlcreater (talk | contribs) 02:28, 16 March 2021 (UTC)

Expanding 3D projects

Unresolved ^{(see all...)}

So it looks like a few users are creating more articles on 3D projects, so we should probably have a well-defined approach to this. We need to decide: what is worth including/not including, how will we organize them, what deserves its own article vs. being part of another article, and what amount of depth they should go into.
jvvg (talk | contribs) 18:24, 27 March 2021 (UTC)

Horizontal Blocks

Unresolved ^{(see all...)}

The user on the forums suggested that we make an article about horizontal blocks, pointing out that the French Wiki already has one. (You can see a Google translated version of the French Wiki article here) I am hesitant to make that its own article here since horizontal blocks were never actually released, and we are not a Wiki about ScratchJr (we document that it exists and what it is, but that is mostly just contained within that article). However, it may be worth including in Development of Scratch 3.0. Thoughts?
jvvg (talk | contribs) 17:13, 5 April 2021 (UTC)

Would this be an ok article?

Unresolved ^{(see all...)}

Would list of stickys in the forums be a good enough article?
Bobcat0701 (talk | contribs) 15:51, 15 April 2021 (UTC)

Can we make all dicussions be on separate pages?

Unresolved ^{(see all...)}

This scratch wiki forum is so cluttered up
PenguinLover1123 (talk | contribs) 19:59, 19 August 2021 (UTC)

A draft namespace suggestion

Unresolved ^{(see all...)}

I think there should be a new namespace (similar to Wikipedia's Draft: namespace) for mostly incomplete pages or for pages that have the Wiki Standards template and need a lot of edits to the entire page to meet editing guidelines. Such namespace could be called Draft:, WIP: or something similar.
Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 15:55, 24 September 2021 (UTC)

Proposal for new scratch:explore style content-actions tabs

Unresolved ^{(see all...)}

Hi all,

There is a new proposal for "page", "discussion", etc. tabs currently found in the pencil menu to be included in tabs at the top of the page (which could be instead of or in addition to the pencil menu) in the style of the Scratch Explore page.

The pull request, which includes mock-up screenshots, can be found here: https://github.com/InternationalScratchWiki/ScratchWikiSkin2/pull/95 However, please keep discussion that isn't code review on this topic.

There are several things that still need discussion:

Is this change even necessary?
I think so, because this location for the actions is a click less.
Should these tabs replace the pencil menu?
I think not, because the original explore tab design is unfortunately not very accessible at all... The contrast is simply far too low. The original menu can remain as a more accessible alternative.

However, it's also not completely out of the question to mildly modify the tabs to be more accessible.
1. If so, should the pencil now-button remain (perhaps as a quick edit button) or be removed completely?
Should this be made a user preference?
1. If so, opt-in or out?
Current behavior is to still not have these tabs (i.e. hide them) for anonymous users. Is this ideal?
I'd say so: readers won't be using those links and it would only be visual clutter for them (while being convenient for editors).

This is a major change to Wiki interface design, so I would appreciate as much community input as possible.
kenny2scratch Talk Contribs Directory 07:13, 19 October 2021 (UTC)

Suggestion: Warn users if they add first or second person pronouns to an article

Unresolved ^{(see all...)}

I think it is very common for more newer users to use first or second person articles to mainspace articles, even though not doing so is part of the guidelines (implying that that section might have been skimmed over) So, I think users should be warned in the editor if they introduce non-third person articles, explaining that the wiki is supposed to look professional and that third person pronouns must be used.

Since quotes and reference citations must be put in articles as it was originally written (unless it needs to fit the Scratch Guidelines), and articles like My Blocks have to use the word 'my', I think a template should be used to mark where it is okay to puy first and second person pronouns (and would not be triggering a warning) or what is used to detect the pronouns could skip over quotes and references as well as the template.

I think AbuseFilter can warn users if a certain condition is met, but there might be a chance warning users for using these pronouns in mainspace articles could be a bit too complex.
Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 07:16, 8 November 2021 (UTC)

The Wiki now has (beta) dark theme!

Unresolved ^{(see all...)}

The Wiki interface now has a dark theme! This theme is still in beta - expect issues. You can enable it in Special:Preferences#mw-prefsection-rendering. Please report any issues you encounter on this CP topic or in the Wiki forum topic.

We're already aware of some compatibility issues, but please mention whatever you see. Please report issues by adding them to the list in the following format:

* Issue https://link.to/screenshot~~~~

Please use an approved Image Host for your screenshot. Note also that we are prioritizing cases where the interface is actually unusable (e.g. dark-theme-white text on light-theme-white background) over cases where regular light theme styling is appearing in the midst of dark theme styling.
kenny2scratch Talk Contribs Directory 04:11, 20 December 2021 (UTC)

Recent changes legend is white on white https://u.cubeupload.com/Kenny2cubeupload/recentchangeslegend.png
kenny2scratch Talk Contribs Directory 04:11, 20 December 2021 (UTC)
Done in https://github.com/InternationalScratchWiki/ScratchWikiSkin2/pull/101
kenny2scratch Talk Contribs Directory 23:12, 26 December 2021 (UTC)
File captions are white on white https://u.cubeupload.com/Kenny2cubeupload/filecaptions.png
kenny2scratch Talk Contribs Directory 04:49, 20 December 2021 (UTC)
Done in https://github.com/InternationalScratchWiki/ScratchWikiSkin2/pull/101
kenny2scratch Talk Contribs Directory 23:12, 26 December 2021 (UTC)
Editor is partially white. https://u.cubeupload.com/dhuls/352Screenshot2021122014.png
Dhuls (Talk|918 Contributions|Scratch) 20:31, 20 December 2021 (UTC)
Done in https://github.com/InternationalScratchWiki/ScratchWikiSkin2/pull/101
kenny2scratch Talk Contribs Directory 23:12, 26 December 2021 (UTC)
Protection warning box (and presumably other similar boxes) are dark on dark https://u.cubeupload.com/Kenny2cubeupload/protectionwarning.png
kenny2scratch Talk Contribs Directory 23:12, 26 December 2021 (UTC)
Done in https://github.com/InternationalScratchWiki/ScratchWikiSkin2/commit/91cf619351070ed0a30c2f418db138bbe4c2710a
kenny2scratch Talk Contribs Directory 05:23, 3 March 2022 (UTC)
Text in the editor is white on white when selected https://u.cubeupload.com/CrazyBoy826/72cUntitled.png. Also the arrow before "Advanced" and "special characters" are dark on dark
CrazyBoy826 | Talk | 8,237 edits | Scratch 17:30, 15 March 2022 (UTC)
File metadata is white on white https://u.cubeupload.com/CrazyBoy826/31dUntitled.png
CrazyBoy826 | Talk | 8,237 edits | Scratch 17:39, 15 March 2022 (UTC)
Visual editor top bar is white on white https://u.cubeupload.com/CrazyBoy826/a53Untitled.png
CrazyBoy826 | Talk | 8,237 edits | Scratch 17:53, 15 March 2022 (UTC)
Stripes in "username" form on special pages make text unreadable https://u.cubeupload.com/CrazyBoy826/d46Untitled.png
CrazyBoy826 | Talk | 8,237 edits | Scratch 18:02, 16 March 2022 (UTC)
First two entries in edit history have the light theme https://u.cubeupload.com/CrazyBoy826/927Untitled.png
CrazyBoy826 | Talk | 8,237 edits | Scratch 18:09, 16 March 2022 (UTC)
Search suggestions are white https://assets.scratch.mit.edu/get_image/.%2E/d1ee5d1ef2a1fe8f01a3ca28fb7a8168.png
mybearworld • Talk • Contributions • Profile 11:57, 5 March 2023 (UTC)
The line number bar in the editor is white https://assets.scratch.mit.edu/get_image/.%2E/3af75440f26899a17f5e09e58ce17b68.png
mybearworld • Talk • Contributions • Profile 11:57, 5 March 2023 (UTC)
Links in the editor are a very dark blue https://assets.scratch.mit.edu/get_image/.%2E/f7ccb4207c6c9644366670747bee6c90.png
mybearworld • Talk • Contributions • Profile 11:57, 5 March 2023 (UTC)
The formatting help text is black https://assets.scratch.mit.edu/get_image/.%2E/0f08836d13615d0f25b436f5dda432ab.png
mybearworld • Talk • Contributions • Profile 11:57, 5 March 2023 (UTC)
"Remember that this is only a preview." and other similar warning boxes are light https://assets.scratch.mit.edu/get_image/.%2E/cb6c14d8728f39c895441093306894aa.png
mybearworld • Talk • Contributions • Profile 11:57, 5 March 2023 (UTC)
Some Wiki names are dark on dark on scratch-wiki.info https://assets.scratch.mit.edu/get_image/.%2E/ba4497419f1d237bdb9edcd2f0563a98.png
mybearworld • Talk • Contributions • Profile 05:54, 14 March 2023 (UTC)
The math tag is dark-on-dark as reported by users:Spentine at post:7223078 https://u.cubeupload.com/Spentine/cebimage.png
mybearworld • Talk • Contributions • Profile 14:13, 11 May 2023 (UTC)
Scratch Blocks have a Black outline<sb> and <scratchblocks> tags have different results (see below with dark mode) for example
```
Example<scratchblocks>
```
Example<sb>
Scratchgodo (Talk|Contributions|Scratch) 12:40, 15 June 2023 (UTC)

https://scratch-wiki.info

Unresolved ^{(see all...)}

The page [3] has some visual problems. The link "Scratch" in the description is colored very similarly to the background. Also, the wiki logos are on a dark background, which makes some parts unreadable. For example, the "wiki" in the English wiki logo does not have a border, which means it is difficult to see. Also, the Dutch wiki logo has background removal mistakes which are easily seen. Could this page be improved to remove these problems?
CrazyBoy826 | Talk | 8,237 edits | Scratch 23:28, 19 January 2022 (UTC)

I agree with you on the first point; the link does seem very similar to the background. I don't think it necessarily needs to be changed, however.

Filmlover12 Talk Contribs Scratch 15:07, 20 January 2022 (UTC)

I'm not sure what you're seeing, but for me, the header is purple, the link to "Scratch" is blue, and the wiki logos are on a white background. What device are you using?

KangaCoder talk • contribs • profile 16:55, 20 January 2022 (UTC)

@Wangat Not sure if this is directed to me, but yes, you are correct. They just mean that the blue link looks fairly similar to the purple header.

Filmlover12 Talk Contribs Scratch 17:15, 20 January 2022 (UTC)

@Filmlover12: I was asking CrazyBoy826, but I suppose it could’ve been for you as well. However, I switched devices to my phone (rather than my laptop) and the page shows up as is described in the OP.

KangaCoder talk • contribs • profile 17:20, 20 January 2022 (UTC)

This probably happens because I am using dark mode and the website did not specify a background color, so it defaulted to black.
CrazyBoy826 | Talk | 8,237 edits | Scratch 23:19, 20 January 2022 (UTC)

Adding a background color to the CSS should fix this.
CrazyBoy826 | Talk | 8,237 edits | Scratch 23:10, 21 January 2022 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘Yes, it has a bad contrast ratio of 2.21 which makes the link color appear similar to the background color for colorblind people. The header link's color should be changed to #d3f0ff, and the interwiki links at the bottom's color should be changed to #0074b5. Really wish someone would fix this.
　-iviedwall-　‖　talk　contributions　🐱　 06:20, 22 August 2022 (UTC)

The site is intentionally styled differently based on whether your browser indicates it prefers dark theme or not. This includes the background color - it's not dark because it's missing.

It so happens that someone noticed these issues and opened a GitHub issue about them already.

Since the source of the site is open, you can try your hand at fixing the issues yourself. I'd welcome a pull request. However, the logo images cannot be modified (though the English one should be updated to match the current logo) - what if you try body > main > ul > li > a > img {background-image: radial-gradient(white, transparent 75%);}?

kenny2scratch Talk Contribs Directory 19:09, 3 January 2023 (UTC)

Suggestion: Rule page for welcome templates

Unresolved ^{(see all...)}

If it is considered necessary, I think a page on rules on custom welcome templates could be created. Some things it could mention include the 5 welcome templates maximum per talk page, that users should think that they know enough about Wiki contributing to state that they can help users on talk pages, and possibly less likely (although covered by the Wiki guidelines as well), using proper spelling and grammar in welcome templates.
Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 15:19, 18 February 2022 (UTC)

I support this. We already indicate in the userspace policy that only five are allowed, I think it's reasonable to have more fleshed out rules to ensure that these give a fitting welcome to the Wiki.

jvvg (talk | contribs) 15:46, 18 February 2022 (UTC)

I have some objections.

First of all, I don't think that limiting the amount of welcome templates on the talk page is very helpful, in order to encourage users to edit more, unless requested by the user. While the users definitely should not only limit their contributions with non-mainspace edits for continuously maintaining the wiki, I don't see any harm if users also focuses outside of the mainspace. And, in my opinion, this also keeps the wiki thriving because the people find a reason to check the wiki - and hence not cutting their ties with the wiki.

However, if there'd be a guideline (like how Bigpuppy led about standardizing signatures before) to standardize welcome templates (i.e those shouldn't be too flashy, shouldn't cover the whole page, etc.), or maybe listing some suggestions as common sense (for example not posting too much templates at the same time); then that would be nice indeed.

ahmetlii Talk Contributions Directory 18:51, 19 February 2022 (UTC)

Revive-bump: I created a proposal for such help page a short time after first posting this, which I have recently restarted editing. Some of the rules listed might not be official yet.

Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 18:29, 29 January 2023 (UTC)

Encourage user talk page topics that only say hello to go on Scratch profiles instead

Unresolved ^{(see all...)}

I think that user talk page topics where users only say hello (except welcome templates and messages) should go on users' Scratch profiles, as I think they are not very Wiki-related, might be a very broad and/or generic topic, and they take a very short amount of time to write.
Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 10:55, 21 February 2022 (UTC) modified 16:24, 21 February 2022 (UTC)

You are free to do this on your own talk page if you wish, but I personally don't see any problem with messages that simply say "hello." We allow non-wiki-related messages on user talk pages. The Scratch Wiki is a community, and sometimes people in our community wish to greet each other for no reason other than to be friendly. I don't see why they should be required to go to a separate website to be able to do that.

bigpuppy talk ▪︎ contribs 15:52, 21 February 2022 (UTC)

This talk page contains a long streak of messages (the users who posted them all joined the wiki after I became EW) that only say hello. I think these could be more convenient to the user and keeping the talk page more wiki-related or formal if those messages went on Scratch profiles instead.

Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 07:56, 24 February 2022 (UTC)

Like bigpuppy said, you can enforce it on your own page, but unless it becomes spammy I see no reason to do it for all talk pages.

78ch3 : [My talk] | [|Contribs] | [|Main] 02:50, 7 March 2022 (UTC)

Support. It could be very annoying for some users when it gets spammy and makes it hard to focus on more important discussions about the wiki than random greetings. However, if a user was blocked on Scratch or can't access Scratch, saying "Hi" and not making it look spammy is still reasonable since they probably just want to interact with people.

　-iviedwall-　‖　talk　contributions　🐱　 06:25, 22 August 2022 (UTC)

Tip of the Day

Unresolved ^{(see all...)}

The Tip of the Day project was started some time ago. I think it is a very good idea, but not much work has been done on it. It will take a very long time before we have 366 tips (one for each day of the year).

Instead of having that many tips, we can start with the tips we have and randomly post one on Scratch Wiki Home each day. There are already enough tips to start doing this. Having the tips on Scratch Wiki Home will also encourage more editors to add tips. (At User:CrazyBoy826/Scratch Wiki Home, there is a version of the home page with a section for tips.)

Instead of having one tip for each day of the year, we can have a human (or bot) randomly select one of the tips to be posted on the home page (similar to how News works). This will encourage more editors to suggest tips that we can post later.

Thoughts and suggestions?
CrazyBoy826 | Talk | 8,237 edits | Scratch 19:10, 20 March 2022 (UTC)

I currently believe this is a good idea as I think it would be a useful addition to the homepage. Just one question, would the tips be related to articles on the Wiki? For example, a tip about using a certain type of block and having a link to that block's page on the Wiki.

Adzboy (talk | contribs) 19:22, 20 March 2022 (UTC)

The tips would have links, but they would not necessarily be related to individual articles. See User:Bigpuppy/Tip of the Day for more information.
CrazyBoy826 | Talk | 8,237 edits | Scratch 00:17, 21 March 2022 (UTC)

Ah, ok then.

Support

Adzboy (talk | contribs) 06:48, 21 March 2022 (UTC)

I think this is a good way to bring back tip of the day without too much extra work

Support

Godslamb (talk | contribs) 15:54, 24 March 2022 (UTC)

Nice idea, I support. There are only 365 days and there are 2 type of tips and also there can be enough tips for 365 days soon but why not start with putting 1 tip for a week? and once we get enough tips we can start with the original plan of a new tip everyday and Bigpuppy itself update the homepage maybe. We can first check all tips in both scratch and scratch wiki tip of the day sections and delete the duplicates. We can use the same tips which display there 1st on the project page.
Purvitekriwal (talk | contribs)

This seems like a great way for Scratchers to learn new (albeit possibly not useful) things.

Support

NFlex23 (Talk • 109 Contribs • Scratch) 11:44, 25 March 2022 (UTC)

Support

Vdiu | Talk | Contributions | Scratch Profile 07:06, 7 May 2022 (UTC)

Give the navigation box, tools box and for editors box the `position: fixed;` property

Unresolved ^{(see all...)}

This would help a lot. For example, if I'm at the bottom of the community portal, I have to scroll all the way up to purge it. But is the boxes had the position: fixed; property they would stay in one place.
Vdiu | Talk | Contributions | Scratch Profile 02:44, 31 July 2022 (UTC)

I agree that this should be added. It's really annoying having to scroll all the way up.

starhero5697 • talk • 229 contributions • scratch profile 11:23, 31 July 2022 (UTC)

I agree, this would make navigation more convenient. Now this isn't implemented yet, so you have to add this:

.left {
    position: sticky; /* Sticky is better than fixed because it doesn't overlap the footer ig */
    top: 0;
}

into your CSS page. Hope this helps.

　-iviedwall-　‖　talk　contributions　🐱　 03:34, 1 August 2022 (UTC)

Oh. That works pretty well, but I still think it should be set as a default as not many people (Me, as a example) know what a CSS page is.

Vdiu | Talk | Contributions | Scratch Profile 11:56, 1 August 2022 (UTC)

Btw, I found the page for Wiki CSS: MediaWiki:Common.css

　-iviedwall-　‖　talk　contributions　🐱　 09:14, 5 August 2022 (UTC)

Hi, I'm the person who made the skin. I realize this is a necropost but I wanted to provide some context.

I did consider this when I was originally designing it. The problem that arose was if the boxes became taller than your screen, either you wouldn't be able to access the bottom parts of the last boxes, or there would be an ugly scroll bar on the right of the boxes, to the left of the page. I didn't want to make that choice for everyone, including viewers, so I did it this way instead.

You can use user styling to make that choice yourself. I recommend putting it in skin-specific CSS rather than common CSS; i.e. in Special:MyPage/scratchwikiskin2.css rather than Special:MyPage/common.css.

The MediaWiki:*.css pages follow a similar rule, but they apply to the whole site instead of specific users. So MediaWiki:Common.css applies to the whole site no matter what skin you use; while MediaWiki:Vector.css applies to the whole site when using the Vector skin. They also augment the existing skin styling which can be found here for SWS2.

kenny2scratch Talk Contribs Directory 18:57, 3 January 2023 (UTC)

Rule Change

Unresolved ^{(see all...)}

I beleive the last rule of S:PRO should be changed, the wiki is for information for the community. If everyone already knew it we wouldn't have a wiki.
han614698 talk • contribs • profile 23:48, 26 November 2022 (UTC)

It kinda agree with that, because if we added something everyone already knew there would'nt really be a point in adding it unless someone else that didn't know looked at that page.

SpaghettiAG852097- (talk | contribs) 03:00, 27 November 2022 (UTC)

I agree with that too. Also, just so you know you forgot to add the unresolved.

Python_master20 (talk | contribs) 03:08, 27 November 2022 (UTC)

Well, on this case it is meant as a way to fence unnecessary new pages by new users, though the wording of example is a bit off in my opinion. Notability is a core part of this wiki as it's a selective place, and it's not as same as popularity. (see Notability as judged by Wikipedia, though Scratch Wiki is not Wikipedia so take with a pinch of salt).

If you still didn't acknowledge why is that has to be a rule, imagine if all the people started to write about their own forgotten, dusty projects around there. Not everyone knows those, but also not something informative or makes sense have on a wiki at all. But, that was the case before the introduction of the S:UGC policy, which outright banned user-generated content outside userspaces to create consistency among mainspace articles.

Feel free to see all the relatable mess with S:NOSP here: Relax S:NOSP even more.

ahmetlii Talk Contributions Directory 21:48, 27 November 2022 (UTC)

I changed the wording a few months before this topic was posted from 'the majority of users' to 'a significant amount of users'. Now looking back at that edit, the wording might be a bit vague on how many users 'significant' might be. I think it could be changed to state that notable Scratch topics are significant to the program or website.

Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 17:47, 13 January 2023 (UTC)

TurboWarp Template

Unresolved ^{(see all...)}

Some projects are really laggy, and crash browsers if you try them with scratch. How about making a template for it?

Note:

I've made some code for it here

Vdiu | Talk | Contributions | Scratch Profile 10:59, 28 November 2022 (UTC)

Linking to a Scratch Modification/unofficial Extension doesn't seem like a good idea tbh. Useful? Definitely yes. Should be formatted under a template? Not sure. Does linking allowed? Might as well not be.

ahmetlii Talk Contributions Directory 19:15, 28 November 2022 (UTC)

So yes or no according to you?

Vdiu | Talk | Contributions | Scratch Profile 10:10, 30 November 2022 (UTC)

I'd err on no, at least not as a template. We use Andrew's unofficial 1.4 archive for old posts, but something like an unofficial Scratch Extension is a different level, IMHO. (despite the fact that I've seen many people linking it on the projects)

ahmetlii Talk Contributions Directory 20:07, 30 November 2022 (UTC)

Well, the Scratch Team has noticed turbowarp and made some changes to make it more scratch-friendly, but technically Andrew's archive is a unofficial too, a extension isn't much different. And not all scratch policies are enforced on the wiki so...?

Vdiu | Talk | Contributions | Scratch Profile 15:02, 16 December 2022 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ That's true, but it says on the same page you linked that "TurboWarp is not affiliated with the Scratch Team in any way". The External Programs template is designed to be used for linked websites "not trusted by Scratch or hosted by Wikipedia", which definitely applies to turbowarp. It seems contradictory to have a template suggesting to use a site that another one warns may not be safe.

That said, we know pretty much for a fact that turbowarp is trustworthy and safe. Also, although they haven't endorsed it, the Scratch Team seems to be completely fine with turbowarp. Such a template would definitely be useful. So I'm conflicted, but I'm leaning towards supporting this.
Jackson49 (talk | contribs) 08:07, 31 December 2022 (UTC)

Update on the MediaWiki version upgrade

Hi everyone,

I have mentioned before that we intend to upgrade the Wiki to MediaWiki 1.39. The main thing standing in our way was upgrading all of our custom logic and checking for anything that would be affected by the breaking changes. I am happy to report that I was able to set up a Wiki with all of our custom extensions, and all previously identified issues have been resolved. Some more testing will still be needed to make sure that there aren't any other breaking changes (version 1.39 seems to have a lot of them), but with any luck I'll have another update in a week or two. Thank you to our engineering team for their work in bringing everything up to date, especially kenny2scratch and apple502j.

Thank you everyone for your patience.
jvvg (talk | contribs) 02:34, 28 January 2023 (UTC)

Awesome!

Adzboy • Talk • Contributions • Scratch Profile 08:01, 28 January 2023 (UTC)

Everything looks to be on track, so we are tentatively looking at Tuesday, February 7, for the upgrade. This will result in some downtime (hopefully not more than 30 minutes) and we will give a more specific time once we have confirmed everything is ready.

jvvg (talk | contribs) 20:54, 31 January 2023 (UTC)

Nice, Thanks for the information!

SpaghettiAG852097- talk • contribs • profile 03:00, 1 February 2023 (UTC)

The update will be on Tuesday, February 7, at 9pm Scratch Time. This will result in some downtime, hopefully not more than about 30 minutes. Sorry for the short notice, but hopefully this should be pretty painless.

jvvg (talk | contribs) 17:10, 6 February 2023 (UTC)

Good to know. Luckily, that's not an annoying time for me (It's 2am on February 8th in the UK).

Adzboy • Talk • Contributions • Scratch Profile 06:25, 7 February 2023 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ It looks like the upgrade completed successfully. Please let me know either here or on the Wiki forum topic if you notice anything not looking right. So far the only issue I can see is that a few boxes aren't styled properly.
jvvg (talk | contribs) 02:29, 8 February 2023 (UTC)

I am seeing a lot of changes... first of all the community portal has disappered from the sidebar. Also, a lot of other stuff have dissperared from the sidebar too. It looks very different from before. Also it says "edit source" even though I am not using visual editor. And at the top of each page it says "From scratch wiki" and also in the sidebar it says "Help about MediaWiki" its also EXTREMLY slow. Probably because i am typing this 5 mins after the update...

Thanks
SpaghettiAG852097- talk • contribs • profile 02:36, 8 February 2023 (UTC)

(Edit conflict) For some reason, the text "From Scratch Wiki" is showing up at the top of every page. The site's being extremely slow and buggy for me too.

Jackson49 (talk | contribs) 02:40, 8 February 2023 (UTC)

Pretty much all of this can be explained by caching. The interface cache somehow stored all of the stock interface text and none of our overrides, so I cleared that cache (thank you to kenny2scratch for suggesting that) and it's good now. Similarly the slow performance seems to be getting better, I think also mainly due to stuff being cached.

jvvg (talk | contribs) 02:45, 8 February 2023 (UTC)

Yeah, everything just fixed itself for me, with the exception of the "Edit Source" bug.

Jackson49 (talk | contribs) 02:47, 8 February 2023 (UTC)

I'm not sure what the deal is with "edit source." It doesn't say that on Wikipedia, so it's not just the default for a VisualEditor-enabled Wiki, I'll have to look into it. On the plus side, VisualEditor now works on subpages. The spacing will be kinda awkward since we had to use a janky CSS hack to get it to work in 1.35, but 1.39 may have made that unnecessary.

jvvg (talk | contribs) 02:53, 8 February 2023 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘When you are logged out of the wiki the sidebar looks completely different from when you are logged in. Let me know if you want an image of it Edit:The wiki is more faster now by the way
SpaghettiAG852097- talk • contribs • profile 03:08, 8 February 2023 (UTC)

SYNTAX HIGHLIGHTING IN THE EDITING BOX. ITS GONE. I’m going insane because I can’t see what the elements are easily.

han614698 talk • contribs • profile 03:10, 8 February 2023 (UTC)

There’s also a really annoying “Edit Saved!” box that covers up the navbar until you reload.

han614698 talk • contribs • profile 03:12, 8 February 2023 (UTC)

Try clicking the highliter at the top of the screen

SpaghettiAG852097- talk • contribs • profile 03:12, 8 February 2023 (UTC)

I kinda like the edit saved box. It looks nice lol

SpaghettiAG852097- talk • contribs • profile 03:13, 8 February 2023 (UTC)

I figured out how to get rid of the "edit source" you just gotta go to prefrences then to editing, then check the "Temporaily disable the visual editor while it is in beta"

SpaghettiAG852097- talk • contribs • profile 03:17, 8 February 2023 (UTC)

The Syntax Highlighter is still there for me.

Jackson49 (talk | contribs) 04:43, 8 February 2023 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Small changes - in the pencil menu, it says edit SOURCE, ADD topic, VIEW history.
han614698 talk • contribs • profile 12:38, 8 February 2023 (UTC)

You gotta go to "prefrences" then to "editing" then check the box that says "Temporarily disable visual editor while it is in beta" then it should go away. I do not exactly know why it automatically enabled visual editor for everyone though..

Note:

This does not get rid of the "View history", or the add topic, it only gets rid of "edit source"

sorry for all the spelling mistakes. I don't have autocorrect
SpaghettiAG852097- talk • contribs • profile 14:16, 8 February 2023 (UTC)

I noticed that it shows a not secure warning as if there was no HTTPS, but then it loads with HTTPS fine
-unsigned comment by Ideapad-320 (talk | contribs)

Another thing: VisualEditor works a lot better in this version. It works without any problems on subpages and I remove a CSS hack we needed to make it properly fit on the page before.

jvvg (talk | contribs) 20:15, 8 February 2023 (UTC)

My JS welcomed does not work anymore. Can someone tell me why? (I will leave a link soon)

han614698 talk • contribs • profile 21:49, 8 February 2023 (UTC)

Here’s the link to the welcomer. It’s made by Kenny2scratch, but I use it.User:Kenny2scratch/welcome.js.

han614698 talk • contribs • profile 21:52, 8 February 2023 (UTC)

It could have already been like this, but both of the buttons at the top of the CP to search the archives (not sure what the difference is) search the entire Wiki instead.

Jonathan50 (talk | contribs) 22:02, 8 February 2023 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘Yes I noticed that too, but if you press the search button it only shows the ones on the CP.
SpaghettiAG852097- talk • contribs • profile 22:21, 8 February 2023 (UTC)

Huh, neither button works for me.

Jonathan50 (talk | contribs) 22:25, 8 February 2023 (UTC)

@Jonathan50 I believe this has been an issue for a long time and isn't new to this version of MW.

jvvg (talk | contribs) 03:08, 9 February 2023 (UTC)

Issue with pages

There seems to be a giant white space above every page, and you have to scroll down to read the page.
han614698 talk • contribs • profile 12:06, 8 April 2023 (UTC)

I am experiencing the same issue. This has been happening to me for 3 days and it is kinda annoying having to scroll down each time.

SpaghettiAG852097- talk • contribs • profile 23:31, 8 April 2023 (UTC)

Could any of you mention what browser and operating system you use? I have not experienced this issue so far (Chrome 112 on Windows 10), so this issue could be browser-specific.

Jammum (💬 Talk - ✍️ Contribs - 🐱 Scratch) 06:05, 9 April 2023 (UTC)

Not happening to me (Fully updated Chrome on ChromeOS). I could check on another device? It does sound browser/OS specific like Jammum said.

Adzboy • Talk • Contributions • Scratch Profile 06:19, 9 April 2023 (UTC)

I’m on an iPad, running fully updated (just updated around when the issue started). Safari.

han614698 talk • contribs • profile 10:58, 9 April 2023 (UTC)

bump00:47, 11 April 2023 (UTC)
-unsigned comment by han614698 (talk | contribs)

I am on an iPad, fully updated to iPadOS 16.4.1. I also use Safari.

SpaghettiAG852097- talk • contribs • profile 02:19, 11 April 2023 (UTC)

I have confirmed that this happens on all WebKit browsers, which includes Safari.
-unsigned comment by AppData174 (talk | contribs)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘Please remember to sign your posts with the 4 tidles.
SpaghettiAG852097- talk • contribs • profile 13:33, 12 April 2023 (UTC)

Bump.

han614698 talk • contribs • profile 00:00, 14 April 2023 (UTC)

Bump.

han614698 talk • contribs • profile 18:27, 22 April 2023 (UTC)

Another bump. Jvvg, can you please help? It’s almost impossible to edit the wiki.

han614698 talk • contribs • profile 17:55, 23 April 2023 (UTC)

I have the same issue. You could try using a different browser such as Google Chrome, Microsoft Bing, or Mozilla Firefox. Opera Browser is also a really good choice. I don't exactly know if using different broswers will help, because I use a school iPad and we are only allowed to use Safari on here, but you could try using a different browser.

SpaghettiAG852097- talk • contribs • profile 01:11, 26 April 2023 (UTC)

I can’t change browsers on my iPad.

han614698 talk • contribs • profile 11:22, 28 April 2023 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘Oh. I can't either. It's kinda annoying having to always scroll down, but I don't think there is anything you can really do about it now. I tried everything I could to fix mine but nothing worked.
SpaghettiAG852097- talk • contribs • profile 18:40, 30 April 2023 (UTC)

Help the wiki!

Scratch Wiki talk:Community Portal/Not Done

We need your help: Apply for getting "International Scratch Wiki Coach"

TOC

Introduction

Individual Threads with scratch-wiki-authors that want to help

answer of TheHockeyist

answer of KrIsMa

answer of ErnieParke

answer of jvvg

answer of Mathfreak231

answer of Rumanti

answer of Eribetra

answer of OurPrincess

Forum Thread: Scratch Wiki in Your Native Language

Link-Table: Authors wih multiple Scratch-Wiki-Accounts

New Idea for the future of international Scratch-Wiki or even more

Challenges:

Solution:

Discussion:

First Successes

Test-Scratch-Wiki is online!

Not Done!

Why is Interwiki not possible in the english community-portal?

Not Done

Embedding of Scratch Projects

3.0 updating

We have to delete Fair Use

Help:Contents Is missing some help pages

Account Request Notes

Not Done doesn't get enough attention

Relax S:NOSP even more

Not Done

Suggestion: Scratch Wiki:Featured Image Suggestions

New page for mall simulators

Split the Paint Article

Block Problems

Scratch Wiki Adventure

Suggestion: Mention that the Privacy Policy and Disclaimers are in German

Scratch Wiki YT Channel

Constructiveness in Community Portal - An Idea

Merging Cloud Data Articles?

Suggestion: Have a dedicated page for feedback on the account request system

Tip of the Day

Scratch Wiki talk:Community Portal/Archive 107#Tell users on Wiki Wednesday topics not to spam in replies continuation

json Editing

Hide 'Save changes' in the editor until Show Preview is clicked

About the block

Expanding 3D projects

Horizontal Blocks

Would this be an ok article?

Can we make all dicussions be on separate pages?

A draft namespace suggestion

Proposal for new scratch:explore style content-actions tabs

Suggestion: Warn users if they add first or second person pronouns to an article

The Wiki now has (beta) dark theme!

https://scratch-wiki.info

Suggestion: Rule page for welcome templates

Encourage user talk page topics that only say hello to go on Scratch profiles instead

Tip of the Day

Give the navigation box, tools box and for editors box the position: fixed; property

Rule Change

TurboWarp Template

Update on the MediaWiki version upgrade

Issue with pages

Give the navigation box, tools box and for editors box the `position: fixed;` property