{
  "id": 13726665,
  "title": "I Almost Used Nuxt Content for My Blog, but I Chose a Database Instead",
  "url": "https://urgent.news/2026/10/11/i-almost-used-nuxt-content-for-my-blog-but-i-chose-a-database-instead",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-11T13:49:28.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/tcandra24/i-almost-used-nuxt-content-for-my-blog-but-i-chose-a-database-instead-568h"
  },
  "original_language": "en",
  "account": "When embarking on creating a personal blog using Nuxt, one of the initial choices involved selecting a method for content storage. While Nuxt Content offered a simple solution by allowing articles to be written in Markdown, the reporter found it lacked a custom admin panel for managing articles, categories, and tags. This limitation led the reporter to opt for a database instead.\n\nPostgreSQL was chosen as the database, coupled with Drizzle ORM for database operations. The initial schema included tables for Articles, Categories, Tags, Users, and Comments. The Articles table contained fields for titles, content, slugs, publication status, and SEO information. Categories helped separate different types of articles, while Tags organized articles by topic. Users stored information for authentication and administration, with a many-to-many relationship established between Articles and Tags.\n\nChoosing a database meant taking responsibility for database schemas, relationships, migrations, and queries, which added an extra layer of complexity to the project. However, this trade-off was justified as it provided more control over content organization and management, along with the ability to implement an admin panel, structured content, authentication, and future feature additions.\n\nThe reporter learned that the best technology is not always the one with the simplest setup, but rather the one that aligns with the project's requirements. Before selecting a tool, it's essential to consider how content will be managed, where the application will run, and potential future additions. This approach helped the reporter make a decision that suited their project's needs, rather than opting for a tool solely based on convenience at the start.\n\nThe blog continues to evolve, and the reporter anticipates revisiting some of these decisions as the project progresses. For now, PostgreSQL and Drizzle ORM are proving effective for the direction the project is heading. The reporter invites readers to share their thoughts on choosing Nuxt Content or a database when building a blog with Nuxt.",
  "summary": "When I started building my personal blog with Nuxt, one of the first decisions I had to make was how to store my content. At first, Nuxt Content seemed like a good option. Writing articles in Markdown sounded simple, and I wouldn't need to worry too much about database setup. But there was one thing I needed: a custom admin panel where I could manage my articles, categories, and tags. That made…",
  "key_points": [
    "Reporter chose PostgreSQL and Drizzle ORM for blog content management.",
    "Custom admin panel lacked in Nuxt Content, leading to database selection.",
    "Database provided control over content organization and future feature additions."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}