JDoodle for writers

A code block in a tutorial is a picture of a program. The reader has to trust it, copy it somewhere, and install something before they find out whether it does what you said.

An embed is the same code, running in your page, that they can change and run themselves.

• One program in a post

  Drop an editor into an article where the code block would have gone. Readers run it, break it, and see what happens.

  Good for a blog post, a tutorial, or documentation with examples.

• A course made of them

  Use as many as the material needs, each starting from the code that step is about.

  Good for a course, a workshop, or a book with exercises.

What you can decide

• The language and version. Fixed to the one you are writing about, or a list your reader can switch between.
• What it starts with. The code already in the editor when the page loads.
• What is on screen. An editor, a run button, output, input. You compose the embed from those parts rather than taking a fixed layout.
• Whether readers can edit. Run-only, or a scratchpad they can rewrite.
• Whether your page can drive it. Your own scripts can set the code, run it, and be told what came back.

Where to start

Make one embed and put it in a page. Everything else, what readers can do, and whether your own scripts drive it, is worth deciding once you have seen one working.