Closed davidskalinder closed 3 years ago
Reviewing the diffs, I think that in fact this issue should precede #129. It's much simpler since it only requires a wholesale toggle for the article template, whereas the differences in #129 are much more thoroughgoing. Also after this is done I believe activate_article_level
could (in theory) be PR'd right away.
I think the template customization in #129 means that the only things left for this is the little hack to get the event-level article descriptions in the UI, which should now be configable as of db3b12e1e. So this should only need PRing now.
Deployed and tested with the other project-conforming changes.
Like #129 but for article-level stuff. I guess this should (for now) be a wholesale toggle that sits in the coding page container template and puts an if statement around the bit that sources the article template? Though there might be some stuff in the JS files too; I should diff those (or indeed, maybe everything, after #129 is done -- I think at that point the only diffs should be article-level stuff?) between
master
andupstream_development
to find out.