# Documenting conventions **URL:** \ **Category:** Conventions\ **Created:** [June 7, 2022, 8:21pm UTC](https://farmos.discourse.group/t/documenting-conventions/1263 "2022-06-07T20:21:52Z")\ **Posts on this page:** 1\ **Showing post:** 26
**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:** [August 23, 2026, 12:01pm UTC](https://farmos.discourse.group/t/documenting-conventions/1263/26 "2026-08-23T12:01:50Z")
> [@Declarative data entry conventions](https://farmos.discourse.group/t/declarative-data-entry-conventions/2591): > > (Quite the obtuse topic name, but we have to start somewhere! laughing) Spinning this off as a dedicated topic from: This is a fun (and functional) idea that relates to the “Documenting Conventions” discussion. The first step to exploring this might be brainstorming what the YML might look like for representing a “data entry pattern” (aka a “declarative data entry convention”)… This is essentially an ETL ([Extract, transform, load - Wikipedia](https://en.wikipedia.org/wiki/Extract%2C_transform%2C_load)) specification. We are starting with some sem… --- _[View the full topic](https://farmos.discourse.group/t/documenting-conventions/1263)._