Each lesson is made up of steps, and each step is made up of checkpoints. A checkpoint is one or more jest tests that run in the browser against the user's code.
I look forward to any and all of this communities feedback!
I recommend dis-requiring sign in/log in, so a user can experience some of the tutorials. It asked me to log in, then I just closed out of it.
OP: reading your comments make me want to check it out more.
Also I'm not sure what codeacademy-style lessons means. Like, interactive thingy?
Maybe you could let the first level of each lesson wide open. I don't know
I'll definitely work on lowering the barrier to entry, currently sign up is required to save any edits you make to any lessons you create/take. Clearly this isn't ideal for playing around though.
(Thanks for the feedback!)
But for the platform itself-- pretty cool that you have file separations and visual renderings, going beyond simple code execution. I like it. I tried build something similar on algodaily.com a while back, but found that my audience wasn't that interested in creating tutorials.
1) I wasn't immediately sure there were multiple steps at first.
2) Execution time is a bit slow.
3) I was monitoring the network calls and saw no requests when code executed -- are you doing this in the client? Just a heads up that there's some security vulnerabilities to be aware of.
4) The UI could use some polishing. Maybe look for a color palette that blends colors together better.
Congrats on shipping!
1) I'll try to make that more obvious
2) Working on it :)
3) Code and dependencies are bundled in the browser
4) Check out settings/themes!
Looks cool, but would like to be able to check out an existing demo lesson before signing up.
If the former, then how about using Codeamigo to highlight various parts of Codeamigo source? Two birds with one stone.
It occurred to me that you have a working app, presumably written in React. (Actually Tic Tac Toe lesson is not working for me right now, but that is beside the point).
If some of the Codeamigo code were presented as a lesson, it could serve two purposes. To help me learn React and to see in context a working app where the lesson's code has been implemented. It needn't be all of it, just those points you feel might be most instructive. Presumably you wouldn't do that if you are planning to keep the app closed source. Hence my question.