Ask HN: What's your blog / portfolio stack?
41–49 of 49 posts
Re: Ask HN: What's your blog / portfolio stack?
#42It works so well, that I’m working on oknext.io using the same stack .
Re: Ask HN: What's your blog / portfolio stack?
#43Re: Ask HN: What's your blog / portfolio stack?
#44All self-hosted, no middlemen, just me, my own templates, formatting, code. I focus on design simplicity, lightweight pages, and being as accessible as I can. This means both visual accessibility(Every page is hand-checked with WAVE's browser extension(https://wave.webaim.org/) and Sa11y(https://sa11y.netlify.app/)) and technical accessibility(Low- or no-JS always, make pages as lightweight as possible).
To me, this is the ideal experience, where it's all stuff I've written, and even helped contribute to(I've been doing a lot of revising the Lume docs since the author isn't a native English speaker, been a relaxing and fun experience). Also, the entire design makes sense to me, and I haven't had that in the past with any other blog stack, so this feels like an end-game blog setup.
Re: Ask HN: What's your blog / portfolio stack?
#45Re: Ask HN: What's your blog / portfolio stack?
#46Re: Ask HN: What's your blog / portfolio stack?
#47Re: Ask HN: What's your blog / portfolio stack?
#48https://github.com/eoncarlyle/portfolio-website https://iainschmitt.com/post/november-2024-grab-bag#moving-t... https://iainschmitt.com/post/new-syntax-highlighting
Re: Ask HN: What's your blog / portfolio stack?
#49I built shedtheshade.com few years ago, and learnt a few things about blogs along the way.
Here are my takeaways:
- Substack is great for starters
- Mailing should be always included with blog config for best results
- If a blog is updated, best way is to make sure changes are reflected in real-time as it can do a lot of damage.
- People(and crawlers) don't tend to wait for a lot of time, make sure it is fast for at least first paragraph loading in few seconds
- Understanding about Readability in modern society is important
- Media hosts should be served via CDN
- Comments should be independent to blog post db because it's the only user entered content with possiblity of getting your blog hacked
Hence the best way would be:
- Some SSG (preferably SEO optimised)
- Backend API on CF Workers
- Websockets for Blog Update
- Some DB (Preferably NoSQL for Posts and SQL for User Acc. info)
- Additional Layer of CDN
- API for Top or Suggestive Posts
- Editor.js for Editing