GA-Factory / modern-trousseau-gatsby

SEI 34 Client Project Build for Modern Trousseau Site (Gatsby + Contentful Serverless on Netlify)
MIT License
3 stars 2 forks source link

Client Questions #103

Open jserrao opened 4 years ago

jserrao commented 4 years ago

QUESTIONS CAREERS: Are we doing this at all? If we are, are we doing this custom in the CMS or do they use an external service (Jazz, Bamboo, Workday, etc)? BOOKING: When an appointment gets booked, we are assuming there is not service that handles an integration with a real calendar. EMAIL: We need access to their Mailchimp account to sync the sites together. GOWNS / ACCESSORIES: Accessories are mentioned for dresses, as if they would be an additional set of items a bride could browse online. We are treating them as general optional items: each gown can have an accessory but clients will have to inquire about what those are with their representative. CONTENTFUL: We need the client to pay for a license. CONTENT: How far back do we need to go with content? What content is available?

jserrao commented 4 years ago

ANSWERS

CAREERS - we need to continue to show these. Simple posts, no integration with a 3rd party HR solution. Each application should deliver an email over to: kelly@moderntrousseau.com

BOOKING - wide open availability, no calendar integration is needed. Appointment goes to whichever location, they choose the location individually when going through the booking process. Each booking needs to email to a specific person at each flagship location. Kelly says we can find the emails by looking at the old site and doing some testing with it.

LOCATION PAGES - each flagship page needs to put user into the funnel for booking an appointment. Bonus points if it already pre-selects the correction location.

EMAIL - Mailchimp integration. General newsletter list is where the names should go. Kelly to send mailchimp information my way.

GOWNS - just a brochure of gowns, nice to know jackets and accessories are there but you wont see them as individual options on the site.

COLLECTIONS - all old content should go in the new site. New collection is in coming (FALL 2020, Kelly to send it my way).

HOMEPAGE:

CONTENTFUL: We will give access to client once all content is uploaded

SEO / URLS: Speed is number 1 goal of this redo (good thing we went with Gatsby). Second concern is URL structure: /gown/gown-name for gowns /gown-collection/collection-name for each collection /flagship-stores/region-name for each flagship location

REDIRECTS: We need to point from old gown URLs (which are /portfolio_page) to the new structure (/gown-collection/)

mrrogercampbell commented 4 years ago

Looks good! This answers a lot a of questions. I see now how it affects the build but not in a bad way.

jserrao commented 4 years ago

Additional Questions: