Read article URL from FrontMatter instead of automatically generating it about revista-gatsby-blog-magazine HOT 3 OPEN

Hey David,

Hmm, this might take a bit of planning to implement. I have the slugs autogenerating in several places.

As a start, you would need to:

1. Add the slug as markdown metadata. E.g. path: "5-linqpad-tricks"
2. In gatsby-node.js, this is where the slugs are autogenerated. Check if a slug was provided, and if it was, use that. If not, use autogenerated one.

Then, you'd need to ensure that when the links to articles are placed in the blog lists, the correct link is used. This might need to be changed in several places. Starting in src/components/Posts/Post.js:

3. Update GraphQL to include slug.
4. Similar to point 2: Check if a slug was provided, and if it was, use that within links. If not, use autogenerated one.

I unfortunately am way too busy to try to fix this at the moment, but the least I can do is point you in the right direction!

from revista-gatsby-blog-magazine.

Thanks!
Would this approach make me lose the "/blog/" part?

from revista-gatsby-blog-magazine.

With the approach I described - depends.

Gatsby is very flexible in this regard so you can create the pages however you like.

My preference is to just include the slug, which allows you to also use the same Markdown metadata for multiple content types. E.g. if you want to also generate Portfolio links/pages based on Markdown files, you can re-use the slug: "..." for different purposes.

However I think you can leave it, if you already have blog/... in all of your files. Just ensure that the path in gatsby-node.js is correctly generating. As long as your links are generating consistently throughout the project, you can set up your urls however you choose.

from revista-gatsby-blog-magazine.