Skip to content
CAI
Software that uses CAICheck a score

bridgetownrb/bridgetown

45.9

Weak · 6 November 2026

16.7k

lines of production code

Ruby

primary language

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Bridgetown is a modern, Ruby-based static site generator that replaces legacy Jekyll tooling with a flexible, component-driven architecture. It supports multiple templating engines including Liquid, ERB, and Serbea, and features a robust plugin system via Builders for extending the build lifecycle. The framework integrates native server-side rendering through Roda, automated frontend asset bundling with esbuild, and comprehensive features for pagination, localization, and dynamic routing.

How it got here

2020 — Bridgetown core migration and rewrite

49 changes.

The project underwent a comprehensive migration from Jekyll to Bridgetown, involving the removal of legacy Jekyll codebases, test suites, and tooling. This period established the new Bridgetown core architecture, including a rewritten CLI, modular site logic, and a new builder plugin system. It also introduced modernized development workflows, updated site templates, and essential features like pagination and caching.

2021–2022 — Roda server and Serbea templating integration

39 changes.

This period focused on overhauling the server infrastructure by migrating to a Roda-based architecture with file-based dynamic routing and server-side rendering. It introduced the Serbea templating engine as a first-class citizen, replacing ad-hoc startup mechanisms with a structured Rack layer and signal-based fast refresh. The work also expanded the ecosystem with bundled configurations for modern frontend tools like Lit and esbuild, while standardizing CLI tasks and test coverage for the new routing and data model systems.

2023–2024 — Front matter refactoring and foundation updates

5 changes.

This period focused on restructuring front matter handling by introducing a modular loader system that supports both YAML and Ruby-based definitions, enabling dot-access defaults. Concurrently, the project replaced Active Support dependencies with in-house Ruby refinements and core extensions in Bridgetown Foundation to reduce external coupling. The work also included adding test coverage for nested route rendering and updating the YARD documentation theme.

Features

Add bundled Cypress integration testing configuration

Bridgetown now includes a pre-configured Cypress setup for integration testing. This adds a \cypress.json\ configuration pointing to the local server, along with example test files (including a navbar link test), fixtures, and support files. It also introduces Rake tasks (\cy:open\, \cy:run\, \cy:test\, \cy:test:ci\) that use NPM to launch the Cypress runner or run tests headlessly, automatically starting and stopping the Bridgetown server in test mode.

bridgetown-core/lib/bridgetown-core/configurations/cypress · high confidence

Add new Bridgetown Center and 2022 logo assets

The website now includes new SVG assets for the Bridgetown Center program (\bridgetown-center.svg\) and the updated 2022 brand logo (\bridgetown-logo-2022.svg\). These files are added to the \src/images\ directory to support the new program and updated branding.

bridgetown-website/src/images · high confidence

Added CI and testing helper scripts

The bridgetown-builder project now includes a set of shell and Ruby scripts to streamline local development and continuous integration workflows. The new \script/cibuild\ script automates the CI pipeline by running formatting checks and tests. The \script/fmt\ script executes Rubocop for code style enforcement and suggests using the \-a\ flag for auto-correction. The \script/test\ script provides a convenient way to run the test suite via Rake or execute specific test files directly, while also cleaning up the test destination directory before running. Additionally, \script/minitest\ is included to facilitate running Minitest tests through Bundler.

bridgetown-builder/script · high confidence

Added bridgetown CLI binstubs

Added \bin/bridgetown\ and \bin/bt\ executable scripts to the project. These binstubs facilitate running the \bridgetown\ command-line interface by loading the \bridgetown-core\ gem, ensuring consistent execution environments for site management tasks.

bridgetown-website/bin · high confidence

Added bundled Render configuration template

A new bundled configuration file (render.yaml.erb) is now included to simplify deploying Bridgetown sites to the Render platform. This template provides a pre-configured static web service setup, including build commands, static publish paths, and essential security headers (such as X-Frame-Options and Strict-Transport-Security). It also sets the BRIDGETOWN\_ENV to production and includes commented-out examples for hybrid deployments, database integration, and API services, allowing users to easily adapt the configuration for more complex needs.

bridgetown-core/lib/bridgetown-core/configurations/render · high confidence

Added site builder template for custom plugin development

The site template now includes a \SiteBuilder\ class and a \builders\ directory, providing a structured starting point for users to create custom builders that subclass \SiteBuilder\ within their plugins.

_bridgetown-core/lib/site\template/plugins · high confidence

Bridgetown core library initialization and configuration

The \bridgetown-core/lib/bridgetown-core.rb\ file establishes the main entry point for the Bridgetown static site generator. It configures the Ruby load path, requires essential standard library modules (such as \net/http\, \yaml\, \json\), and loads third-party dependencies including Liquid, Kramdown, I18n, and Faraday. The file sets up I18n fallbacks, defines a \HashWithDotAccess\ helper for Liquid template compatibility, and implements the \Bridgetown\ module's core methods for managing environment detection, configuration loading (merging defaults with user config), and preflight setup. It also autoloads key classes like \Site\, \Component\, \PluginManager\, and various readers/generators, effectively wiring together the framework's internal architecture.

bridgetown-core/lib · high confidence

Introduce Model and Origin abstractions for data resources

Bridgetown now provides a new \Bridgetown::Model\ API that allows site builders to treat data files (YAML, JSON, CSV, TSV, Ruby) as first-class model objects. The \Model::Base\ class offers methods to find, save, and convert data into resources, while the \Origin\ hierarchy (\RepoOrigin\, \PluginOrigin\, \BuilderOrigin\) handles reading from and writing to various data sources, including the local filesystem and external manifests.

