Experiment with language slugs for blogs
Closed this issue · 3 comments
Blogs that fit into a specific language should be easy enough to reslug to use the language. For example /blog/s/python-sortedlist-vs-list-sort
could become /python/a/sortedlist-vs-list-sort
. This might be super easy or extremely difficult depending on the approach. We should investigate it and see if it can work for us.
This is still valid, but the approach should be different. The preferred option would be to categorize blog posts into subdirectories and use the same classification on the website. For example: blog/python/s/sortedlist-vs-list-sort
. This would require some (if not a lot of) changes to the scheduling system, but it would also improve the content creation experience and potentially the content extraction speed.
Due to reslugging being fairly costly and problematic with SEO, let's address this and the changes proposed in #237 all at once. The proposal would be to use slugs like article/python/sortedlist-vs-list-sort
or article/python/s/sortedlist-vs-list-sort
. Theoretically, the first slug's parts could be reversed so that article
and python
are reversed in the actual URL resulting to python/article/sortedlist-vs-list-sort
, but that might be too much effort.
Language slugs are very complex to implement and probably not worth since the slug already contains the language in it. We're going to reslug to /articles
URLs and resolve.