-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Wagtail Templates] Flow chart of different templates #1405
Comments
Excellent! @sabrinang might be interested in this as well since she might be working on some onboarding, documentation, CMS ux stuff! |
@sabrinang let's connect and collaborate! |
Sounds great! |
@sabrinang @kristinashu and I analyzed the pages and came up with 4 basic templates staff constantly use. Here are the diagrams: Campaign Page (2 templates) @gvn are we missing anything there? Please let us know - you can comment on InVision as well. As you can see from there, the templates we already have can be used by staff with minimal production team support - designers are needed for images and icons, but that's all. However, if staff needs another type of page that doens't fit into the templates categories above, then production team (designer + engineer) + a staff member should work together to find the best solution. Next (suggested) steps:
!!!!!!Feel free to add/edit the next steps above.!!!!! |
Thank you @taisdesouzalessa! This is so helpful to see. Being about to show these explicit rules helps us move away from giving so many options to the admin user and moves us towards baking the options into the template (i.e. campaign pages always have x number of columns). |
I've received feedback that some multi-page campaigns might not have a petition form. This means some campaign pages will look like the Opportunity pages. Because of this, I think the sub nav on Campaign pages should match the sub nav on Opportunity pages. I've mocked up the four possible templates for Opportunity and Campaign pages https://redpen.io/p/zm3711d264ee11ad4f but I'm struggling to find a consistent grid. @taisdesouzalessa @sabrinang do you have any feedback? It's confusing so let me know if you have any questions. |
@kristinashu I find the 4th option For what I've seen in other petition page examples, usually the copy is very focused (not super long) because the goal is to make people sign the petition and I feel if we give them too much to read they may give up. I really think the option we had before (with horizontal menu below image) is a good option for campaigns because it forces us to be focused on a few items. Plus it has space for localization (see Here is my suggestion (mixing what you proposed with the horizontal menu from Rebecca): Opportunities pages, in my mind, should allow for more content (it is almost a mini site inside our site) so I think it makes sense for opportunity pages to be different from campaigns page. |
Ok thanks Tais! What you mocked up is what I had originally but feedback from stakeholders was that the sub nav on campaign pages with a form should look similar to sub nav on campaign pages without a form. But you think it's ok for them to be different? I'm happy to push for that, just want to make sure we are all ok with that. |
@kristinashu nice! So we are on the same page...lol. In my opinion they should be different because their purpose is different. |
@ScottDowne @alanmoo @Pomax have had questions about the different types of templates so I've used what Tais has been working on to make this overview https://redpen.io/gnce740629099e94c7 |
Adding visual IA to this since it's loosely related https://redpen.io/nwef7202a9fbd86f1a I think we can close this ticket. Only thing left to do is to add this to the user documentation in #1491 |
Issue
In meeting between Gavin, Kristina and Taís, we decided to do a flow chart (based on Gavin's suggestion) to have a visual representation of when a staff member can add their content and use an existing template (with little or zero support from prod team) and when design and engineers are needed (more complex pages).
To do:
@gvn @kristinashu please let me know if those steps make sense and feel free to edit/add things.
The text was updated successfully, but these errors were encountered: