Talk:Codex

About this board

Aligning the text to the right of a toggle

1
Original Authority (talkcontribs)

Perhaps I'm just being silly, but it does not seem possible to easily align the text of a toggle to the right of the toggle? Wherever in the code I put the label, it always seems to go to the left of the toggle, and not to the right. This presents issues when the labels are not all the same size in length, as if they are stacked vertically, the toggle is in different places on each line, which is visually unappealing.

Is there a way to do this and it just isn't documented? Or is there no way? I'd rather not align all of the toggles to the right of the screen. This is using the CSS only toggles in MediaWiki itself.

Reply to "Aligning the text to the right of a toggle"
GregRundlett (talkcontribs)

Since accessibility is so critical, it's nice to read that it's "built-in" but are there some more details? I'm interested in how the new Codex will enable MediaWiki and other projects to be fully compliant with WACG and also how developers or testers should use tools to verify accessibility in Codex.

GregRundlett (talkcontribs)

Answering my own question, I see the README states "Web accessibility compliant (Web Content Accessibility Guidelines 2.1 level AA)"

Digging further, there is info in the project sources (docs) at packages/codex-docs/docs/style-guide/accessibility.md which includes reference to wikipedia:Wikipedia:Manual_of_Style/Accessibility Wikipedia's Manual of Style (that goes into great depth about Content Accessibility); plus links to the Accessibility guide for developers that describes techniques, guidelines and some tools for developers.

It's only a suggestion since I'm not that familiar with the sources, the tools (such as automated cross-browser testing), and project contributors' methods but perhaps there should be some guideline or specific process added to e.g. https://doc.wikimedia.org/codex/latest/contributing/contributing-code/testing-components.html that says something like "Open WAVE or your Firefox Accessibility Inspector to confirm WCAG 2.1 level AA compliance".

Reply to "Accessibility built in"
Omotecho (talkcontribs)

@Volker E. (WMF), a translator asked me if we could clarify. Is the code for v0.20.0 faltered or altered? Do we see a typo here? It reads:

<translate><!--T:17--> With v0.20.0 it got deprecated and its code faltered into <tvar name="1"><code>codex</code></tvar> package.</translate>
Roan Kattouw (WMF) (talkcontribs)

Thanks for pointing this out! I have edited this wording slightly.

Omotecho (talkcontribs)

Wonderful! Allow me to ping the person at translation, and @Tmv: would be updated. Cheers,

Reply to "typo?"

Hints about how to integrate in js

2
Adamw (talkcontribs)

Really great documentation so far! As a reader, I was curious what "index.js" should contain, any hints would be appreciated. Perhaps something like Vue.mwCreateApp( { render: ... } ).mount( domElement )?

Roan Kattouw (WMF) (talkcontribs)

Yes, that's exactly right, init.js should contain code mounting the component. I've tried to make this clearer by linking to the Vue.js documentation page at the top of the Codex page, and also linking to the section about init files below the example that uses an init file.

One thing that I'd still like to find a place to add is an example showing how all these pieces come together into an example module. That would probably fit best on the Vue.js page.

Reply to "Hints about how to integrate in js"
There are no older topics