search

arcestia / arcestia.github.io

My Digital Garden running on Gatsby, React, and Node.js.
https://skiddle.id/
MIT License
2 stars 1 forks source link

Moving out from Jekyll to Gatsby. #4

Open arcestia opened 9 months ago

arcestia commented 9 months ago

Guideline for Moving from Jekyll to Gatsby

  1. Understand the differences between Jekyll and Gatsby:

    • Jekyll is a static site generator written in Ruby, while Gatsby is a modern static site generator built with React.
    • Gatsby offers more flexibility, performance, and a rich ecosystem of plugins and themes.

  2. Set up a new Gatsby project:

    • Install Node.js and npm if you haven't already.
    • Use the Gatsby CLI to create a new Gatsby project: gatsby new my-gatsby-project.

  3. Migrate your content:

    • Identify the content files in your Jekyll project (e.g., Markdown files, HTML files).
    • Convert your Jekyll templates to Gatsby components using React syntax.
    • Update the front matter of your content files to match Gatsby's GraphQL schema.

  4. Update your site configuration:

    • Review and update your site configuration file (gatsby-config.js) to include any necessary plugins and settings.
    • Configure Gatsby's data layer using GraphQL queries.

  5. Customize your Gatsby site:

    • Explore Gatsby's theming system and choose a suitable theme or create your own.
    • Customize the layout, styling, and functionality of your Gatsby components.

  6. Test and optimize your Gatsby site:

    • Run your Gatsby site locally using gatsby develop and ensure everything works as expected.
    • Optimize your site's performance by leveraging Gatsby's built-in optimizations and best practices.

  7. Deploy your Gatsby site:

    • Choose a hosting provider that supports static site deployment (e.g., Netlify, Vercel).
    • Configure your deployment settings and deploy your Gatsby site.

  8. Update your workflows and tools:

    • Update any build scripts, CI/CD pipelines, and other development workflows to accommodate Gatsby.

Remember, this is just a starting point. You may need to adapt the guideline based on your specific project requirements and constraints. Good luck with your migration from Jekyll to Gatsby!

arcestia commented 9 months ago

the commit c5d0266f0f458d34f47d946369b495be79f9f53e failed to runs jekyll so it might be to overhaul manually.