3 ms·

Another feather in Tailwind's cap.

• danabramov 4y ago
  Haha :) For what it's worth, the site has been developed by different people over time, so the choice to use Tailwind was made by someone else early on. The team working on the site now doesn't feel strongly about it either way — it's sometimes annoying but overall using it feels really nice! And I'd probably say the same about other CSS solutions too. I think we'll keep it for now. Where it really shines IMO is fast prototyping. But yeah, it's cool. Edit: Ok ok tbh I do like it.
• benatkin 4y ago
  Doesn't appear to be using Docusaurus. Interesting.
  • starkparker 4y ago
    Of course they don't. Docusaurus still doesn't support MDX v2, so they'd be stuck on React 17.
    • danabramov 4y ago
      Docusaurus is a fine project, but we thought it is important to use React very directly — so that we have a good sense of what it feels like to make an app with React.
      • starkparker 4y ago
        Awesome. So now that this has rolled out, can you all help the Docusaurus team figure out how to migrate from MDX v1 to MDX v2, and why it's been so difficult? It's been six months of work and it's to a point where we're considering moving off a React-powered docs solution altogether so we can unblock the rest of our app from getting off React 17.
        • slorber 4y ago
          Sorry from the Docusaurus team. It's taking a long time because there are edge cases to figure out if we don't want the upgrade to be painful for certain sites, notably the ones using anchor links or i18n. It's not far from the end so hopefully mdx2 will be merged soon.
  • slorber 4y ago
    Docusaurus maintainer here. Wrote a Twitter thread explaining why Docusaurus is not a good fit in this case. https://twitter.com/sebastienlorber/status/1452722568390221825 https://twitter.com/sebastienlorber/status/14527225683902218... Old but still relevant.
• deleted 4y ago
  [deleted]