[TB] Do Design Thinking around a new landing page

[aaronreed708]

Problem/Concern

This issue is associated with #678. We need to do some Design Thinking about what type of user experience do we want to give to people discovering Theme Builder for the first time as well as potential new community members/contributors in order to attract new eyes and new talent to the project. How do we improve a person's ability to search for/find Theme Builder and to enhance their interest once they come this new landing page? Will a new domain name help?

Proposed Solution

@lwnoble and @PaulaPaul to be involved at a minimum. The community should be invited as optional.

[evangk6]

Update from Today's Meeting: Lise, Paula and Cody are getting together and will share what they discussed with Aaron.

[aaronreed708]

Depends on roadmap completion (#762) @lwnoble wants to create the website theme using Theme Builder, working on that now

[Chessel]

@aaronreed708, @lwnoble and I have collaborated on a few design thinking sessions to understand what would be the most important information that our main potential visitors (developers and designers) might need from the site.

These are our final thoughts. Feel free to chime in if we missed anything.

Leading with the information, I propose a site that "shows not tell" by taking the viewer to the journey of an out of the box site that uses the Accessibility Theme Builder. We start with our wide browser view in light more and we highlight some of the accessibility features. As the viewer scrolls, the same site switches effortlessly from light mode to dar mode (magic). We Again highlight some of the accessibility features. As the viewer keeps scrolling the site continues its responsiveness journey from browser to table to mobile (Android and iPhone) morphing effortlessly and beautifully while always keeping accessibility at front and center.

At the end we think a section that contrast a site built with and without Theme Builder could make a strong argument pro Theme Builder. During this section we can list some of the main accessibility features.

Then we are suggesting a section that arguments how we are helping the design between designer and developers to become smoother. And the implementations to become less painful and with greater fidelity to the deigns.

Lastly, a section that lists all the new features we are working on and a link to the GitHub repo as an open invitation for them to get interested in becoming contributors. This followed by a list of the upcoming events and links to the event site.

Suggestions are welcome!

This is a very rough sketch

Next steps:

@lwnoble will start a list of the most important components to show in action. and I will select possible color palettes and typographies to use on the site.