Single listing (hotel) page (Netlify+Gatsby)

- Use the LTL WP CMS as a headless CMS for our JAMstack - Write a swagger doc with the exact api implementation - Write a wp plugin that builds your content according to this spec - Rebuild front end using gatsby (sprint by sprint) that consumes this api - Migrate necessary assets to S3 (plugin) - Deploy straight to AWS with Circle - Split-test versus Contentful and Netlify This is our current website: [login to view URL] It's a project we have been working on for the past 10 years. At its core, it is a curated collection of 1000 places to Live The Life with around 10.000 images that tell a story. LIVE THE LIFE today represents and markets a hand-selected collection hotels, from world capitals and exclusive mountaintops to hidden beaches, off-the-beaten-path escapes, and beyond. With a passion for genuine, culturally rooted hospitality and cutting-edge design and architecture, members go beyond merely curating their own neighbourhoods, we created an ecosystem for shared experiences among people united by passions like surfing, snowboarding, yoga, wine tasting, ... As we're now working to switch to the JAM stack, these are the micro-services we consider using => PRESENTATION LAYER: UI Design: Framer X, Sketch, Figma, InVision JS Framework: React SSG: Gatsby UI Dev/Management: Storybook for React, Chromaticqa: Visual Testing for React GIT: GitHub, BitBucket (Import a repository from GitHub or GitLab) HOSTING/CDN: Circle, AWS, Netlify, Firebase, (GitLab) (ZEIT) BACKEND: Amazon S3, GraphQL (Apollo) (Hasura) (Heroku) (Prisma) API (leverage third-party APIs to focus on value-added features) Headless CMS: WP, Contentful (GraphCMS) (ButterCMS) (Flamelink CMS) Utility API: Algolia, Booking, Typeform (Elastic/Swifttype) (Auth0) (Stripe) Content API: TripAdvisor Reviews, ... Customer Services API: Dialog Flow, Slack, Twilio, ... Deliverables: Run a speed test on a single listing (hotel) page. Goal: explore if we can experience benefits from moving to Contentful as our CMS, against connecting the REST API. Currently, the homepage prototype has a page load speed of 0.8 sec and a 100/100 score. We would love to stay under a second for our single listing page. The challenge to connect our REST API is that we have a highly custom setup in WP and our hotels are listed through a custom post type. We have looked at [login to view URL] and set up a SWAGGER hub account to document the API modification if needed but are stuck and could use some help to make this crucial decision at this stage: go headless WP or go Contentful. If possible we would like to avoid using a bunch of plugins (like shown here [login to view URL] ) by editing our child theme to enable the REST to work with our ACF's and Custom Post Type. At this stage, we prefer a headless WP versus Contentful solution to keep it simple Starter Code on GitHub: [login to view URL] Create: [login to view URL] [login to view URL] and use REST to get data from a single listing page like [login to view URL] This is the new test site (hosted on Netlify). [login to view URL] Hope to hear from you soon!