The New Gatsby Homepage Starters - Less Is More

• gatsby-starter-contentful-homepage

  3 59 0.8 JavaScript
  

The setup for the starter was very straightforward. I created a new folder in my projects directory, downloaded the starter using npx, ran the setup command, entered in my Contentful API keys, started up the local dev server, and I was up and running (more detailed steps can be found on the GitHub page, of course)!

• gatsby-starter-datocms-homepage

  1 16 0.0 JavaScript
  

New CMS starters - new headless CMS starters were released for Contentful, DatoCMS, Drupal, & WordPress!

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• gatsby-starter-drupal-homepage

  1 23 0.8 JavaScript
  

New CMS starters - new headless CMS starters were released for Contentful, DatoCMS, Drupal, & WordPress!

• gatsby-starter-wordpress-homepage

  2 69 0.0 JavaScript
  

New CMS starters - new headless CMS starters were released for Contentful, DatoCMS, Drupal, & WordPress!

• starter-gatsby-blog

  4 191 4.6 JavaScript

  Gatsby starter for a Contentful project from the community.

  

Ultimately, I think there is too much content being created at the start here. There is, I think, a pretty decent chance you will end scrapping a decent portion of these models and content. Or, you will have to spend a lot of time restructuring/renaming it to meet your project's needs, which is not ideal. On the other hand, the existing contentful/starter-gatsby-blog I think has too little content. Therefore, I think there needs to be a nice middle ground with the quantity of content being generated out of the box.

• demo-gatsby-contentful

  2 1 0.0 TypeScript

You can see my approach here (at the time I already had a Page model, so I named it Dynamic Page just for testing as an FYI). We can use React.lazy() to dynamically import and render each component based on the value of the ComponentToRender field, and pass along the content as a prop. You then set the styles/props/types/etc. for each component as you normally would.

• eslint-plugin-react

  67 8,810 8.6 JavaScript

  React-specific linting rules for ESLint

  

I would like to strongly encourage prop spreading to be removed where it is being used. The reason for this I think is explained perfectly on the react/jsx-props-no-spreading ESLint page:

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project