Something's wrong in the preview (as I said, commit is pretty old) will investigate

Would be really cool if Docusaurus worked like a GatsbyJS plugin. Keep the SSR, single build step, but ability to hydrate the DOM for the playground.

@azz Yeah that's the gist of what I suggested in facebook/docusaurus#292

Can you deploy this somewhere, so people could test it easier?

@lipis https://deploy-preview-3573--prettier.netlify.com/playground/

Something's wrong in the preview (as I said, commit is pretty old) will investigate

From @duailibe above.

That's #3581, should be fine now.

I merged the master branch, let's see if that fixes it

[off-topic]: Could whoever has access to Netlify make the deploy logs publicly visible so contributors can see what wen wrong if the build fails?

Sorry guys, I forgot this is based on #3433 and I removed the reference to it before creating the PR

Let's see if we can land that soon... otherwise, I'll reference by the commit hash and continue work on this

Yay it's finally working :)

👍, but 3️⃣❓:

1. What happened to the “Debug” section?
2. Would it be possible to add a “Reset to default” button that resets all of the buttons to their defaults?
3. Would it be possible to make the example code a placeholder so you don’t have to delete it before putting your own code in? (or would that be a bad idea?)

1. Not implemented yet
2. Yeah sure.. as a P/React component it's easy to do that =)
3. I don't know.. we can choose to:
   • always use a placeholder
   • save last code used (+ options)
   • always empty

Those are great but are unrelated to this PR (2 & 3).. I mostly wanted to gather feedback if we should continue with no build steps (just serving from static/) or if we should put a separate build step for the playground

I think we can add separate issues for those subjects :)

@azz @ikatyang @vjeux do you guys think I should go forward to get this landed "as is", wait for docusaurus to support this or implement a separate build step? Or give up on this at all

I don't personally care either way as long as we have a working playground at the end :)

I just reviewed the code, it does look a lot better than what we have now. Do you want to bring it back up to date and land it as-is?

Possibly related, I was just reading the code of https://github.com/sandhose/prettier-animated-logo which is also written with Preact, but is for the main page. Would be nice to get full p?react support with Docusaurus to make integrating that easier. Currently it is rendered to static markup build-time.

Placeholders were nice to have (or any other way to have have the sample code).. will they land in another PR if this is about to get merged or we dropping them?

I'm still gonna add them in this PR.. only the range stuff I'm gonna do in another PR

I ended up doing both the examples and the range feature in this PR =)

Gonna merge when lint/tests pass and I do some smoke testing with the deploy preview

I hate when I press merge instead of the squash button 😔

@duailibe Should we disable the other merge types (admins can do it in settings), or are there times we use them in this repo?

@j-f1 I think we can (TBH I don't think there's much use in doing it other way anyway) cc @vjeux @azz @suchipi

Sgtm

I disabled the other two options (if for whatever reason, we need any other option, we can easily enable it before doing it)