EBernhardson added a comment.
If I understand the above our intent is to use the same microsite deployment repo/branch as wdqs. Looking over things, one open question I see relates to how we will manage per-site resources. Various files such as index.html, embed.html, custom-config.json, logo(-embed).svg, favicon.*, etc. reference wikidata directly. For the images and json we could have a directory for each site (`docroot/wcqs`?) to drop the site-specific resources in. Apache is fronting the assets, it wouldn't be too hard to rewrite 404's at the top level to check the site-specific docroot. For the html files things are a little murkier. There are lots of links to wikidata.org that may or may not have matching commons resources. Some of the links we likely want to keep pointing to wikidata.org.Some templating build step combined with the per-site docroots could plausibly do it, but some effort has to be invested in reviewing and tracking down all the appropriate links. For the initial microsite deployment I'm expecting correcting this is out of scope. Will need to do a couple steps in puppet to transition the existing wdqs microsite to using the new docroot, then we can update the puppet to expose the second docroot for wcqs. TASK DETAIL https://phabricator.wikimedia.org/T280247 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: EBernhardson Cc: Addshore, Aklapper, Gehel, CBogen, ttaylor, Zbyszko, Invadibot, MPhamWMF, maantietaja, Akuckartz, Nandana, Namenlos314, Lahi, Gq86, Lucas_Werkmeister_WMDE, GoranSMilovanovic, QZanden, EBjune, merbst, LawExplorer, _jensen, rosalieper, Scott_WUaS, Jonas, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
