search

ItsY8S / capstone

0 stars 0 forks source link

readme

Project Spec

Outline

Brief

Artist Store targets young artists that want to quickly get a store up and running without much technical knowledge. It makes it easy to add your products, and set tour exclusive merchandise.

Audience

This is influenced by watching this type of market on Instagram. I also have experience talking to artists in this range and a lot of them just don't know where to start, but are interested in selling clothes and other merchandise.

Problem

Music artists just want make music. They quickly find out there's more to it than making music. From photography, designs, a website, music videos, mixing, mastering, & more, it's a lot to juggle. Websites like Shopify can be intimidating, especially for somebody without technical experience.

Solution

Shopify provides good documentation and help all over. Big Cartel is good at getting straight to the point and getting set up. I want to find a good balance and add some of my own features. My number one goal is to make it easy to use. One of my selling points will be tour exclusive items.

Unique Value Proposition

Connecting with artists on Instagram will hit a specific market that those websites aren't hitting. I have experience and knowledge among this market as I've helped a friend in the music industry. Selling exclusive items on tour is also something I haven't seen done on a website. By keeping a consistent theme, I will build my brand as a trustworthly application.

Pitch

Pitch

Spec

Feature Definitions

Features

Sitemap

Store Owner Flow Not Pictured - Login / Signup Flow

Landing Page -> Login -> Input Username & Password -> Redirect to Dashboard (Success) -> Redirect to Login (Fail) or Landing Page -> Sign Up -> Input Username & Password & Artist Name -> Redirect to Dashboard (Success) -> Redirect to Sign Up (Fail)

Store Owner Flow

Customer Shop Flow Customer Shop Flow

Interface

Information Architecture

Dashboard Text Content

Products: Preview/Edit Text Content

Concerts

Orders

Manage

Contact

Browser Support

I would like to support all current browsers and IE11+. Older versions have a less than 1% usage rate. I will use something such as autoprefixer. Portrait mode will be supported on smaller devices such as phones, with landscape potentially coming later. There is a minimum requirement of 320px width.

Infrastructure

Technical Requirements

I will be using the MERN stack, minus React.

Programming Languages

Integrations

Deployment Workflow

I will be creating new issues for features labeled as 'features'. As I complete the features, I will mark them as completed. At the end of the week, I create a pull request. I'll be using GitHub Pages to host my application. I will use the command npm run deploy.

Web Host

GitHub Pages

Project Milestones

Initial Pitch

Initial Pitch

I found some things about my application that I wasn't even thinking about. Some things such as adding a tour date completely went over my head as a designer / developer. It was good getting feedback and talking through the vision of my project.

Initial Project Spec

Link to your initial Project Spec.

MVP

Direct Link to the tagged release of your MVP on your repo.

This should be a link to a specific commit.

Pivot

Direct Link to the tagged release of your Pivot on your repo.

This should be a link to a specific commit.

Alpha Release

Date of the Alpha Release Milestone. Once completed this should be updated with the proper link.

Beta Release

Date of the Beta Release Milestone. Once completed this should be updated with the proper link.

Public Release

Date of the Public Release Milestone. Once completed this should be updated with the proper link.

Best Practices

Documentation Standards

Deployment Standards

Deployment of this milestone should be handled with the following criteria.

Prior to submission, ideally on the first day of the milestone's development preform the following procedures:

On final Milestone Submission:

Additional clarification may be needed by the Capstone team, please monitor this pull request until approval to merge is given.

Continue working on your project in the Dev branch using feature branch development. Approval from your Capstone Team will take time to evaluate the submission in its entirety. This approval should not hold up development, however, and you should proceed with development.

APPROVAL

You have been approved to proceed forward! There may be additional considerations outline that should be addressed but you're doing well!

Follow-Up Actions:

REJECTION

You should suspend your current workflow and address the items outlined in the rejection notice that would be posted to the pull request and notify the Capstone Team once you have remedied the outlined items. Common reasons for rejection would be not following your project spec (once defined), not completing the pre-requisite elements of the milestone, or deviating significantly from the outlined requirements or requests made by the Capstone Team.

Follow-Up Actions:

Velocity Check

At the end of the week your progress will be evaluated to see how many points you have earned based upon closed issues point value. Successfully completed issues will be tallied and a velocity will be established to help provide a baseline for the following week's work. You are able to use this velocity check to estimate if you are on track for completion of your issues from early milestones or if you are off track. This relies on accurate and honest usage of the issue system.

The Velocity Check will calculated by Zenhub and you can view it at any point. Your role in this requirement is to maintain your progress within the issue system of github and accurately estimate time per issue and as you close issues adjust that estimate to how much time was invested in each issue.

This is a pass/fail assignment where failing represents a significant drop in velocity, attributed to not using the issue system to correctly communicate, with the Capstone Team, your current and accurate progress or neglecting to make progress toward your set goals.

Requirements

A specific velocity is not required, just the ability to calculate the project's velocity. The following requirements have been developed to ensure the velocity can be accurately checked.