Currently we’re in the process of building the the GAIA2.0 components and it’s documentation. As this is an ongoing process, we want to identify the right way for us to build a public facing website that can meet the following requirements:

<aside> ⏳ Can be built in 2 weeks

</aside>

<aside> 🚧 Easy to iterate and make changes to the documentation

</aside>

<aside> 🛠 Can embed Storybooks and include code snippets

</aside>

<aside> 🔥 Can add Stryber branding

</aside>

While a Webflow template meets these requirements, it does not offer the ease of collaboration that is offered by a tool like Google Docs. Additionally, it has tons of features that are just overkill for us at this stage that adds unnecessary bloat to the interface that might detract us from focusing on perfecting our documentation structure, layout, and language.

Secret sauce

The Notion Alternative (+ what I think is ideal)

I propose using Notion to build the initial GAIA Website. By combining it with Super or Fruition, we will be able to inject custom code and also use a custom domain name for the site to ensure that we have the needed level of control when it comes to branding.

Setup and maintenance can be done by basically anyone at Stryber and doesn’t need a dedicated resource. If needed, the design team will be able to take the lead thus ensuring end-to-end control from research to final documentation.

Sample structures

[Default Notion Template]

Design System Documentation [Detailed Template]

What our CL can look like (without any custom code)

Working view where everyone has a clear view of what needs to be prioritized.

Working view where everyone has a clear view of what needs to be prioritized.

Storybook embeds ensure that our documentation is always up-to-date with the latest component builds.

Storybook embeds ensure that our documentation is always up-to-date with the latest component builds.