@levino/[email protected]

Patch Changes

• 6cf308b: The yaml dependency is now correctly declared in package.json. This fixes build failures in clean environments (e.g., Docker) where transitive dependencies aren't available.

@levino/[email protected]

Patch Changes

• e9cdc63: You can now use a simpler CSS import syntax in your Tailwind CSS 4 setup. Instead of manually adding @source directives for each package, simply import the packages directly:

  @import "tailwindcss";
  
  @import "@levino/shipyard-base";
  @import "@levino/shipyard-blog";
  @import "@levino/shipyard-docs";
  
  @plugin "daisyui";
  @plugin "@tailwindcss/typography";

  Each package now includes its own @source directives, so Tailwind automatically scans the package components for CSS classes. This eliminates the need for path-based @source directives that could break in different project structures.

• Updated dependencies [e9cdc63]

• Updated dependencies [ed3ef9a]

  • @levino/[email protected]

@levino/[email protected]

Patch Changes

• e9cdc63: You can now use a simpler CSS import syntax in your Tailwind CSS 4 setup. Instead of manually adding @source directives for each package, simply import the packages directly:

  @import "tailwindcss";
  
  @import "@levino/shipyard-base";
  @import "@levino/shipyard-blog";
  @import "@levino/shipyard-docs";
  
  @plugin "daisyui";
  @plugin "@tailwindcss/typography";

  Each package now includes its own @source directives, so Tailwind automatically scans the package components for CSS classes. This eliminates the need for path-based @source directives that could break in different project structures.

• Updated dependencies [e9cdc63]

• Updated dependencies [ed3ef9a]

  • @levino/[email protected]

@levino/[email protected]

Minor Changes

• ed3ef9a: Upgrade to Tailwind CSS 4 and DaisyUI 5. This is a breaking change that requires migration from the old @astrojs/tailwind integration to the new @tailwindcss/vite plugin.

  Migration Guide:

  1. Update dependencies:

     • Replace @astrojs/tailwind with @tailwindcss/vite
     • Update tailwindcss to ^4
     • Update daisyui to ^5

  2. Update astro.config.mjs:

     // Before
     import tailwind from "@astrojs/tailwind";
     integrations: [tailwind({ applyBaseStyles: false })];
     
     // After
     import tailwindcss from "@tailwindcss/vite";
     vite: {
       plugins: [tailwindcss()];
     }

  3. Remove tailwind.config.mjs - no longer needed. Tailwind 4 uses CSS-first configuration.

  4. The globals.css now uses new CSS syntax with @import "tailwindcss" and @plugin directives.

  5. DaisyUI class renames:

     • avatar placeholder → avatar avatar-placeholder

Patch Changes

• e9cdc63: You can now use a simpler CSS import syntax in your Tailwind CSS 4 setup. Instead of manually adding @source directives for each package, simply import the packages directly:

  @import "tailwindcss";
  
  @import "@levino/shipyard-base";
  @import "@levino/shipyard-blog";
  @import "@levino/shipyard-docs";
  
  @plugin "daisyui";
  @plugin "@tailwindcss/typography";

  Each package now includes its own @source directives, so Tailwind automatically scans the package components for CSS classes. This eliminates the need for path-based @source directives that could break in different project structures.

@levino/[email protected]

Patch Changes

• f8a73a6: You can now create versioned documentation to maintain multiple versions of your docs side-by-side.

  Key features:

  • Configure multiple documentation versions (e.g., v1, v2, latest) with automatic URL routing
  • Version selector UI component displays in both navbar and sidebar for easy version switching
  • Mark versions as stable, deprecated, or unreleased with visual badges
  • Sidebar automatically filters to show only pages in the current version
  • Pagination stays within the same version boundaries
  • Support for a "latest" alias that always points to the current version
  • Automatic redirect from docs root to current version

  Getting started:

  // astro.config.mjs
  shipyardDocs({
    routeBasePath: "docs",
    versions: {
      current: "v2",
      available: [
        { version: "v2", label: "Version 2.0" },
        { version: "v1", label: "Version 1.0" },
      ],
      deprecated: ["v1"],
      stable: "v2",
    },
  });

  See the versioning guide for complete documentation.

