Website Update: navigational framework, landing page update #1328
Conversation
…variants) to docsite header bar.
…g code to fix contrast issues. Change github icon to inline SVG. Add examples of Important and Caution blocks in markdown. Change link colors to match RNW and RN sites.
…einstate homepage feature area, which now appears to be a little broken.
…e code formatting in markdown, color refining/sharing, footer logo size/opacity.
… the box, local search uses Algolia's color scheme and doesn't pick up Docusaurus colors. I have it polished and working, though. Going to try using the DocSearch-based service instead which is supposed to integrate w/Docusaurus CSS vars.
…tter tags and category files, and instead be get name from markdown title and order from sidebar.js.
…ons in the top nav bar.
… sizes. Update MS open source logo with light and dark mode variants in Segoe UI font.
…ame out the remaining pages for V1 of the site and mark with warnings at the top of each page.
|
Part of #1255 |
There was a problem hiding this comment.
Overall: great stuff, thanks for working on this! I've left a few comments, mostly just to have some conversations around certain aspects. I don't feel strongly about any of those, and most can be addressed in follow up PRs anyway.
About this:
This PR removes the blog, since there are no posts to share, and my intent is to use a different platform with social features such as like, share, and comment.
Let's have a separate chat about this, I think having a local blog is the option that will most resonate with the developer community and would be in-line with other projects in this space.
Sidenote:
Guides should be step-by-step instructions. Devs use them to complete a task. Doing, not learning.
YES. I like this.
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
Description
This PR is another update to the rnx-kit documentation web site (which is still a work-in-progress).
It creates the navigational framework of the site:
This PR removes the blog, since there are no posts to share, and my intent is to use a different platform with social features such as like, share, and comment. We can easily reinstate the blog later, if needed, with a few lines of docusaurus config.
This PR also updates the messaging content and styling used on the landing page. I used a bolder font for the title. I chose a shorter, more impactful tagline. I updated the 3 breakout blurbs under the title. And I made the page responsive to different device sizes -- whether you are growing/shrinking your browser, or looking at it on a small-screen device.
I also updated the footer to change during light and dark mode, and I used a better-looking the Microsoft OSS logo image.
Test plan
None.