"We broke down this guide into the following topics: Writing Spec / Design, Documentation, Generators, Servers, Clients, Testing & Monitoring, Gateways / Management, Public Specifications"
Agreed! Frameworks, libraries, and APIs are all about tradeoffs. Because they will never make sense for some programmers and use cases, the last line of code will probably never be written... but there's an undeniable trend heading that direction for so many. Thanks for reading.
This is the technical co-founder question in different skin. Most creative people don't want to "put a pretty face" on your idea. The best way to find creative talent is to get them excited about the idea early on and involve them through the project.
The implication is that if they've written about it once, they may write about it again. However, as you point out, a personal connection goes a long, long way. The personal connection lets you know whether the writer wrote about it once because nobody else was covering or if it's a topic they're looking to dive into and cover more.
A style guide is an important way to keep everybody on the same page. Not enough products have one. As others (including the OP) suggest, this is not the entirety of design, but it's a great step after something like Bootstrap to help differentiate the product.
You're dealing with sensitive information, so you need to do a lot more to make users feel comfortable giving you their data.
The first step of the form (that's as far as I got) didn't make clear why I would select Address or Home Value. I figured out that you can use either. I'd lean toward home value because that's the smallest invasion of privacy.