Revamp Static Website with Template System

@webbookstudio

Hi there, We understand you're looking to revamp your static website by reintroducing a template system to maintain design consistency across all pages and enable your team to update content without requiring developer assistance for every change. Our team at Webbook Studio has experience in similar projects, such as rebuilding a website for a luxury leather retailer using PHP and custom Photoshop design, and creating multiple WooCommerce stores with integrated payment systems. We're proficient in static site generators like Eleventy and can help you achieve a clean and consistent design system. We'll deliver a rebuilt site with redesigned templates for each page type, a one-page reference doc for brand basics and new layout patterns, and a guide on how to edit content files and push changes live. Can you tell us more about your current workflow for updating the website and how you envision the new template system fitting into that process? Feel free to message us to discuss the details! — Webbook Studio

@diektech

Hi, This is Elias from Miami. I checked your brief and understand the core problem: the static export removed the shared template layer, so layouts and components have gradually become inconsistent. You want to restore that structure while modernizing the UI, without changing the existing branding or adding a CMS. I’ve worked with component-based web architectures, static sites, Git workflows, and maintainable content/template separation. I’d first audit the 10 pages to identify shared patterns, then create reusable layouts/components and Markdown-driven page structures in Eleventy. I’d validate the initial templates with you before completing the remaining system, deployment workflow, and documentation. The four-week timeline and milestone approach sound reasonable, and I’m comfortable collaborating through Teams and Git. I have a few questions for clarification: Q1 – What static hosting platform is the site currently deployed on? Q2 – Is the existing repo using any build tooling, CSS framework, or plain HTML/CSS? Q3 – Should existing URLs remain identical for SEO/backlink preservation? Looking forward to hearing from you.

@gauravgargcs

Hello, Hope you are doing well, I understand you need to rebuild the 10-page static site with Eleventy templates, reusable components, Markdown content files, consistent UI, existing branding, and the same hosting/deployment workflow. I’ll first audit the current repo/site, define page templates and component patterns, then build, test responsive layouts, configure deployment and provide clear editing/documentation for your team. With 10 years of web development experience, I can work within your 4-week plan, AEST schedule, MS Teams workflow and milestone process. Let’s chat and schedule the 1.5-hour discovery call to review the current site and agree on the template approach. thank you Regards Gaurav Garg

@raheel2k29

Hello, I can rebuild your static site into a maintainable Eleventy-based template system, preserving the current colours, fonts, logo, and URLs while improving layout consistency across homepage, location, service, and contact page types. I’ll separate content into clear Markdown files, create reusable navigation, headers, cards, forms, and footer components, and configure deployment to your existing host. I’ll also provide the brand and layout reference, sample content files, and a straightforward guide for editing content with an AI coding assistant, previewing changes, and submitting pull requests. I’m comfortable working through GitHub, MS Teams, milestone reviews, and your AEST schedule. The discovery call and mid-project check-in fit well with this approach. I’ll keep the implementation tidy, documented, and easy for your team to maintain. I’m Muhammad, and I look forward to helping untangle the current static site. Thank you!

@extreamcode

Hi, You’ve got the classic static-site drift problem: the pages still exist, but the system that kept them consistent is gone. I can rebuild that structure cleanly with Eleventy or a similar static generator, restore shared templates for each page type, and make the site easier for your team to update through Markdown content files and pull requests. I’ve worked on PHP/WordPress and static web builds, template cleanup, UI consistency, deployment, and documentation, so I’m comfortable turning a flattened HTML export back into a maintainable system. I’ll keep your colours, fonts, and logo intact while tightening the layout, navigation, cards, forms, and footer into a clear pattern library. I’ve shared an initial estimate based on your description, and once we go over a few technical or functional details, I’ll confirm the exact cost and delivery schedule. Would you prefer the rebuilt templates to preserve every current URL exactly, or are a few controlled redirects acceptable? A few points I’d like to clarify: do you want the rebuilt site to match current URLs exactly, and is the current host supporting Eleventy-style deploys without changes? Also, should the one-page reference doc include only design rules, or a short component usage guide as well? Looking forward to your reply so we can finalize the exact plan. Best regards, Asad

@ranjika08

Right now your team has the worst of both worlds: a static site that still needs consistency, but no template layer to enforce it. The fix is not just rebuilding pages, but extracting the repeating page patterns, turning them into reusable templates, and cleaning up the UI system so future edits stay simple and don’t reintroduce drift. I work regularly with content-structured builds, Git-based workflows, and redesigning existing sites without throwing away the brand that already works. For this job, the important part is making the layouts and components feel intentionally designed while also leaving behind a setup your team can actually edit through Markdown-style files and PRs. Your phased review process makes sense, especially the midpoint check before all templates are rolled out. - Do you want the new templates to preserve the current HTML/CSS approach as much as possible, or are you open to a cleaner rebuilt frontend structure if deployment remains unchanged? - How many repeating page types do you expect in practice beyond home, location, service, and contact? - Would you like the documentation written more for a technical repo manager, or for non-developers using an AI assistant to make content edits?

@ritu9382

Hello, I can start immediately. I’ve reviewed the scope and understand the main requirement is to turn the current standalone HTML pages into a reusable template system while improving the overall UI and keeping your existing branding unchanged. I can work with Eleventy, Git/GitHub, Markdown-based content, reusable components, and the existing deployment setup. I’ll also include the sample content structure, brand/layout documentation, editing workflow, and handover. For transparency, AUD 1000 is tight for the complete scope. I’d estimate AUD 1200 and around 4 weeks for a proper implementation. If the budget needs to remain at AUD 1000, we can discuss prioritising the scope during the discovery call. Let me know if we can move further. Regards, Ritu Gupta

@seefattechnologi

I believe I can do this project in an efficient and professional manner------------>>The real issue is not the static HTML itself. It is that the export removed the shared template layer, leaving every page to evolve independently. I can rebuild that foundation with Eleventy so navigation, layouts, components, and page structures stay consistent while your team edits content through simple Markdown files. I can audit the existing repo, identify the repeating page types, create reusable Eleventy templates/components, refresh the UI while preserving your existing brand, configure the current deployment flow, and provide the content structure, brand/layout guide, and AI-assisted Git/PR editing workflow. I am comfortable with Eleventy/static site generators, JavaScript, HTML/CSS, Git/GitHub, responsive UI, reusable component systems, and documentation. I can work within your four-week plan and include the requested mid-project review and handover. question: Can you provide the current repository and live site before the discovery call so I can assess the existing page patterns and confirm the Eleventy structure? Please ping me to get started and provide you great results. Thanks!!!

@Hubready

Hello!, I am a Florida-based senior software engineer and this looks like the kind of rebuild that needs careful planning, not just a quick visual refresh. Your main pain point seems to be that the current site has outgrown its old structure and needs a solid template system so content can be updated cleanly without breaking design, performance, or accessibility. I can help by auditing the existing site, rebuilding the frontend with a reusable template/component approach, and testing everything for responsiveness, SEO basics, and accessibility so the site is easy to maintain going forward. I pay close attention to details like layout consistency, code structure, and edge cases, because that is usually what separates a patch job from a proper rebuild. If needed, I can suggest a phased approach so we lock in the core pages first, then refine templates and optimize the final build. A few relevant projects I’ve handled: - local service business site rebuild with reusable page templates - SaaS marketing site redesign focused on speed and accessibility - e-commerce frontend cleanup with improved navigation and conversion flow - documentation-style website restructure with editable content sections Quick questions: 1) What platform is the current site on, and do you want to keep it or rebuild on a new stack? 2) Which pages need to become templates first, and how many unique layouts are required? 3) Is the priority visual consistency, easier content editing, or fixing a specific

@ludiac

Good day, I can rebuild your static site into a clean, maintainable Eleventy-based template system while keeping your existing colours, fonts and logo. I’ll identify the repeating page types, create reusable templates/components, move content into Markdown, modernize the layouts/UI, preserve existing URLs where possible and keep deployment compatible with your current host. I will also provide the brand/layout guide, sample content files, GitHub/AI-assisted editing workflow, documentation and handover call. I’m comfortable with Git/GitHub and static-site workflows and understand the importance of making content updates simple for a non-developer. I can work within your 4-week timeline and $1,000 AUD budget with milestones agreed during the discovery call. Happy to collaborate through MS Teams and work around AEST. Thanks.

@onkarkulkarni8

With over a decade of experience as a full-stack developer, I am confident that I have the skills and knowledge necessary to revamp your static website and rebuild it with a proper template system. My expertise with frontend technologies such as JavaScript and HTML, along with proficiency in utilizing static site generators like Eleventy and employing Markdown for content management make me an excellent fit for this project. I understand the value of maintaining consistent design throughout a website, particularly when it comes to navigation, headers, cards, forms, footers, and UI components. Equally important is finding the balance between retaining your branding aesthetics while infusing modernity, which is precisely what I intend to achieve with your project. I will begin by identifying the repeating page types across your 10 pages and building one template per type, simultaneously enhancing layouts and components to ensure a polished interface. Within the scope of this project, I will not only rebuild your site but also provide detailed references and guides for future updates. Moreover, not only will collaborating with me result in a revitalized site with matching current URLs deployed to your current host, but it'll also establish an efficient workflow using an AI coding assistant and pull requests for smoother content editing.

@corpmember29

HEY {{{ I HAVE WORKED ON SIMILAR ELEVENTY/STATIC SITE TEMPLATE PROJECTS WHERE EXISTING HTML WAS RESTRUCTURED INTO REUSABLE PAGE TYPES AND COMPONENTS AND CAN SHOW YOU RELEVANT WORK. }}} I understand the real issue: the static export removed the shared template layer, so pages have drifted into separate layouts. You don’t need a CMS or new content—you need clean reusable templates, consistent UI, and simple content files your team can edit through Git/AI + PRs. I have 12+ years of IT experience and have worked on similar static-site rebuilds, template systems and Git-based deployments. I’ll audit the existing pages → define homepage/location/service/contact templates → rebuild navigation, headers, cards, forms and footer → move structure to Markdown/data files → preserve URLs and current branding → configure the existing deployment → provide brand/layout documentation, sample content files and a clear editing/PR guide. I’ll follow your 4-week workflow, AEST availability, MS Teams collaboration and milestone process, including the 1.5-hour discovery call and mid-project review. Thanks, Karuna

@ZohaibRoy

⭐⭐⭐⭐⭐ Rebuild Your Website with a Consistent Template System ❇️ Hi My Friend, I hope you're doing well. I've reviewed your project requirements and see you're looking for someone to rebuild your website with a proper template system. Look no further; Zohaib is here to help you! My team has successfully completed 50+ similar projects focused on website rebuilding. I will create a clean and consistent design using a static site generator, ensuring that your team can easily update content. ➡️ Why Me? I can easily rebuild your website as I have 5 years of experience in web development, specializing in static site generators, HTML, and UI design. My expertise includes content management, template creation, and responsive design. Additionally, I have a strong grip on Git and Markdown, which will ensure seamless content updates. ➡️ Let's have a quick chat to discuss your project in detail and let me show you samples of my previous work. Looking forward to discussing with you in chat. ➡️ Skills & Experience: ✅ Web Development ✅ Static Site Generators ✅ HTML/CSS ✅ UI Design ✅ Git & GitHub ✅ Template Creation ✅ Content Management ✅ Markdown ✅ Responsive Design ✅ Documentation ✅ Collaboration Tools ✅ Troubleshooting Waiting for your response! Best Regards, Zohaib

@flapjakc

SEE THE VISION HERE. Hi, Mateo here, from Toronto. I’d rebuild the site with Eleventy, reusable templates, structured Markdown content, and a clean component system while preserving your existing branding, URLs, and hosting setup. I’d first map the current page types, build the shared layouts and UI components, then migrate the structure into content files with Git-based deployment. I’ll also provide the brand/layout guide, sample content files, editing workflow, and handover documentation so your team can manage content confidently with an AI coding assistant and PRs. The four-week phased approach works well, including the discovery call and mid-project check-in. 1: Can you share the current repository and live site before the discovery call? 2: Is GitHub currently handling your deployment to the existing host?

@juanpablomacf

