3 ms·
My thinking would be this: * If you have a subdomain for your blog(example: blog.mydomain.com) then you don't need /posts * if you don't have subdomain, you c
by mindwork 4y ago
My thinking would be this:
* If you have a subdomain for your blog(example: blog.mydomain.com) then you don't need /posts
* if you don't have subdomain, you can use /posts, to distinguish between regular pages of your site and blog articles. Because you might have mydomain.com/about and mydomain.com/contact pages
* Don't put metadata such as publish dates as it can be modified or changed in the future. Also it's relative.
* As for example 3, you would probably need it in case when you have lots of articles and there might be a slug collision. I wouldn't worry about that unless you are media organization