From: Danilo M. Date: Wed, 22 Apr 2026 12:47:18 +0000 (+0200) Subject: Chore: updated CLAUDE.md for latest git procedures. X-Git-Tag: release_22042026-1447 X-Git-Url: https://git.danix.xyz/?a=commitdiff_plain;h=f25bb16223fa7321b3090437a4bafcadda38a837;p=danix.xyz-2.git Chore: updated CLAUDE.md for latest git procedures. --- diff --git a/CLAUDE.md b/CLAUDE.md index 35de8db..3afcf7c 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -34,7 +34,27 @@ DO NOT write code for shortcodes without consulting the user first. Implement: 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. -4. **Weekly Git Branching**: Each week of implementation work must start on a new feature branch named `week-N` (e.g., `week-3-cards-nav`). This allows code review and safe integration back into master at the end of each week. + +## 🔧 Git Workflow + +**Two repos, one site:** +- Content repo: `~/Programming/GIT/danix.xyz-hacker-theme/` → `danix_git:danix.xyz-2` +- Theme repo: `~/Programming/GIT/danix2-hugo-theme/` → `danix_git:danix2-hugo-theme` +- Theme lives as submodule at `themes/danix-xyz-hacker/` in content repo + +**Theme work:** +1. Edit in theme repo OR submodule (always `git checkout master` first if using submodule) +2. Commit and push to `danix2-hugo-theme` +3. Bump submodule pointer in content repo: `git add themes/danix-xyz-hacker && git commit -m "chore: bump theme submodule" && git push origin master` + +**CSS rebuild (after template changes with new Tailwind classes):** +1. From content repo root: `npm run build` +2. Commit compiled CSS in theme: `cd themes/danix-xyz-hacker && git add assets/css/main.min.css && git commit -m "build: recompile CSS" && git push origin master` +3. Bump submodule: `cd .. && git add themes/danix-xyz-hacker && git commit -m "chore: bump theme submodule (CSS rebuild)" && git push origin master` + +**Deployment:** +- Production hook clones latest `danix2-hugo-theme` master tip on each content push +- Theme changes deploy automatically on next content push (no submodule bump required for deployment, only for local tracking) ## 🎨 Styling & Build Pipeline - **Tailwind CSS**: Uses npm build pipeline with `tailwind.config.js`