61–70 of 115 posts
https://pioneer.mymailbox.site/
Link to vite
The deployment can be as simple as one command, in my case
npm run docs:build && scp -r docs/.vitepress/dist/* dev://var/www/pioneer.mymailbox.site/web
Earlier quoted context omitted.
> just manually I would find this tedious for any number of comments. Is there a better way?
Don't host comments. The day when comments tended to have any value on the web passed ages ago. No one blogs anymore, and no one reads blogs anymore, so most of the traffic you get is just going to be bots or cancerous trolls anyway - if you're lucky enough to get any actual human readers at all in the latter case. Or use a hosted service like Disqus or an alternative if you want comments, but the better solution is…
If you need better vetting, consider using webmention/ActivityPub federation and allowlisting individual hosts for automatic approval. There is definitely spam on such protocols too, but they tend to come from the same domain/IP so denylisting is very efficient in dealing with it.
Jekyll + GitHub Pages = Static blog with free hosting You could substitute Jekyll for other supported frameworks. Pros: * Markdown (so super flexible) * Git as the backbone (free CRM, free history) * Customisable (if you know how to code) * Free templates Cons: * Jekyll is a bit of a pain on Windows but should be fine on Linux/Mac * Images might not load super quick from GitHub's servers * You need to know basic Git
Another con: you depend on Microsoft's good will to serve your blog, as they own Github. That kind of workflow is amazing but you should probably consider going with a non-profit software forge that runs on donations and will protect (y)our interests (like codeberg.org for example).
A key take away from many years of running a blog as a static website is that may add friction to your process. Unless you have some sort of CI/CD going on, the chances are that one can only post from their own computer, while using something like Wordpress allows them to post from anywhere — including their mobile devices — which leads to a ton of serendipity. You might want to evaluate if posting from multiple devi…
I just do git push to post, the site generator does the rest (including diffs and optimized change rendering in my case). You can git push from anything these days, including an iPad (which is basically what I do). (edit: why the downvotes?)
Earlier quoted context omitted.
Why all the JS/TS though? Part of what's great about a static site is serving simple HTML/CSS pages that look great, degrade gracefully, and don't hog users CPU/RAM like JS applets do.
With Next/Svelte/Remix you can only ship HTML/CSS if you want. Reason to use those frameworks is that I find their mental model to fit nicely for progressive enhancement. For my blog, I plan to have interactive content via MDX or something similar so there will always be optional JS involved.
I use Zola[1]. Single binary, simple structure, minimal frontmatter. 1. https://getzola.org
I am really interested in the 'buggy'ness of WP. Especially when you basically would be served with a static website, I do wonder which 'bugs' in WP are annoying you so much.
Not OP, but maybe the new over-designed/over-engineered Gutenberg UI may feel slow, overkill and may only brings loads of unnecessary complexity, especially for someone who want to keep a simple blog, or is used to write his posts in simple markdown.
I don't use Gutenberg but I don't think it is over-engineered, I think a block-based approach is a sensible way forward.
I'm not exactly recommending to use it as i make no guarantees (yet) about keeping a proper changelog and maintaining backwards-compatibility, but if someone's feeling hacky i would certainly love for other people to try it and expand it or just give feedback.
Earlier quoted context omitted.
Another con: you depend on Microsoft's good will to serve your blog, as they own Github. That kind of workflow is amazing but you should probably consider going with a non-profit software forge that runs on donations and will protect (y)our interests (like codeberg.org for example).
GitHub sites were in place long before the acquisition. (I'm an MS FTE now, but have been using GitHub since the beginning and am a bit weirded out by this perception that corporate ownership is a taint of some kind.)
Microsoft famously tried to outcompete the Internet via their existing monopoly on Windows with MSN (not just the messenger) back in the day, and have always been super hostile to free-software. They have also, like any corporation, stopped to maintain several services over the years and the fact that beyond their public image they don't have any incentive to keep Github Pages going doesn't inspire me confidence.
The fact that Github Pages were up and running before Microsoft's acquisition of Github is a reason to be worried. There's no money flowing in from that service and it probably costs a fair amount. Despite their "we love open source" statements, i've yet to see Microsoft open-sourcing any significant product (including Github) and specifying/standardizing existing stuff like Github Actions.