2nd iteration of 'Model' & 'Notebook' as Main Nav items
For a first iteration we updated the Main Nav to contain both 'Model' and 'Notebook' to improve the at-a-glance communication that Meltano will empower users with modeling and notebooking functionality (hence "Help shape this feature..." in the screenshot below). Each nav item currently just links to our Meltano issue tracker pre-filtered with 'model' and 'notebook' respectively. Maybe not ideal, but a step forward.
- Do we want to have dedicated landing pages for each nav item pre-v1?
- Assuming yes (that's why I have this issue in this milestone), please add anything specific you think they should communicate. @sytses I intentionally didn't house our Analyze CTAs in this new top-level "Model" as this feels a more "big picture" opportunity vs. solely referencing our Analyze CTAs (Meltano Model as config-files-that-enable-click-to-code-sql-generation).
Technically speaking Meltano's modeling occurs both in transforms (via dbt) and pre-analyze (via Meltano Model). So currently, modeling is more of an embedded quality vs. a theme-of-tasks container.
My current gut for this second iteration is: