|
Top-level
 @hi_mayank yeah—a fair question! I’ve hit this a few times too as I slowly gravitate towards recommending using a `content` or `src` folder by default. I think the benefits outweigh the negatives though—the onramp with immediate markdown support is hard to beat. We couldn’t do a default `content`/`src` folder either because that would require an additional folder creation step or even head towards a boilerplate CLI which I have a real hard time getting onboard with. 4 comments
@hi_mayank I like `pages`! How you describe `pages` is exactly how the input folder operates! You can change your input folder to be anything, currently: Onboarding: $ touch pages/index.html I wonder if this would be a better thing to try out in our quickstart!  @zachleat in my mind, the difference between `pages` and `input` is that the includes and layouts are currently relative to the input folder and default to being inside of it. (the `_` prefix certainly helps tho) also i should have tried `touch pages/index.html` before posting. 🤦 it needs to be `mkdir pages && touch pages/index.html` @hi_mayank classic issue #67, I’ll try to add support for this https://github.com/11ty/eleventy/issues/67 😭 |
Gregory's Server
@zachleat maybe not a `src` folder but a `pages` folder that's a different thing from the input dir.
everything (including *.MD) inside `pages` could generate an .html file, and everything outside will still be considered by 11ty but not used as pages.
onboarding:
$ touch pages/index.html
$ npx @11ty/eleventy