Skip to content

Instantly share code, notes, and snippets.

@rakia
Last active May 14, 2026 12:47
Show Gist options
  • Select an option

  • Save rakia/f6a266c196cfacc510e66c27f8fc5a43 to your computer and use it in GitHub Desktop.

Select an option

Save rakia/f6a266c196cfacc510e66c27f8fc5a43 to your computer and use it in GitHub Desktop.
Tasks.md generated by OpenSpec

1. Environment & Base Setup

  • 1.1 Initialize Astro project with Tailwind CSS integration (latest versions).
  • 1.2 Configure tailwind.config.mjs with the redesigned theme colors (#f5f1ea, #1a1612, #c2410c) and Fraunces font.
  • 1.3 Setup Astro's native i18n for English (EN) and German (DE) routing and content.
  • 1.4 Define the base Astro layout using Tailwind's container and grid utilities.

2. Global UI Components (Astro)

  • 2.1 Implement the redesigned Header as an Astro component with Tailwind responsive classes.
  • 2.2 Implement the redesigned Footer as an Astro component with Tailwind utility styling.
  • 2.3 Create the primary and secondary CTA Button components using Tailwind's component pattern.

3. Specialized Layout Components (Astro)

  • 3.1 Implement the redesigned Hero component extracting SVG assets from the redesign file.
  • 3.2 Implement the Service Card component using Tailwind for hover effects and transitions.
  • 3.3 Implement the Metric Block component for company statistics.
  • 3.4 Implement the Client Logo Slider (using minimal JS or an Astro-compatible library if needed).

4. Page Assembly & Content Collections

  • 4.1 Define Astro Content Collections for Services, About, and Insights content.
  • 4.2 Assemble the Home page (index.astro) for both /en/ and /de/ locales.
  • 4.3 Implement dynamic routes for detailed Service pages and Insights.
  • 4.4 Implement the About Us page, migrating content into the new Astro structure.
  • 4.5 Implement the Contact page with integrated booking widget (client-side hydration if needed).

5. Final Verification & Launch Readiness

  • 5.1 Perform responsive design validation across mobile, tablet, and desktop viewports.
  • 5.2 Conduct a full content audit against https://engforge.com/ to ensure no data loss.
  • 5.3 Verify accessibility standards (ARIA labels, color contrast) for the new design.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment