Hacker News new | past | comments | ask | show | jobs | submit login

Why would you do this? Who else does it? And how is it superior to just signing up with a hosted Wordpress (like 30% of the Internet)?

EDIT: Feel free to downvote but please answer. TFA does not answer it.




My mother for example does this. She’s writing her travel blog in Botswana, where internet connectivity is not a given and often spotty. She uses middleman as static site generator, hosted on an S3 bucket. That gives her the option to write the post, check it, commit and upload it. If the push doesn’t go through, try again (another day or hour sometimes). Try doing that with hosted wordpress.

We do it for our company website. Markdown makes it easy to have a pull-request-based workflow for reviews. It’s neat and uses the tools we as developers are used to. Another advantage is that the end result is static pages. We can literally host them anywhere, though we’re currently using netlify for convenience. They don’t need security patches either.

Does that make it superior to hosted WordPress? For our needs: yes. For other people’s needs? Don’t know.


A lot of people do it. Performance and minimal maintenance are among the reasons.

WordPress is good, but some see it as overkill.


You'd be very surprised just how many people are doing this (sort of thing). A ton. Netlify itself is a revelation.


I have no idea. But I do know that I'm not giving control to some walled garden that can yank it at a moments notice.

Might as well be a Facebook page.

Why is the youth so adverse to owning their own data?


It's just static pages. All the code is in your Gitlab/GitHub repo. I wouldn't call Netlify a walled garden, but the workflow definitely does not imply a situation where you'd lose your data in the unlikely event that Netlify goes down or closes shop.

I don't see any vendor lock in evident in any of this. Plenty of flexibility to both move your git code to your own self hosted git, and quite easy to host it on your own webserver on DO or wherever instead of Netlify.


What are you referring to as "walled garden" here? (Also, what does this have to do with "youth"?)


I do that myself for a personal travel-blog I recently started (https://blog.nomakuma.com/) entirely for free using: - GitHub - Hugo with the Casper-Two theme (https://github.com/eueung/hugo-casper-two) - Netlify - TinyLetter (https://tinyletter.com/) for newsletter signups and distribution - Disqus for comments - Forestry (https://forestry.io/) to allow for less-technically inclined people to author posts without touching Git

I think the appeal is that you have complete control over your site/blog and should you choose to somehow monetise the content, e.g., adding singups and subscriptions to premium content or even ads, you can have complete control. With a combination like this you start at 0$/m for ever (or at least until Netlify stops offering free services) and take it from there. I probably won't do this for a travel-blog but its nice to have the choice and to be honest I wanted to try out a combination of the tech mentioned above and see how far I can take it for 0$.

I still have an old blog on Wordpress (http://pyscience.wordpress.com) and its done very well but I never liked the fact that Wordpress just sticks ads wherever it wants to unless I get the premium subscription.


For WordPress, I’ve to be always worried that it might go down unless hosted with a good dedicated provider. Unless it is complex and I want to do lots of things besides just writing/blogging, I try to choose something static than WordPress.

For the many many static sites that I throw out with either Jekyll or just plain HTML/CSS/JS, I know that once I drop them to something like S3 + CloudFront fronted by Cloudflare, it will very very unlikely go down.

They all have their time, places and circumstances.


Please avoid "why would you do X?" when discussing some tool or workflow. It's needlessly confrontational (and through that, restrictive of diversity, as different groups can have different needs and preferences), devoid of information (it doesn't explain the converse, why you shouldn't do X), and lacking in imagination (establishes tradition as a hard principle, and not just a guideline that can be broken depending on the context).

It's good to want to know why some people want to do X, but try to ask it in a way that doesn't make a negative assumption about the people taking a certain approach.


try to ask it in a way that doesn't make a negative assumption about the people taking a certain approach.

I feel like there is a LOT in this comment that is reading much more into a question that very likely are not even there, to take the position of scolding someone just because their inquiry was delivered in brevity.


I don't mean to scold, but I understand that it comes across as pedantry.

It's hard to give good advice in a tone that isn't paternalistic, and I should get better at doing that. Sometimes you just want to ask a genuine question without somebody questioning your phrasing.

What prompted me to give out advice is "Feel free to downvote but please answer". I don't believe the comment deserves a downvote, but I assume (and it may be, as you put it, reading too much into it) that some downvotes come from people who are tired of seeing the attitude I describe in my reply (https://news.ycombinator.com/item?id=7650799#7651343).

It's a case of greedy matching /why would you do/.


Actually, I agree with dictum (and appreciate the pointy comment). Many people read my comment confrontational, or it wouldn't be downvoted.

And then I learned that there is a niche (compared to 30% WP) of technical people that have their content in GitHub anyway and profit from simple deployment through netlify. It just fits their workflow. I had the typical business user (another blog post said everyone!) in mind and I don't see them to be able to handle git so it sounded very far fetched which was reflected in the tone.


What if English is the persons second/third/xth language and that's the best way they know to ask?


Here's why I don't do it: Wordpress.com does not allow for custom Javascript.


I wrote my own static page generator [1] because it feels easier to write in markdown in Emacs and less worries about updates/security. I've also managed to keep a continues stream of output for close to 2 months :-) [2]

[1] https://github.com/john-bokma/tumblelog [2] http://plurrrr.com/


Isn't Wordpress the most hacked software on the web?

This is free (domain aside), doesn't require managing upgrades and presumably has some redundancy.


Free plugins with awful code usually are, wp itself might be okay if you know how to secure it properly - but that so much more technically demanding that almost no one does it. Being so prevalent makes it to a huge target.

SEO experts and social media marketers will tell you that nothing beats Wordpress, but that's not true I've seen plenty of static sites that are much more engaging, work faster and rank higher when they post good content often.


some people (especially HNers) prefer a simple and DIY approach




Registration is open for Startup School 2019. Classes start July 22nd.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: