Joe Ammann
5674fe005a
- Set up complete Hugo project structure with bilingual support (EN/DE) - Create custom pyx-theme with modern, clean design - Implement infinite scrolling single-page layout with sections - Style with white background, black text, and blue accent color - Add responsive navigation with smooth anchor scrolling - Move logo assets to static/images directory - Configure i18n translations for English and German (Swiss spelling) - Add company data structure in data/company.yaml - Create archetypes for consistent content frontmatter - Update CLAUDE.md with comprehensive project documentation Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
32 lines
1.9 KiB
Markdown
32 lines
1.9 KiB
Markdown
# Project Context: Pyx Engineering AG (Hugo Website)
|
|
|
|
## 1. Corporate Identity
|
|
* **Company:** Pyx Engineering AG
|
|
* **Industry:** IT Consulting Services / [ML ops, technologies like Kafka, Elasticsearch]
|
|
* **Tone of Voice:** Professional, precise, reliable, and high-quality (Swiss engineering standard).
|
|
* **Language:** Provide a multilanguage website in English (US) and German (CH) - *Note: Always use Swiss-German spelling (no "ß", use "ss").*
|
|
|
|
## 2. Technical Stack
|
|
* **SSG:** Hugo (v0.150 or newer))
|
|
* **Deployment:** manual deployment for now
|
|
* **Auth:** HTTPS access to Gitea repo on https://git.jammann.ch/joe/pyx-website
|
|
* **Styling:** logos available in EPS and PNG format. Choose whatever fits better
|
|
|
|
## 3. Content Architecture
|
|
* **Services:** Located in `/content/services/`. Each service should have a dedicated page.
|
|
* **Projects/References:** Essential for credibility. Format: Image, project scope, year, and services provided.
|
|
* **Frontmatter Requirements:** Every `.md` file must include: `title`, `description` (for SEO), `date`, and `thumbnail`.
|
|
* **Global Data:** Company address, phone, and UID are stored in `/data/company.yaml`.
|
|
|
|
## 4. Claude's Operational Guidelines
|
|
* **Hugo Best Practices:** Use `partials` for reusable elements (Header/Footer). Use `shortcodes` for UI components in Markdown files.
|
|
* **Image Handling:** Always use Hugo Resource Processing (`.Resize`, `.Fill`, `.Process "webp"`) to ensure fast load times.
|
|
* **Clean Code:** Keep layouts modular. Avoid hardcoding strings; use i18n or data files where possible.
|
|
* **SEO Focus:** Ensure proper `H1` to `H3` hierarchy. Meta descriptions should be concise and professional.
|
|
|
|
## 5. Current Roadmap & Tasks
|
|
- [ ] Initialize project structure and Hugo theme.
|
|
- [ ] Draft content for "About Us" and "Core Services".
|
|
- [ ] Implement Swiss-compliant Imprint (Impressum) and Privacy Policy.
|
|
|