starter-gatsby-blog
demo-gatsby-contentful
Our great sponsors
starter-gatsby-blog | demo-gatsby-contentful | |
---|---|---|
4 | 2 | |
191 | 1 | |
0.5% | - | |
4.6 | 0.0 | |
about 2 months ago | over 1 year ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
starter-gatsby-blog
-
Developer Showcase Spotlight: Low-code examples of building blogs
So, my first port of call was the official GitHub repository where Contentful maintains a starter blog template built using Gatsby, which has push button deployment for Gatsby Cloud. This template is basic but properly formatted with all the necessary features of a functional blog. Things like an index page, formatting for individual posts and key visuals, plus timestamps, authors, and tagging.
-
An Unnecessarily Extensive Comparison of Gatsby & Next.js (While Rebuilding My Portfolio)
Now to be fair to both, if you use the starter-gatsby-blog from Contentful themselves, the new gatsby-starter-contentful-homepage from Gatsby, or the Next.js Contentful example, these do use environment variables. It's just these basic starters that do not.
-
The New Gatsby Homepage Starters - Less Is More
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.
-
Setup a modern Jamstack project using Gatsby, TypeScript, Styled Components, and Contentful!
npx gatsby new . https://github.com/contentful/starter-gatsby-blog
demo-gatsby-contentful
-
The New Gatsby Homepage Starters - Less Is More
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.
-
Setup a modern Jamstack project using Gatsby, TypeScript, Styled Components, and Contentful!
Please check out the repo I've created with the finished files. You can use this if you get stuck and need to reference anything.
What are some alternatives?
gatsby-contentful-blog - [Moved to: https://github.com/andrews1022/contentful-blog-gatsby-starter]
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
gatsby-starter-wordpress-homepage
gatsby-starter-drupal-homepage
gatsby-starter-contentful-homepage
contentful-remix-starter-blog - Remix starter for a Contentful blog (template) project
gatsby-starter-mate - An accessible and fast portfolio starter for Gatsby integrated with Contentful CMS
eslint-plugin-react - React-specific linting rules for ESLint
jamstack.org - The official Jamstack site
vercel - Develop. Preview. Ship.
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