Dfyjkt

I'm building a website with several articles. I'm using Vue Router, and for the moment the urls of my articles look like /article/id, for example : http://localhost:8080/article/85.

How can I slug an URL with the article title so it can be http://localhost:8080/article/the-article-title for example ?

I have no idea what kind of code should I provide so here is my article route :

routes: [
 
 path: '/article/:id',
 component: require('../components/articlePage.vue').default,
 name: 'article',
 meta: title: "article"
 , 
]

There are different approaches with increasing level of complexity and aspects taken care of.

So to start - in order to slug-ify articles, you have to introduce slugs to the application. Since it is mentioned in comments that all articles are fetched priorly, slugs can be added to each article data before saving them to store with custom function that converts words to kebab-case or one of helper libraries (e.g. dashify).

This will make possible to render list of article links using :slug as route param, instead of id and search in store for by param before rendering article page. Good thing is that it still possible to keep both options (slug and id) available by extending logic to search by 2 fields.

Depending on your target - that might be it. But the problem arises in case article title has been changed and user accesses article via externally saved link (shared in social media, indexed by search engines, etc). This defeats SEO.

In order to keep article accessible, it is a good practice to include slug as a required field on back-end. Slug still can be generated with same approach, but in CMS - before article is stored in database. In such case it can be double checked, manually edited (as slugs do not always represent full article title because of characters length, special symbols, etc) and be accessible for querying, thus removing hassle of string manipulation from front-end.

Also this creates options to configure 301 redirects to preserve indexation even after slug is changed by saving old slugs. But that is out-side of current question scope, even though is a good practice.