bridgetown-core/lib/bridgetown-core/model · high confidence

Introduce Prototype Pages for dynamic paginated archives

Users can now define 'prototype' pages in front matter to automatically generate paginated archive pages for categories, tags, or other collection values. This new \PrototypeGenerator\ creates dynamic pages based on a template, handling pagination configuration and title placeholders (such as \:prototype-term-titleize\ and \:prototype-data-label\) out of the box, while integrating with the site's fast-refresh mechanism for development.

bridgetown-core/lib/bridgetown-core/generators · high confidence

Introduce bridgetown-paginate gem for content pagination

The new bridgetown-paginate gem provides a comprehensive pagination system for Bridgetown sites. It allows users to paginate collections of content (such as posts or custom collections) by configuring options like items per page, sorting, and filtering by categories, tags, or locales. The gem integrates via site and page hooks to automatically generate paginated pages, supports customizable URL structures and titles, and exposes a \paginator\ object in templates to navigate through pages, view page trails, and access the current set of documents.

bridgetown-paginate · high confidence

Introduce file-based dynamic routes via Roda server template

The site template now includes a \RodaApp\ class and a sample route file (\routes/hello.rb.sample\) to enable file-based dynamic routing. Users can define custom server-side routes by placing Ruby files in the \server/routes\ directory, which are loaded via the \bridgetown\ Roda plugin, allowing for fast, dynamic application logic in both development and production.

_bridgetown-core/lib/site\template/server · high confidence

Introduces Builder plugin system with priority-based execution

The library now registers a \pre\_read\ hook that discovers and instantiates Builder plugins (including those from \PluginBuilder\ and \SiteBuilder\ descendants), sorting them by priority before execution. It also adds a \pre\_reload\ hook to clean up anonymous generator classes to support autoreloading.

bridgetown-builder/lib · high confidence

Introduction of a new persistent caching system and site cleanup logic

Bridgetown now includes a new \Bridgetown::Cache\ class that provides both in-memory and on-disk caching for site data, with the ability to automatically clear caches when the configuration changes. Additionally, a new \Bridgetown::Cleaner\ class handles the removal of obsolete files from the destination directory before each build, ensuring that only current site assets are published.

bridgetown-core/lib/bridgetown-core · high confidence

New Builder DSL modules for generators, helpers, hooks, and resource management

The builder DSL now includes dedicated modules for defining generators, template helpers, build hooks, and dynamic resources. Users can use the \generator\ DSL to register custom generators that inherit builder priority, \helper\ to expose builder methods as view helpers, \hook\ to register site or resource lifecycle hooks with priority, and \add\_resource\ to dynamically create resources within collections. Additionally, \define\_resource\_method\ allows extending resource classes with custom methods, and \permalink\_placeholder\ enables custom permalink processing. These changes provide a more structured and explicit API for extending build behavior compared to previous implicit or less-organized approaches.

bridgetown-builder/lib/bridgetown-builder/dsl · high confidence

New CLI automation helpers and configuration overrides

The CLI now includes new command concerns to streamline site setup and configuration. The \Automations\ module provides helpers for creating site builders, managing JavaScript imports, adding Ruby gems and NPM packages, and applying remote automation scripts. A new \BuildOptions\ concern standardizes CLI flags for build commands, including options for custom source/destination directories, plugins, layouts, and verbose output. The \ConfigurationOverridable\ concern allows environment-specific configuration overrides via the \-e\ flag. Additionally, \GitHelpers\ ensures new repositories are initialized with the user's configured default branch (e.g., \main\ or \master\).

bridgetown-core/lib/bridgetown-core/commands/concerns · high confidence

New CLI tasks for secret generation, frontend watching, route inspection, and date formatting

The Bridgetown CLI now includes several new rake tasks to streamline development workflows. Users can generate a secure secret key using the \secret\ task, monitor frontend assets independently via \frontend:watcher\ (which supports a sidecar mode for integration with the main start command), and inspect the application's Roda routes using \roda:routes\. Additionally, a new \date\ task is available to output the current time in the site's configured timezone, formatted for easy use in front matter. These tasks rely on the new Freyia automation framework and ensure initializers run before site context is accessed.

bridgetown-core/lib/bridgetown-core/tasks · high confidence

New Liquid tags for asset paths, class mapping, content finding, and localization

This update introduces several new Liquid tags to the core templating engine. The \asset\_path\ tag resolves paths for JavaScript and CSS assets from the esbuild manifest (replacing the legacy \webpack\_path\), while \class\_map\ simplifies conditional CSS class application based on truthy/falsy variables. Content filtering is enhanced with the \find\ tag, offering a more intuitive syntax than \where\_exp\ for searching collections. Additionally, new tags \l\ and \t\ provide shortcuts for localization and translation lookups, \rendercontent\ handles component content rendering with region support, and \ruby\_render\ allows direct instantiation of Ruby components from Liquid templates.

bridgetown-core/lib/bridgetown-core/tags · high confidence

New Ruby DSL for configuration initializers

Bridgetown now supports a Ruby-based configuration DSL (configuration\_dsl.rb) for defining initializers, allowing users to configure plugins, register hooks, set timezones, and define Roda server initializers using Ruby code instead of or alongside YAML. This DSL provides methods like \init\ for plugin initialization, \hook\ for registering event hooks with reloadable:false by default, \timezone\ for setting the application timezone, \roda\ for server configuration blocks, and \only\/\except\ for context-specific configuration execution.

bridgetown-core/lib/bridgetown-core/configuration · high confidence

New author listing and individual author pages

