Hmm, personally I never really cared for dated paths, seems like a problem that's solved by metadata defined in the frontmatter.

my-blog-article-title.md seems enough, and dates usually feel like clutter, since titles are distinct as they are and you don't really need the date in the filename to do anything useful.

But again, different people prefer different setups.

▲

mikae1 5 days ago | parent [-]

> my-blog-article-title.md seems enough, and dates usually feel like clutter, since titles are distinct as they are and you don't really need the date in the filename to do anything useful.

I love to see when a page by posted just by looking at the URL. It also avoids naming collisions. For a static site, not rendered from a db, I wouldn't want to store every post ever written in one dir either. How well does that scale? Yeah, you can probably store 100K files in dir, but it will become unwieldy and slow to load when browsing a lot sooner. Just a dir per year probably solve any such problem.

	▲	h4ch1 4 days ago \| parent [-]
		you're correct, I had mistakenly interpreted your comment as dates in file paths instead of dirpaths, and I would second this, it really gets unwieldy once you have 100k or even 500+ files in a single directory. Apologies for the miscommunication. Also > I love to see when a page by posted just by looking at the URL. would solve that with a URL path /2015/my-article-title; also creates a nice way to go to articles by year for example by simply navigating to the /2015 route