CDN Mapping

How local CDN files are stored, mapped, versioned, and validated.

Local File Storage

Local CDN files are stored under the public /cdn/ folder using this pattern:

/cdn/{library-slug}/{version}/{file-path}

Example:

/cdn/fontawesome/6.5.2/css/all.min.css

The public URL is generated by joining site.url from _config.yml with the local path:

https://cdn.itisuniqueofficial.com/cdn/fontawesome/6.5.2/css/all.min.css

Data Source

All listings are managed in _data/cdns.yml. Each entry must include name, slug, category, version, local_path, local_url, original_source_url, files, usage_html, license, fallback_note, tags, icon, and status.

Updating Versions

Never overwrite an existing version folder. Add a new folder instead:

/cdn/jquery/3.7.1/jquery.min.js
/cdn/jquery/3.8.0/jquery.min.js

Then add the new version to _data/versions.yml and create or update the matching entry in _data/cdns.yml.

Adding New Libraries

  1. Download the library from the official source or trusted package CDN.
  2. Place files under /cdn/{slug}/{version}/.
  3. Add the version to _data/versions.yml.
  4. Add a complete entry to _data/cdns.yml.
  5. Set local_url to https://cdn.itisuniqueofficial.com plus local_path.
  6. Run ruby scripts/validate-local-cdn.rb.
  7. Run jekyll build.

Avoiding Broken URLs

Keep every path in files, css_files, js_files, font_files, and local_path synced with an actual file in the repository. Font libraries often reference files with relative paths, so keep CSS and webfont folders in the same structure used by the original package.

Reliability Notes

Only mirror files that can safely run as static assets. Service-managed scripts that depend on account IDs, dynamic responses, or vendor-side runtime behavior should not be listed as local CDN files unless they are intentionally self-hostable.