Some reports cover more than a single event. Latest examples are from Vietnam and Argentina. For both of them, I got stuck for a moment thinking whether to split or keep as one report.
The problem with combined reports is any given event is no longer represented by its single file. If you look for Argentina Crypto Fest using filenames, you won't find it. You'll have to remember that it lives in the report for La Conexion or use text search.
The good side of allowing multiple events in one file is that it allows to
- cover multiple related events (e.g. in a single trip to some country)
- cover multiple small events (there's often an afterparty after the main event)
- describe a series of events in a common context
- avoid text duplication by not copying common context in N files
- save time by not thinking how to arrange M events in N files
I suggest to do two things:
- define some criteria when the related reports must be split
- when the reports can be kept in one file, define how to name the file
Some reports cover more than a single event. Latest examples are from Vietnam and Argentina. For both of them, I got stuck for a moment thinking whether to split or keep as one report.
The problem with combined reports is any given event is no longer represented by its single file. If you look for Argentina Crypto Fest using filenames, you won't find it. You'll have to remember that it lives in the report for La Conexion or use text search.
The good side of allowing multiple events in one file is that it allows to
I suggest to do two things: