uncenter

My thoughts... ## Guide Every project needs to start off with the very basics. Installing, setting up, adding templates/pages, and deploying. We can link to the starter tutorial here, but...

Adding on to Bob, here is another example of guiding users through installing pre-requisites: https://learn-eleventy.pages.dev/lesson/1/.

> > ...One thing that I think is skipped, particularly if we're trying to attract and provide guidance to those who have never developed a website or done any kind...

I'm against giving people tools they don't understand. And for the record, I've yet to see any other framework/tool in the frontend web dev space take that approach.

(Luckily, 11ty@v3 only requires Node 18!) I see what you mean though. I think an ideal solution would be to have a standard guide through Git and Node and all...

You can make a `require()` to import JSON data like you would in CJS. ```js import { createRequire } from "node:module"; const require = createRequire(import.meta.url); ``` And then you can...

I've also been trying to learn the code base and I have to say, the last part that you mentioned is the most confusing. I often find myself starting at...

#3060 removed the .d.ts file to rely on JSDoc entirely, but the .d.ts had been exporting UserConfig (https://github.com/11ty/eleventy/blob/ecd0579a2dded6939510b7c23841388b26eb6d16/src/index.d.ts) and the issue now that is UserConfig isn't exported anywhere else. Would...

> > #3060 removed the .d.ts file to rely on JSDoc entirely, but the .d.ts had been exporting UserConfig ([`ecd0579`/src/index.d.ts](https://github.com/11ty/eleventy/blob/ecd0579a2dded6939510b7c23841388b26eb6d16/src/index.d.ts)) and the issue now that is UserConfig isn't exported anywhere...

Would you ever consider writing Eleventy in TS itself? And then compiling down to JS with generated type definition files?