From 92c8c1344b69b9ae95267cc797cbac5ad6bd5f9b Mon Sep 17 00:00:00 2001 From: Romain Bioteau Date: Thu, 2 Jun 2022 14:05:52 +0200 Subject: [PATCH] fix(doc): explicit location of the public folder MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I spent way too much time figuring this out 😝 For me, the "project root" is where the `package.json` belongs. Seems not to be the case here for the public folder. Or am I missing something ? --- docs/guide/asset-handling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/asset-handling.md b/docs/guide/asset-handling.md index 20969f9c..6a482192 100644 --- a/docs/guide/asset-handling.md +++ b/docs/guide/asset-handling.md @@ -16,7 +16,7 @@ All **static** path references, including absolute paths, should be based on you ## Public Files -Sometimes you may need to provide static assets that are not directly referenced in any of your Markdown or theme components (for example, favicons and PWA icons). The `public` directory under project root can be used as an escape hatch to provide static assets that either are never referenced in source code (e.g. `robots.txt`), or must retain the exact same file name (without hashing). +Sometimes you may need to provide static assets that are not directly referenced in any of your Markdown or theme components (for example, favicons and PWA icons). The `public` directory under project root (`docs` folder by default) can be used as an escape hatch to provide static assets that either are never referenced in source code (e.g. `robots.txt`), or must retain the exact same file name (without hashing). Assets placed in `public` will be copied to the root of the dist directory as-is.