mozilla / advocacy.mozilla.org

https://advocacy.mozilla.org
Mozilla Public License 2.0
203 stars 34 forks source link

Partial templates for content editing #133

Open alicoding opened 8 years ago

alicoding commented 8 years ago

Problems

  1. Have to use github to update the copy
  2. Have to get dev to change the copy

    Propose solution

update copy flow

Using CMS that allows anyone to change the copy with the option to preview before apply their changes (draft preview).

Goal

We need to allow anyone who's working on the campaign to be able to change the copy or even add new section to the site like the example before

ruaaxfbp

cc @simonwex @lovegushwa

simonwex commented 8 years ago

@alicoding the proposal needs some more details. Let's start with a flow diagram of the current way content makes its way onto the campaign sites. Who has to approve it? Who writes it? What are the constraints?

alicoding commented 8 years ago

@simonwex I updated the issue, but I might be wrong in some of the step there, and @lovegushwa might be able to help identify or point out if my flow chart is in the right track here?

lovegushwa commented 8 years ago

@alicoding @simonwex we're really talking about these campaign pages: (not the advocacy.mozilla.org page above.)

https://advocacy.mozilla.org/encrypt/social/4

Ali your current flow above is close but copy comes in two different ways: Final approved copy: goes into a github build ticket along with UI comps. Additional copy edits: go into the QA ticket (not individual copy change tickets.)

I'm not convinced we have a problem here that needs to be addressed with a CMS. For example, final approved copy would still be implemented by a developer. We're not setting up a simple static page here, there are multiple variants of these pages running various AB tests / different segmentation so we will not be able to just create a new page and send traffic to it without work from a developer ... That leaves us with using a CMS for Additional copy edits, which are fixed during the QA process.

screen shot 2016-04-04 at 2 40 36 pm

screen shot 2016-04-04 at 2 40 45 pm