Learn by experimenting
Tuklas helps students, self-taught beginners, and junior frontend developers connect code with its behavior. Lessons explain concepts with interactive examples. Practice checkpoints ask you to build or repair something using the concepts that came before them. Optional challenges let you predict and explain JavaScript behavior.
Discover how code works. That is the whole invitation: make a small change, observe it, and understand why. You do not need an account or a perfect streak.
Who maintains Tuklas
Tuklas is created and maintained by Kyla Marie Angeles. For questions, corrections, or problems with a lesson or practice, use the contact page. Include the page URL and what you expected so the issue can be investigated.
What you can explore
The curriculum covers HTML, CSS fundamentals, Flexbox, CSS Grid, and JavaScript foundations. It includes 56 lessons and guides, 12 practices, and 20 prediction challenges. Follow HTML, CSS, Flexbox, CSS Grid, JavaScript, and Local projects in order, or revisit a topic from its course outline. Progress is local to your browser.
What learning here looks like
Start with your first HTML page: change the example and compare the browser tab with the page heading. After learning semantic HTML, structure a study plan in the editor and use the checks to find missing pieces.
Later, the counter practice separates a working behavior reference from your code. You can compare repeated clicks and reset behavior, try progressive hints, and inspect feedback before reading the solution. These activities aim to make the reason for a result visible.
What progress means
Mark a lesson complete after trying its task. Coding practices record completion when their checks pass; downloadable projects use a self-review checklist. A passed check tests the stated requirements, not every possible implementation. There are no certificates, accounts, or promises of job readiness.
How examples are checked
Automated checks validate links, counts, and answer structure. The JavaScript prediction examples and follow-up experiments are executed in isolated tests to compare their output with the explanations. The JavaScript practices run your JavaScript locally in an isolated worker with a limited preview interface. Layout behavior is checked against browser rendering and primary reference documentation.
Automated checks do not amount to independent human editorial review. If an explanation seems incomplete or a result looks wrong, note the page URL and what you observed. See the contact page for availability.
Updated October 22, 2026