Website redesign, branding, and long term structure #978
Comments
thescientist13
added
website
thescientist13
added
the
RFC
thescientist13
moved this to 📋 Backlog
in [Greenwood] Phase 9 - Standards and Conventions
|
Should probably consider E2E testing (finally) when considering going out with our "final" docs. - #560 |
|
After reviewing the initial design for the #1094 , some good discussions around rethinking parts of the website came up
One good exercise we considered was doing a live mockup with all the elements we want, and just drag and drop them in real time. We can use it as forcing function to really understand what we care about most in terms of showing off and what to prioritize. All these items are important, unfortunately they can't all be above the fold, so we'll have to pick something, and ideally that also works well on mobile to make sure we retain the "above the fold" experience. |
thescientist13
moved this to 📋 Backlog
in [Greenwood] Phase 9 - Standards and Conventions
thescientist13
moved this from 📋 Backlog
to 🔖 Ready
in [Greenwood] Phase 9 - Standards and Conventions
thescientist13
moved this from 🔖 Ready
to 🏗 In progress
in [Greenwood] Phase 9 - Standards and Conventions
|
For anyone following along, please feel free to get involved in some discussions i've started for the new website. ✌️ |
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in [Greenwood] Phase 9 - Standards and Conventions
thescientist13
moved this from ✅ Done
to 👀 In review
in [Greenwood] Phase 9 - Standards and Conventions
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in [Greenwood] Phase 9 - Standards and Conventions
Discussed in #503
Originally posted by thescientist13 April 3, 2021
As we plan for the next set of features to get Greenwood to a 1.0 release it would be to start discussing some related issues around structure, navigation, discoverability, and design.
Some previous related issues on this topic were
Some things we would like to consider are:
Details
These are the things we should do as part of the actual cutover
Locationredirects for new website - content/issue 33 guides pages www.greenwoodjs.dev#94 + content/issue 31 Docs pages www.greenwoodjs.dev#117/guides/cloudflare-workers-deployment/->/guides/hosting/cloudflare//guides/firebase/-> 404/guides/github-pages/->/guides/hosting/github//guides/netlify-deploy/(netlify) ->/guides/hosting/netlify//guides/netlify-cms/(netlify???) -> 404/guides/now/(vercel) ->/guides/hosting/vercel//guides/s3-cloudfront/(AWS) ->/guides/hosting/aws//guides/theme-packs/->/guides/tutorials/theme-packs//getting-started/->/guides/getting-started//about/*->/docs/introduction/about//plugins/->/docs/references/plugins-api//plugins/adapter/->/docs/reference/plugins-api/#adapter/plugins/context/->/docs/reference/plugins-api/#context/plugins/copy/->/docs/reference/plugins-api/#copy/plugins/renderer/->/docs/reference/plugins-api/#renderer/plugins/resource/->/docs/reference/plugins-api/#resource/plugins/rollup/->/docs/reference/plugins-api/#rollup/plugins/server/->/docs/reference/plugins-api/#server/plugins/source/->/docs/reference/plugins-api/#source/plugins/custom-plugins/->/docs/plugins//docs/component-model/->/docs/introduction/web-standards/#web-components/docs/configuration/->/docs/reference/configuration//docs/front-matter/->/docs/resources/markdown//docs/markdown/->/docs/resources/markdown/#frontmatter/docs/scripts/->/docs/resources/scripts//docs/css-and-images/->/docs/resources/styles//docs/layouts/->/docs/pages/layouts//docs/server-rendering/->/docs/pages/server-rendering//docs/api-routes/->/docs/pages/api-routes//docs/menus/->/docs/content-as-data/collections//docs/data/->/docs/content-as-data/These are the things to track after the cutover
peerDependencieserror for npm (by bumping peer deps in our packages on each release?)The text was updated successfully, but these errors were encountered: