Experienced Astro Developer: Agent-First WordPress Migration Using GitHub Copilot

UPWORK APPLICATIONS ONLY Apply and communicate exclusively through Upwork. Contacting us or our employees through any other channel will result in immediate disqualification. --------- PROJECT OVERVIEW We are an MSP replacing our existing WordPress marketing website with a fast, maintainable, GitHub-based website hosted on Sevalla. Our current website has become unnecessarily complex through plugins and customisations. We want to simplify the architecture and use an agent-first workflow for development, maintenance and content publishing. This is not another WordPress redesign or page-builder project. We need an experienced developer who can deliver a reliable migration and leave our team able to maintain the website independently. WHAT WE PROVIDE We are technically experienced and control all environments. We will provide: - Full WordPress access, including exports and API access. - Additional API or MCP access where justified. - Invitations to our GitHub repository and Sevalla environment. - Agreed AI tooling and credits. - Existing branding, content and consolidated feedback. All work must take place in our accounts and repository from day one. PREFERRED TECHNOLOGY STACK - Astro and TypeScript. - Tailwind CSS and reusable components. - Astro Content Collections with structured, Git-managed content. - React only where genuinely needed. - GitHub-based development, pull requests and automated checks. - Sevalla hosting with preview and production deployments. GitHub Copilot is our preferred development tool. Claude Code, Cursor or other coding agents may be used with prior approval. The tool is not the deliverable. We require maintainable code, documented workflows and a successful handover. Our team must be able to continue making changes using GitHub Copilot. Do not introduce a CMS, database, proprietary builder or paid dependency without approval. SCOPE OF WORK 1. INVENTORY AND WORKING PILOT - Inventory existing pages, articles, media, languages and integrations. - Identify custom fields, page-builder content, shortcodes and plugin functionality. - Import a representative service page and blog post, including images and metadata. - Preserve their existing URLs. - Deploy a working preview from our GitHub repository. - Confirm the remaining scope, exceptions and delivery plan. The pilot must demonstrate the actual migration and development workflow, not just a generic starter template. 2. WEBSITE FOUNDATION AND TEMPLATES - Build reusable homepage, service, blog and listing templates. - Implement responsive navigation and consistent shared components. - Reuse existing branding and content with a cleaner presentation. - Define structured content schemas and validation. - Include one consolidated design revision. This is not a full rebrand, unlimited redesign or copywriting engagement. 3. CONTENT AND SEO MIGRATION - Build a repeatable import process rather than manually copying every article. - Transfer all agreed content, images, downloads and existing translations. - Preserve existing public URLs, including language-specific routes. - Transfer available titles, descriptions and relevant SEO metadata. - Preserve relevant internal links and translation relationships. - Configure appropriate canonical URLs, indexing rules and sitemaps. - Report unsupported content and migration exceptions explicitly. Existing URLs should serve their corresponding migrated content directly. Redirects are for approved exceptions, not the default migration strategy. Do not silently omit, summarise or rewrite existing content. Provide a reconciliation report showing source items, migrated items and unresolved exceptions. 4. AGENT-FIRST BLOG PUBLISHING We publish a blog every two weeks. Deliver a practical workflow for: - Creating and updating articles through an agent. - Managing images, metadata and translations. - Reviewing changes through pull requests and website previews. - Approving and publishing content. - Scheduling publication, including the required deployment mechanism. Publishing an article should use an existing template, not require changes to application components. Repository instructions, scripts, tests and documentation must be included. Essential knowledge must not exist only in your private agent conversations. 5. VALIDATION, LAUNCH AND HANDOVER - Validate migrated URLs against the agreed inventory. - Check links, images, downloads and genuinely missing pages. - Test agreed forms and integrations end to end. - Validate agreed tracking and consent behaviour. - Perform mobile, accessibility and performance checks. - Complete the final content synchronisation and production launch. - Provide deployment, rollback and maintenance documentation. - Demonstrate that our team can independently publish a blog and make a small website change using GitHub Copilot. - Include a 14-day post-launch defect-fix period for failures against the agreed scope. A visually convincing homepage alone is not a completed migration. DELIVERY APPROACH We prefer a fixed-price, milestone-based engagement: 1. Paid pilot and scope confirmation. 2. Foundation and templates. 3. Content migration. 4. Publishing workflow and validation. 5. Launch and handover. Only the pilot will be committed initially. Subsequent milestones will be agreed after the pilot confirms the scope. Please propose your pricing per milestone, availability and realistic timeline. Our target is a working pilot within two working days of receiving access and overall delivery in approximately two to three calendar weeks. Explain any dependencies or scope factors that would change this. We expect AI-assisted development to improve efficiency. We do not expect testing, migration validation or engineering judgement to be skipped. WORKING EXPECTATIONS AND BOUNDARIES - Regular commits and reviewable pull requests in our repository. - No final-ZIP-only delivery. - You are responsible for reviewing and testing AI-generated code. - No production changes or destructive operations without approval. - No unapproved changes to existing URLs. - No credentials in source control or browser-delivered code. - No sharing access or subcontracting without written approval. - Additional AI tools, spending and data access require approval. - No uploading credentials or customer data to unapproved AI services. - No manual per-article migration fees for content covered by the agreed importer. - No additional charges or scope changes without written agreement. - No guaranteed SEO rankings or vague “fully optimised” claims. Propose measurable acceptance criteria. - Flag blockers and exceptions promptly rather than hiding them until delivery. REQUIRED EXPERIENCE This project requires practical experience with: - Astro and TypeScript. - WordPress extraction and content migration. - SEO-sensitive URL preservation. - Multilingual content. - GitHub deployment workflows. - Agentic development and automated validation. This should not be your first Astro implementation or first production migration. We welcome concise, project-specific proposals. Generic agency introductions without answers to the questions below will not be prioritised. No unpaid custom demonstration is required. The first milestone is a paid technical pilot.