Skip to main content
On this page

Dawnlight Changelog

4.2.0 - 2025-05-10

  • New i18n features!

    • New content collection localization capabilities, where individual blog posts in different languages can be linked with a mappingKey in the frontmatter. This allows content collections to be easily translated without needing to update the routeTranslations object each time!

      • This is accomplished in the new localizedCollections object
      src/config/translationData.json.ts
      /**
       * * Content collection translations used by the language switcher and hreflang generator
       *
       * Per-collection, per-locale route base mapping (collections to localize are the keys)
       *
       * If you have a key of "blog" then the blog content collection will be localized. This will look
       * for a "mappingKey" in the entry metadata, and use that to map the entry to the correct locale
       *
       * You can use the locale value to map the collection to a different route if desired
       *
       * Note: this does NOT affect the getLocalizedRoute() function. To translate the base routes use the routeTranslations object
       */
      export const localizedCollections = {
        blog: {
          en: "blog",
          fr: "blog",
        },
        // Add more collections/locales as needed
      } as const;

    • Add wildcard support in the routeTranslations object, allowing you to map multiple routes at once.

      • For example, you could route all English category routes /categories/* to the base French route of /categories
      src/config/translationData.json.ts
      /**
       * * Route translations are used to translate route names for the language switcher component
       * This can be useful for SEO reasons. The key does not matter, it just needs to match between languages
       *
       * ## Notes
       *
       * - These routes must be everything after the base domain. So if this is "atlas.com/blog", the route would be "blog"
       *   - Or if this is "atlas.com/legal/privacy", the route would be "legal/privacy"
       * - This also supports wildcards for language switcher and SEO purposes, and works in conjunction with the localizedCollections object below
       *   - For example, "categories/*" would match "categories/1" or "categories/2" etc for that language.
       */
      export const routeTranslations = {
        en: {
          overviewKey: "overview",
          categoryKey: "categories",
          categoryKey2: "categories/*",
          categoryKey3: "categories",
        },
        fr: {
          overviewKey: "apercu",
          categoryKey: "categories",
          categoryKey2: "categories",
          categoryKey3: "categories/*",
        },
      } as const;

    • You’ll also find a new getLocalizedRoute() function as a drop-in replacement for getRelativeLocaleUrl(). This is more flexible as it utilizes the routeTranslations object to auto-translate routes for you in components. You can use it like this:

      import { getLocaleFromUrl } from "@/js/localeUtils";
      import { getLocalizedRoute } from "@/js/translationUtils";
      

      const currLocale = getLocaleFromUrl(Astro.url);
      const route = getLocalizedRoute(currLocale, "/overview");
      // for the above routeTranslations, this would become "/fr/apercu" for French

    • Adjust existing i18n config script to account for additional features

  • Change from tailwindcss-animate to tw-animate-css package

  • Lock package versions to limit potential issues with new package updates

  • Improve Prettier and ESLint setup

  • Update to Astro 5.7.12

  • Update other dependencies

4.1.0 - 2025-04-01

  • Add eslint
  • i18n script fixes
  • Upgrade to Astro 5.5.5
  • Update other dependencies

4.0.0 - 2025-02-12

  • Upgrade to Tailwind CSS v4
    • Removed sass dependency as a result. Everything is now only CSS
  • Implemented my own CSS file for rendered markdown content, making it easier to understand and customize
    • Removed @tailwindcss/typography dependency as a result
  • Add a slew of extra components under src/components/starwind
  • Update code tours
  • Upgrade to Astro 5.3.0
  • Update other dependencies

3.0.0 - 2025-01-04

  • Upgrade to Astro 5.1.2
  • Add hreflang links as meta tags to improve SEO for multi-language websites
  • i18n script improvements when using one language only
    • script now removes all getRelativeLocaleUrl() and text translation uses, simplifying the code
  • Keystatic unistall script improvement - detects your package manager and uses the appropriate uninstall command
  • Upgrade astro-icon
  • Add data-astro-reload on language switcher component so that pagefind works right when using ClientRouter
  • Fix related posts so they only show related posts for the current language
  • pnpm support
    • added .npmrc file with a few settings to enable pnpm local builds
    • removed package-lock.json and replaced with pnpm-lock.yaml
      • If you install with npm install a normal package-lock.json file will be created
  • Update prettier config file to be more strict (and help remove potential script issues if your setup differs)
  • Change versioning structure to the more standard major, minor, patch
  • Update other dependencies

2.1 - 2024-11-21

  • New configuration scripts npm run config-i18n and npm run remove-keystatic
    • It is now incredibly easy to configure i18n features when starting a project, and remove keystatic features if desired
  • Enhance global.scss to remove usage of sass @import and use @use instead
    • The @import directive is being deprecated in Dart Sass and will be removed in future versions
  • Update playform/compress config setting to not optimize images or SVGs
    • In particular, using the image optimization here can dramatically increase build times for sites with many images, and astro:assets already handles it
  • Add vite config in astro.config.mjs to remove Dart Sass deprecation warning
    • This is not necessary, but it removes a minor annoyance
  • Updated NavLink.astro so that trailing slashes are removed from navbar links
    • This allows ID’s to be used in the navbar through the navData.json.ts files
  • Update README
  • Update to Astro 4.16.13
  • Update other dependencies

2.0 - 2024-09-28

  • Add all i18n features originally seen in Atlas
    • Language switcher component
    • Keystatic CMS support for multiple languages
    • Translate routes
    • Utility functions to:
      • Translate text
      • Filter content collections by locale
      • Format dates in the correct locale
      • Get the current locale from the current URL
      • & more
  • AffiliateLink.astro component now accepts more file extension variants for images when dynamically importing
  • Updated to Astro 4.15.9
  • Update other dependencies

1.0 - 2024-04-20

  • Initial release