[Al_Abut]Ugh, after two years of using Astro, I might have to throw in the towel and migrate to something like Eleventy. It’s been an awesome ride but RSS support isn’t native and supporting full content posts is a constant struggle that’s finally worn me down.
DanQ, barnaby, JadedBlueEyes and [aciccarello] joined the channel
[aciccarello][Al_Abut] 11ty has worked well for me. It's not very opinionated so it can get messy if you're not careful. But it does have an RSS plugin and there are lots of community examples that are helpful.
[Al_Abut][aciccarello] nice. Get ready for me to bug you about it. That’d be a nice full circle moment actually, considering you helped me get my Astro setup going at the first IWCSD :)
[aciccarello]I migrated from a Jekyll site so it was nice to be able to reuse the same code structure. Plus I'm more comfortable in node/JS land than Ruby.
[aciccarello]There are a million starter projects which are helpful if not overwhelming. I kinda like to start with a blank slate so I have more control/understanding but I'd at least recommend getting a sense of how others have structured things.
[Al_Abut]I’ve got a good amount of technical debt I want to clean up before I attempt a migration, things I’ve been putting off that would clean up the templating a lot
[Al_Abut]But just even the quick research I did today looks promising and I see what you mean by the flexibility. E.g. I can keep using components and switch from using MDX to WebC instead, or even add some support for MDX and use components that way, and compile it all to RSS whichever way I go with.
[Trevor_Morris]"Inscrutable" is the *perfect* description for the 11ty docs, but I just don't know *why*. I often get lost looking for something I know is there.
[Trevor_Morris]I've built a few *small* projects with 11ty, making improvements to how I organise it each time. Also, moved from Nunjuck to WebC which was a frustrating process.
barnabywalters and [John_Gorenfeld] joined the channel
[Murray]that said, just re-read your post, and think I now understand what you mean by "supporting full content posts", so I imagine you've already tried this (swea
[Al_Abut][Murray] no apologies necessary, thanks for chipping in! I feel like there’s way more Astro people coming out of the woodwork lately compared to when I started and felt like I was hacking through a jungle alone. I still love it and could see ending up with a hybrid setup, with Astro for my non-blog pages, who knows?
[Al_Abut]But yeah, the native package for RSS only supports full content posts for markdown, not MDX. Which is a baffling design flaw considering the entire power of Astro comes from components, it’s way overkill if you just want to throw some markdown up on the web.
[Al_Abut]Baffling until I realized that blogging isn’t the main use case, Astro’s target audience seems to be DX documentation type of knowledge bases and also marketing pages, which to be fair it is absolutely world class at. The documentation for Astro is *gorgeous* and best in class, I’ve never seen anything like it. It’s why I got sucked in! Very newbie-friendly. It didn’t just get my initial setup going, it leveled up my javascript sk
[Murray]Ah yeah, that's fair. I don't really use Markdown at all, let alone MDX; blog posts are all pulled in from a CMS (another area Astro is very good at 😄). Likely why I'm not having the same issues. Or maybe I am, but I haven't noticed!
[Murray]Funnily enough, I just started a new (and also *very* old) project at the weekend, where I want to test MDX in Astro, so nice to know about a potential footgun. Luckily, this is an archive job, so it will never get updates and doesn't really benefit from RSS; I can always handwrite a feed if I deem it worthwhile 🙂
[Murray]I use Craft for just about everything I do these days 🙂 Its Headless mode has been a mini revelation for me, but its the actual editorial experience that keeps me locked in
gRegorLove_, DanQ, [KevinMarks]1, [Trevor_Morris]2, [Trevor_Morris]1, barnaby, gRegor and [John_Gorenfeld] joined the channel
[morganm]Hey I think I've been the target of a false generated bug report that an API key was exposed on one of my old repositories for a personal project from years ago . Mainly I'm convinced there is no such a active API key as described in the report but it's possible a API key was previously active there buried in a commit from 2016. A sketchy seeming account sent the report to the W3C under a subject line that I was an employee , the
[morganm]I got forwarded the report from someone at the W3C anyways I'm convinced so far it's spam I really don't have any Google maps API key as claimed on any active account
[Al_Abut]Scary stuff. The fact that it’s highly targeted and got a rise out of you means they succeeded on some level. A friend told me about how their coworkers at google got targeted by “spearphishing” attacks like that.
[Al_Abut]E.g. here’s the updated schedule for your kid’s soccer games. Open the PDF and boom, you’re silently owned in the background. And this was like 10+ years ago.