-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switching site to Docusaurus #17
Comments
View your post at https://sgrove.essay.dev/post/17/switching-site-to-docusaurus |
That's a fantastic move, congrats! |
What's next for this site? Maybe a move to essay.dev? |
I could get behind that, for sure! |
This sounds like a great idea! |
I'm using essay.dev, loving it! |
Looks like a great pie! |
Looks like there's a mass migration... |
Looking good! |
Sharp! |
I agree, slick! |
When's this happening? |
Are we doing this, then? |
Ding ding ding! |
1 similar comment
Ding ding ding! |
Looks great! |
Love the idea! |
Is the data still accessible via the GitHub API? Do we have full control over the content? |
Hello world! |
I've switched my personal site (riseos.com)
over to Docusaurus from a Mirage unikernel
for a few reasons. First, I was putting off writing blog posts because
of the amount of yak shaving I was doing. Second, the dependency
situation never really got to the point I felt it was worth the
effort. And third, some projects I've been working on have pushed me
to get a lot more familiar with frontend topics, especially
static-sites that are rendered with React.
I've deployed a few sites with Gatsby,
and was looking for something significantly simpler and more
reliable. At the recommendation of the
ReasonML team, I gave docusaurus a shot
on another site, and it worked out nicely. I appreciate that it's
limited enough to encourage you not to yak-shave too much (which is
good from time to time, but not for my personal site at this time).
Anyway, certainly recommend giving
Docusaurus +
netlify a shot, worked like a charm for
me.
The text was updated successfully, but these errors were encountered: