iraleigh
commented
7 years ago So this is going to be a very iterative process. We will define bite size goals for ourselves, but that being said, it will be worth going over some high level goals.
-About page: primarily this will be an information website and will have to convey the message of the organization -Artists page: this website also needs to list and give info about the current artist that are going through the program. This may have a bio for each artist, some of their art, and a link to where to purchase their art (we wont actually be handling any purchasing within our domain) -Donation page: Its a non-profit and donations will be a big source of income for them, currently they have square account, so a simple way to either integrate with that API (or a similar a service's API -- we can definitely give them suggestions on what service they should use)
We don't have to have all of these use cases ready for the first release, and can decide on the scope we think is doable. I'll relay that with the org, they will let us operate with almost full autonomy--so our opinion will be taken seriously.
At some point there may be a use case for a content management system in place (mostly pertaining to the artists page)
What is the website used for How are the users (admin vs reg user) using the website (performing tasks from home page, other pages, etc) Create user flow diagram (draw.io)