OnlineCompiler.io Code Runner: Online Compiler and Runnable Code Blocks
OnlineCompiler.io Code Runner adds an online compiler to WordPress. Put a Code runner block in a post or page (or the [onlinecompiler] shortcode in the classic editor), write the code, and readers get a code editor with a Run button right in the page. They can change the code and its input and run i
OnlineCompiler.io Code Runner adds an online compiler to WordPress. Put a Code runner block in a post or page (or the [onlinecompiler] shortcode in the classic editor), write the code, and readers get a code editor with a Run button right in the page. They can change the code and its input and run it again, with no account and nothing to install. Syntax highlighters only show code; this one runs it.
The code runs on OnlineCompiler.io , a code execution service, in an isolated sandbox with no network access. Nothing runs on your WordPress server.
Who it’s for
- Programming tutorials and blogs: every example in a post becomes one readers can try and change.
- Online courses and coding lessons: students practise in the lesson itself instead of installing a compiler.
- Teachers and schools: exercises with tests that students judge their code against.
- Documentation: runnable examples for an API, library or language.
Features
- 46 languages , with the code highlighted as readers type.
- Runs in a sandbox, not on your server: a fresh sandbox for each run, no network access, thrown away afterwards.
- Standard input: give the program its input; readers can change it.
- Exercises with tests: show a problem stored in your OnlineCompiler.io account, with its statement and starter code, and readers judge their code against its sample tests.
- Read-only examples, themes and heights: light, dark or the reader’s system setting; the editor fits the code or takes the height you set.
- Buttons and messages in English, Portuguese or Spanish.
- Search-friendly: the code is in the page as text before the editor loads, so search engines index it.
- Light on your site: the widget script loads only on pages with a Code runner, deferred, and each runner connects only when it scrolls into view (one showing a stored problem connects when the page loads).
