Design & front-end
Responsive layouts, custom interfaces, HTML/CSS, JavaScript, accessibility and the details that make a site feel deliberate rather than templated.
About WebViper
Independent
by design.
WebViper is one person: me, Alex. I design websites, write code and build web systems for businesses that need something more useful than a stock theme.
I started with hand-coded HTML and CSS, moved through custom WordPress, databases and business automation, and now build everything from focused marketing sites to bespoke quoting, catalogue and internal web tools.
15+ yearsbuilding for the web
Design + codehandled together
Practicaltech chosen for the job
Independent by design
Highertogether.
Start with the real problem. Pick the technology afterwards. It sounds obvious, but it saves a lot of expensive nonsense.
What I bring
More than
a page builder.
I’m comfortable crossing the line between design and development. That means I can think about the visual experience, the content structure, the data underneath it and the practical workflow around it.
WordPress & CMS
Custom themes and content-managed sites when clients need to own and update content without being forced into a generic page-builder workflow.
Systems & data
PHP, ASP, SQL, PostgreSQL, Python and bespoke web-app logic for catalogues, quoting, forms, internal tools and business-specific workflows.
Automation & integration
APIs, data handling, VBA and workflow automation where the useful part of the project lives behind the screen rather than on it.
Deployment & ownership
Docker, static deployments and maintainable project structures. I want the finished thing to be understandable and liveable after launch.
Modern tools, human judgement
I use modern AI-assisted tools where they genuinely speed up research, prototyping and development — but the decisions, testing and responsibility stay human.
Then & now
The tools changed.
The standards didn’t.
WebViper existed before responsive design became the default, before component frameworks became normal, and long before AI-assisted development. Back then I was hand-coding CSS, building WordPress themes and even making a custom icon webfont for the site.
The stack is different now. The basic job is not: understand what somebody is trying to achieve, make sensible technical decisions, and build it properly.
How I work
How a project
actually gets done.
Start with the problem.
Tell me what needs building, fixing or improving. We can work out the pages and technology once the job itself is clear.
Pick the right tool.
Astro, WordPress, PHP, a bespoke application or something simpler — whatever fits the job without adding machinery for the sake of it.
Leave it understandable.
Good-looking matters. So do speed, accessibility, maintainability and knowing how the thing works after it has been handed over.
Have something in mind?