wokwi-docs VS wokwi-server

The website looks lovely with the usual wonky logo, subtitle in a sans serif font, links to stuff and silky smooth scrolling over stuff. Cracking images that must have taken a while to create for buttons and a Google-esque search errr email address harvester close to the top.

So why ... oh ... https://docs.wokwi.com/?utm_source=wokwi which is squirreled away off to the top right.

Your site is absolutely cool as fuck but a bit crap for a first time user. How on earth do I get to work out what is what? You might put an overlay in a tasteful shade of a tasteful colour for a first time user with links and text boxes with information, then set a cookie to avoid it in future. IDK.

I'm not joking when I say cool as fuck. It really is lovely but please get the value prop over to a 52 y/o Brit (wot owns an IT company) and other strange minorities!

The idea of those image tags is to use them as devcontainers with Gitpod, Github Codespaces, or VS Code. The recommended way is to use one of our templates, both templates include a prompt asking for devcontainer support, when devcontainers are enabled, projects include web-flash, wokwi-server, and other useful crates. Also, some bash scripts and buttons in the VsCode UI are added to facilitate building, flashing, and simulating with Wokwi. Once you generate a template project with devcontainer support, a Readme will be generated with further instructions on how to use it, but here is the template so you can have a look at them!

When first stumbling across this, it seemed to be only arduino (even on esp stuff), but it also supports esp-idf so you can test esp native stuff too.

There is also a project to auto launch your project inside wokwi instead of using the web ui for wokwi (with integration into cargo). You can even use gdb.

https://github.com/MabezDev/wokwi-server