TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: How do you handle blog post uploads for your website?

3 pointsby jdnordyalmost 5 years ago
Currently, I’m adding markdown files to the github repo for my website, which then deploys through vercel. I use next js and the getStaticProps api and the dynamic routes functionality to generate a page for each markdown file. Right now, this works great as I only have 3 writings. But I imagine as a continue to post, this won’t scale well. So I’m curious to hear what everyone else does for their website?

2 comments

outerouterspacealmost 5 years ago
I use a Node-based static site generator called Hexo [1] for the blog I&#x27;m most active with. I actually wrote about my experience setting up Hexo on that blog. [2] I went with Hexo because of the availability of themes, plugins and documentation.<p>My workflow goes like this: 1) Write blog post in markdown, making sure to include the YAML front-matter (JSON&#x27;s also an option), 2) Generate the static pages from that blog post using `hexo generate` in my CLI, 3) Use `hexo server` in my CLI to preview my changes locally in my browser, 4) Upload my files to my remote server (I haven&#x27;t automated this part yet)<p>Alternatively, I&#x27;ve tried static site generation &amp; deployment with Node, TiddlyWiki [3] and GitHub Pages. Although TiddlyWiki&#x27;s not meant to be a static site by default (nor a blog), there&#x27;s a lot of helpful documentation out there [4] that explains how it can be used in that way. I got a static representation of my TiddlyWiki digital garden [5] up and running in an afternoon, whereas Hexo took me a few days to figure out.<p>[1]: <a href="https:&#x2F;&#x2F;hexo.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hexo.io&#x2F;</a><p>[2]: <a href="http:&#x2F;&#x2F;practicing.design&#x2F;2020&#x2F;05&#x2F;02&#x2F;my-review-of-hexo-a-node-powered-static-site-generator&#x2F;" rel="nofollow">http:&#x2F;&#x2F;practicing.design&#x2F;2020&#x2F;05&#x2F;02&#x2F;my-review-of-hexo-a-node...</a><p>[3]: <a href="https:&#x2F;&#x2F;tiddlywiki.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;tiddlywiki.com&#x2F;</a><p>[4]: <a href="https:&#x2F;&#x2F;nesslabs.com&#x2F;tiddlywiki-static-website-generator" rel="nofollow">https:&#x2F;&#x2F;nesslabs.com&#x2F;tiddlywiki-static-website-generator</a><p>[5]: <a href="http:&#x2F;&#x2F;meet-me-in.space&#x2F;" rel="nofollow">http:&#x2F;&#x2F;meet-me-in.space&#x2F;</a>
noble_plebalmost 5 years ago
Just like you, I use github pages for hosting my blog, but I also use a static generator called Pelican[1] to generate its contents (pages and blog posts). Its written in python and open source, although other options like Jekyll and Hugo are also quite popular.<p>Using a static generator gives structure to your blog content and links, its also easier to maintain a static site compared to any other method.<p>[1]: <a href="https:&#x2F;&#x2F;docs.getpelican.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;docs.getpelican.com&#x2F;</a>