01 / 08 Case study
Webwify
A bilingual, static-first technology-services platform: 106 localized routes, a strict content compiler, and no JavaScript required for the core experience.
106
Generated localized routes
2
Complete language editions
0 KB
JavaScript in the baseline experience
02 / 08 The business challenge
Broad technical capability has to remain understandable, verifiable, and discoverable
Webwify brings services, specialist solutions, project evidence, and editorial authority into one coherent commercial system. Instead of treating every page as a manual exception, the platform validates both languages, search metadata, relationships, and evidence before publication.
Content system
One structure for services, work, company, and editorial authority
A constrained Markdown format compiles into typed Dioxus pages. Service, project, and article catalogues generate localized relationships and context without duplicated navigation logic.
Publication safety
Incomplete content cannot quietly enter the production artifact
A missing translation, duplicate route, oversized SEO field, invalid internal link, or unfinished legal page fails the build instead of becoming a silent defect.
Progressive experience
Visual character never holds the content hostage
Semantic HTML, navigation, and conversion paths work without JavaScript. Optional islands load only where they add measured value and include explicit reduced-motion and failure-recovery behavior.
03 / 08 Implemented system
RustDX and Dioxus for content, TypeScript only for isolated enhancement, Cloudflare for delivery
The project combines Rust/Dioxus static generation, typed bilingual contracts, generated SEO and relationship indexes, fingerprinted assets, security headers, and Cloudflare Pages. The contact flow is a separate edge contract, so static pages do not inherit a general server runtime.
04 / 08 Architecture flow
From approved source material to a verified static artifact
Each layer reduces the chance that incomplete content, a broken relationship, or a localization defect reaches a visitor.
- 01
Sources
Approved English and Bulgarian content in a constrained authoring format.
- 02
Compiler
Typing, classification, locale pairing, and fail-closed validation.
- 03
Composition
Semantic Dioxus templates for services, projects, articles, and company pages.
- 04
Evidence
SEO, schema, sitemap, redirects, budgets, and internal links checked at build time.
- 05
Edge
Static pages and fingerprinted assets delivered through Cloudflare.
05 / 08 Decisions
The decisions that shape the system
Implemented
The site works without JavaScript
Content, language switching, and navigation remain complete; JavaScript is an optional, local enhancement.
Implemented
Localization is one publication contract
English and Bulgarian routes are validated as pairs with reciprocal hreflang rather than maintained as unrelated editions.
Implemented
Caching follows asset identity
CSS and loader assets receive deterministic fingerprinted URLs; mutable runtime modules are not incorrectly advertised as immutable.
Operational boundary
A verified build is not presented as a customer outcome
Automated evidence proves structure, accessibility, and delivery behavior. Conversion outcomes and field Core Web Vitals require production data.
06 / 08 Verifiable evidence
What the platform supports today
- 106 generated localized routes plus bilingual 404 recovery
- Fail-closed catalogue, SEO-length, schema, route, and internal-link validation
- A zero-JavaScript baseline across every route family with enforced transfer budgets
- A Chromium, Firefox, and WebKit Playwright matrix covering responsive, keyboard, and JavaScript-disabled behavior
- Static Cloudflare artifacts with fingerprinted CSS, cache contracts, CSP, and narrowly scoped edge functions
08 / 08 The next move
Need a website that sells your expertise without accumulating delivery debt?
I can turn a complex offer into a clear, fast, and measurable system of pages, evidence, and enquiry paths.
Start a project->Explore the service->