Available for development-focused web projects
Build. Ship. Iterate.
I build the code behind useful interfaces: CMS features, WordPress extensions, and focused tools that stay maintainable.
PHP · SQL · TypeScript · CSS · WordPress · HTTP APIs
About
Full-stack developer with a backend focus and a preference for systems that are easy to inspect.
I am Simon Ringwelski. I build web products end to end: databases, admin interfaces, public frontends, and the scripts that connect them.
This site runs on a CMS I built to test my own patterns for migrations, translations, accessibility settings, and deployment-friendly defaults. The sandbox is where smaller experiments live.
Selected work
CMS core, WordPress plugins, and practical browser tools, built to be understood after launch.
Custom CMS
The codebase behind this site: versioned migrations, role-based admin, Danish/English/German UI, theme-driven pages, a unified media library, and security tooling - built so each layer can grow without a framework treadmill.
Read about the CMS project
WordPress Task Manager plugin
A task model, metaboxes, and sensible defaults inside wp-admin, so project work stays out of scattered spreadsheets.
Read about the plugin
WordPress custom admin dashboard
A tailored wp-admin layer with custom menus, dashboards, and workflows, shaped by real WordPress constraints.
Read about this project
Sandbox tools
Browser-based experiments and demos on this site - small utilities you can run without leaving the portfolio.
Browse sandbox
Toast notification layer
Vanilla JS notifications with positions, a timer bar, pause on hover, and optional links. GPL-3 and easy to drop into a page.
Read about the library
EXIF extractor
Client-side metadata extraction with structured output for debugging media files and upload flows.
Run itHow I work
A practical loop for turning unclear ideas into maintainable software.
Prototype in the open
Start with the data model, then shape the UI around it. If the idea cannot be explained clearly, it is not ready to build.
Ship reliable PHP
Use migrations, prepared statements, and predictable folders. Clever is fine; fragile is not.
Extend WordPress without hacks
Use hooks, custom post types, and capabilities in ways that survive plugin updates and client edits.
Publish the toolbox
Publish small utilities for formatting, minifying, and inspecting data, each with clear inputs and outputs.
Current focus
Hardening this CMS, expanding the sandbox, and taking on builds where code quality matters from day one.
FAQ
Straight answers about the work, the stack, and how collaboration usually runs.
Mostly PHP for server-rendered apps and WordPress plugins, plus modern JavaScript and CSS on the front end. SQL comes in when the data model needs it.
No. I implement what I design. If you already have designs, I can build to spec and flag the places where the browser or data model needs attention.
Yes. Admin panels, importers, browser-based utilities, and small workflow tools are often the most valuable work.
WordPress is excellent when the product is content-first and the ecosystem fits. I reach for a custom CMS when I need tighter control over migrations, capability-based permissions, multi-app admin, or a data model that should not be forced into posts and meta boxes. This portfolio runs on that stack so the patterns stay honest - translations, themes, and security included.
Use core APIs, avoid unnecessary global state, and test with realistic content. Gutenberg or classic can both work when the architecture is clean.
Short written specs, async reviews, and a shared issue list. Meetings are useful when something is blocked, not as a replacement for progress.
Contact
Send a short note with the stack, timeline, and what done should look like. I reply personally.