What theme are you using with Docusaurus? The classic theme (default). I am curious what you are seeing that is Facebook-specific that you are cleaning up. Would love to hear the feedback. Thanks!

I remember removing the /blog part was tedious, because there were links in a lot of places. And once I removed it, it didn't build anymore.

I'll give it another shot and see if I have the same feeling, if so I'll write a feedback

For sure, our init template contains a blog.

You can definitively remove it ("blog: false" in preset config).

If you remove it, you also need to remove the links to the blog, because it would lead to 404 errors.

Docusaurus is fail-fast by default and try to prevent you to deploy broken sites, I understand how it can be annoying in some cases but consider it an useful feature

I didn't know about the config parameter, is it recent? I don't remember finding it when I tried to remove it.

not new, we have many sites that are just using the blog, or just using the docs.

Example of just using the blog: https://blog.johnnyreilly.com/ https://blog.developersam.com/

Have you seen the community plugins - https://docusaurus.io/community/resources/#community-plugins. There are some search options there that may be of use to you.

Thank you! And the FDISK story is absolutely true. I can still remember my father's surprise at how reckless I was with his computer.

Default is definitely different than mandated. Facebook provides engineers a ton of freedom for their development environment.

There are many at FB where we would have to pry vim or emacs out of their hands, and, even then, we would not be successful. :-)

Thanks Jim!

I just updated the text on the features page to straight #000000. I hope that ends up being more readable for you.

Wow that is so much better! Thanks a lot.

Btw, the color on other pages is still #6c6c6d. Given how readable features page is, it'd be nice to see #000 on others as well :)

I doubt it's the color so much as it's "font-weight: 300;"... that's pretty thin. Removing that makes it a lot more pleasing to look at, in my opinion.

Thanks @Alupis. Got a tip for that internally as well. I just pushed the fix up with 400 instead of 300.

Awesome! It seems such thin and/or light fonts are okay to read on retina displays (which is where I assume they were tested) but not on other displays. I happened to be reading on a non-retina display.

Gatsby is a great tool for documentation as well. In fact, some of our open source projects use Gatsby (e.g., reactjs.org). We feel that Docusaurus serves a bit of a different audience. Docusaurus is focused on the fastest way to document a project. We wanted to provide a really quick way to get a site running with certain core functionality that folks might find useful. We can see Gatsby and Docusaurus possibly collaborating on some features. In fact, we could see integrating/adopting parts of Gatsby into Docusaurus under the hood. That is something that is worth exploring moving forward.

Hi @eitland! We wanted to start off relatively simply for the launch. Support for markdown and static assets, including images, css, raw HTML, etc.

However, we are definitely looking at supporting other formats moving forward. We just want to make sure we do not complicate Docusaurus too much by doing so. Trying to find a good balance.

Hi and thanks for answering!

I already bookmarked it the other day and anyway I'm happy for everybody who contributes to open source even if I choose to use another problem.

Thanks @chenglou for being one of our earliest adopters. You and your team really helped improve the quality of Docusaurus for launch.

Thanks @EricVicenti! And congrats to you as well, especially since you were the one who brought this idea to us back in the summer. So happy you did. :)