# Cattle admin workflow

**URL:** <https://farmos.discourse.group/t/cattle-admin-workflow/2598>\
**Category:** Using farmOS\
**Created:** [September 6, 2026, 3:57pm UTC](https://farmos.discourse.group/t/cattle-admin-workflow/2598 "2026-09-06T15:57:29Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [September 8, 2026, 9:15am UTC](https://farmos.discourse.group/t/cattle-admin-workflow/2598/5 "2026-09-08T09:15:13Z")

</div>

I forgot to explain what “conventions” are… 😄

> **[Conventions](https://farmos.org/model/convention/)**
>
> farmOS is a free and open source web-based application for farm management, planning, and record keeping.

> [@Documenting conventions](https://farmos.discourse.group/t/documenting-conventions/1263):
>
> I’d like to propose we establish some standard processes for documenting conventions used in farmOS, in the form of a new Git repository managed by the farmOS community. For background on what we mean by “conventions”, see: [Conventions | farmOS](https://farmos.org/model/convention/) To quote from an earlier discussion: A lot of the discussions thusfar have been focused on how to implement conventions in different ways (eg: with quick forms, config entities, JSON schemas, RDF/JSON-LD, tooling for validation, etc). But as a first s…

---

_[View the full topic](https://farmos.discourse.group/t/cattle-admin-workflow/2598)._