## 📝 Work Protocol
1. **Pianification**: Propose the `i18n` structure and partials layout before writing.
2. **Consultation**: Always ask before implementing complex logic or shortcodes.
-3. **KISS**: Keep It Simple, Stupid.
\ No newline at end of file
+3. **KISS**: Keep It Simple, Stupid.
+
+## 🎨 Styling & Build Pipeline
+- **Tailwind CSS**: Uses npm build pipeline with `tailwind.config.js`
+- **CSS Compilation**: Run `npm run build` to compile `main.css` → `main.min.css`
+- **Watch Mode**: Run `npm run watch` during development to auto-rebuild CSS when templates change
+- **Required Before Commits**: Always rebuild CSS if you modify templates with new Tailwind classes (`npm run build`)
\ No newline at end of file
Who this is for:
- You are Danilo (danix), building a Hugo theme for your portfolio/blog site at danix.xyz. You're working with Claude Code to design and implement a bilingual (Italian/English), configuration-driven theme with a hacker/open-source asthetic, drawing visual inspiration from your existing danix.me site.
+ You are Danilo (danix), building a Hugo theme for danix.xyz. You've completed a comprehensive 32-task implementation across 8 phases with Claude Code assistance, creating a bilingual (Italian/English), configuration-driven hacker-themed portfolio/blog site. The theme is now production-ready.
What we covered:
- We completed a comprehensive design phase using visual brainstorming, creating detailed mockups and specifications for a Hugo theme. The design covers a landing page with hero and CTAs, bilingual navigation with hamburger overlay menu, 5 article types (Life, Photo, Link, Quote, Tech) with distinct color badges, dark/light theme toggle, responsive sidebar (sticky on desktop, bottom on mobile), Feather Icons system, and 4 shortcodes (gravatar, image, gallery, contact-form). We then created a 32-task implementation plan organized into 8 phases, with comprehensive documentation. You chose subagent-driven development to execute the plan. Phase 1 (Tasks 1-3) scaffolded the theme directory structure, theme.toml metadata, and hugo.toml site configuration. Phase 2 (Tasks 4-7) created all base templates: baseof.html with theme persistence, responsive header.html with logo, hamburger-menu.html with Alpine.js state management, and footer.html with dynamic links.
+ You completed all 32 implementation tasks organized into 8 phases: Phase 1 scaffolded the theme directory and configuration (3 tasks), Phase 2 created base templates for layout structure (4 tasks), Phase 3 built styling and JavaScript functionality (5 tasks including CSS with dark/light themes and menu/theme toggle scripts), Phase 4 created internationalization files for Italian and English (2 tasks with 40 key translation pairs each), Phase 5 developed page templates for landing page, article lists, and single articles (4 tasks), Phase 6 created 5 article type-specific templates (Life, Photo, Link, Quote, Tech) plus a dispatcher (6 tasks), Phase 7 built 4 reusable shortcodes (Gravatar, Image, Gallery, Contact Form) plus a PHP placeholder (4 tasks), and Phase 8 finalized documentation (2 tasks creating SHORTCODES.md with 283
+ lines and updating AGENTS.md with 444 lines of content management guide).
What was confirmed:
- The design spec is saved at docs/superpowers/specs/2026-04-15-hugo-theme-design.md and covers all requirements: bilingual i18n, 5 article types with color mappings, responsive layouts with sticky sidebar, Feather Icons, dark/light theme toggle with localStorage, WCAG 2.1 AA
- accessibility target, and configuration-driven structure in hugo.toml. The implementation plan is saved at docs/superpowers/plans/2026-04-15-hugo-theme-implementation.md with all 32 tasks fully specified with code, commands, and expected outputs. SHORTCODES.md and AGENTS.md
- documentation have been created and committed. Phase 1 and Phase 2 are fully complete with 6 commits (theme structure, theme.toml, hugo.toml, baseof.html, header.html, hamburger-menu.html, footer.html).
+ The complete theme architecture is documented in CLAUDE.md (35 lines) with Slackware-style philosophy instructions. The design specification and 32-task implementation plan were previously created and saved. All 52 feature/fix commits were made with proper messages. The theme includes 50+ files: multiple layout templates, 3 JavaScript files for theme/menu/language functionality, 2 CSS files (main.css with Tailwind and theme variables, chroma-custom.css for syntax highlighting), 4 shortcodes, Italian and English i18n files with identical key structures, responsive design targeting WCAG 2.1 AA accessibility, and comprehensive documentation. The theme supports 5 article types, dark/light theme switching with localStorage persistence, bilingual navigation, Feather Icons integration, Alpine.js for interactivity, and Tailwind CSS styling.
Still in progress:
- Phase 3 (Tasks 8-12) on styling and JavaScript has not yet been started. This phase includes creating main.css with Tailwind directives and CSS custom properties, chroma-custom.css for syntax highlighting, and three JavaScript files for theme toggle, menu toggle, and language switcher persistence. Phases 4-8 remain to be executed: i18n files, page templates, article type templates, shortcodes, and documentation updates.
+ Nothing was left open in this session. All 32 tasks were completed and committed.
Next steps:
- Continue with Phase 3 (Tasks 8-12) by dispatching a subagent to create the CSS files (main.css and chroma-custom.css) and JavaScript files (theme-toggle.js, menu.js, language-switcher.js) with full commits. After Phase 3, proceed through Phases 4-8 in order using the same subagent-driven approach: Phase 4 creates i18n files, Phase 5 creates page templates (landing, articles list, single article, sidebar), Phase 6 creates article type-specific templates, Phase 7 creates the four shortcodes, and Phase 8 finalizes documentation. After all 32 tasks are complete, use superpowers:finishing-a-development-branch to finalize and prepare for merge.
+ In the next session, you should implement the contact.php backend to handle form submissions (email sending, validation, honeypot), create sample content bundles in Italian and English to populate the theme with articles, configure DNS to point danix.xyz to your hosting, deploy the Hugo theme to production, test the bilingual navigation end-to-end to verify language switching works correctly, conduct a performance review using Lighthouse and PageSpeed audits, and set up SEO infrastructure (sitemap.xml, robots.txt, meta tags). You may also want to create a final git tag for version 1.0 and generate a theme README if not already done.
\ No newline at end of file
--- /dev/null
++++
+title = "about danix.xyz"
+author = "Danilo M."
+type = "page"
+draft = false
+date = "2009-06-01T22:04:43+00:00"
++++
+
+{{< gravatar mail="danixland@gmail.com" class="image right circle" size=250 >}}
+
+Welcome to danix.xyz, my name is Danilo but you can call me danix.
+
+What is this website? Well, **danix.xyz** is my personal website, in here you can read about everything I find interesting, you'll find the code I write, WordPress plugins or themes, php or bash scripts that I use on my systems, and programs that I find interesting.
+
+I use this website to keep track of all the snippets of code that I tend to forget, I consider this website like my notepad (in the hope that it can turn useful to somebody else).
+
+I deeply dislike sharing readers data with other companies so you can be sure that I don't collect any data from my readers. I've setup hugo not to track my readers and to instruct other sites referenced on my pages to do so as well.
+
+Read more about [my Privacy Policy]({{< ref "legal" >}} "Privacy Policy here at danix.xyz").
