>
If you know of any resources on this I'd love to read them.I don't really know of anyone who would write about this. Part of it is predicting human behavior, and the rest of it is observation.
For example, users make a lot of mistakes. They get part of an order wrong, and sometimes they don't realize it until the restaurant has begun making the order.
How do you handle it? If the user can just cancel the order, the restaurant is losing money for a potentially fixable mistake. If the user can edit the order, how is that communicated to the restaurant?
Ordering systems are bidirectional. Both words (what the user has ordered) and money are moving back and forth even after the transaction is complete. What happens if a user does a charge-back? What happens if a user is unhappy and wants a partial refund?
It's just not something a beginner could accomplish in a reasonable amount of time. It would even take an expert quite a while to build it all out, even if she had it 100% architected in her head.
> clicking and dragging on squarespace isnt a marketable skill, so I'd rather avoid that
I agree, but that's a reason to follow a more traditional career path (working as a junior developer at a place that will teach you) rather than allowing a business to roll the dice on an experiment. It's honestly not really ethical. I've cleaned up messes made by beginners, and I've also encountered messes that were bad enough that no one could clean them up.
It's not unlike an unlicensed contractor telling someone they can build something they've never built before. If you do it, you're taking advantage of their trust and ignorance, especially because there are tons of alternatives.
Help this company implement an existing, trusted SaaS, put it on your resume as a consulting project, and find something else to work on. You won't advance your career by muddying your name on projects that are more harmful for a client than helpful.