[ Plan] Proposed new IA #27
Conversation
✅ Deploy Preview for web-components-cg ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
| - /build-a-web-component | ||
| - /:step-number | ||
| - web-components-explained | ||
| - /:article-slug |
There was a problem hiding this comment.
Feel like we got close to agreeing that a minimum viable content might focus on just these sections or a subset of the content the might belong in them, and we see that in #26, should we include a MVC IA here?
There was a problem hiding this comment.
personally, I would consider this IA to be mostly MVC IA, because there's really not much to it. Depending of course on how the conversation goes about the component catalog, and CMS-based site stuff. If we become more tech bloggy in our presentation, I'd think that a collection of some articles would also become MVC, but thats already kind accounted for here in this IA, would just be a matter of how many blogroll articles we start with, etc.
There was a problem hiding this comment.
Awesome, thanks for putting this all together @michaelwarren1106 🙏
Left a couple of thoughts of my own for the group review and chime in on as well.
| - popular framework features that can be implemented with Web Components | ||
| - SSR, SSG, etc explain only that there are ways to do it, not the "how, with code samples" | ||
| - **Educate** | ||
| - Provide basic, generic MDN-like documentation for WC topics |
There was a problem hiding this comment.
Provide basic, generic MDN-like documentation for WC topics
As it relates to "MDN-like" docs, it might be good to tease this out because I think it will be important for all contributors to understand how to differentiate any of our technical content from the MDN docs. Perhaps the distinction could come through things like:
- our tone / approach (less technical / reference / dry)
- more guide / outcome driven (step 1, then step 2, ???, profit)
- other?
| Full with page descriptions [below](#full-ia) | ||
|
|
||
| - Root / | ||
| - /our-work |
There was a problem hiding this comment.
Unless i am interpreting it incorrectly, this seems like it would come out to be 10 top level navigation items?
- / (Home)
- /our-work
- /build-a-web-component
- web-components-explained
- /featured-components
- /submit-component
- /articles
- /become-an-author
- /highlight-article
- /about
Perhaps something a little more compact could be a little less daunting for responsive design maintenance, and for user navigation?
- / (Home) - featured items would not be a route, just a tile / section on the home page
- featured component(s)
- highlighted article(s)
- /catalog
- /browse
- /submit-component
- /articles
- /web-components-explained
- /build-a-web-component
- /about
- /our-work
- /become-an-author
There was a problem hiding this comment.
i didnt really touch on what would land in the nav vs page that would be accessible by other means. We could definitely divide up the links into "main nav" and "utility nav" though so that we only have a few items in the main nav.
imo stuff like "submit a component" and "become an author" totally dont belong in the main nav. I was just doing a sitemap style organization. i definitely didnt touch on navigation items, but thats something i can totally add!
There was a problem hiding this comment.
Ah, then indeed I may be a little ahead of the curve. 😅
Tear it up!
~MW