from Q3 brainstorming meeting:

Use translatable pages for banner content. This could wipe out ¼ of our CentralNotice backlog, plus make it way more pleasant to write and translate banners. **Need to talk to Peter and Jessica about how much this would help them to prioritize

might want to kick this until after roadmapping.

We have this as a stretch goal for Q3 - @AndyRussG and @awight with you being gone, I'm removing it as a goal for this quarter.

I'm very surprised by this proposal, I hope you'll investigate the design thoroughly before starting implementation.

I'm curious how you will automate the generation and update of a translatable page from the banner management special pages and how you will prevent manual edits from breaking the communication between the two.

It's not clear what the expected benefits are, other than the supposed decrease in amount of code and the wishful thinking that this will magically shift the burden of maintaining Translate features for CentralNotice on someone else's shoulders. Most of the blocked bugs seem quite hard to fix this way, you may want to go through them with the assistance of someone more confident with the Translate extension.

Do you CentralNotice folks still believe this is the way to go?

Hi @Nemo_bis, thanks for taking a look at the issue. This was erratic and wishful thinking on my part, for sure, and I'm open to anything we can do to reduce the technical debt of CentralNotice banner translation. I'll try to reword this bug to make fewer assumptions about how we might implement a solution.

There has been no movement on this task for several years - am resolving.