You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd signed myself up previously to rework the site, and I think my thoughts have coalesced that I am starting to put a real plan together.
Information Architecture
First up is the information architecture. This is the structure and organization of information presented on the site. The goal of the IA is to be clear and for the right information to be easy to discover for people who want to find it. I am imagining the following structure for the top-level navigation and pages:
Overview (the home page)
Specification (explain the draft status of the spec, link to it, and direct to the "Get Involved" page)
Tools (links to current tools and, again, point to get involved if you want to integrate it in more places or build new tools around it)
Blog (place to share informational and time-relevant material)
Get Involved (call to action page explaining the Slack and meetings)
In the future I'd like to create a Use Cases page as well which provides more concrete examples of the value gained from GitBOM.
Content Writing
The second is actually writing the content. I think right now the content suffers from a couple of keys issues:
Explaining what GitBOM isn't rather than what it is.
Overuse of jargon and (relatedly) too many links to the glossary explaining that jargon.
I'll likely start with the Overview page and work outward from there. It's the most important.
Design
The current design is fine, but I think it could be better! This is my personal favorite part of web development but I am going to hold off starting on it until the content organization is right.
I'll start working on the above materials, and I can keep everyone updated during meetings with how it's going.
The text was updated successfully, but these errors were encountered:
Hi everyone!
I'd signed myself up previously to rework the site, and I think my thoughts have coalesced that I am starting to put a real plan together.
Information Architecture
First up is the information architecture. This is the structure and organization of information presented on the site. The goal of the IA is to be clear and for the right information to be easy to discover for people who want to find it. I am imagining the following structure for the top-level navigation and pages:
In the future I'd like to create a Use Cases page as well which provides more concrete examples of the value gained from GitBOM.
Content Writing
The second is actually writing the content. I think right now the content suffers from a couple of keys issues:
I'll likely start with the Overview page and work outward from there. It's the most important.
Design
The current design is fine, but I think it could be better! This is my personal favorite part of web development but I am going to hold off starting on it until the content organization is right.
I'll start working on the above materials, and I can keep everyone updated during meetings with how it's going.
The text was updated successfully, but these errors were encountered: