Skip to content

Remove PostCSS, use standalone Tailwind CSS CLI#160

Open
diamantidis wants to merge 7 commits intosourcefrom
remove-postcss-use-tailwind-cli
Open

Remove PostCSS, use standalone Tailwind CSS CLI#160
diamantidis wants to merge 7 commits intosourcefrom
remove-postcss-use-tailwind-cli

Conversation

@diamantidis
Copy link
Copy Markdown
Owner

Plan

  • Replace jekyll-postcss + PostCSS pipeline with standalone Tailwind CSS CLI
  • Create assets/css/input.css with @tailwind directives and @apply rules (moved from _scss/custom.scss)
  • Add dev:css (watch) and build:css (minify) npm scripts
  • Remove postcss, cssnano, and jekyll-postcss dependencies
  • Delete postcss.config.js
  • Update CI/CD workflows to run npm run build:css before Jekyll build
  • Update documentation (AGENTS.md) for new two-process dev workflow

Tests

  • Playwright smoke test: PASS
    • Home page loads correctly with post listings and navigation
    • Blog post page loads with title, content, and metadata
    • Static pages (About, Archive, Tags) render correctly
  • npm run build:css produces valid minified Tailwind output
  • JEKYLL_ENV=production bundle exec jekyll build succeeds

Replace PostCSS pipeline with standalone Tailwind CLI. Add input.css
with @tailwind directives and @apply rules, add dev:css and build:css
scripts, remove postcss and cssnano dependencies.
Remove jekyll-postcss gem and its configuration (postcss cache setting,
exclude entry for postcss.config.js) since Tailwind is now built via
standalone CLI.
Delete PostCSS config file. Move @layer utilities block with @apply
directives from _scss/custom.scss to assets/css/input.css since @apply
only works within the Tailwind CLI build pipeline.
Add assets/css/main.css to .gitignore since it is now a build artifact
generated by the Tailwind CLI.
Add 'npm run build:css' step before Jekyll build in both ci.yml and
github-pages.yml to ensure Tailwind CSS is compiled before site build.
Replace all jekyll-postcss/PostCSS references with standalone Tailwind
CLI instructions. Document two-process dev workflow with CSS watcher,
PID-based process management, and livereload.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 13, 2026

Proselint found issues

AGENTS.md

Line Message Severity
228 'off' is the preferred form. warning

Spell Checker found issues

AGENTS.md

Line Typo
1 # AGENTS.md - Guide for Agentic Software
1 # AGENTS.md - Guide for Agentic Software Development
5 Ioannis Diamantidis's personal blog —
5 Ioannis Diamantidis's personal blog — a software de
5 tic site generator) using the minima theme and styled with a combi
7 Technology Stack*: Jekyll + minima theme + Tailwind CSS (standal
7 CSS (standalone CLI) + Ruby + Node.js
69 - Analytics: TelemetryDeck and PostHog
69 - Analytics: TelemetryDeck and PostHog (production envir
69 nalytics**: TelemetryDeck and PostHog (production environment only)
70 tHub Actions CI with Danger + proselint for prose linting on PRs
71 - SEO: jekyll-sitemap, jekyll-feed, and jekyll-seo-
71 - SEO: jekyll-sitemap, jekyll-feed, and jekyll-seo-tag
71 yll-sitemap, jekyll-feed, and jekyll-seo-tag
81 - Node.js 22.2.0
130 tcher in Terminal 1 (creates .css-watcher.pid)
130 minal 1 (creates .css-watcher.pid)
132 r on available port (creates .jekyll.pid)
164 lwind CSS standalone CLI (not PostCSS or jekyll-postcss).
164 tandalone CLI (not PostCSS or jekyll-postcss).
169 le**: assets/css/main.cssgitignored, generated by the CLI
170 - Dev script: npm run dev:css
190 aded with title, content, and metadata
220 ## Git Workflow with gh-cli
298 ### Useful gh-cli Commands

Generated by 🚫 Danger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant