3 ms·
I'm interested in why you opted for a name tied to such a specific use case. Surely there are lots of other document types where this kind of service could com
by philbo 15y ago
I'm interested in why you opted for a name tied to such a specific use case.
Surely there are lots of other document types where this kind of service could come in handy. Briefly and just off the top of my head: CVs/résumés, marketing mailshots, blog posts...
Was it an intentional choice to try and limit the scope of the application?
- stevelosh 15y agoYou're definitely right -- the concept can be used in lots of other places. We talked about this a bunch, and decided that we'd stick with proposals. If we tried to make the user interface general enough to support any kind of document it would get more complicated. Off the top of my head, we'd need: * Arbitrary keywords, not just "client names". * More help text to explain how things work, give examples, etc. * Probably some more options for the layout of the result, like "show date". We decided to go with the "do one thing well" approach partly to avoid this extra UI complexity, partly because we only had 48 hours to make it, and partly because "Proposalmatic" is a much cooler/stronger name than "Document-maker". The site could be easily forked, reskinned and set up for another type of document though. It really fits perfectly with the resume idea -- I hadn't thought of that particular case before. Maybe we should make a "Resume-o-matic" sister site.