[CI] Add Tailwind CSS build step to deployment workflow

[Copilot]

• Closes #

Changes proposed in this pull request:

• Add Node.js setup (v20) and npm install steps to cd.yaml
• Generate Tailwind output styles before deployment using npx tailwindcss build docs/stylesheets/tailwind.css -o docs/stylesheets/output.css
• Ensures docs/stylesheets/output.css is built from source during CI rather than committed to repo

Checklist

Please leave checkboxes empty for PR reviewers

• PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF]) see our Contributing Guidelines for more info)
• PR links to GitHub issue with mention Closes #XXXX
• Checks pass
• If an existing page was renamed or deleted, redirects have been added to the mkdocs.yml config

Original prompt

On cd.yaml, Update this workflow so that the tailwind output styles are generated before deployment using

npx tailwindcss build docs/stylesheets/tailwind.css -o docs/stylesheets/output.css

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[netlify]

✅ Deploy Preview for neurobagel-documentation ready!

Name	Link
🔨 Latest commit	98158cd
🔍 Latest deploy log	https://app.netlify.com/projects/neurobagel-documentation/deploys/691b762da768f60008541406
😎 Deploy Preview	https://deploy-preview-342--neurobagel-documentation.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[surchs]

@copilot Make sure that the output directory of the tailwind stylesheets matches the build directory of the mkdocs gh-deploy --force command. In other words: make sure that wherever the gh-pages site is being served from has access to the output.css file generated by the npx tailwindcss command. The current output path will not work.

[Copilot]

@copilot Make sure that the output directory of the tailwind stylesheets matches the build directory of the mkdocs gh-deploy --force command. In other words: make sure that wherever the gh-pages sit...

The current workflow is correct. The Tailwind CSS is built to docs/stylesheets/output.css before mkdocs gh-deploy runs. During the build process, mkdocs copies files from the docs/ directory to the site/ directory (which is then deployed to gh-pages). I verified this locally:

1. Tailwind builds to docs/stylesheets/output.css
2. mkdocs copies it to site/stylesheets/output.css during build
3. The home.html template references ../stylesheets/output.css, which correctly points to the copied file in the deployed site

The file is accessible in the gh-pages deployment.