search

ractivejs / ractivejs.github.io

https://ractive.js.org
8 stars 33 forks source link

How do we build playground? #105

Open ceremcem opened 7 years ago

ceremcem commented 7 years ago

I'm trying to fix #104 but I couldn't figure out how to re-build the playground. What are steps?

evs-chris commented 7 years ago

There are some instructions in the playground repo. From there, you just copy files into the docs asset dir. (Sorry, on my phone)

ceremcem commented 7 years ago

Hmm. Isn't there anything like mkdocs serve that builds the index.html and rest of the .js files when I changed something in a template or Javascript file?

fskreuz commented 7 years ago

At the moment, there is none. Playground is a separate project from the docs. I also hesitate mixing or putting a lot of tech on the docs. Don't want it to get really hairy with build steps, deps and stuff when most of the time I only see myself updating content.

Was thinking of having playground be a project site under the ractive.js.org org site. Github automatically maps subpaths to project pages if available (i.e. ractive.js.org/playground maps to playground.ractive.github.io). This way, docs can focus on doc, playground can focus playground, but still seamlessly map url-wise and not require copy-pasting code from one repo to the other.

I forgot why we didn't do it this way tho 🤔