Implementation
Rebuild a website or shop
Build a small website or a defined shop as one connected project, from site structure through to a technical test version.
Implementation / Frontend development & interaction
VAT-exempt under section 19 of the German VAT Act
Build a website or landing page
We turn an approved design into a responsive website or landing page that works on small and large screens.
US$2,249.00
Total price · one-offVAT-exempt under section 19 of the German VAT Act
- Implement up to three designed page types with twelve distinct sections in total
- Responsive HTML, CSS and, where needed, JavaScript in the agreed existing stack
- Navigation, metadata fields and supplied text and images
Your enquiry is non-binding. An order is created only when you accept our quotation .
Image 1 of 4
Service scope
Your result
- Implemented page types with source code in the agreed project
- Documented components and maintenance and publication notes
Included
- Implement up to three designed page types with twelve distinct sections in total
- Responsive HTML, CSS and, where needed, JavaScript in the agreed existing stack
- Navigation, metadata fields and supplied text and images
- Browser, keyboard and size checks plus one shared correction round
Excluded
- New brand or page design, copywriting and image production
- New CMS, user accounts or custom backend functions
- Migration of an entire legacy content inventory and ongoing content maintenance
Which projects does this service suit?
Suitable if …
- A finished design needs website implementation
- A clearly defined landing page needs robust technical implementation
Not suitable if …
- The offer, content and design still need developing
- A complete web app with custom data processes is required
Possible overlaps with: Rebuild a website or shop. If you enquire about these services for the same project, we check for duplicated work before commissioning. Your selection also shows a notice.
What this covers
How does my design become a working website?
A layout shows how a page should look. Frontend development turns it into a usable website: text and images adapt to screen sizes, links reach the right destination and interactive elements have meaningful states. The package requires approved design and finished content.
We work in the agreed technical environment and build up to three page types. Recurring elements become shared components. If a complete design concept, new content system or server-side functions are still missing, we clarify those tasks first. A website rebuild may then fit better.
A page must work beyond the design mock-up
Many widths lie between a large screen and a smartphone. Long headings, enlarged text and keyboard interaction reveal whether layouts work there. We define how each agreed page type adapts.
Public content should be available as meaningfully structured HTML. Interactive technology is used where functions need it. Metadata and headings are technically prepared; this does not automatically produce search rankings. Supplied content quality remains a separate factor.
Does this sound familiar?
The design is ready
You want an existing design implemented. We first check whether page states, content and mobile requirements are sufficiently clear.
The landing page should fit your project
A new page needs shared navigation, typography and technical conventions. We extend the existing structure and agree necessary exceptions.
The current implementation breaks on mobile
A good desktop image is insufficient. Long text and narrow views are tested with actual content to preserve usability and readability.
How we approach it.
Define the design and page types
We count distinct layouts and sections, clarify missing states and identify where implementation belongs technically. This creates testable scope.
Develop components and pages
Shared building blocks represent navigation, content and interactions. Implementation follows the approved design and considers different screen sizes.
Check content and interaction
Pages are checked with supplied content. Browser display, keyboard paths and the shared correction round are addressed before handover.
After handover
Your team receives implemented page types with documented test results and dependencies on the existing application. Additional page types, a new design concept or new imagery are planned separately. Certification of the entire website is excluded.
Describe what already exists: design, website or application. A specific journey with the views and states to develop or change is useful.
We then clarify which technology the site uses, where changes are tested and how they reach you. We also discuss missing content. Do not send repository tokens or production credentials through the enquiry form.
Terms used in this service
What does that mean?
- Frontend
- The part of a website visitors see and use, including layout, navigation, interactions and their behaviour on different devices.
- Page type
- An independent layout pattern, such as a service page or article. Several pages can share a type if structure and behaviour match.
- Responsive implementation
- Page structure reacting to available widths. Arrangement and spacing change without making content or functions inaccessible.
Before your enquiry
Questions about the offer.
What is included, what do you need and what happens after your enquiry?
The process in detail →Must the design come from Figma?
Not necessarily. Accessible, authoritative layouts, dimensions, states and usable assets matter. The handover format is reviewed before starting.
Is a mobile version included?
Yes. Responsive implementation is included. If the design lacks mobile rules, these are agreed beforehand for the selected page types.
Can I change content myself later?
That depends on your existing content system. We use agreed existing content workflows; building a new CMS adds scope.
Are contact forms included?
Presentation of an existing form can be planned. A new sending or storage process with validation is a separate function and scoped separately.
Is the website published directly?
Handover first takes place in the agreed test environment. Publication requires approved content, appropriate access and an expressly agreed process.
When does work begin?
We confirm the start and delivery deadline in writing after reviewing your documents. The agreed scope and complete source data determine the schedule.
Which access is needed?
Approved layouts including mobile requirements and finished content Repository and test-environment access or an agreed technical foundation Credentials must not be included in the enquiry. Details are agreed only after written commissioning.
What happens after handover?
One written follow-up round is included. The service scope lists the analyses, designs or technical changes covered by the package. We agree additional work with you before it begins.
Read more on this topic
Implementing a Figma design as a website: preparing the handover
A desktop design is rarely enough for implementation. Clarify content, narrow layouts and the states of interactive elements.
Read the guide ↗Related services
These may fit too.
Implementation
Build a component library
We build recurring interface elements as shared code components, with defined variants, states and documentation.