Is there a way to immediately down grade all the heading types in a page? For example: Heading to Sub-Heading 1.

Hello, i operate and maintain the National Hockey League (NHL) wiki, I've been actively developing the wiki since I adopted the wiki. I was wondering: how would I access what CSS, JS, MediaWiki the wiki is running?

Please help, I am having trouble figuring it out. thanks in advance

-lolbitlover56

Can I add my own work to dev wiki?

As an idea of mine from three years ago, I have written a proposal for a policy that expands on the Author control point of our policy, giving maintainers more control over content they maintain.

In the past several years we've had incidents where users would introduce a change to a script, stylesheet or a Lua module (referred to as "content") that the author of that content would disagree with if they were properly notified of it. To prevent these incidents, the proposed maintainership policy places restrictions on what changes are acceptable without maintainer approval, allows users to revert changes that they see (or suspect) are not following the policy, and allows administrators to block after a few of such violations. The policy of "only maintainers are allowed to change content" is, of course, too strict for our needs, so there are several additions to the policy to reduce that strictness, such as interventions, community-maintained content, maintainership expiry, maintainership requests and the maintainership abuse procedure.

For the last two years, during the UCP and UCX migration, as well as the MediaWiki 1.37 migration, it was of great importance to understand who is the maintainer of a certain piece of content, so they can be contacted about getting it fixed. I'm sure this information is going to be useful in the future as well, and this policy would force us into regularly updating maintainer information, which benefits both users and maintainers. Which users become maintainers is going to be a topic of discussion after this policy passes, but I'm sure current maintainers will, in time, be appropriately assigned and visible in the infoboxes of relevant pages.

I am starting this discussion as a sort of community vote, to see whether such a policy is worth implementing, whether certain parts need to be clarified and whether there seem to be scenarios where the policy would not work in practice. Please express your opinion in the replies, and after enough discussion we can decide the final outcome. I may be announcing this thread, so please do not leave off-topic replies. I'm particularly looking for opinions of users who are authors, maintainers or really in any way contributed to JavaScript, CSS and Lua content (aside from its documentation and translations, which the policy does not cover) on Dev.

Thanks!

Colors look abnormal to me after recent edits to Common.css. Can it be changed so as to not affect light-mode users?

The template color scheme shows me this

<includeonly>
{{#invoke:color scheme|main}}
</includeonly>
<noinclude>
{{Documentation}}
</noinclude>

So how am I able to find the template's content?

Does anyone know whether it was intentional, and if so what's the reasoning?

Recently DemoScripts stopped functioning to me in most cases, while normal JS works fine. It looks like there are race conditions between the module that defines the importArticles() function and the module that load the gadgets, so the console is filled with ReferenceError: importArticle is not defined

Uh the wiki logo kinda blends in with the header color. So… it’s kind of hard to see. Can dev wiki change the background maybe so it’s better?

I finally got around to fixing and finishing some things with UserLastActivity. I want to update the documentation page but there is a bit of a hiccup. The updates would change a substantial part of the documentation and there is already a Spanish translation of the page. This wouldn't be a problem if I had left things as they were but I also decided to parameterize (following KockaAdmiralac's example with ViewNotificationsUsers) the documentation page to make future translations easier.

The issue here is that, when I make the changes to the English page, I won't be able to translate and update the Spanish page since I don't know Spanish. I tried looking around and there doesn't seem to be any way to use an old version of a page when transcluding content. Any ideas? Perhaps I should revert the Spanish page to before the parameterization?

UCP status is there, but probably needs FandomDesktop status.

I am referring to api.php which is also usable via mw.Api. Is there a page for these changes already? If not, should we create one? I have already noticed a few significant differences and I think it might be helpful to users to have them conveniently documented rather then them having to figure it out by themselves. This especially so now that there won't be many (if any) legacy wikis to compare to in order to determine what might give analogous results.

Also, why are there so many duplicate categories in this Discussions and which ones are we supposed to post to?

I made a bookmarklet, is there a specific page it should go on, or can it have it's own page in the main namespace?

So I added UCP compatibility to MessageWallUserTags, but I can't seem to get the infobox to show it. I looked at other UCP compatible pages and didn't see anything that shows it is UCP compatible in the source. Does it have to be marked by staff? The UCP page also doesn't give that much information about marking scripts.

Any plans for custom namespace for the features like:

• Tool: | Tool talk:

• Javascript: | Javascript talk: (or something like that)

• Etcetera: | Etcetera talk:

In this thread, we were trying to figure out why PurgeButton is listed as "personal use only". Does anyone know the answer? NullEditButton and WhatLinksHere are not listed as "personal use only". Is there something different between them that justifies this difference in treatment?

Also, why are there duplicate Discussions categories?