Content Model - Draft 01
Overview
In the following diagram we can see the current implemented content models for Clubhouses (Rapha Clubhouses / Pop Ups / Partner Cafes) and any referenced content models. It includes both web and mobile models and a proposed omni channel content model. Remember in tranditional CMS(s) we design content around page templates and in headless CMS(s) like Contentful we design collections of related content based around related themes called content models. The reason for this abstraction is that it allows content owners to distribute and reuse these blocks of content over a variety of different platforms without worrying about breaking templates.
Considerations
Based on the rcc locations page we have the opportunity to link the following attributes at either city level or clubhouse level or a mixture of both.
- Ride Leaders
- Local Benefits
- Members Locally
- Bike Hire
- Chapter
Its important to consider how and where we would use each individual attributes in the future when making the decision.
When configuring clubhouses and partner cafes we are able to customize the editorial experience with entry extensions. This would mean that we are able to have conditional fields such as rccChapterLogo, rccChapterDescription etc when creating Clubhouses and not Parter Cafes as those attributes are unnessasry.
Questions
- How do we currently populate the members locally?
- How does the googleMapsPlaceID differ in use from the location?
- What do we see happening with Events in the short/mid/long term? They are currently hacked into the mobile application via lat/long co-ordinates rather than a reference/relationship to regoin, city or clubhouse.
Opportunities
- City specific email campaigns highlighting ride leaders, local benefits, chapters, popups etc.
- Region specifc emails highlighting the same as city specific.
- Opportunity to link seasonal products to regions and/or cities.
Resources
Customize your whole editorial experience with entry extensions