In development of the version control folder listing of the definition of IFC from IfcDoc, I trialed grouping of entities into alphabetical folders. This resulted in something like this:
I’m worried about this approach though, as it requires either a predetermination of some number of entities at which to group into subfolders (and when a list is at a threshold an undesireable momental change), or a bespoke attribute decorator (at the moment the serializer has no dependency on the ifc definition data structure and vice versa). This isn’t ideal, as now on github you get the effect of listing truncation.
It might be a single letter might get 1000 files at some point in time, you can still access the entity by predetermined URL.
Any thoughts and opinions?