daniel added a comment. @spage if we have multiple content slot, we //can// store categories separately. We can store them in a primary slot and edit them directly, or in a derived slots (extracted from wikitext). Or we can leave things as they are. Or we could allow people to enter categories in the wikitext, and then move them to the second primary content in a pre-safe transformation.
Similarly, template documentation (the typical use case for <noinclude>) //could// then be managed in a second primary content slot, as well as the "template data" schema, but we don't have to do that. Also, html and diffs could go into a derived slot. That would be a nice way to consolidate the different storage and caching solutions we have. I'm proposing a storage layer that is flexible enough to accommodate these use cases. Whether we actually do all that remains an open question. But from the conversations we had, it seems like a storage layer like this will come in handy at least for quite a few of these and similar cases. TASK DETAIL https://phabricator.wikimedia.org/T107595 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel Cc: Qgil, Tobi_WMDE_SW, Addshore, Lydia_Pintscher, cscott, PleaseStand, awight, Ricordisamoa, GWicke, MarkTraceur, waldyrious, Legoktm, Aklapper, Jdforrester-WMF, Ltrlg, brion, Spage, MZMcBride, daniel, Wikidata-bugs, aude, Jay8g, bd808 _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
