v1.0.5

Patch Changes

• 4b1ea0d: Fixes the BreadcrumbList format used in Schema.org structured data.

v1.0.4

Patch Changes

• 1099999: Enables the customization of the cover position for content collections that supports a cover.

  A new position property is available in the cover object for content collections accepting a cover. The value should match the tokens supported by the CSS object-position property (only strings like top, left, etc. are supported).

• 1099999: Removes alt text for decorative images.

  The collections entries using a cover no longer accepts an alt property to define the alternative text of the images. Those are purely decorative so they shouldn't be announced to screen readers.

• a49c607: Fixes an issue where pagination styles was overridden by other styles in production.

  The CSS order seems a bit inconsistent between development and production modes. The style for pagination links was not correctly applied to the built website.

• 1099999: Readjusts the cover dimensions.

• 6165c62: Removes links pointing to the current page.

  Some pages (tags, categories) was linking to themselves. This removes those useless links.

v1.0.3

Patch Changes

• 076b0ad: Fixes an issue where OG images could be malformed because of a trailing slash in the path.

v1.0.2

Patch Changes

• 9f87ca4: Fixes an issue where CONTENT_PATH was no longer defined when using this project as a Git submodule.

v1.0.1

Patch Changes

• f048cca: Removes the notes from the global feed.

  I'm using them as "personal" notes so I think they shouldn't be in the feed. If someone wants to subscribe to my notes, it's still possible using the individual feed.

• 20e4205: Fixes a style issue in code blocks preventing the line numbers and prompts to stay sticky while scrolling horizontally.

• 7720df5: Adds missing cover on individual pages (posts, guides and projects).

• 20e4205: Fixes a style issue when using diff notation inside code blocks.

  This fixes an issue where the lines marked as diff were not taking the full width of their parent, so the background was not displayed correctly.

• 0da391f: Improves the differentiation of RSS items by prefixing their title with the content type.

  Since I have some collections that target external resources (e.g. "John Doe" being in the blog roll), it might be confusing for someone subscribed to the RSS feed to see only "John Doe". By prefixing the title with the content type (e.g. "[Blogroll] John Doe"), it should prevent any confusion.

• 20e4205: Fixes the text alignment inside code blocks' caption.

• 993be5e: Fixes a style issue in callouts where the last child could add an extra margin.

• 7720df5: Fixes images performance by using picture and srcset.

  This enables the experimental responsiveImages feature of Astro in addition to wrapping all images in a picture element to provide multiple sources. This also adds a srcset attribute to images to try to please a bit more Lighthouse.

• 993be5e: Fixes a style issue in callouts where a long heading was not correctly aligned with the icon.

v1.0.0

Major Changes

• 3967fcc: Sets French version as the default language.

Minor Changes

• 1d920ee: Adds all (global + per collection) RSS feeds.

• 1349da2: Adds support for custom components in MDX without the need of imports.

  Here a list of the syntax automatically mapped to a custom component:

  Markdown/HTML	Component
  a	Link
  blockquote	Blockquote
  callout	Callout
  div	Placeholder
  figure	Figure
  h2	H2
  h3	H3
  h4	H4
  h5	H5
  h6	H6
  img	Img
  li	ListItem
  ol	Ol
  ul	List

  The use of div is a bit special: according to its class, it could be a custom component or a div. For example, when using gallery as class, the div will be replace with a Grid component.

• e9314a4: Upgrades to Astro v5.

• 3967fcc: Adds French version.

• 4af7172: Replaces static rendering with hybrid rendering to support API endpoints.

  This project now uses Node.js adapter to handle on-demand pages like API endpoints.

• e1efe03: Adds a Search page.

• f700427: Adds queryCollection and queryEntry helpers to reduce boilerplate code when querying collections entries.

  Instead of using directly the getCollection helper from Astro, you should use the queryCollection helper declared in this project. This function helps you query a collection with filters, offset and ordering. queryCollection will also resolves every references!

  You can also use it if you need to resolve multiple collections at once or you can use queryEntry to resolve a single entry.

  You can now reduce the amount of code in your templates:

  ---
  import { queryCollection } from "src/lib/astro/collections/query-collection";
  const { entries, total } = await queryCollection("blogPosts", {
    first: 10,
    orderBy: { key: "publishedOn", order: "DESC" },
  });
  ---
  
  // Your template here

  Instead of:

  ---
  import { getCollection, getEntries, getEntry } from "astro:content";
  const rawBlogPosts = await getCollection("blogPosts");
  const blogPosts = await Promise.all(
    rawBlogPosts.map(async (blogPost) => {
      const category = blogPost.data.category
        ? await getEntry(blogPost.data.category)
        : null;
      const tags = blogPost.data.tags
        ? await getEntries(blogPost.data.tags)
        : null;
      return {
        ...blogPost,
        data: {
          ...blogPost.data,
          category,
          tags,
        },
      };
    }),
  );
  const orderedBlogPosts = blogPosts.sort(/* some method to sort posts */);
  const firstTenBlogPosts = orderedBlogPosts.slice(0, 10);
  ---
  
  // Your template here

• 5a080c0: Adds support for dev-only pages.

  To use this feature, you need to add a new integration in your configuration file:

  import { defineConfig } from "astro/config";
  +import { devOnlyPages } from "./src/lib/astro/integrations/dev-only-pages";
  
  export default defineConfig({
  +  integrations: [
  +    devOnlyPages({
  +      prefix: "_dev_",
  +    }),
  +  ],
  });

  You can now create pages without adding them to the final build by using the _dev_ prefix. To access those pages in your browser, just use the filename without the prefix (e.g. /src/pages/_dev_design-system can be accessed using /design-system as slug).

