Yea! Views is super powerful! It’s basically an SQL query builder UI, and we use it for pretty much all the lists in farmOS.
Can you explain a bit more about how changing things in views works with updates? I thought after an update everything outside of the “sites” folder is changed. Is the views part of the sites folder?
Yea, so basically Views is “configuration” and that stuff is potentially stored in two places: in code and in the database. All of the Views that farmOS provides are stored in code in various modules. But, it’s possible to “override” that code by making changes to the Views config in the UI. When that’s done, the new config is saved in the database.
When it comes time to update, if there are upstream changes to Views config, the code files will be changed, but the database config will not (shouldn’t be anyway). Then, you have the option to “revert” the Views to use the config stored in code, and discard your overrides, if you want.
The Features and Diff modules can also be used to examine exactly what is overridden. Try this: make some changes to a View, then go to /admin/structure/features.
There’s a lot more to it, but that’s the basic idea! It’s super powerful for customizing things, but the main consideration is updating. That’s why I wrote this (somewhat vague) page on farmOS.org: https://farmos.org/development/update-safety/