Skip to content
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

Open
sgrove opened this issue Nov 18, 2020 · 19 comments
Open

Switching site to Docusaurus #17

sgrove opened this issue Nov 18, 2020 · 19 comments
Assignees
Labels
Publish Add this label to an issue to publish it on the blog

Comments

@sgrove
Copy link

sgrove commented Nov 18, 2020

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.

@sgrove sgrove added the Publish Add this label to an issue to publish it on the blog label Nov 18, 2020
@sgrove sgrove self-assigned this Nov 18, 2020
@oneblog-bot
Copy link

@sgrove
Copy link
Author

sgrove commented Nov 19, 2020

That's a fantastic move, congrats!

@sgrove
Copy link
Author

sgrove commented Nov 19, 2020

What's next for this site? Maybe a move to essay.dev?

@sgrove
Copy link
Author

sgrove commented Nov 19, 2020

I could get behind that, for sure!

@sgrove
Copy link
Author

sgrove commented Nov 19, 2020

This sounds like a great idea!

@sgrove
Copy link
Author

sgrove commented Nov 19, 2020

I'm using essay.dev, loving it!

@sgrove
Copy link
Author

sgrove commented Nov 19, 2020

Looks like a great pie!

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Looks like there's a mass migration...

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Looking good!

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Sharp!

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

I agree, slick!

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

When's this happening?

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Are we doing this, then?

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Ding ding ding!

1 similar comment
@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Ding ding ding!

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Looks great!

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Love the idea!

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Is the data still accessible via the GitHub API? Do we have full control over the content?

@sgrove
Copy link
Author

sgrove commented Nov 25, 2020

Hello world!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Publish Add this label to an issue to publish it on the blog
Projects
None yet
Development

No branches or pull requests

2 participants