Show HN: Our Django Dash project: Proposalmatic
proposalmatic.dwaiter.com
proposalmatic.dwaiter.com
The code is at https://bitbucket.org/dwaiter/proposalmatic if you're interested. Warning: there are definitely a few messy sections since it was built in two days.
(But I think you guys forgot to filter the proposal queryset by account in the SnippetForm.)
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?
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.
"Use ProposalMatic to save snippets of text that you use often and mix and match to create personalized proposals" This really struck me as odd...
And yeah, the copy wasn't number one on the todo list. We'll clean it up and flesh it out once the sites are unfrozen from the judging process.