What you can check
- 03
- sites deployed and reachable
- 01
- built for a paying client
- 04
- public repositories
Approach
I would rather show finished work than describe intentions.
A website can look good and still be hard to use. What decides it is duller than the visual design: the mobile layout, the error states, and everything that still has to be true a month after launch.
Process
Six stages, one order
The steps change with the project. The order does not. Each one below carries a real example.
01
Understand
Collect the business information, the required pages, the main actions, and the technical limits.
99 AKTAU: the guest and the administrator needed the same booking to make sense from two sides.
02
Structure
Decide how the pages connect and where each piece of information belongs.
Tuesday: practical information moves above the atmospheric content on a phone.
03
Design
Build the layouts, typography, components, mobile version, and interaction states.
99 AKTAU: accept, reject, and delete got labels that are hard to confuse.
04
Build
Develop the frontend, and connect forms, databases, authentication, or APIs when the project needs them.
Tuesday needed no backend, so it did not get one.
05
Test
Check mobile screens, links, forms, error states, loading speed, and the production build.
99 AKTAU: most of the real bugs only appeared in the deployed build.
06
Deliver
Configure deployment, environment variables, metadata, and the notes the owner will need later.
The client keeps a working admin area, not a project only I can operate.
Contact
Need a website?
Send a short description of the project, the pages you need, and any examples you like. I will read it and reply with questions.