Hi all,
I sat down this weekend and finished up the new landing page for my book Deployment from Scratch:
https://deploymentfromscratch.com
I appreciate any feedback you might have, so I can fix it before my launch!
Love how the first thing you do is describe how the reader will be transformed: "Imagine what could you do if you read this book..." instead of just telling us the content.
Thanks Jake!
Hello! First off, I think the book idea is great. We need more of these type of resources that explain how things should work in production. Especially for those people that are trying to learn as they build.
I have some feedback regarding the site, but please take it with a grain of salt as I am not a web designer.
Hopefully this helps. Again, take it with a grain of salt. These were just the thoughts I had as I looked at the page for the first time.
Good luck!
Thanks a lot for taking the time to review the page!
I think your insight is great. As for beta & the icons yes, they will be different, I just didn't have a good idea what to put there and though it's empty. I'll rethink it. I thought the "beta" page will stay only a few days so I didn't implement what I had there before -- this should already be ready for the final release.
As for the chapters, yes, I think everybody thinks it's long and I am thinking how to shorter it. Great you liked the preview, it's my fav part so I don't want to give it up:).
Thanks again!
The landing page is good but honestly, I wouldn't like to pay $35 and read 500+ pages just to make deployment. I'd prefer to pay $5/month to somebody or something what makes deployment for me.
Thank you for taking the time looking at it.
Yes, you are right. That's not the value proposition of the book. It cannot be. It's much more about knowledge targeting developers that have interest in learning it.
That said, even the money argument stands -- just not the way you read it (which is my fault that it's not clear).
The demonstrations I have are ready to be used. For example a Heroku Standard 0 managed database with 4 GB of RAM and 60 GB data is $50/month [0]. Just the database demo gives you an option to run a DO droplet with 4 GB of RAM, 2 vCPUs, and 80 GB of storage for $24/month.
That means you'll get your $35 back in just 2 months. Heck, you'll earn yourself $17 and then keep earning $26 every month, plus you'll learn how to set up a production database + many more other things.
Is it really a bad proposition?
(*Yes, it does not have all the niceties of Heroku, it's not 1:1 comparison. You need to learn a little bit about running a database.)
[0] https://elements.heroku.com/addons/heroku-postgresql
Sorry, I don't get this part. What is a "database demo"?
I see, your book is about saving money but I can't figure out how.
I see. The demonstration is a script that sets up a virtual server. There are three. One for a static website, one for a Rails application (all on one server inc. PostgreSQL and Redis), and one for standalone PostgreSQL.
I call them demonstrations since they show many things learned in the book, but I expect people to tweak them for their use-case. As for the database demo, you don't really have to tweak it, it just works.
Here's the example readme: https://gist.github.com/strzibny/4f38345317a4d0866a35ede5aba99a1e
I get the concept of the book and why some one would want it alternatively having to look through mountains of docs but why not AWS ECS or is it in the book?
Because ECS "is a fully managed container orchestration service (...)" and I didn't want to write a book about one specific service.
But don't get me wrong, Amazon ECS is fine!
While I don't write about ECS, the gist of starting on ECS is to build a good container. I cover that part. And if you want to combine it with a self-hosted database, I cover that part too.
This comment was deleted 5 years ago
IMHO,
I do have a e-mail list and that's where most of my sales are happening. Just this redesign version don't have it right now. I am close to the final release, so I am not sure if I continue collecting the addresses.
Thanks a lot for the input, will certainly have to think about those CTA buttons!
Hey Josef, great page. In most points I agree with @unsungNovelty. That what I would add:
Good luck with your book 🙃
Dennis
Thanks a lot for taking the time, Dennis!
I'll think again of those call to action buttons.
Hey @strzibnyj,
I am new to the Indie community. So please take the suggestions with a pinch of salt.
These are the things that I thought could be improved. Hope this helps.
PS: My native tongue is not English. So if the tone came out rude with the above feedback, please ignore as that is not intentionally.
Thanks a lot of taking the time to think about it!
You made some good points. I agree with you on the chapter section, I am already thinking how to make it more compact/interesting. One testimonial isn't much, but it's the one I got without asking. I'll be hopefully adding more.
I won't remove the preview section as that's the one I really like personally and something other book pages should probably steal. It allows me to put content further down the book as examples. I mean I might need to improve it, but I really think it should be there.
Thanks again!
You definitely will. This is an interesting topic. I've been researching on this too. All the best with the book!
Hi Josef,
Here's some opinions. :)
The design is clean and text-oriented, which I think is good, since your target audience are developers. However, I don't like the testimonial section, I think that should stand out more. Same goes for the author section. Also, maybe the buttons could be improved (add some colors, make them bigger, etc.)?
Hi Hrvoje,
thanks a lot for taking the time to think about the layout. The testimonial section is one that might change for sure, especially because it will hold more testimonials in the future. Do you have some exact changes in mind?
I kept the buttons from the last version since people liked it, but perhaps there is a way to make them stand out more.
Thanks again!
Sure. As for testimonials, I would prefer a card-like design, resembling embedded tweets.