I’ve never used grav. I’m a very database oriented person so it might seem counter intuitive to have an interest in grav but there is a circumstance that I’d like to check into.
I have to deal with an existing file system based knowledge store. Structurally it’s very simple, folders and files organized by topic and date. The root folder is “ref” for reference. A typical section is like this:
–apex (a folder)
----20180901 installation on bolide09 (a folder)
------sometextfile.txt (contains textual info)
–drupal (a folder)
----20180905 update to 8.6.1 (a folder)
------anothertextfile.txt (contains textual info)
------log.log (a text file)
and so forth. What’s good about the system as it has has the simplicity and versatility of the file system, and also that is that everything is discoverable in a clunky manner - if we know the topic (apex or drupal) and can approx the time frame, the info will be found. Where is lacks is search, integration, cross referencing, etc.
Is there any chance that grav can (in part) lean on an existing structure like this? Not import the information (which is what I’ve done in my turn-it-into-a-database experiments), but actually tap the existing assets? It can be very low overhead to place whatever resources are useful into the event’s folder. That’s why I have been hesitating to pull it into a db.
My initial guess is that this kind of data adoption will be difficult even for a file based system like grav, but thought it be worth asking. There might be other reasons to evaluation grav but this is my initial interest.
I’m not a php coder so it’d be a compound task to attempt to write something that might extend grav for a purpose like this.