I need feedback on the first version of Nana's landing page

Hi fellow indie hackers,

Some of my side projects got impacted due to COVID-19, and since we all got stuck at home, I decided to invest some time into my new project: Nana.

Over the years I have built a couple of tools and projects for myself, for my clients and for the companies I have worked with, and I have noticed that for the majority of these projects there was quite a lot of lost time building the same basic features over and over again. Almost all the projects I have worked on needed some sort of authentication mechanism, emails, queues, some basic UI, and more importantly, checkout pages, subscription payments, 3D Secure, invoices, and all that stuff around it. Even though every project had different needs and business cases, there was quite a lot of code that was duplicated between applications and I have found myself referring to my own previous implementations for new projects, which was an important signal for myself.

As a developer, I am very interested in developer experience in general, which means I am trying to follow development tooling and improvements there closely. One of the important changes in my own workflow was adopting Docker for my projects, which allowed me to standardize many of my dependencies, have an easy-to-share setup to bring my friends onboard for various projects, and have a more streamlined way to deploy things. After I have adopted Docker, I have started tinkering with continuous integration, and by the time I was done with the first project I have tried this on, ReportMonkey, I had a working setup that was running some basic tests on every push. I was in the camp of "build now, test later" at that point; however, I have quickly noticed that writing tests and running them constantly after every push allowed me to move much faster and much more confidently, and I made it a part of my default workflow since then.

The last leap I had in my dev experience for my side projects was adopting Kubernetes. There are quite a lot of arguments about how Kubernetes is overkill and small projects don't need that, my experience says completely otherwise. After adopting Kubernetes I have managed to move all my side projects into a small $20 cluster on DigitalOcean, have a standardized CI/CD pipeline that checked my code, ran all the tests, and deploy to live when everything was merged to master. I have been happily running 4 projects on the same $20 cluster for more than a year now, and I haven't had a single problem. Also, thanks to Kubernetes, I have automated rolling deployments, automated rollbacks, load balancing, auto-scaling, configuration management, and many more benefits that just take away all the mental load I have and allow me to focus on the product.

As I believe all kinds of small gains in terms of productivity is a win for indie hackers, I have started building a starter kit focused on a specific tech stack that might not be very attractive to everyone, but would be killer for people that are already slightly familiar with the basic technologies there. Based on Laravel, I have started pouring all of my previous experiences in the domain into Nana, which is still in progress now.

I have recently finished preparing the first version of the landing page, I am looking for some feedback regarding how it looks, how it feels, and what else can be improved there. The links and buttons are not functional as the product is not ready yet, but I am open to all kinds of feedback. You can also subscribe to the newsletter to follow Nana's development.

Stay healthy everyone!

Nana looks great. Are you interested in getting a Logo made for Nana. Good luck!