destructure Nuxt routing and Content markdow files

[thibautSchmutz]

Hi,

Thank you so much for having developed this awesome content v2 module !

I would like to create a Blog website with two main topics : Vue and Nuxt. Each topic page will display a list of all the blog articles related to it.

The content folder looks looks like this :

• content
  • vue
    • handle-events.md
    • state-management.md
  • nuxt
    • universal-rendering.md
    • create-custom-module.md

The pages folder looks like this :

• pages
  • [topic]
    • index.vue
    • [...slug].vue

The issue I am facing is : since [...slug].vue destructures every routes under either /vue/ or /nuxt/, the index.vue file is never read.

Is there a way to keep the dynamic load of each document.md through destructurig [...slug] and also be able to display the index.vue when we hit localhost:3000/vue or localhost:3000/nuxt ?

Thank you !

[ManasMadrecha]

Maybe you can try such structure in pages/:

• pages
  • [topic]
    • [...slug].vue
  • [topic].vue

[thibautSchmutz]

Thank you for taking to time. Unfortunatly, this approach doesn't work. [...slug].vue still fetches all routing attempts.

[thibautSchmutz]

Here is the console warn message :

[Vue Router warn]: Found duplicated params with name "topics" for path "/articles/:topics/:topics". Only the last one will be available on "$route.params".

Thank you though.

[danvega]

I don't know that I would move them into separate folders. What happens when you want to create a third category? What you could do is use front matter to tag each of your posts

---

title: Hello Content v2
tags: [nuxt]

Now you have one template to display all of your blog posts in a list
A template to display /tag/nuxt (or whatever tag the visitor chooses)
A template to display a single blog post by slug

[thibautSchmutz]

Thanks Dan for taking to time.

I still face the issue where [...slug].vue route keeps on fetching all routes from its parent route, because of destructuring. Although, I tried to declare a route without destructuring ( [slug].vue ). This seems to work and let me use the index.vue to show all relatied content.
The only issue I am facing now is when I try to generate a static site (through 'yarn generate'). The builder doesn't know it has to go over each markdown document to render it statically.

Thank you though for your help Dan.