• Updated dependencies [50fb3e5]

• Updated dependencies [f8a73a6]

  • @levino/[email protected]

@levino/[email protected]

Patch Changes

• 50fb3e5: Admonitions and other markdown features now work out-of-the-box without manual configuration. The shipyard integration automatically registers the required remark plugins (remarkDirective, remarkAdmonitions, remarkNpm2Yarn), so you no longer need to add them to your Astro config.

• f8a73a6: You can now create versioned documentation to maintain multiple versions of your docs side-by-side.

  Key features:

  • Configure multiple documentation versions (e.g., v1, v2, latest) with automatic URL routing
  • Version selector UI component displays in both navbar and sidebar for easy version switching
  • Mark versions as stable, deprecated, or unreleased with visual badges
  • Sidebar automatically filters to show only pages in the current version
  • Pagination stays within the same version boundaries
  • Support for a "latest" alias that always points to the current version
  • Automatic redirect from docs root to current version

  Getting started:

  // astro.config.mjs
  shipyardDocs({
    routeBasePath: "docs",
    versions: {
      current: "v2",
      available: [
        { version: "v2", label: "Version 2.0" },
        { version: "v1", label: "Version 1.0" },
      ],
      deprecated: ["v1"],
      stable: "v2",
    },
  });

  See the versioning guide for complete documentation.

@levino/[email protected]

Patch Changes

• c5e24d0: Add configurable footer with Docusaurus-like API

  You can now customize your site's footer with links, copyright notice, and styling. Shipyard supports both simple (single row) and multi-column footer layouts, similar to Docusaurus.

  Simple footer:

  shipyard({
    footer: {
      links: [
        { label: "Documentation", to: "/docs" },
        { label: "GitHub", href: "https://github.com/myorg/myrepo" },
      ],
      copyright: "Copyright © 2025 My Company.",
    },
  });

  Multi-column footer:

  shipyard({
    footer: {
      style: "dark",
      links: [
        {
          title: "Docs",
          items: [{ label: "Getting Started", to: "/docs" }],
        },
      ],
      copyright: "Copyright © 2025 My Company.",
    },
  });

  The footer also includes a "Built with Shipyard" branding link by default, which can be hidden with hideBranding: true.

@levino/[email protected]

Patch Changes

• 526e99f: You can now use shipyard with Astro's server mode (output: 'server') without needing to set prerender: false explicitly. Shipyard automatically detects the output mode and configures prerendering accordingly:

  • output: 'server' → SSR by default (no prerendering)
  • output: 'static' or output: 'hybrid' → prerendering by default

  This enables use cases like authentication middleware that needs access to request headers/cookies at runtime.

@levino/[email protected]

Patch Changes

• 5805704: Add prerender configuration option to disable prerendering for SSR sites with auth middleware

  You can now set prerender: false when configuring shipyard-docs to render docs pages on-demand instead of at build time. This is useful for SSR sites with authentication middleware that need access to Astro.request.headers or cookies.

  shipyardDocs({
    routeBasePath: "docs",
    prerender: false, // Required for SSR sites with auth middleware
  });

• Updated dependencies [cd94056]

• Updated dependencies [7086067]

  • @levino/[email protected]

@levino/[email protected]

Patch Changes

• 526e99f: You can now use shipyard with Astro's server mode (output: 'server') without needing to set prerender: false explicitly. Shipyard automatically detects the output mode and configures prerendering accordingly:

  • output: 'server' → SSR by default (no prerendering)
  • output: 'static' or output: 'hybrid' → prerendering by default

  This enables use cases like authentication middleware that needs access to request headers/cookies at runtime.