| [10:41:00] | * jonasbits has quit (Quit: No Ping reply in 180 seconds.) |
| [10:42:09] | * jonasbits has joined #farmos |
| [15:07:30] | <mstenta[m]> | jgaehring: regarding www.farmos.org vs docs.farmos.org question... i suppose the blog idea is a good distinguishing point |
| [15:07:43] | <mstenta[m]> | using gatsby to aggregate is what would enable pulling from a blog repo |
| [15:08:32] | <mstenta[m]> | and i assume that if we had two sites (one "public facing" www + one "technical facing" docs) then the blog would probably be on the www |
| [15:09:53] | <mstenta[m]> | (we could make ANOTHER gatsby aggregation setup separately, if they needed to be separate, i suppose...) |
| [15:10:16] | <mstenta[m]> | i'm still a bit on the fence about whether we should have two sites or not... kinda leaning more towards having two now :-) |
| [15:11:03] | <mstenta[m]> | it would provide more flexibility to be creative with the "public facing" one - while being more rigid and technical with docs.farmos.org |
| [15:11:30] | <mstenta[m]> | also, i've been linking to docs.farmos.org everywhere haha... so we'd either need to maintain those links or have redirects if things change |
| [15:11:33] | <mstenta[m]> | (just thinking out loud right now) :-) |
| [15:12:16] | <jgaehring[m]> | mstenta[m]: yea, that's just what I was gonna say, definitely an option |
| [15:12:30] | <mstenta[m]> | feels overly complicated though |
| [15:12:41] | <mstenta[m]> | maybe the www site should be more simple/static |
| [15:12:46] | <mstenta[m]> | (shrug) |
| [15:13:13] | <mstenta[m]> | just thinking - if we hired a designer, who also knows HTML+CSS, we could give them more freedom if we didn't have any code constraints to begin with |
| [15:14:18] | <mstenta[m]> | keeping the public-facing site as decoupled from everything else as possible might be good |
| [15:14:30] | <mstenta[m]> | (makes it easier for the NEXT redesign) ;-) |
| [15:14:30] | <jgaehring[m]> | I've been keeping this opinion under my hat a bit til I finish the scaffolding, but I personally think there is a really strong argument to be made for integrating everything, end-user-facing and developer-facing, which I can go on about when the time is right |
| [15:14:59] | <mstenta[m]> | micro-service style |
| [15:16:45] | <jgaehring[m]> | <mstenta[m]> "also, i've been linking to docs..." <- well, this is all part and parcel of the sitemap decisions we discussed, but if we decide to have a shared landing site for all the technical docs, at say farmos.org/development, then we could just redirect docs.farmos.org to that, or to farmos.org/docs, or farmos.org/farmos, or whatever the heck we end up calling it |
| [15:17:05] | <paul121[m]> | mind = blown re: a potential integration with discourse :-) 🤯 |
| [15:17:09] | <jgaehring[m]> | again, it's a rabbit-hole of decision making, and ultimately more a matter of design |
| [15:17:29] | <jgaehring[m]> | paul121[m]: oh yea! I love that idea too! |
| [15:20:52] | <paul121[m]> | this just in, fairly important consideration for the Gin theme: https://www.drupal.org/project/gin/issues/3205375#comment-14287758 |
| [15:33:05] | <jgaehring[m]> | <mstenta[m]> "just thinking - if we hired a..." <- honestly, I think the Gatsby stack is still a great choice there... It's basically just React, which is honestly the prevailing standard when it comes to frontend web design these days, and there wouldn't be anything the designer would need to work with that would even require any knowledge of Gatsby, just React, and any other tools they wanted to bring with them |
| [15:37:21] | <jgaehring[m]> | also, I dropped this again in the call/agenda topic, but this is where the scaffolding fits into the bigger scheme of the farmos.org redesign, as I saw/see it: |
| [15:37:22] | <jgaehring[m]> | https://farmos.discourse.group/t/farmos-org-redesign/505 |
| [16:29:57] | <symbioquine[m]> | <paul121[m]> "mind = blown re: a potential..." <- Relevant: https://conversation.sevarg.net/t/moving-my-blog-from-blogger-to-jekyll/498 |