Web Development and Corporate Sites

Corporate web development is the work of designing and engineering a company website so that it loads quickly, is readable by both people and machines, can be maintained by non-developers, and supports the markets the business actually sells in. It is an engineering project with a marketing purpose, and treating it as only one of the two is where most website projects go wrong.

Moon Workshop has built websites and web applications since 2013 from Antalya, Türkiye, for clients selling domestically and in international markets including Germany, the United Kingdom, the Netherlands and the United States.

What a corporate site has to do

Before technology choices, we establish what the site is for. Most corporate sites carry three jobs simultaneously:

1. Explain what the company does clearly enough that a stranger understands it in thirty seconds
2. Generate qualified inquiries through content that answers real buying questions
3. Serve as infrastructure for advertising, search visibility and sales conversations

These goals conflict occasionally, and the conflicts are worth resolving explicitly at the start rather than discovering them during a design review.

Performance is a business requirement

Page speed affects bounce rate, conversion rate, ad quality scores and search visibility. It is not a technical nicety.

Our approach:

• Static generation where possible. Most corporate pages have no reason to be computed on every request.
• Minimal JavaScript. Interactive components load only where they are used, not site-wide.
• Modern image handling. Correctly sized, modern formats, lazy loaded below the fold, with explicit dimensions to prevent layout shift.
• Self-hosted or preloaded fonts with proper fallback metrics.
• Core Web Vitals measured on mobile, on realistic network conditions, throughout development rather than as a final check.

The content model decides maintainability

The most common reason a website ages badly is a content model built around the first design instead of around the content itself. Pages become hand-built layouts, adding a new service requires a developer, and within two years the site is out of date because updating it is inconvenient.

We define the content model during discovery: what entity types exist, what fields they have, how they relate, and which parts of the page are editable. Then the design implements the model, rather than the model being reverse-engineered from a design file.

Choosing a content management approach

• File-based collections suit sites where content changes occasionally and the team is comfortable with a simple editing workflow. Fastest to build, fastest to serve.
• Headless CMS suits marketing teams publishing regularly, needing preview, scheduling and role management.
• Custom admin panel suits sites with domain-specific data structures that a generic CMS models awkwardly.

We recommend based on publishing frequency, team size and technical comfort, not on what is easiest for us.

Multilingual structure from day one

Retrofitting a second language is expensive. Designing for it costs almost nothing at the start.

Our multilingual architecture covers:

• Language-specific URL structure defined before build
• A translation key linking equivalent pages across languages
• Correct hreflang annotations, generated from the content model rather than maintained by hand
• Per-language metadata, structured data and sitemaps
• Interface strings separated from content so the UI translates cleanly
• Layout that tolerates German compound words and longer text without breaking

Turkish and English are our standard pair. We also deliver German and Dutch versions where the market requires it.

Built to be read by machines

An increasing share of first contact with a brand happens through search summaries and AI answers rather than through a homepage visit. Sites we build include a connected structured data graph — Organization, WebSite, WebPage, Service and BreadcrumbList entities referencing each other — plus semantic HTML, clear heading hierarchy and factual, quotable content blocks.

This overlaps heavily with accessibility. Semantic markup, proper heading order, labeled form fields and sufficient contrast serve screen readers and machine parsers with the same work.

Migration without losing visibility

Replacing an existing site is the moment search visibility is most at risk. Our migration checklist:

1. Full inventory of existing URLs from crawl data and Search Console
2. Traffic and ranking data per URL, so valuable pages are identified before anything is removed
3. A mapped redirect plan, one to one wherever a target exists
4. Metadata and structured data preserved or improved, never silently dropped
5. Staging validation with a crawl comparison against the old site
6. Post-launch monitoring of index coverage and rankings for at least four weeks

Handover and what comes after

At launch you receive the source code, documentation of the content model, editor training, and a defined support arrangement. You own the code and the hosting accounts. We can maintain the site on an ongoing basis, but you are not locked into that to keep it running.

Last updated: August 2026.