Skip to content

Source: docs/adr/0002-separate-content-models.md. Edit it there; this page is generated at build time.

Separate Eloquent models per content type, not one polymorphic content table ​

We considered a single Article model with a type enum and a JSON catch-all for type-specific fields, versus separate models (Review, Comparison, Listicle, Article) each with their own schema. We chose separate models: Review (ratings, sub-scores, spec table, verdict, FAQ), Comparison (multi-product feature matrix), and Listicle (ordered product picks) have genuinely different structured fields, and cramming them into one polymorphic table would force conditional-field sprawl in Filament forms and make per-type schema.org markup harder to emit cleanly. The one exception is Guide and Blog content, which share an identical shape (title, body, hero image, no ratings/product refs) — those two are merged into the single Article model, with type used only for URL/section routing.