Multilingual WordPress Build from Webflow

ABOUT THE COMPANY
Centrum Bad (Kaps Consulting ApS, CVR 46402340) is a Danish startup specializing in complex bathroom renovation projects inside apartment buildings - projects that require technical design, engineering, and formal approval from housing associations and sometimes municipal authorities. Small, highly competent team with strong supply-chain relationships. Budget is a real constraint - this is a lean startup, not a corporate account.

WHAT ALREADY EXISTS
The site's content, structure, and visual identity are fully finished and live as a working reference, built in Webflow at centrum-bad.webflow.io (not yet on a custom domain). All five main pages have real, finished, client-approved copy: Home, Ydelser (Services), Referencer (Case studies), Om os (About us), and Inspiration (a small blog/resource section with a "Stilarter" sub-page). Content, structure, and information architecture are locked - this is NOT a content, copywriting, or structural-design project.

IMPORTANT: this is not a Webflow project. The Webflow site is the definitive reference for content, structure, and visual direction only. You will not be given Webflow access, and nothing will be edited there. The deliverable is a fresh build of this same site in WordPress, hosted at one.com, matching the reference closely in content, layout, and visual feel, adapted naturally to how WordPress themes/page builders work.

A separate contest already produced the company's new logo and visual identity (wordmark, mark, color palette), already implemented on the Webflow reference. This identity carries over 1:1 into the WordPress build.

SCOPE

1) Homepage
- Replace the current hero image (a bathroom photo of uncertain origin) with a properly-licensed open-source/stock photograph or an original illustration - see Imagery Policy below. Highest-priority visual item on the site.
- Design a small custom icon set (line-art style) for the four-item "core services" grid and the five-item services list on the Services page - one shared visual language, sitting comfortably next to the logo mark.
- Recreate the "typical timeline" Gantt-style chart. On the Webflow reference this is a live, code-driven HTML/CSS component, not a static image or off-the-shelf WordPress feature - propose your approach (custom code, plugin, or a simpler equivalent that still gets a six-phase timeline across clearly).
- A large six-step accordion "how we work" section sits beneath that chart (each step expands to show what we do, what we need from the client, deliverables, an approval-gate callout, and a lessons-learned note, plus example-document thumbnails for two of the six steps). This is one connected design system on the reference - rebuild as a whole, not element by element. Only step one has its own line-illustration; treat the rest as optional/parked until confirmed.
- Minor site-wide items: a subtle "current page" nav indicator, light touch-ups to CTA buttons and page background.

2) Services page
- Apply the shared icon set to the five-item services list.
- Recreate the FAQ section (12 finalized Q&As, copy locked) - only the visual treatment (accordion behavior, spacing, optional process-flow graphic) is open.

3) Case studies ("Referencer") page
- Currently text-only, one completed case study (finished, approved copy). No real client photos will be supplied (see Imagery Policy) - support this page with open-source photography and/or original illustration/diagram work (stylized process timeline, icon-based scope summary, generic material/texture imagery) rather than before/after photos of an actual property. Top priority for this page.

4) About us page
- Already close to finished on the reference (founder-spotlight layout, photo, accent line, contact section). Replicate as-is; only optional finishing polish is open, not a redesign.

5) Inspiration / resources section
- The overview page currently shows flat category tiles; we are separately deciding whether to reorganize by construction discipline or keep a flat, tag-filterable list. Do not lock a layout for this page until that decision is confirmed - it will be communicated before this piece of work starts.
- Five existing articles have no imagery yet - add representative open-source photography and/or illustration per article (generic material shots, not tied to any specific client project).
- One sub-page ("Stilarter" - interior styles) is further along: real photography for four style categories with a caption band under each. Recreate closely - mainly needs the caption band and thumbnail grid styled to match the final type/color system.

6) Danish/English multilingual build
- All copy for an English version of the entire site (all main pages plus the five articles) is already translated and approved - this is a build task, not a translation task.
- Build using WPML or Polylang (your choice, whichever you have stronger hands-on experience with) with a visible DA|EN language switcher in the header, matching the reference site's understated nav style.
- The client must be able to edit both language versions' text herself afterward through WordPress's normal editor - this needs to be a first-class, ongoing workflow, not a one-time build-and-forget.

LOGO & TAGLINE IMPLEMENTATION (hard requirement)
The tagline/subtext shown on the site must be built as live, editable text in WordPress - never baked into the logo artwork itself. The client wants to swap in a new tagline at any time by editing text directly in WordPress, without commissioning new logo files or involving a developer.
- Implement the logo as a mark/icon asset (SVG or image) next to a SEPARATE text element for the tagline, styled in the site's own type system - not a single flattened image containing both the mark and the words.
- Wherever the tagline appears (header, footer, homepage hero, etc.) it must be normal, editable text, sized/positioned to survive a text swap of similar length without breaking the layout.
- The mark/icon itself (no tagline baked in) is the one asset that should be a locked-down static logo file.
This is a hard requirement, not a nice-to-have.

IMAGERY POLICY (hard constraint)
No photographs of actual clients' bathrooms or homes anywhere on the site - firm rule, applies to the hero image, case studies page, blog articles, everywhere. All imagery must be either:
- Properly-licensed open-source or stock photography (a license clearly permitting commercial use, documented so the client can rely on it later). Generic material/interior photography (tile, fixtures, water, natural materials) is welcome.
- Original illustration or explanatory graphic (line illustrations, diagrams, cutaway/technical drawings, stylized process timelines, icon-based summaries) created for this project, not implying a specific real property.
One exception: a photo of the company's own workshop or team (not a client's home) may be used if the client supplies one - optional, low priority.

OUT OF SCOPE
- Copywriting or content strategy - all copy is finished and approved.
- The logo/visual identity itself (separate, already-completed engagement) - only the implementation requirement above applies here.
- Structural/information-architecture decisions still pending internally (e.g. the Inspiration page's category model) - will be confirmed before that piece of work is handed over.
- Automated migration from Webflow - there is no compatible export between the two platforms. This is a fresh build guided by a finished spec, priced accordingly.
- Contact form backend wiring is optional, not required - currently a visual mock on the reference. Feel free to include as a priced add-on if you'd like.

PRACTICAL REQUIREMENTS
- Comfortable building a WordPress site from scratch (custom/child theme or a proven page builder such as Elementor or Bricks), hosted on one.com's WordPress hosting. Direct one.com experience is a plus, not required - solid general WordPress/cPanel hosting experience is the baseline.
- Comfortable setting up a multilingual site with WPML or Polylang.
- You'll be given full view access to the Webflow reference, all approved copy documents, and the logo/visual identity assets. You will NOT be given Webflow edit access.
- Work from the existing documented color/typography system (CSS custom properties driving the reference site's palette) as the target visual system to recreate in WordPress.
- This is a defined build project ending at go-live handover, not an ongoing retainer - future maintenance is a separate conversation.

WHAT TO INCLUDE IN YOUR PROPOSAL
- Relevant WordPress portfolio examples - ideally an understated, editorial/earthy visual style rather than a bold SaaS/tech look.
- Your experience with one.com's WordPress hosting specifically, or general WordPress/cPanel hosting.
- Your experience with WPML or Polylang for multilingual sites.
- Your recommended approach to replicating the homepage's interactive process/timeline section.
- Examples of open-source photography curation and/or original illustration work.
- Your suggested approach to implementing the mark + editable tagline as separate elements.
- A rough estimate broken down by section (homepage, services, case studies, about, inspiration, multilingual setup) so I can prioritize within budget if needed - a phased/optional-items proposal is welcome over an all-or-nothing quote.