nuxt / nuxt/content

How to handle content assets?

Open
#3,140 17 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
TypeScript
Stars
3.7k
Forks
746
Avg merge
1d 16h
Merged PRs (30d)
3

Description

I see there is Nuxt Studio which looks super cool. But I'd like to deploy my Nuxt Content V3 elsewhere. My 'content' folder itself is a repo of markdown files. I'd like to store and serve images with and from the content folder. To keep the content images with the markdown content files. I'd like to link those local images from Markdown. Imagine that I use Obsidian to author the content like so:

![View from the hotel](images/hotel-view.jpg)

So far I have been using Nuxt Content Assets with Nuxt Content V2: https://github.com/davestewart/nuxt-content-assets

But the plugin does not seem to be maintained, nor does it work with Nuxt Content 3.

What options, beside Nuxt Content Studio, are available?

I am not considering public and assets folder from Nuxt, since I want to store those content assets with the content repo. The content repo should be independent of the Nuxt application. I have asked this on Discord before.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names a separate content repo, Markdown files with local image links, and the Nuxt Content Assets plugin, but no source file or test. Start by tracing how Nuxt Content V3 handles Markdown asset paths and compare that with the plugin's approach. Done means establishing a supported option for serving content-local images independently of the Nuxt application.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, nuxt, typescript
Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.