Following on the discussion in the last monthly call, here are some notes from this week’s dev call with ideas for the first farmOS.org blog posts.
The idea is: we (the core team) can collaboratively write the first one (as a basic intro), and then we can commission future posts from other members of the community, with bounties paid from OpenCollective.
Ideas for first few posts:
- Intro to farmOS (see below) - written by core team
- How do you get farmOS installed/running?
- Demo site (for playing)
- Farmier (hosted option)
- Self-hosted (not covered? stay tuned for future posts!)
- Plant management in more depth
- Animal management in more depth
Intro to farmOS (first post)
- How to get started with farmOS as a complete beginner
- Link to previous post for getting a farmOS instance / point to demo site as a quick suggestion (emphasize data will be lost, great for experimenting)
- Quick overview/walkthrough of structure
- Brief data model overview (assets and logs)
- Basic navigation/pages/hierarchy
- Point to docs for user guide / more info
- Mapping some locations to start
- How to use farmOS map (briefly)
- “Locations” (aka Land/Structure assets)
- Maybe two pathways/examples:
- Planting quick form (unless using demo site, you may need to install via Settings > Modules)
- Submit the quick form once, then go to see the records created
- Look at the map to find your plant
- Add an input/harvest log?
- When your plant is harvested/terminated (assuming it’s an annual), archive it!
- Add an animal asset
- Use bulk actions to “Move” them to a paddock
- Add an observation log?
- When an animal is sold/died/etc archive it!
- How to think about data
- “Data is intended to be iterative. Assets can be archived. Logs flow into the past. Your records can become better / refine over time!”
- Most important: Start putting data in! Even if it isn’t perfect. The process of learning what data needs to be tracked will be a bit different for everyone.
- Happy record keeping!