Spike a better solution for handling data in Nuxt pages
Goal
We'd like to manage the content in the Nuxt site in a more consistent, extensible, flexible way.
The pages this matters most for are in the upcoming work. @mpreuss22
gave us the rundown of our current commitment in Slack:
Goal is to deliver 10 amazing, newly designed pages with the rest of the site being on brand, live by April 27th:
Tier 01 (Doing 2nd): 3-4 page templates - Complete new vision, design, and content
- Homepage
- Pricing Page
- Solutions / Features Pages
- Install (stretch)
Tier 02 (Doing 3rd): 6-7 page templates - Well considered new design, significant new content, limited new branded/image/motion assets
- Category Leadership (Currently called Topics)
- Demo
- Enterprise
- SMB
- DevOps Lifecycle Pages
- Getting Started
- Contact Sales
Tier 03 (Doing 1st): - New coat of paint: updated fonts, colours, logos Everything else: https://docs.google.com/spreadsheets/d/1ualGLPCyFjEpiskrfAe2ftqoTAw8t56lO1LMzMT7Ojo/edit
So to start, I'm going to look at the Tier 01 pages and do the following:
- See which, if any, we have represented in
content
- Take a look at how their page level
.vue
files consume that data - Identify common data structures, identify oddities and outliers (stuff that needs special handling)
- Write up a spec for how we should structure data to be consumed by pages
- Pitch that spec to @ndubord as a first iteration
Once I do that, I'll write up an interface and try it out on the Homepage. I'll put together more specific issues for each page as I go.
I'm going to timebox this to about a day-and-a-half, and see how far I can get on it. Once I know more, I'll add additional points, add additional issues, etc.