The website now includes a dedicated section for authors, featuring an index page that generates a JSON manifest of all authors and individual dynamic pages for each author. These pages display the author's name, link to their website or social profiles (Mastodon or GitHub), and list their blog posts using a paginated card layout, complete with breadcrumb navigation and previous/next page controls.

_bridgetown-website/src/\pages/authors · high confidence

New bundled Lit configuration for server-side rendering

Bridgetown now includes a bundled configuration for Lit web components, enabling server-side rendering (SSR) out of the box. This addition provides the necessary esbuild plugins to process sidecar \.lit.css\ files via PostCSS, a sample \HappyDays\ component to demonstrate usage, and an entry point to automatically import Lit components. The configuration wires these elements together via a dedicated SSR build script, allowing developers to easily integrate Lit components into their Bridgetown sites with minimal setup.

bridgetown-core/lib/bridgetown-core/configurations/lit · high confidence

New bundled configurations for PostCSS, Lit, SEO, Feed, and more

Bridgetown introduces a suite of new bundled configurations that automate the setup of common frontend and deployment tools. The \bt-postcss\ configuration installs PostCSS plugins and generates a config file, while \lit\ sets up the Lit web component library with SSR support via esbuild. SEO and Feed functionality are now configurable through \seo\ and \feed\ configurations, which automatically inject necessary meta tags into the site head. Deployment and testing are streamlined with new configurations for GitHub Pages (\gh-pages\), Netlify (\netlify\), Render (\render\), and Cypress (\cypress\). Additionally, \minitesting\ configures Minitest with Rack::Test, \is-land\ adds lazy-loading support, \open-props\ integrates CSS variables, \purgecss\ adds CSS optimization, and \webawesome\ provides a new component library, replacing the previous Shoelace and Tailwind bundled configs.

bridgetown-core/lib/bridgetown-core/configurations · high confidence

New development and maintenance utility scripts

The \bridgetown-core/script\ directory now includes a set of new shell and Ruby scripts to streamline development workflows. These include \console\ for an interactive IRB environment with test fixtures, \test\ and \cibuild\ for running the test suite, \fmt\ for Rubocop linting, \memprof\ for memory profiling, \backport-pr\ for cherry-picking changes to release branches, \branding\ for displaying project art, and \vendor-mimes\ for updating MIME type configurations. These tools provide standardized ways to interact with the core library during development and CI.

bridgetown-core/script · high confidence

New documentation components for multilingual code examples and sidebar navigation

The documentation site now includes a new \multilang\ component that displays code examples in tabs for different languages (Ruby, ERB, Liquid, Serbea, YAML), and a new \sidebar\ component that renders the documentation navigation with proper accessibility attributes. Additionally, the \variables\_table\ component has been refactored to use a Serbea template instead of an HTML include, improving how configuration variables are displayed.

_bridgetown-website/src/\components/documentation · high confidence

New frontend JavaScript entry point and UI components

The website's frontend JavaScript bundle now initializes the Shoelace design system (including light/dark themes and specific web components like buttons, dialogs, and tabs) and configures the Remixicon icon library. It introduces a keyboard shortcut (Cmd/Ctrl+K) to focus the search input, dynamically loads the Quick Search plugin and theme picker, and registers new custom elements: a theme picker that respects OS-level color scheme preferences and persists user choice, and a 'wiggle note' component that animates when scrolled into view.

bridgetown-website/frontend/javascript · high confidence

New plugins directory structure for the website

The website now includes a dedicated plugins directory containing a SiteBuilder class and a text file directing users to the correct plugin path (src/\_plugins). This change establishes the structural foundation for custom plugin development within the website project, clarifying where users should place their own plugin code.

bridgetown-website/plugins · high confidence

New site template includes server configuration files and initializers

The site template now provides explicit configuration files for production web servers (Puma and Falcon) and a new \initializers.rb\ file for site-wide settings. Users can now configure server-specific options like concurrency, threads, and ports via environment variables, and customize site behavior such as the template engine (defaulting to ERB) and Fast Refresh in development through the new initializer.

_bridgetown-core/lib/site\template/config · high confidence

New site templates with ERB, Serbea, and Liquid support

The default Bridgetown site template now includes starter layouts and components for ERB, Serbea, and Liquid templating engines. New users generating a site will receive a structured set of files including a shared navbar, default layout, page/post layouts, and head/footer partials for each engine, allowing them to choose their preferred syntax immediately. The templates utilize the component system (e.g., Shared::Navbar) and provide consistent structure across all three supported template languages.

_bridgetown-core/lib/site\template/TEMPLATES · high confidence

New template converter implementations for ERB, Liquid, Markdown, Ruby, and Serbea

The converters directory now contains the core implementation files for Bridgetown's template processing engine. This includes the ERB converter using Erubi with custom capture blocks, the Liquid converter with payload configuration and caching, the Markdown converter supporting Kramdown and custom processors, the Ruby template converter for pure Ruby views, and the Serbea template converter for the new pure Ruby syntax. These files establish the foundation for how different template types are parsed, rendered, and cached during site builds.

bridgetown-core/lib/bridgetown-core/converters · high confidence

New test helper for Bridgetown integration testing

The bridgetown gem now includes a dedicated test helper (lib/bridgetown/test.rb) that simplifies writing integration tests for Bridgetown sites. This helper sets up the Minitest environment, boots the Rack application, and provides convenient methods like \app\, \site\, \html\, and \json\ for interacting with the running site during tests. It also integrates Rack::Test and Bridgetown's intuitive expectations for more readable assertions.

bridgetown · high confidence

