Page MenuHomePhabricator

Create special page(s) for turning collaborationhubs/lists back into legible wikitext
Open, Needs TriagePublic

Description

Create some sort of Special:ConvertCollaborationPageToWikitext to revert creation of a CollaborationHub.

  • input page title, change content model and replace with output wikitext of basically the same thing, sans silly styles/boxen/whatever
  • subpages remain subpages, but with partial transclusions replaced with links (or maybe just output that too?)
  • also convert subpage collaborationlists to wikitext? Maybe have this be an optional (set of) checkboxes, listing all such pages
  • creates new revision as wikitext; does not touch existing revisions, or content models; assumed general script will be used for that if needed per T192326

Note that this should later be interoperable with the handler for creating CollaborationHubs by converting from existing wikiprojects in-place (T135408). Or something.

Event Timeline

Maybe special:changecontentmodel could do it

Special:ChangeContentModel + stuffing everything in a template would probably cover it?

<Skizzerz> maybe you can have a Template: which is the conversion page
<Skizzerz> and you fill in {{{params}}} based on the json bits
<Skizzerz> then editors can control how it converts

<Skizzerz> make a somewhat barebones default, unleash it on enwp to let them tweak it to how they like it, then adopt that as the new default come time to finish everything up :D
Isarra renamed this task from Special page(s) for turning collaborationhubs/lists back into regular wikitext in actually readable fashion to Create special page(s) for turning collaborationhubs/lists back into legible wikitext.Jan 17 2019, 11:58 PM
Isarra updated the task description. (Show Details)

Just using changecontentmodel technically works (so fine for handling), but then you just wind up with the json content... in a wikitext page.

Any special specialpage made for this needs a longer name.

If there's any way to hook into specialchangecontentmodel and make it cram the specific json items into template params in the template/whatever when changing to wikitext specifically, we should probably just do that...

Haven't looked into how smart this thing can be, though.