On the farmOS Monthly Call for April 2020, we recorded an overview of some of the ways that you can customize/modify farmOS. This is intended for advanced audiences and developers.
This is “Part 1”, which covers a lot of the things that can be customized directly in the farmOS UI, without requiring code or custom module development. The intention is to cover those topics in “Part 2” on the May 2020 Monthly Call.
Part 1: https://youtu.be/V1oTO3QSSWY
Update Part 2: https://youtu.be/iypN8X0Nf9k
The idea to do this came out of the discussion in this GitHub issue: https://github.com/farmOS/farmOS/issues/262
Thanks @BOTLFarm for putting together an agenda document that we worked from (link below) and @jgaehring for taking notes in that same document while I was talking. 
Agenda and notes: https://docs.google.com/document/d/1yO15xdGGH4YkqhRXjtAkmI6SZy0uelwN3w2kDnNEsuc/edit
Looking forward to digging in a bit deeper for “Part 2” next month!
Is the /admin/modules page seen in the video available if you are using Farmier or only with a local instance?
Great question @applecreekacres!
No, Farmier hosting is considered “standard farmOS” and does not allow access to modify the data architecture or entity configuration through the UI.
Note that this is intended for advanced users. And you must be hosting farmOS yourself to access most of the options demonstrated (not enabled on Farmier instances to keep upgrades simple and hosting cheaper).
(https://twitter.com/getFarmier/status/1247984327440445440)
The main reason for this is if you override things, it can cause conflicts during upgrades. I provide “farmOS-as-a-service” through Farmier in a way that ensures things can’t break, and allows me to be confident that I can upgrade everyone from one version of farmOS to the next. So if you want to experiment with advanced configuration/development, you must do it on your own server.
BUT! If you make something that would be useful to others, you can contribute that back so that it can be included in “standard farmOS” for everyone’s benefit!
See also this big and very vague warning page on farmOS.org: Update Safety - farmOS.org
I try to balance the super flexibility of Drupal/farmOS with making sure it doesn’t break for the majority of folks who need it to “just work”. So that’s what Farmier is for, in my mind. Hope that all makes sense! 
Update: we recorded part 2. I added a link to the description above.