This change introduces several new utility modules in the core library. The \Aux\ module manages background processes (like sidecars) by tracking their PIDs and handling their output with optional color coding. The \Initializers\ module registers core setup hooks, including support for external sources, server-side rendering (SSR), route parsing, and a new wikilinks feature. The \Wikilinks\ module itself provides a parser that converts wiki-style \\[\[links\]\]\ in Markdown content into standard HTML links, handling missing pages with a visual indicator. Additionally, new modules \LoadersManager\ (managing Zeitwerk autoloaders), \RequireGems\ (providing graceful dependency error messages), \RubyExec\ (executing inline Ruby in data), and \SmartyPantsConverter\ (enabling typographic smart quotes via Kramdown) are added to support these features and improve developer experience.

bridgetown-core/lib/bridgetown-core/utils · high confidence

New website component library for documentation, posts, and plugins

The website now uses a new set of Bridgetown components to render content. A \Note\ component displays contextual alerts with automatic icons based on type. \PostCard\ components present blog posts with titles, categories, dates, and read-more buttons. A \PluginsGrid\ component lists plugins with their versions and author details. Additionally, \Documentation\ components provide a sidebar and a variables table for technical reference pages.

_bridgetown-website/src/\components · high confidence

Support for file-based dynamic routes in src/\_routes

Users can now define dynamic routes using files located in the \src/\_routes\ directory. This new Roda plugin automatically processes these files, converting file paths (such as \\[slug\].erb\) into URL segments with parameters. It provides a \render\_with\ method to execute route logic and access front-matter data, enabling server-side rendering of content based on the file structure.

bridgetown-routes/lib/roda · high confidence

Support for text highlighting using == or :: delimiters

Users can now highlight text in Markdown by wrapping content with double equals signs (==) or double colons (::), which are converted to HTML \<mark\> tags. This feature is enabled via the \mark\_highlighting\ option and is implemented by extending the GFM parser in bridgetown-core to recognize and process these specific delimiters.

bridgetown-core/lib/bridgetown-core/kramdown · high confidence

Removals

Removal of development and maintenance Rake tasks

The project has removed several Rake tasks used for development, maintenance, and documentation generation. Specifically, the \profile:memory\ task for profiling Jekyll build sessions, the \release\ and \build\ tasks for packaging and publishing gems, and the \site\ namespace tasks for generating, previewing, and publishing the documentation site have been deleted. Users relying on these commands for local development workflows or automated release processes will no longer have access to them.

rake · high confidence

Removal of legacy Bridgetown v0.1 scaffolding and core library

The \lib/bridgetown\ directory has been completely removed, deleting the entire v0.1 codebase including the main entry point (\bridgetown.rb\), core modules (Cache, Cleaner, Collection, Site, etc.), and all CLI commands (build, clean, doctor, help, new, new-theme, serve). This also removes the default site scaffolding templates (\blank\_template\ and \site\_template\) and the \New\ command's ability to generate new sites or themes. Users will no longer have access to the initial Bridgetown implementation or its associated commands and templates.

lib/bridgetown · high confidence

Removal of legacy Cucumber support files

Deleted the custom Cucumber formatter and helper modules from the test support directory, removing the previous implementation that handled test output formatting and Jekyll execution utilities.

features/support · high confidence

Removal of legacy development and CI scripts

The repository has removed a suite of shell and Ruby scripts used for local development, testing, and continuous integration. Specifically, \script/backport-pr\ (for backporting pull requests), \script/bootstrap\ (for initial setup), \script/cibuild\ (for CI orchestration), \script/console\ (for interactive debugging), \script/cucumber\ (for Cucumber tests), \script/default-site\ (for sanity checks), \script/fmt\ (for RuboCop linting), \script/memprof\ and \script/rubyprof\ (for memory profiling), \script/proof\ (for link checking), \script/rubies\ (for Ruby version detection), \script/stackprof\ (for CPU profiling), \script/test\ (for running test suites), \script/travis\ (for Docker-based Travis CI simulation), and \script/vendor-mimes\ (for updating MIME types) have all been deleted. This change eliminates the local tooling for these specific workflows.

script · high confidence

Removed benchmark scripts

The benchmark directory has been removed, deleting all Ruby scripts used to compare performance of Liquid processing, path handling, string operations, and other internal optimizations.

benchmark · high confidence

Architecture

Site logic refactored into modular concerns

The monolithic Site class has been decomposed into a set of focused concerns (Configurable, Content, Extensible, FastRefreshable, Localizable, Processable, Renderable, SSR, and Writable). This structural change organizes site behavior into distinct responsibilities—such as configuration management, content handling, plugin setup, fast-refresh logic, internationalization, build processing, rendering, server-side rendering, and output writing—making the codebase easier to maintain and extend without altering the external build behavior.

bridgetown-core/lib/bridgetown-core/concerns/site · high confidence

Behavioural changes

Add RuboCop configuration, YARD setup, and Open Props template

This change introduces a dedicated RuboCop configuration file (.rubocop.yml) to manage linting rules and exclusions specific to the bridgetown-core gem, alongside a .yardopts file to standardize YARD documentation generation. It also adds a Rakefile to streamline testing and documentation tasks, and includes a new Open Props CSS template (variables.css.erb) that conditionally imports styles based on the frontend bundler type.

bridgetown-core · high confidence

Benchmark suite migrated to Bridgetown core with new performance tests

The benchmark suite has been moved into the bridgetown-core directory and updated to test Bridgetown instead of Jekyll. Several new benchmarks were added to measure the performance of path sanitization, string concatenation and replacement, and hash access patterns (including dot-access and indifferent access). Existing benchmarks were updated to reference Bridgetown classes and modules, and the Schwartzian transform benchmark was adjusted to test different document properties.

bridgetown-core/benchmark · high confidence

Bridgetown Foundation v2.2.2 introduces in-house Ruby refinements and core extensions

Bridgetown Foundation v2.2.2 replaces Active Support dependencies with in-house implementations, introducing a suite of Ruby refinements and core extensions. Users gain access to a \Bridgetown::Refinements\ module that provides \within?\ for intuitive object comparisons, \deep\_dup\ and \deep\_merge\ for Hashes and Arrays, and string methods like \camelize\, \underscore\, and \indent\. The release also adds a \WrappedObjectWithRefinements\ class to apply these refinements to arbitrary objects, a \QuestionableString\ for predicate-style string checks, and a \SafeTranslations\ package for secure i18n handling. Additionally, it includes a \CoreExt::Class\ module for reliable descendant tracking under Zeitwerk, an \IntuitiveExpectations\ module to enrich Minitest assertions, and an ANSI color package for terminal output.

bridgetown-foundation · high confidence

File-based dynamic routes now support localization and improved sorting

The routing system for file-based dynamic routes (located in \src/\_routes\ and islands) has been refactored to automatically generate localized URL slugs based on the site's configured available locales, enabling multi-language route definitions. Additionally, the manifest now implements a deterministic sorting algorithm for routes, prioritizing them by path depth and segment count to ensure consistent URL matching order. The change also introduces view helpers for CSRF protection and a stub flash object to support these dynamic routes within the rendering context.

bridgetown-routes/lib/bridgetown-routes · high confidence

