The work, with something to inspect.
A look inside 0OP.dev: the brief, the choices, and the features you can try. A concrete example of turning an idea into a useful website.
Explore the project ↓0op.dev/workA working example, on the site you are using.
0OP.dev brings a short domain, a clear service directory, and a small interactive feature into one workspace. It is our own project: a public example of how we organize content and build around a defined task.
The brief
Explain Zero Operation Development in plain English. Give each area of work a memorable address. Let visitors move between services, understand the scope, and reach the person behind the work. Keep a simple five-star question about the name on the home page.
What was built
A brand that starts with zero
An orange slashed zero and dark green OP make the numeric character visible. The interface uses a shared workspace, navigation, and typography so the service pages feel like parts of one product.
Separate pages with separate jobs
AI workflows, advertising operations, and custom apps have their own descriptions, scope, questions, and related links. Each page has a canonical URL and metadata, with a sitemap for discovery.
Small, real interactions
The home page accepts a rating about the name. The tools page provides a URL slug generator and a manual time calculator that run in the browser.
Inspect a finished interaction
The live time calculator, shown with example inputs. Try it yourself or inspect the standalone calculation source.
How it is put together
The site uses TypeScript, React, and Vinext on Cloudflare Workers. Service content is rendered into HTML on the server. The rating feature stores one editable vote per browser cookie in D1; it does not establish a unique person or represent a service review.
What was checked
The published pages are checked for response codes, a single main heading, distinct metadata, canonical addresses, structured data, and working internal navigation. The browser tools are tested with valid, empty, and invalid inputs. The rating API checks input limits and same-origin requests. The site includes accessible mobile navigation and a cookie information notice.
This is an own-project implementation. The guides explain design decisions, while the editable templates show how a new workflow can be scoped.
What this example demonstrates
You can inspect the navigation, page content, metadata, and interactive tools directly. This is an implementation example, with no claimed client results, traffic increase, or measured business savings. Search visibility and commercial impact need their own evidence over time.
Another own project: oguzerol.com
Oğuz Erol’s personal business website brings advertising, measurement, custom applications, and connected business workflows into one public portfolio. It is the wider home for the person behind 0OP, with a different role from this focused Zero Operation Development site.
You can inspect its service explanations and contact routes directly. This reference identifies an owned public website, with no claim about traffic growth or customer results.
Apply the approach to your workflow
Start with one audience, one recurring problem, and one useful outcome. Build a complete path, check its behavior, and expand when the next step is clear. Explore web development for a public site or app development for a working interface around your process.
What should stop being manual?
Bring a recurring task, an example input, and the outcome you need. We can use that to define a practical first scope.
Discuss it with Oğuz ↗0OP · Zero Operation Development
by oguzerol.com