Renaming folders works as expected, with the exception of renaming/moving the assets folder. If I modify the configuration of all relevant plugins, those work but Obsibrain functions like Add area don't, because presumably the path to assets is hardcoded (which I assume from glancing at the minified code). This is not a big problem, it's likely straightforward to make it configurable like the rest. I understand why. That said, having an interface where one could define views and buttons by overloading your methods I think would solve my "problem". E.g. Area template has a task view which is basically "just" a custom dataview view which in turn works through a callback in Obsibrain afaics pp.utils.dataview.tasks.render({ dv, ...props }) . I'm looking for a way to edit this to be able to do basic things like renaming Completed Tasks to Completed or changing the color. I could presumably do this by having my own render function that is called instead. My point with forking your repo was just a potential short term solution. Yes, I don't intend to contest whether PARA is a good choice. The Bulletproof paradigm is simply a flashy PARA, it's just an example of why you might want to have a project view in an area template, when you link projects to areas. I'm interested in having options like defining my own connections between notes and using my own properties, which I could do by editing the template and defining my own buttons while using your generic scripts and templates. I believe this something powerful that Obsibrain can potentially offer. To illustrate my point in the simplest manner possible, I'm basically saying that it would be good to have the ability to modify the views like the ones below (changing color, text, merging the two etc.). I presume you've coded up these views within Obsibrain render function and editing the minified code isn't the way to go about it. For power users this is as simple as copying your method and modifying it to their liking and sticking it in scripts/dataview/views/ then changing the templates to call it instead, it's quite straightforward afaics. P.S.: I could also be entirely wrong, I'm making a lot of assumptions about how Obsibrain works Image N4M3Z — Yesterday at 6:55 PM The more I think about, we could basically just have a folder named custom within assets, and if there are files of the same name, e.g. templates/para/area those get used by your existing functions instead and then you can just put a sample render method there for people to overload but keep your codebase private.
