- How do I install log1x/crumb in a Sage 10 theme?
- Run composer require log1x/crumb from your Sage theme directory and confirm Acorn boots the auto-discovered service provider. In most setups no manual registration is needed, and you can optionally publish the package config through Acorn's console. After that you define a trail and call the Blade component from your layout or header partial.
- Does log1x/crumb work in a plain Laravel app without WordPress or Sage?
- Crumb is described as a Laravel package, but its real host is a Roots Sage theme running Acorn, which provides the Laravel-shaped container, Blade layer, and console inside WordPress. It is not aimed at a vanilla laravel new application, and introducing Acorn purely to get breadcrumbs is not justified. If you are not on Sage or Acorn, a small native Blade component is the simpler route.
- How do I define breadcrumb trails with the Crumb fluent API?
- You assemble a trail by chaining nodes through the package's fluent surface, typically inside a service provider, a view composer, or a dedicated breadcrumb builder class. Keep the rules that decide which trail applies, such as home, post type archive, taxonomy, and singular conditions, in one place rather than scattering conditionals across templates. The package owns assembly and rendering, while the WordPress-facing logic that picks the trail is yours.
- How do I render breadcrumbs in Blade using Crumb?
- Crumb ships a Blade rendering path, so you call it from a layout or header partial and let it output the assembled trail as markup. This keeps templates free of trail-building logic and means every page gets breadcrumbs from a single place. Separators, wrappers, and styling hooks are configurable so the output matches your theme.
- Can I customize Crumb's breadcrumb markup, separator, and CSS classes?
- Yes. The package explicitly supports customizing markup, separators, and styling, which is a large part of its value over hand-written breadcrumb HTML. Check how far the renderer customization goes before committing if your design system needs very specific output such as schema.org microdata or unusual casing and wrappers. Heavy overrides can effectively become a forked template, at which point an in-house component may be cleaner.
- Which Laravel and Acorn versions does log1x/crumb support?
- Compatibility tracks Acorn rather than Laravel itself, and the most recent release was an Acorn 4.x dependency update. Check the version constraint in the package composer.json against the Acorn major your Sage theme runs before upgrading either side. Because the surface area is small, patching for a new Acorn major is usually trivial if upstream lags behind.
- Is log1x/crumb still maintained and safe to use in production?
- Treat it as maintenance-mode software: one maintainer, a modest star count, and a last release in November 2023 that only bumped an Acorn dependency. Technical risk is low because the problem domain is trivial and the codebase can be audited in an afternoon, but the bus factor is real. Use it as a leaf dependency, keep trail logic in code you own, and be ready to fork or replace it if upstream stalls again.
- How do I build breadcrumbs from WordPress custom post types and taxonomies with Crumb?
- Crumb does not derive trails from WordPress hierarchy for you, so you write that adapter using conditionals like is_singular(), is_tax(), and your CPT registration. Put those rules in a single builder class and let Crumb handle assembly and rendering. For structural breadcrumbs, the adapter is where most of the implementation effort sits, not the package.
- How do I test breadcrumbs built with Crumb?
- Keep the trail rules in your own builder class behind a clean interface so you can unit test the node list without touching rendering. Assert on the trail produced for home, archive, taxonomy, and singular cases, and reserve output assertions for the Blade markup. This isolation also makes swapping Crumb for an in-house component a contained change rather than a rewrite.
- What are the alternatives to log1x/crumb?
- The realistic alternatives are a 100 to 200 line in-house Blade component plus a trail builder, or an existing WordPress SEO plugin trail such as Yoast or Breadcrumb NavXT if you already run one. Crumb's honest business case is saving an afternoon of work, so it mainly makes sense when the theme is already Acorn-based and the output requirements are modest. Isolating your trail logic keeps the decision reversible.