11–15 of 15 posts
Ruby is a terrible choice. Use a Node.js based static site generator. You could even host on Amazon S3 (super low cost but globally distributed and redundant)! Look at Whitesmith/Blacksmith/etc.
You have a fiction book. People will want to know what genre it is; what the reviews say; what it looks like; a sample chapter; where to buy it; publisher and ISBN and etc. If you're lucky they'll want to discuss it with other readers or to ask you questions.
If I'm in a bookshop and I see a book, and I websearch it there are a few things that happen.
1) I get a great website. I am more likely to buy the book.
2) I get a terrible website. I am less likely to buy the book.
A terrible website is one that does a bunch of stuff before I get to the information I need.
Skip the SASS, LESS, Python, WordPress, Flask or other stuff everyone here is talking about. You don't need it.
Some plain static webpages. Period.
Ruby is a terrible choice. Use a Node.js based static site generator. You could even host on Amazon S3 (super low cost but globally distributed and redundant)! Look at Whitesmith/Blacksmith/etc.
Pray tell, why is ruby a terrible choice? You can get a basic website up and running with Rails in less than 10 mins.