IRC logs for #farmOS, 2022-01-14 (GMT)

2022-01-13
2022-01-15
TimeNickMessage
[23:39:55]* coilWinder[m] has joined #farmos
[01:25:18]* farmBOT has joined #farmos
[11:00:11]* raul[m] has quit (Quit: You have been kicked for being idle)
[11:09:48]* MarcosCarballal[ has joined #farmos
[11:12:21]<MarcosCarballal[>Spatial Front begins development today on using FarmOS as an input source for soil health demo trial data! Exciting stuff. Expect us to start bugging you all more :)
[11:13:30]<mstenta[m]>That's great news Marcos Carballal!
[11:13:34]<mstenta[m]>> Expect us to start bugging you all more :)
[11:13:35]<mstenta[m]>You
[11:13:44]<mstenta[m]>* You've come to the right place ;-)
[11:14:38]<mstenta[m]>We also host a weekly development call at 12 noon Eastern on Thursdays via Jitsi: https://meet.jit.si/farmos-dev
[11:15:31]<mstenta[m]>But if we need something more dedicated I'm happy to make time when necessary
[11:18:45]<MarcosCarballal[>I'll let the team know about it. Many of the SFI developers that will be working on this are looking at farmOS/Drupal for the first time, so maybe it would be a good idea to set up a dedicated meeting.
[11:18:58]<MarcosCarballal[>Of course, I will try and knowledge share all the great stuff you have already given me
[11:20:04]<mstenta[m]>Sure thing! It sounds like Drupal is being used in a few other parts of the USDA projects, so hopefully the long-term consistency will offset some of the short-term learning curve. :-)
[11:20:53]<mstenta[m]>And yea! I'm excited to see what SFI can contribute back to the project in the process of refining/improving things for USDA's requirements!
[11:24:26]<mstenta[m]>Especially when you get some of your UI/UX folks looking at it. :-)
[11:31:09]<MarcosCarballal[>Yeah absolutely! We are setting up a FarmOS instance on Redhat 7. I know that our designer is going to be working on the design for FarmOS this sprint (next 2 weeks), so I may want to do some knowledge sharing on what is easy/hard to change within the UI.
[12:32:16]<paul121[m]>Hey Marcos Carballal - so exciting! Welcome, and please, don't hesitate to bug us!
[12:33:32]<paul121[m]>re: the farmOS design, I wanted to point out real quick that the Gin admin theme we depend on has some "moderately" significant design changes in the works
[12:35:51]<paul121[m]>You can actually test it out by installing the `3.x-dev`of Gin
[12:36:23]<paul121[m]>* `3.x-dev`of Gin: https://www.drupal.org/project/gin
[12:37:08]<paul121[m]>The changes are pretty minimal really, but it does change some things. Worth noting to the designer I think
[12:37:30]<paul121[m]>* the `3.x-dev` branch of Gin, * of Gin: https://www.drupal.org/project/gin
[12:38:11]<paul121[m]> * You can actually test it out by installing the `3.x-dev` branch of Gin:
[12:38:11]<paul121[m]>(project page) https://www.drupal.org/project/gin
[12:38:11]<paul121[m]>(source code) https://git.drupalcode.org/project/gin
[12:55:36]<MarcosCarballal[>Sure. Is it fair to say that most of the theming of the project is reliant on the Gin admin theme?
[12:56:11]<mstenta[m]>Gin is the Drupal theme that farmOS uses
[12:56:31]<mstenta[m]>It is responsible for all of the CSS, and some of the general HTML wrappers etc
[12:57:01]<mstenta[m]>More structural things (like actual form fields, sections of the page, etc) are generally lower-level
[12:57:13]<mstenta[m]>So a Drupal theme is a bit like a "skin"
[12:57:58]<mstenta[m]>That's just to say: sometimes "UI/UX" changes involve overriding theme CSS, and others involve altering things provided by modules
[12:58:39]<mstenta[m]>Generally speaking, modules will be agnostic of the theme, and just focus on the functionality they need to provide (which includes the content of pages and forms)
[12:59:28]<MarcosCarballal[>Okay great, that gives a lot of clarity, thank you both.
[13:01:17]<paul121[m]>Yes! That's a good way to frame it - these changes I'm mentioning are largely CSS styling. The structure and layout remains the same.
[13:03:10]<mstenta[m]>Marcos Carballal: here are a few more links you might share with designers... they give some good context to the design process that the Gin creators went through
[13:03:16]<mstenta[m]>https://noti.st/saschaeggi/0X9WTY/drupal-gin-admin-theme-the-past-the-pr...
[13:03:36]<mstenta[m]>https://medium.com/unic-com/the-gin-admin-theme-facelift-your-drupal-adm...\
[13:03:41]<mstenta[m]>s/https://medium.com/unic-com/the-gin-admin-theme-facelift-your-drupal-adm...\/https://medium.com/unic-com/the-gin-admin-theme-facelift-your-drupal-adm...
[13:03:58]<MarcosCarballal[>You guys are relentlessly helpful. I love it. :) I will share that info with the designer.
[13:04:10]<mstenta[m]>Gin extends "Claro" which is a new admin theme that is included in Drupal core - so it has a solid future