Earlier quoted context omitted.
I'm really shocked at these types of comments (which I'll note have only appeared from HN) but it's worth addressing. Nonprofits have limited resources and thus need to be able to update their own website with a tool like Wordpress or another CMS. Static templates are sometimes okay but are not an end-all solution. So far in our first three weeks since launch we have had 25 applicants - half of which require a featur…
GitHub can work as a CMS for most use cases. At least in most of the cases where the nonprofits wouldn't have the money to waste on expensive hosting services every month, or to deal with CMS systems bugs. It would have been much better if you made websites static by default and only in the cases in which the nonprofits would really need a hosted solution you would do that. Doesn't make sense to do the expensive/slow…
And "trapped forever" is defined as the inability to copy / paste the output source of the CMS into a static file HTML, correct?