• 5a080c0: Adds CSS tokens for colors, borders, fonts, spacings and shadows.

  Instead of using fixed values in your components and layouts styles, you should use tokens. This ensures harmonization within the site for colors, spaces, fonts, etc. Also, this is easier to update if needed.

  ---
  ---
  
  <button class="btn"><slot /></button>
  
  <style>
      .btn {
  -        padding: 1rem;
  -        background: #fff;
  -        border: 1px solid #ccc;
  -        font-size: 16px;
  +        padding: var(--spacing-md);
  +        background: var(--color-regular);
  +        border: var(--border-size-sm) solid var(--color-border);
  +        font-size: var(--font-size-md);
      }
  </style>

• d8654ed: Adds a PageLayout component to define global structure and styles for pages.

• 508521e: Adds Schema.org structured data.

• 5dd33bf: Adds support for switching theme between light and dark.

  ou can choose to use either a light, a dark theme or to let the theme being updated according to your OS preferences. This feature is especially useful when you want to change the theme depending on the time of day.

• 2000005: Adds support to redirect to a translated page using the language picker.

  Previously, when using the language picker, the user was redirected to the homepage of the selected locale. Now, it is possible to redirect to the matching translated page.

  For example, if an user lands on /en/blog/posts, he can switch to /fr/blog/articles instead! If a translated route is not provided, the user will be redirected to the homepage of the selected locale.

• 3a62260: Adds a Remark plugin to retrieve the words count from Markdown files.

  This plugin allows the calculation of a new reading time meta using the number of words in a Markdown file.

• 1d5eea9: Adds the website navbar.

  A stub was previously here. This adds the popover functionality and the different behavior depending on the viewport size.

• 6556bab: Adds independent theme mode support for code blocks.

  A new setting is available in the website header and in each code block to update the theme used for code blocks. This allows users to use a light theme for the website and a dark theme for the code blocks, and conversely. It is also possible to infer the code block theme from the website theme when set to Auto.

• 6bd1f12: Defines content collections schemas.

  The following collections are now available: authors, blogroll, bookmarks, blogCategories, blogPosts, guides, notes, projects and tags. To define contents for these collections, your content directory should use the following structure:

  content/
  ├── authors/
  │   └── john-doe.json
  ├── blogroll/
  │   ├── index.md
  │   └── blog1.json
  ├── bookmarks/
  │   ├── index.md
  │   └── bookmark1.json
  └── en/
      ├── blog/
      │   ├── categories/
      │   │   ├── index.md
      │   │   └── category1.md
      │   ├── posts/
      │   │   ├── index.md
      │   │   └── post1.md
      │   └── posts/
      ├── guides/
      │   ├── index.md
      │   └── guide1.md
      ├── notes/
      │   ├── index.md
      │   └── note1.md
      ├── pages/
      │   ├── home.md
      │   └── search.md
      ├── projects/
      │   ├── index.md
      │   └── project1.md
      └── tags/
          ├── index.md
          └── tag1.md
  

  There are two types of pages available:

  • the pages co-located with your collection (to provide meta and optional content for the index page) named index.md
  • the ones located in the pages directory and that can use any filename

• 15a3611: Adds support for i18n.

  This project now exports a useI18n() function to help you translating all the UI strings and routes. It accepts a locale as argument and returns a validated locale (which fallback to default locale) and three methods:

  • translate(): to help you translate UI strings
  • translatePlural(): to help you translate UI strings while dealing with pluralization
  • route(): to help you localize the routes.

  Both translate() and translatePlural() support interpolations by providing an object as second argument. For example:

  import { useI18n } from "src/utils/helpers/i18n";
  
  const { locale, route, translate, translatePlural } = useI18n("en");
  console.log(locale); // "en"
  
  const contactPage = route("contact");
  console.log(contactPage); // "/contact"
  
  const contactPageFr = route("contact");
  console.log(contactPageFr); // If "fr" is defined and default locale is "en", "/fr/contact". Else "/contact";
  
  const greeting = translate("greeting", { name: "John" });
  console.log(greeting); // "Hello, John!";
  
  const threePeopleLike = translatePlural("people.likes", { count: 3 });
  console.log(threePeopleLike); // "3 people like this post"
  
  const noLikes = translatePlural("people.likes", { count: 0 });
  console.log(noLikes); // "No one like this post yet"

• b63d9f9: Adds a Layout component to define global structure and styles.

• 6556bab: Adds a custom CodeBlock component.

  The CodeBlock component should be used instead of the Astro default one. It provides the following features:

  • snippet file path
  • prompt for shell and sql sessions with custom user/host
  • line numbers with custom line start if needed
  • diff notation
  • light/dark theme switch
  • copy to clipboard button

• 85b350c: Adds support for callouts/asides in MDX.

  When using MDX format, you can use a directive for your callouts (or admonitions, asides) for example:

  :::warning
  The contents of the warning.
  :::

  Both custom titles and attributes are supported:

  :::idea[My custom tip]{ariaLabel: "An accessible label for my tip"}
  The contents of the tip.
  :::

  Here are the supported callouts type: "critical", "...