I built something for a similar goal, make it easy for someone to start their blog. But instead it's a static website, clone the repo, adjust the config.ts, write the posts in markdown, host anywhere: https://starter.bryanhogan.com/
This is the one use-case where !important makes the most sense, as it's a utility class they you only use if you want it. The other solution would be to make other CSS less specific, e.g. using `where` in the markdown.css file, but that would be more messy.
> The simplest way to build a high-quality website.
The build (generation) step should be able to execute on/inside the browser runtime (using standardized APIs, not hardcoded against proprietary APIs that the NodeJS people invented).
That would mean using a completely different architecture, and I think there many benefits to using Astro. I like your underlying goal of fewer environment-specific dependencies, but the ones used here were carefully selected because they do provide a benefit.
I don't think that's moving the goalposts. The goal isn't to minimize dependencies or avoid Node APIs. It's to make it easy to build a high-quality website with a good, simple developer / creator experience.
The thing you linked doesn't meet the bar I'm aiming for, either for the resulting site or for the experience of building it. Astro helps me achieve those goals as part of this project, which is why I consider it a beneficial dependency.
You moved the goalposts from "The simplest way to build a high-quality website" to "there are benefits to using Astro".
> The thing you linked doesn't meet the bar I'm aiming for, either for the resulting site or for the experience of building it.
And now you're applying a standard that was never claimed to have been met.
There's a way this back-and-forth could have gone, which is right after I emphasize that "The simplest way to build a high-quality site" doesn't belong at the top of the page because it doesn't reflect what you're actually doing, then you say, "Oh yeah, I see what you mean. I went ahead and changed it to something that's more accurate and (a little less hyperbolic). I'm not trying to fundamentally throw out the experience that people who are already familiar with building sites with conventional NodeJS-based frameworks like Astro are used to. Just trying to make it a little easier."
The build (generation) step should be able to execute on/inside the browser runtime (using standardized APIs, not hardcoded against proprietary APIs that the NodeJS people invented).
See also <https://crussell.ichi.city/pager.app.htm>
> the [dependencies] used here were carefully selected because they do provide a benefit.
You're moving the goalposts.
The thing you linked doesn't meet the bar I'm aiming for, either for the resulting site or for the experience of building it. Astro helps me achieve those goals as part of this project, which is why I consider it a beneficial dependency.
> The thing you linked doesn't meet the bar I'm aiming for, either for the resulting site or for the experience of building it.
And now you're applying a standard that was never claimed to have been met.
There's a way this back-and-forth could have gone, which is right after I emphasize that "The simplest way to build a high-quality site" doesn't belong at the top of the page because it doesn't reflect what you're actually doing, then you say, "Oh yeah, I see what you mean. I went ahead and changed it to something that's more accurate and (a little less hyperbolic). I'm not trying to fundamentally throw out the experience that people who are already familiar with building sites with conventional NodeJS-based frameworks like Astro are used to. Just trying to make it a little easier."
Instead we got this.