One file?

[aslakhellesoy]

What are the advantages of the {year}/{month}/{day}.md structure versus one single file with a # {year}-{month}-{day} header for each day?

As a reader, I find it difficult to read several retros as I have to switch between several documents (either on GitHub or in my editor).

With a single file it would be equally easy to read the latest retro (top of the file) as several ones (just scroll).

And if we just have one file, is a tool really needed?

[tooky]

My experience with a really big file after months of retros was that it got unwieldy to edit.

This tool was to make it simple to get past that problem.

[aslakhellesoy]

I understand the file gets unwieldy to edit when it's too large.

My solution to that would be to cut everything below 3 months ago every now and then and paste it to the top of an ever-growing retro-archive.md file.

It's a low-fi solution to the editing problem that also preserves the readability improvements provided by a single file.

[mattwynne]

I did wonder why you went for so many-subfolders. Would it be better to have /doc/retro/<yyyy>-<mm>-<yy>.md by default, then at least they'd all be in the same folder?

Maybe this is a reason to just make the path configurable, and make sure it works as an append rather than a replace if the file exists already.