This is a dupe, but it's an issue with service. <> are stripped for
security reasons.

i.e. found this little script that sort of does that already (with very basic info):

In T174528#3571557, @Tgr wrote:

In T174528#3570076, @Mvolz wrote:

Might it be better to either add to one of these existing tools?
https://tools.wmflabs.org/xtools-ec/ could easily be extended to do something like that, it already has yearly breakdowns, a more detailed breakdown shouldn't be much additional work.

I don't think so, the UI expectations are very different. Power users don't care about the design but want high information density and integration with other power tools; casual users want a nice UI with limited amount of information and lots of explanatory text.
Also this is an Outreachy project and I am not sure I'd want to limit it with candidates who choose PHP as the backend language.
(Some sort of information sharing between the various tools would certainly make sense. But that can be done with an API or shared library as well.)

In T144155#3588622, @Trizek-WMF wrote:

Is possible to define some aliases on each wiki?

0	yes	oui	vrai
1	no	non	faux

If so Templates maintainers will be able to implement the boolean option properly.

The most important thing is to have a nice interface for final users.

In T144155#3588368, @Trizek-WMF wrote:

In T144155#3587780, @Mvolz wrote:

In T144155#2633095, @Trizek-WMF wrote:

Is there any documentation somewhere?

There's the spec here: https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md

Not sure if that's what you were after.

I see the boolean option on 3.4 Type section, but the implementation is not really easy to use. I imagine it as a Yes/No option displayed to the user instead of just a field.

In T144155#2633095, @Trizek-WMF wrote:

Is there any documentation somewhere?

I would also like to see yes/no supported, see: T175247

Hmm maybe T144155 is similar, apparently there *is* a "boolean" type? I guess it's only in the SC?

In T159648#3075080, @Aklapper wrote:

https://www.mediawiki.org/wiki/Extension:SocialLogin
https://www.mediawiki.org/wiki/Extension:GoogleLogin
https://www.mediawiki.org/wiki/Extension:OAuth2_Client
etc.
exist hence closing task as invalid.

Hmm, it just occured to me, where do those "you've just made your 1st/5th/etc edit" notifications come from? We could potentially just display the edit count at all times somewhere, and maybe have little badges for those milestones as well.

How is this different than https://tools.wmflabs.org/guc/ or https://tools.wmflabs.org/xtools-ec/?

I don't think this is a Citoid bug. These are bare references and citoid adds templates. And one of the ISBNs isn't even in worldcat which means citoid can't be used to add it anyway... maybe these were copy-pasted from somewhere?

For prosterity, the Emoji Keyboard extension breaks copy paste in VE. I would put some crying emojis here but it's too inconventient now, :D

In T174268#3558757, @Esanders wrote:

Paste works fine for me - can you give more precise steps with the exact way you copied the text, if reproducible?

Ok, we should add it to the other language wikiversities as well.

Yes, but it also needs to be announced, preferably before it goes live, so
admins have a chance to preemptively undo it.

This also needs to be announced on all wikis and admins need to be told how
to undo it.

In T173706#3551882, @Harjotsingh wrote:

Shuffle auto for questions shuffling using JS ?
But isn't this task for shuffling of proposals/answers ?

Shall we re-enable the other DC now?

This is actually the original behaviour of the tool. But I believe it was changed in order to show the rendered citation. However, when the little citation pop-up that displays the rendered citation was added written, it became redundant.

I should probably note that this is probably done this way in translation server because retrieving each citation individually increases request time quite a lot. We can do it in parallel but it might be too lengthy; request time is already pretty long. We also have a results limit in place currently set to 4, I think, in production? We'd need to lengthen this for this to be useful.

Maybe a first pass we should just use the JS and pass

In T173706#3537326, @Harjotsingh wrote:

Wouldn't it be confusing to have shuffle, shufflequestions and shuffleanswers ?

shuffle and shufflequestions do the same thing and JS is currently enabled on all devices.

I think we should keep shuffle as it is and maybe combine shuffleanswer with it or add shuffleanswer as new parameter like we did and handle it on backend.

Before we get ahead of ourselves with wikidata and what not, there are some slight complications:

In T173706#3537254, @Harjotsingh wrote:

Currently shuffle button is used to shuffle the questions.

Do we remove the shuffle that is done on JS end ?

No.

shufflequestions is trying to do what is already done by shuffle parameter.

We can have automatic shuffle for pageload by JS itself without using the shuffle button.

I've put the shuffling question part of this into a different phab task to avoid confusion: T173706

In T170799#3523622, @Harjotsingh wrote:

In T170799#3523456, @Mvolz wrote:

You can wrap both the feedback and the proposal in the same div, and then shuffle based on that div.

I understand that proposal and feedback are supposed to be wrapped together, however how do we check that the feedback is associated with a proposal ?
Consider the following case :

{Question
|type="()"}
|| Feedback for A
-A
|| Another Feedback for A
-B
|| Feedback for B
-C
|| Feedback for C
-D
|| Feedback for D

Here A has two feedback, one after and one before.

{Question
|type="()"}
|| Feedback for A
-A
|| Feedback for B
-B
|| Another Feedback for B
-C
|| Feedback for C
-D
|| Feedback for D

Here the order in which feedback is presented is changed.
We can either add in documentation that a feedback should always be after the proposal.This way we can be sure that their won't be any inconsistencies.

In T165363#3314276, @Harjotsingh wrote:

@Mvolz As the external link works fine inside tabular response questions, would it be considered a valid workaround to achieve the same?
The following code produces link inside categories.

{Question
|type="()"}
| A | [https://www.google.com B] | C 
+-- A is correct.
-+- [https://www.google.com B is correct].
--+ C is correct.

Screenshot -

@Harjotsingh is this still valid?

@Reedy any chance you can take a look at https://gerrit.wikimedia.org/r/#/c/368536/ ? I can't get it to work on localhost.

You can wrap both the feedback and the proposal in the same div, and then shuffle based on that div.

I don't think it matters *that* much what the order is after submission,
although it might be slightly confusing for the quiz taker? Why don't you
submit what you have an we can take a look at it? You can upload changes for review that
aren't necessarily ready to be merged by putting [WIP] in the subject line,
i.e. "[WIP] Shuffle questions onload".

In T170081#3516519, @Harjotsingh wrote:

Disabling Javascript does show the numbers but not the way they should be.It results in Question statement on the next line.

The question number and question statement should be on the same line no matter the resolution
Screenshot-

The question numbers disappear when the header Quiz wraps around the image, this has been given as a example in the above provided link.

On occasion it is desirable to stop text (or other inline non-floating images) from flowing around a floating image. Depending on the web browser's screen resolution and such, text flow on the right side of an image may cause a section header (for instance, == My Header ==) to appear to the right of the image, instead of below it, as a user may expect.

In our case the header Quiz wraps around the left floating image.In smaller resolution like my screen the text is below the image but in larger resolution the text wraps.We can achieve consistent behaviour by using clear all.

I did the edit on wikiversity, It look similar to the way on my screen.

I don't see how that link is relevant? It's not that the text flow is broken. It's that the numbers are completely gone.

You have to try higher, it's still not wrapping. Or just create a test page
that has less text.

I'm still seeing the problem in production in Chrome. Your screen is smaller so you wouldn't be able to see the wrap in that screenshot anyway.

Ah, you're right :).