Sam Richard
@Snugug
BBQ lead, ChromeOS DevRel. Mostly food, sometimes design and development, especially for the web. 7008px tall. He/him.
An archive of my Twitter timeline up until I moved to Mastodon. You can find me there at @[email protected]
@eaton Following up from seeing you the other week! We’re using Paragraphs (and paragraphs inside paragraphs) for more complex content modeling (think an attribute that’s a collection of attributes).
@eaton All rolling up to a Content Type. So, ex. A Tutorial is the content type, tutorials have tasks, to P for that w/title, optional intro, and inside that task is a P for steps, with title and instructions…
@eaton …Tasks are repeatable, steps are too, each minimum one, allowing us to build effectively reusable content sub-models. Getting from APIs is a bit annoying as they’re entities that need to be retrieved, but we can deal w/that w/JSON:API and GraphQL OK