taphangum
Joined 17 years ago
Joined 17 years ago
I'm working on a book as well, but for the Frontend. I'm very curious to know more about how you marketed this?
I know it's a different niche, but is there any globally applicable advice you'd give?
A general framework that has helped me a lot in the past.
The site in general is in 'under construction' mode right now, so rest assured these issues will all be resolved by launch. We're just dedicating all of our energy towards the first version right now, so have not polished everything.
You might be spending a bit too much time on the problem here. It may be worth spending a bit more on the solution and making that clearer.
Right now it seems that its hidden within the modal underneath the copy. It should be much higher and not within a modal.
I would also try to say more with less with the problem. Again, it felt like it took a little too long to get to the point (and the point you're making is a pretty good one I might add!).
I find that with people who are more on the 'founder' end of the customer spectrum, particularly those who are tech focused, too much 'copy' and 'slow salesmanship' can be a negative. We tend to err on the side of 'just tell me and I'll figure out if its valuable' if that makes any sense.
I hope this helps?
Good luck man!
Tapha
It tries to make planning a website or mobile app as close as possible to the pen and paper experience.
It does this in a simple but (from my, and the experience of those who have tested it out) very effective and engaging way.
I share a bit more about how this is done here: https://simpleprogrammer.com/information-architecture-develo....
There's no better way to put your mind into 'listening mode' than to assume that the person in front of you might know something that you don't.
Be humble, and listening will come naturally. The rest is just getting a better memory/knowledge base for better understanding.
The advantage of Tailwind [1] is very subtle over the short term (such as not having to constantly context switch between HTML & CSS files), but dramatically impactful over the long term.
Both in terms of time-savings, as well as code quality and ability to work with others quickly.
It really is something that you must earnestly try to gain an appreciation for.
My initial reaction was the same as the authors when I first came across it. Actually using it on a real life project changed my mind.
[1] - https://planflow.dev/blog/the-main-advantage-of-tailwindcss.