Introduce \`bt\` shortcut and environment CLI flags

Users can now invoke the Bridgetown CLI using the shorter \bt\ command, which serves as a direct alias for \bridgetown\. Additionally, the CLI now supports specifying the environment via the \-e\ flag or the \--environment=\ option, allowing users to easily switch contexts (e.g., development vs. production) without modifying configuration files.

bridgetown-core/bin · high confidence

Migrate CLI framework from Thor to Samovar

The Bridgetown command-line interface has been rewritten to use the Samovar library instead of Thor, introducing a new command registration and parsing system. This change brings a new CLI architecture with dedicated command classes (such as \Application\, \Build\, \Start\, \Console\, and \New\) and includes a backward-compatibility shim (\thor\_shim.rb\) that allows older Thor-based commands to function while issuing deprecation warnings. Users will experience the same CLI surface but with an underlying framework that supports more flexible option handling and integration with the new Freyia automation system.

bridgetown-core/lib/bridgetown-core/commands · high confidence

Native esbuild integration replaces Webpack with new configuration and migration tools

Bridgetown now uses esbuild as the default frontend build tool, introducing a new set of configuration files including \esbuild.config.js\, \esbuild.defaults.js.erb\, and \jsconfig.json\ to manage asset bundling, PostCSS processing, and Sass support. The \setup.rb\ script initializes these new defaults for new sites, while \migrate-from-webpack.rb\ provides an automated path for existing projects to switch from Webpack, removing redundant packages and updating build scripts. An \update.rb\ command allows existing esbuild setups to upgrade to the latest configuration, including switching to ESM syntax and removing the now-unnecessary \glob\ npm package in favor of Node's native glob capabilities.

bridgetown-core/lib/bridgetown-core/commands/esbuild · high confidence

New Bridgetown Center program & plugins directory

The website configuration has been restructured to support the new Bridgetown Center program and plugins directory. This includes adding custom CLI commands for importing plugins from GitHub and managing the site, configuring esbuild for asset bundling with support for PostCSS and Sass, setting up initializers for various plugins like wikilinks, SEO, feed, search, SVG inlining, and sitemap, and configuring Puma for the development server. Additionally, Ruby2JS is configured to transpile Ruby to JavaScript with camelCase filtering and ES2020 level support.

bridgetown-website/config · medium confidence

New Builder plugin architecture with lifecycle callbacks and DSL

The builder system has been restructured to introduce a new \Bridgetown::Builder\ superclass that extends \PluginBuilder\. This change adds support for \before\_build\ and \after\_build\ lifecycle callbacks, allowing plugins to execute code at specific stages of the build process. The \PluginBuilder\ base class now includes a comprehensive set of DSL modules (Generators, Helpers, Hooks, Inspectors, HTTP, Liquid, and Resources) and implements a priority sorting mechanism (highest to lowest) to control the execution order of builder plugins.

bridgetown-builder/lib/bridgetown-builder · high confidence

New Liquid Renderer with performance metrics and flexible file loading

The Liquid rendering engine has been refactored to include built-in performance tracking and improved template resolution. The renderer now measures and reports execution time, byte size, and render counts for each processed file, displaying these metrics in a summary table (via terminal-table) to help users identify slow templates. Additionally, the file system loader now supports resolving templates with either .liquid or .html extensions, providing more flexibility in template naming conventions.

_bridgetown-core/lib/bridgetown-core/liquid\renderer · high confidence

New Liquid drop classes for Bridgetown objects

The \bridgetown-core/lib/bridgetown-core/drops\ directory now contains a complete set of new Liquid drop classes (\BridgetownDrop\, \Drop\, \CollectionDrop\, \GeneratedPageDrop\, \RelationsDrop\, \ResourceDrop\, \SiteDrop\, \StaticFileDrop\, \UnifiedPayloadDrop\). These classes define how Bridgetown's internal objects (like sites, resources, and pages) are exposed to Liquid templates, including specific handling for mutability, JSON serialization, and resource relations.

bridgetown-core/lib/bridgetown-core/drops · high confidence

New Liquid filters for localization, date formatting, and URL handling

The \bridgetown-core/filters\ directory now includes dedicated modules for internationalization, date manipulation, and URL generation. The \t\ and \l\ filters allow templates to translate strings and format dates using the I18n library, supporting locale-specific formats and fallbacks. The \in\_locale\ filter enables prefixing relative URLs with a locale code or filtering resource arrays by locale, respecting the \prefix\_default\_locale\ configuration. Additionally, new date filters (\date\_to\_string\, \date\_to\_long\_string\, \date\_to\_xmlschema\, \date\_to\_rfc822\) provide standardized formatting with ordinal and regional style support, while URL filters (\absolute\_url\, \relative\_url\, \strip\_index\, \strip\_extname\) handle path normalization and base path integration.

bridgetown-core/lib/bridgetown-core/filters · high confidence

New Rack-based server boot and routing infrastructure

The server boot process now uses a dedicated Rack layer (\bridgetown-core/rack\) to initialize the Roda application, manage Zeitwerk autoloaders for the server folder, and handle live reloads via Server-Sent Events. This introduces a default \config.ru\ entry point, a structured \Routes\ class for prioritizing and merging route definitions, and a \LiveReload\ class that watches for file changes and pushes reload signals or build errors to the browser, replacing previous ad-hoc server startup mechanisms.

bridgetown-core/lib/bridgetown-core/rack · high confidence

The core resource handling in Bridgetown has been rewritten to support a new signal-based change tracking system that enables fast refresh in development. This change introduces locale-aware permalink processing (supporting the :locale placeholder and respecting the prefix\_default\_locale config), a new Relations API for cross-collection linking, and a warning for Rails-style file extensions. It also adds support for pure Ruby layouts and data collections that skip front matter defaults.

bridgetown-core/lib/bridgetown-core/resource · high confidence

New Roda-based server and preview route implementation

The server component now uses a new Roda-based application structure defined in \roda\_app.rb\, replacing previous boot processes. Additionally, a new preview route (\routes/preview.rb\) has been added, allowing users to preview specific pages by collection and path via a \/preview/:collection/:path\ endpoint, with fallback to a 404 page if content is empty.

bridgetown-website/server · high confidence

New documentation site styling and dark mode support

The documentation website now features a completely redesigned visual style, including a new navigation bar component, responsive layout adjustments for mobile and desktop views, and a dedicated dark mode theme. This update introduces CSS View Transitions for smoother page navigation animations, replaces the previous Turbo-based transitions, and enhances code block readability with updated syntax highlighting colors and language labels. The styling also improves accessibility with better contrast ratios and font sizing across different screen sizes.

bridgetown-website/frontend/styles · high confidence

New readers for defaults, layouts, and plugin content

The site now uses dedicated readers to process path-based defaults, layout files, and content from external plugin sources. Defaults are loaded from \_defaults files in the source directory and stored in a hash with dot-access for configuration. Layouts are read from the configured layouts directory and merged with layouts provided by plugin source manifests. Plugin content is read from external source directories, respecting collection-specific external source filters, handling bare-text files, and ignoring symlinks, with results added to the site's static files or resources.

bridgetown-core/lib/bridgetown-core/readers · high confidence

New shared navbar component with sponsorship banner and edge status indicator

The website now uses a new shared navbar component that includes a sponsorship announcement bar at the top, encouraging users to support the project. The navigation bar visually indicates when the site is running an edge version via a distinct background gradient and an animated 'edge' label. It also features improved accessibility with ARIA labels for social links (Mastodon, GitHub) and keyboard shortcuts for search, while maintaining standard navigation sections for Documentation, Plugins, Community, and Blog.

_bridgetown-website/src/\components/shared · high confidence

New site template with ERB/Serbea support and esbuild defaults

The frontend site template has been updated to support ERB and Serbea templating in JavaScript files (e.g., \index.js.erb\), allowing dynamic configuration of asset imports based on build options like esbuild and PostCSS. The default frontend bundler has switched to esbuild with PostCSS, changing how component assets are imported via dynamic glob imports instead of the previous Webpack-based \require.context\. Additionally, a default syntax highlighting stylesheet (\syntax-highlighting.css\) is now included to style code snippets, and the base CSS has been updated with a new default theme.

_bridgetown-core/lib/site\template/frontend · high confidence

The website now uses new \\_footer.serb\ and \\_head.serb\ partials. The footer displays the current Bridgetown version and codename, links to the philosophy page, sponsorship, GitHub issues/PRs, Code of Conduct, Discord, and an RSS feed, along with attribution to Whitefusion and Adrian Valenzuela. The head partial includes SEO and feed meta tags, favicons, and a client-side ThemeManager script that respects the system's prefers-color-scheme and persists the user's theme choice in localStorage, applying theme-dark classes to the document root.

_bridgetown-website/src/\partials · high confidence

New website layout structure with accessibility and navigation enhancements

The website now uses a new set of layout templates (default, docs, page, post) that introduce a 'Skip to main content' link for improved keyboard accessibility, a theme picker component, and structured navigation including breadcrumbs for documentation and blog posts. The default layout serves as the base, while specific layouts for docs, pages, and posts add contextual elements like category breadcrumbs, author information, sharing buttons, and related content sections.

_bridgetown-website/src/\layouts · high confidence

Optimized Kramdown Markdown parsing engine

The Markdown converter now uses a custom \Kramdown::BridgetownDocument\ class to optimize memory usage by reusing the same options hash and parser instance across all documents in a site, rather than initializing a new Kramdown document for each file. This change improves performance and reduces memory overhead during site generation while maintaining full compatibility with existing Kramdown configuration options such as syntax highlighting and GFM support.

bridgetown-core/lib/bridgetown-core/converters/markdown · high confidence

Redesigned website with new pages and Serbea templating

The Bridgetown website has been completely overhauled, introducing new pages for the Home, Community, Plugins, Sponsorship, and Blog sections. The site now utilizes the Serbea template engine (files ending in .serb) for dynamic content rendering, including paginated blog listings and plugin directories. Key additions include a dedicated Community page highlighting core team members and support channels, a Plugins page featuring the new 'Bridgetown Center' program, and a Sponsor page with a Q2 2026 funding goal. The redesign also includes a new 404 error page and uses native web components like Shoelace for UI elements.

_bridgetown-website/src/\pages · high confidence

Refactor core resource concerns and introduce Viewable mixin for Ruby components

The resource lifecycle and rendering logic in bridgetown-core has been reorganized into distinct concerns: LayoutPlaceable now explicitly handles layout assignment (including support for \layout: false\), Publishable manages visibility and future-dating checks, Prioritizable allows route classes to define execution order, and Localizable optimizes locale matching with a pre-computed index. Additionally, the new Viewable mixin enables Ruby-based components to define front matter and render through the standard layout transformation pipeline, while Transformable centralizes the converter execution logic used by these components.

bridgetown-core/lib/bridgetown-core/concerns · high confidence

Refactored front matter handling with support for Ruby layouts and dot-access defaults

Front matter processing has been restructured to support pure Ruby (.rb) layouts via a new loader system and to ensure front matter defaults are accessible via dot notation. The \FrontMatter::Loaders\ module now manages a registry of parsers (YAML and Ruby), allowing the \Importer\ to delegate parsing to specific loaders. A new \RubyDSL\ and \RubyFrontMatter\ class enable dynamic front matter definition in Ruby files, while the \Defaults\ class has been updated to convert default values into hashes that support dot access, improving how site-wide defaults are applied and retrieved.

_bridgetown-core/lib/bridgetown-core/front\matter · high confidence

Refactored front matter parsing into dedicated loader classes

The front matter parsing logic has been restructured into a modular loader system within \Bridgetown::FrontMatter::Loaders\. A new \Base\ class defines the interface, while specific loaders handle different syntaxes: \YAML\ continues to parse standard triple-dash delimited YAML, and a new \Ruby\ loader enables parsing front matter defined via fenced code blocks (e.g., \\\`ruby) or ERB/Serbea indicators. This change isolates the parsing behavior for each data format, making the system more extensible and easier to maintain.

_bridgetown-core/lib/bridgetown-core/front\matter/loaders · high confidence

Relocate Roda server logic to a dedicated plugin

The Bridgetown server implementation has been moved from the core library into a new \bridgetown\_server\ Roda plugin. This change introduces several supporting plugins to handle static site generation (\ssg\), server-side rendering setup (\bridgetown\_ssr\), flash messages (\flashier\), and HTTP method overriding (\method\_override\). As a result, the server now provides a generic fallback index page when the source folder is missing an \index\ file, and it includes built-in support for rendering callable Ruby objects directly in responses.

bridgetown-core/lib/roda · high confidence

Removal of the 'bridgetown' executable script

The 'bridgetown' executable file located in the 'exe' directory has been deleted. This file previously served as the entry point for the command-line interface, defining global options (such as source, destination, and safe mode) and registering subcommands via the Mercenary library. Its removal indicates that the CLI entry point has been relocated or restructured, likely to a 'bin' directory as suggested by the commit message, rather than being executed directly from 'exe'.

exe · medium confidence

Removed Jekyll-based site template in favor of Bridgetown

The default site template previously generated for new projects has been removed. This change deletes the Jekyll-specific configuration file (\_config.yml), the default theme setup (Minima), the 404 page, the welcome post, and other starter content files. Users generating new sites will no longer receive a Jekyll-based scaffold; the template has been replaced to support Bridgetown, as indicated by the commit context.

_lib/site\template · high confidence

Repository modernized with GitPod support and updated tooling configuration

The repository now includes configuration for GitPod cloud development environments, specifying Ruby 3.2.9 for the workspace and Ruby 3.3.11 as the project standard via \.gitpod.dockerfile\ and \.ruby-version\. Legacy CI and code quality configurations for Travis CI (\.travis.yml\) and Code Climate (\.codeclimate.yml\) have been removed, alongside the JRuby runtime configuration (\.jrubyrc\). Documentation tooling is standardized with new \.yardopts\ and \.solargraph.yml\ files, and Prettier is configured to ignore Markdown, HTML, and Liquid files via \.prettierignore\.

(repo-wide) · high confidence

RuboCop configuration migrated from Jekyll to Bridgetown

The RuboCop configuration has been renamed from Jekyll to Bridgetown, and the associated custom cop files have been updated to reflect this change. The \rubocop/jekyll.rb\ file was renamed to \rubocop/bridgetown.rb\, and the \rubocop/jekyll/\ directory was renamed to \rubocop/bridgetown/\. The \AssertEqualLiteralActual\ cop was moved from the Jekyll namespace to the Bridgetown namespace, and the \NoPAllowed\ and \NoPutsAllowed\ cops were removed as they were specific to Jekyll's logging mechanisms.

rubocop · high confidence

Server-side rendering sessions enabled by default

The routes plugin now initializes server-side rendering (SSR) with sessions enabled by default. This ensures that session support is available immediately upon startup without requiring manual configuration, providing a more seamless experience for users relying on session-based features in their dynamic routes.

bridgetown-routes/lib · high confidence

Standardized local development and CI scripts

The repository now includes a set of standardized shell and Ruby scripts in the \script/\ directory to streamline local development and continuous integration workflows. The new \script/cibuild\ script automates the CI pipeline by sequentially running formatting checks and tests. The \script/fmt\ script executes Rubocop for code style enforcement, providing clear feedback and suggestions for automatic fixes. The \script/test\ script manages the test suite, handling cleanup of previous test destinations and supporting both full suite execution and specific test file runs. Additionally, \script/minitest\ provides a dedicated entry point for running Minitest suites via Bundler.

bridgetown-routes/script · high confidence

Updated default HTML documentation theme with new color palette and typography

The default HTML documentation template now uses a new CSS stylesheet that introduces a green and orange color scheme, updates the font stack to prioritize system and modern sans-serif fonts, and applies specific styling for code blocks, links, and signature sections.

yard · high confidence

Updated default site template with ERB/Serbea support and custom error pages

The default Bridgetown site template has been refreshed to include new pages (About, Posts) that support ERB and Serbea templating, allowing users to choose their preferred syntax for dynamic content. Additionally, the template now provides custom 404 and 500 error pages to improve the user experience when errors occur, replacing the previous generic layouts.

_bridgetown-core/lib/site\template/src · high confidence

Updated new site template to use esbuild, PostCSS, and Rack-based server

The default Bridgetown site template has been updated to use esbuild for JavaScript bundling and PostCSS for CSS processing, replacing previous Webpack-based tooling. The template now includes a \config.ru\ file for Rack-based server booting, a \Gemfile\ that defaults to the Falcon web server (with Puma as an option), and a \Rakefile\ with tasks for building and watching assets via esbuild. Additionally, the template now requires Ruby \>= 3.3 and Node \>= 22, and includes a \.gitignore\ file tailored for Bridgetown projects.

_bridgetown-core/lib/site\template · high confidence

Updated welcome post with new documentation and support links

The sample blog post included in new Bridgetown sites has been updated to reflect current project resources. The text now directs users to the official Bridgetown documentation site and GitHub Discussions for questions and support, replacing previous links that may have pointed to older forums or different locations. The post retains its instructional content on file naming conventions and code snippets but ensures all external references are current.

_bridgetown-core/lib/site\_template/src/\posts · high confidence

Website build plugins for TOC, HTML linting, and version labeling

The website now includes new site builder plugins that enhance content rendering and build validation. A Table of Contents helper is added to automatically generate navigation links for article headings, while an HTML inspector enforces semantic markup by warning or failing the build if non-semantic div or span tags are detected outside allowed classes. Additionally, the site dynamically labels itself as 'EDGE' or 'v1' based on the current Bridgetown version and displays the release date of the active gem version in metadata.

bridgetown-website/plugins/builders · high confidence

Website rebuild with native Inspector, esbuild, and file-based routing

The Bridgetown website has been rebuilt to use native HTML Inspector (via Nokolexbor) to enforce semantic HTML by banning div and span tags, switch to esbuild for frontend asset compilation, and implement file-based dynamic routes through a new .routes.json configuration.

bridgetown-website · high confidence

Test coverage

Added SSR route test fixtures for dynamic routing and rendering; Added feature tests for Bridgetown core capabilities; Added test fixtures for .rb and .json translation files; Added test fixtures for SSR server routing; Added test fixtures for Serbea 2.0 template syntax and front matter DSL features; Added test fixtures for alternate routes and SSR output; Added test fixtures for multi-locale pages and Ruby template syntax; Added test fixtures for nested route rendering; Added test suite for Builder DSL capabilities; Added tests for SSR configuration and refinement initialization; Added tests for the Roda-powered routes plugin; Expanded test fixtures for source processing and component rendering; Removal of Jekyll feature tests; Removal of Jekyll test fixtures and helper infrastructure.

Dependencies

Bridgetown 2.2.2 dependency and manifest updates

This change updates the Bridgetown monorepo to version 2.2.2, refreshing the Gemfile.lock and gemspec files for bridgetown-core, bridgetown-builder, bridgetown-foundation, bridgetown-paginate, and bridgetown-routes. Key dependency adjustments include pinning samovar to 2.4.1, updating liquid to the 5.4.0 range (\>= 5.0, \< 5.5), and bumping rack to 3.2.4. The bridgetown-website location updates its Gemfile to use bridgetown-quick-search \~\> 3.0 and bridgetown-svg-inliner \~\> 2.1, while its package.json and package-lock.json reflect upgrades to esbuild ^0.28.0, postcss ^8.4.31, and @shoelace-style/shoelace ^2.2.0. The root Gemfile is refactored to depend on the local bridgetown gems and includes bridgetown-lit-renderer 3.0.0.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 45 → 46 (+1.3)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 51 → 51 (+0.0)
  • Architecture 67 → 67 (-0.2)
  • Maturity 54 → 59 (+4.9)
  • Readiness 35 → 35 (-0.0)
  • Security 48 → 52 (+4.3)
  • Accessibility 66 → 66 (-0.0)
  • Performance 75 → 75 (+0.0)

Resolved (4)

  • Medium CVE: [GHSA redacted] (bridgetown-website/package-lock.json)
  • No inconsistencies found. The API surface shows distinct responsibilities for Configuration (setup, reading files, running initializers) and no obvious duplicate operations with different names.
  • Off-boarding risk: anonymized user #1
  • Split bridgetown-core

New (4)

  • Off-boarding risk: anonymized user #1
  • Outdated: rack-test
  • Projects may be oversized for their cohesion
  • redundant comment (bridgetown-website/config/esbuild.defaults.js)

Architecture

  • Unchanged — 0 containers · 2 contexts · 1 edges

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

bridgetownrb/bridgetown was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 6 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 2cde84a2634482c29c3a311b7c228e6f7ef45580 — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.2+preprod-5c4e66d9318b.