Gatsby VS eleventy 🕚⚡️

Gatsby.

When we decided to open-source our blog and docs, we were spoilt for choices. Today there are multiple well-supported and fully-featured frameworks for open-source content creation. Some of the options that we considered were Ghost, Jekyll, Hugo, Nanoc, and Gatsby. There are even more frameworks beyond these, and each tool has its pros and cons. Which one do we recommend? Well, we don't. The best tool for you is the one that fulfills your requirements.

#31 gatsbyjs/gatsby

Take a look through this thread https://github.com/gatsbyjs/gatsby/pull/19458 and related discussions - not sure if this carried over to the new gatsby image component but appears intentional.

Links to more sources on Gatsby Gatsby Home Site

For the frontend, you have the option to use a starter storefront built with either Next.js or Gatsby. As with both options, you will end up with a static website that connects to the headless server, the speed of your website is almost guaranteed to be fast.

Related discussion - https://github.com/gatsbyjs/gatsby/discussions/33710

As a developer who likes Eleventy, I don’t think I’d reach out to Ink for those features — I’d probably use Eleventy shortcodes for the Oracle & Row paragraphs, and maybe one of the many Markdown Presentation packages to split it up into mini-pages.

For what it’s worth, my favorite is Eleventy https://www.11ty.dev/ It has a plethora of templating options, and I find the dev experience to be very nice. It is very flexible, and does not force you to follow any rigid pattern, like many others do.

You could use something like Netlify CMS with a static site generator like Eleventy (or a framework specific one if you're using a JS framework). I think that'll be easier than getting involved with some server rendered ecosystem.

I find Eleventy as a product to be fairly intuitive but the docs are... sub-optimal. I think the main problem is that they don't follow the typical rules of content types. I.e. reference content is mixed in with the guide content. https://www.11ty.dev/

We always chase productivity on our pages. And Web development community has got many instruments that help achieve this goal. Eleventy is one of them. It is a great tool that offers an easy way of combining templates and data into fully operative static pages that you can host on a server.

I also wanted the ability to handle relative links between Markdown files (and relative links for images). I'm surprised this isn't a default feature of nearly every static site generator, honestly.

Fortunately, some of the extensible static site generators make this fairly easy to add as a feature. Here's an example for Eleventy (aka 11ty):

https://github.com/11ty/eleventy/discussions/1973#discussion...

At first, it felt like it could have been an Eleventy plugin (similar to what Slinkity is doing). I was frustrated that the Astro team felt like they needed to add a whole new thing to the ecosystem.

In our specific context of developing our personal portfolio website or blog, we can totally rely on static site generators. Tools like Jekyll, Eleventy, Hugo and so on do a perfect job in taking a set of markdown files and transform them into static HTML files. These can be deployed to any web server that is able to statically serve files. Often these tools are very opinionated on how you should structure your site and where to place the markdown files. This can be a pro and cons, depending on your needs. While for a simple portfolio website you don't really need any kind of backend, as your site grows, you might find it useful to have access to simple cloud functions and persistent backend storage to create a more dynamic experience for your visitors.