# First blog posts brainstorm (dev call 2022-06-09) **URL:** \ **Category:** Community\ **Created:** [June 9, 2022, 4:50pm UTC](https://farmos.discourse.group/t/first-blog-posts-brainstorm-dev-call-2022-06-09/1264 "2022-06-09T16:50:40Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jgaehring](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/jgaehring/32/927_2.png) [@jgaehring](https://farmos.discourse.group/u/jgaehring)\ **Post date:** [June 9, 2022, 9:21pm UTC](https://farmos.discourse.group/t/first-blog-posts-brainstorm-dev-call-2022-06-09/1264/2 "2022-06-09T21:21:09Z")
I didn’t get around do doing a concrete breakdown of the remaining technical tasks to prepare [farmos.org](http://farmos.org) for the blog’s source repo, as I planned after today’s dev call. It should be rather minimal, as I mentioned earlier, since a lot of the work is done and just needs to be merged, but I still want to look closer at my working branches to make sure I haven’t missed anything. That said, I did want to just drop the links to those branches so anyone chomping at the bit to see how it works can check it out. Here’s my fork: > **[GitHub - jgaehring/farmOS.org: Repository for the official farmOS.org website.](https://github.com/jgaehring/farmOS.org)** > > Repository for the official farmOS.org website. Contribute to jgaehring/farmOS.org development by creating an account on GitHub. The branch you’ll probably want is the `blog` branch: > **[GitHub - jgaehring/farmOS.org at blog](https://github.com/jgaehring/farmOS.org/tree/blog)** > > blog It branches from the [`site-data`](https://github.com/jgaehring/farmOS.org/tree/site-data), which has the changes that restructure `source-repos.js` and renames it to `site-data.js`. I just rebased both onto the current `main`, so they should be good to work with locally. The source I’m using for testing is here: > **[GitHub - jgaehring/farmOS-blog: Community content for the farmOS website](https://github.com/jgaehring/farmOS-blog)** > > Community content for the farmOS website. Contribute to jgaehring/farmOS-blog development by creating an account on GitHub. It’s listed in `site-data.js` as `jgaehring/farmOS-community` b/c I changed the name on GitHub at some point, but you can use it as is or set up your own source repo to test with if you like. I think those are all the links. Hopefully I’ll get time tomorrow to assess more accurately what work remains. Once I do so, I’ll open a new proposal for the work with time estimates and a quote. once that’s all worked out I can The one outstanding issue is how we want to structure Front Matter, because that will have a direct impact on the estimates and quotes I provide. I encourage anyone interested to look at our [previous discussion](https://farmos.discourse.group/t/farmos-blog-tutorials/976/4) about Front Matter, where I laid out some possibilities, but if I don’t hear anything else from anyone on the issue I will just scope it for some minimal YAML properties that seems sensible to me, and we can review/amend before approving that proposal. --- _[View the full topic](https://farmos.discourse.group/t/first-blog-posts-brainstorm-dev-call-2022-06-09/1264)._