The tricky part isn't writing the Eleventy templates - it's reverse-engineering which UI patterns across your 10 flattened pages were meant to be the same component that just drifted apart, versus ones genuinely different from the start. Getting that classification right up front is what makes the template system feel consistent, not just fewer files hiding the same inconsistency. I've worked with static site generators (Eleventy and similar) alongside UI/template redesign. I'd start by cataloging your current page types side-by-side - nav, header, cards, forms, footer - to identify what should genuinely be shared versus what needs its own layout variant, before writing a single template. For content files, I'd design the Markdown frontmatter around what your team will actually edit day-to-day, so the PR-based workflow stays simple for a non-developer using an AI coding assistant - not something requiring Eleventy internals knowledge. Worth flagging early: matching current URLs is usually straightforward, but I'd verify redirect/trailing-slash behavior, since that's a common source of broken links after a static export. Comfortable with AEST check-ins, Teams, and starting with the 1.5-hour discovery call. I've done this kind of "untangle a static site into templates" work before. Juan Pablo

@hassanmustafa01

Hello!⚡ Thank you for one of the clearest briefs I have read. Pulling a consistent system back out of flattened HTML is satisfying work. I recently rebuilt a static site into an Eleventy template system, with content moved into Markdown and the deployment unchanged. How I would proceed: 1. Eleventy is the right call: plain HTML out, no framework at runtime, deployed exactly as your site is now. 2. Keep every URL identical. Eleventy permalinks reproduce your current paths exactly, not just where possible, so nothing you rank for moves. 3. Build the location pages from one data file and one template, so adding a location later is a new entry rather than a new page. 4. Keep layout decisions inside templates, out of content files. An edit made with an AI assistant then changes words only and cannot pull the design apart, which is what makes your pull request workflow safe. 5. Rebuild navigation, cards, forms and footer as shared components, with semantic markup, keyboard access and contrast checked. 6. Reference doc, sample content files, the written guide, then the handover call. $1,000 AUD, four weeks as you set out. Your late afternoon is my morning, so calls are easy. Thanks. Hassan

@CodeAnchors

Greetings, I understand the core objective behind your project to revamp the static website with a template system, ensuring consistent design and enabling easy content updates. Leveraging my expertise in Website Design, JavaScript, HTML, CSS, and Web Development, I propose a structured approach encompassing a static site generator like Eleventy, redesigning page layouts and UI components, and transitioning content to simple content files. My portfolio: ⭐⭐ https://www.freelancer.com/u/CodeAnchors ⭐⭐ To ensure seamless execution, I will focus on controlled planning, clean implementation, testing checkpoints, and milestone-based transparency. Could you share more about your primary goal or priority for this revamp? Let's discuss further in an open chat to finalize the scope smoothly. Best regards, Muhammad Anas Khan

@surender6789

Hello, I understand exactly what you’re looking to achieve: turn the current collection of standalone HTML pages into a proper, reusable site system where layouts and components stay consistent and your team can manage content without touching the code. I can build this with **Eleventy + Nunjucks + Markdown + Git/GitHub**, keeping your existing colours, fonts, logo, URLs, and hosting workflow. I’ll create reusable templates for the homepage, location pages, service pages, contact page, and shared components such as navigation, headers, cards, forms, and footer. I’ll also provide sample content files, the brand/layout reference, deployment setup, and clear documentation for editing content with an AI coding assistant and submitting a pull request. We can follow your four-week plan with the discovery call, mid-project review, and final handover. I’m happy to review the current repository and live site during the initial call and start from there. Please check my portfolio: https://www.freelancer.in/u/surender6789 Looking forward to working with you. Best Regards Surender Sharma

@longngoc2307

==== Hi - Truong here ==== "STATIC SITE TEMPLATE SYSTEM" - you need to turn 10 drifting HTML pages back into one consistent, easy-to-edit structure. I’d use Eleventy with shared layouts, reusable components, and Markdown content files, keeping your existing colours, fonts, logo, URLs, and Git-based deployment. I’d first map the page types, build one representative template for the mid-project check-in, then roll the system across the remaining pages and document the exact editing workflow. My focus would be making content changes feel like content changes, not code changes, while keeping the layout consistent by default. Which current host and GitHub deployment workflow are you using, and can you share the existing repo before the discovery call? Looking forward to work with you.