docs: 2021 recap blog post #6334
Conversation
Josh-Cena
added
the
pr: documentation
|
✔️ [V2] 🔨 Explore the source changes: dd2e433 🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/61eeb0f2ab616600072cdb56 😎 Browse the preview: https://deploy-preview-6334--docusaurus-2.netlify.app |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-6334--docusaurus-2.netlify.app/ |
|
Size Change: +769 B (0%) Total Size: 710 kB
ℹ️ View Unchanged
|
Josh-Cena
added
the
status: awaiting review
There was a problem hiding this comment.
Looks really great! This is IMO the best-written recap so far, love the tone + content and really excited to see that the community and project has matured so much.
I made some tiny changes. Will leave it to @slorber for the final stamp.
Thanks for writing this!!!
| - **Redesigned mobile navigation**: mobile users now enjoy all navigation features as on desktop | ||
| - **UI improvements**: more accessible quotes, better admonitions, back-to-top button... | ||
| - **Blog multi-authors**: credit all the amazing contributors that collaborated on one blog post! | ||
| - **More blog features**: archive page, structured data for SEO, full post content in feeds – empowering you to ship a fully-featured blog in no time |
There was a problem hiding this comment.
@yangshun FYI, although I don't have strong opinions on this, em-dashes are usually used without spaces around them. The AP style guide is the only guide I know that recommends spaces around them. I've just changed to using en-dashes instead because " – " === "—", if you think spaces improve legibility.
There was a problem hiding this comment.
Ah I see. We've been putting spaces around our dashes (for e.g. a few instances on this page https://docusaurus.io/docs). I think legibility is most important, so as long as there are spaces it's good 😄
There was a problem hiding this comment.
Yes, I think legibility is a legitimate point :D
There was a problem hiding this comment.
That looks great!
Some extra suggestions:
- write something like "users said great things about Docusaurus in 2021" + link to Twitter testimonials?
- more stats and curves?
https://risingstars.js.org/2021/en#section-ssg
Should we wait for 30k stars to publish? We are so close
|
I checked that star history curve. We aren't the most impressive so I didn't add it😄 About the Twitter collection, I forgot where that is... |
@yangshun pointed out that we are growing faster than many alternatives, still not bad
https://twitter.com/sebastienlorber/timelines/1392048416872706049 |
| title: Docusaurus 2021 Recap | ||
| authors: [Josh-Cena] | ||
| tags: [recap] | ||
| image: ./img/thumbnail.png |
There was a problem hiding this comment.
Some suggestion:
Make the text more readable
Add the 30k milestone on the card?
| We released 18 versions, going from `2.0.0-alpha.71` to `2.0.0-beta.14`. That's one release every 20 days! | ||
|
|
||
| ### GitHub | ||
|
|
||
| - **Stars**: 20,460 → 29,679 (+45.1% y/y). We are on our way to 30k stars! | ||
| - **Stars**: 20,460 → 29,679 (+45.1% y/y). And, just before this blog post was finally posted |
Josh-Cena
removed
the
status: awaiting review
|
🎉 |
Motivation
2021 is behind us. Let's recap :D
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
https://deploy-preview-6334--docusaurus-2.netlify.app/blog/2022/01/24/docusaurus-2021-recap/
TODO
Media? Other sections I should add?