From a user standpoint, I expect a subdirectory (example.com/blog) to follow the same UI as the main site (example.com). A subdomain in my mind will be a separate entity with its own UI.
I deploy my Hugo site with Netlify, and I can also manage my subdomains there for these third-party services. Within my personal site I have subdirectory paths like /posts and /about, all built with Hugo and using the same styling.
I couldn't agree more. I feel subdomains can be useful if you are going for a subproject per se, but if you are working on the same project, website, ect. I'd definitely recommend the use of subdirectories.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
From a user standpoint, I expect a subdirectory (example.com/blog) to follow the same UI as the main site (example.com). A subdomain in my mind will be a separate entity with its own UI.
This is exactly how I have things set up:
shelbyspees.comnotes.shelbyspees.comspeaking.shelbyspees.comI deploy my Hugo site with Netlify, and I can also manage my subdomains there for these third-party services. Within my personal site I have subdirectory paths like
/postsand/about, all built with Hugo and using the same styling.that’s such a concise way of describing their distinction. thanks for sharing
I couldn't agree more. I feel subdomains can be useful if you are going for a subproject per se, but if you are working on the same project, website, ect. I'd definitely recommend the use of subdirectories.