Back End MVP features

[spences10]

Let's discuss MVP features for the back end

Please add any thoughts you have on what the features are for the back end, we can add them to a checklist here, which can then be added to the MVP Checklist this will help with the planning of the next stage of the project.

[mar-bi]

We have started with gatsby. It does a basic routing (and not only) for us. 🎢
We don't need to set up a node (express) server. 💻

[spences10]

Yeahp! If there's nothing else to add from @miljan-fsd and @asanhix then this can be closed and we'll take the point off of the main list

[mar-bi]

More feature here:

• we use gatsby-remark and .md files to mock-up the API (some third-party API or back-end microservices)
• there is an idea to use GraphQL client like Apollo with GraphCool 🤔

[mar-bi]

The back-end MVP features:

1. third-party API (for jobs, learn, events) are mocked with async functions, .json, and faker.js. It does produce some fake data.
2. stories use gatsby-remark. Please prepare your story/stories and we will store it in .md

[mar-bi]

Server for

• serving queries from Apollo client
• user authentication

Options:

• build your own server with graphql-yoga, prisma, node. Tutorial
• use serverless graphcool back-end. Tutorials:
  1. React + graphcool - https://www.graph.cool/docs/quickstart/frontend/react/apollo-tijghei9go
  2. Gatsby + graphcool - https://medium.com/@dwalsh.sdlr/gatsby-apollo-graphcool-netlify-the-webs-promised-land-6dd510efbd72

[mar-bi]

More options:

• Contentful headless backend