bryancall opened a new pull request, #7:
URL: https://github.com/apache/trafficserver-site/pull/7

   ## Problem
   
   The new site at https://trafficserver.apache.org/newsite/ was displaying 
without any styling (plain unstyled HTML). 
   
   **Root Cause:** Apache's Content Security Policy (CSP) blocks external 
script sources. The CSP only allows scripts from:
   - `'self'`
   - `*.apache.org`
   - `apache.org`
   - A few other whitelisted domains
   
   Since `cdn.tailwindcss.com` is not in the allowed list, the browser blocked 
the Tailwind CSS CDN script, causing the site to render without any styles.
   
   ## Solution
   
   Replaced the external Tailwind CSS CDN with a locally-hosted CSS file.
   
   ### Changes:
   - ✅ Created `content/newsite/styles/tailwind-base.css` with all necessary 
Tailwind utilities
   - ✅ Removed CDN `<script>` tags from all 6 HTML pages
   - ✅ Added local CSS `<link>` tags instead
   - ✅ Includes all utility classes used across the site (responsive, colors, 
typography, layouts, etc.)
   - ✅ Maintains full responsive design functionality
   - ✅ No external dependencies
   
   ### Files Modified:
   - `content/newsite/index.html`
   - `content/newsite/downloads.html`
   - `content/newsite/users.html`
   - `content/newsite/press.html`
   - `content/newsite/acknowledgements.html`
   - `content/newsite/assistance.html`
   - `content/newsite/styles/tailwind-base.css` (new file)
   
   ## Testing
   
   After this fix, the site should render properly with all modern styling, 
gradients, responsive layouts, and hover effects working as designed.
   
   The local CSS file is fully compliant with Apache's CSP and will load 
without being blocked.
   
   ## Impact
   
   - ✅ Fixes styling on production site
   - ✅ No functional changes to the site
   - ✅ CSP compliant
   - ✅ Faster load time (one less external request)
   - ✅ No breaking changes


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to