At the moment, the site input root starts at ./src/. This works, but makes linking slightly more complex. It seems like it would be best to move it to just ".".
Having the source content root overlap with the repo root is helpful because github processes /absolute/to/site/root links as relatively the repo root in the way they render markdown docs, so, having the 11ty source input path root be the same as the repo root has some nice advantage if we want to keep the links in the source material working in github's rendering as well as in the generated site output.
(See discussion in #3 .)
At the moment, the site input root starts at
./src/. This works, but makes linking slightly more complex. It seems like it would be best to move it to just ".".Having the source content root overlap with the repo root is helpful because github processes
/absolute/to/site/rootlinks as relatively the repo root in the way they render markdown docs, so, having the 11ty source input path root be the same as the repo root has some nice advantage if we want to keep the links in the source material working in github's rendering as well as in the generated site output.(See discussion in #3 .)