From: Memet Zx <[email protected]>
To: GNU/Weeb Mailing List <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Irvan Malik <[email protected]>,
Memet Zx <[email protected]>
Subject: [PATCH website v1 5/7] add config for favicon
Date: Sat, 22 Oct 2022 14:23:32 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
From: Memet Zx <[email protected]>
add favicon pass trough copy when rendering
Signed-off-by: Memet Zx <[email protected]>
---
.eleventy.js | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/.eleventy.js b/.eleventy.js
index 2e8473a..d47b932 100644
--- a/.eleventy.js
+++ b/.eleventy.js
@@ -113,8 +113,7 @@ module.exports = function(eleventyConfig) {
-------------------------------------------------------------------------- */
eleventyConfig.setLibrary('md', markdownLib);
eleventyConfig.setDataDeepMerge(true);
- eleventyConfig.addPassthroughCopy({ '_source/_assets/fonts': 'assets/fonts' });
- eleventyConfig.addPassthroughCopy({ '_source/_assets/images': 'assets' });
+ eleventyConfig.addPassthroughCopy({ '_source/_assets/favicon': 'assets/favicon' });
return {
dir: {
--
Memet Zx
next prev parent reply other threads:[~2022-10-22 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 7:23 [PATCH website v1 0/7] add meta tag and favicon Memet Zx
2022-10-22 7:23 ` [PATCH website v1 1/7] remove author data and template Memet Zx
2022-10-22 7:23 ` [PATCH website v1 2/7] rename file manifest to nunjucks format Memet Zx
2022-10-22 7:23 ` [PATCH website v1 4/7] add meta tag list file Memet Zx
2022-10-22 7:23 ` Memet Zx [this message]
2022-10-22 7:23 ` [PATCH website v1 6/7] refactoring head Memet Zx
2022-10-22 7:23 ` [PATCH website v1 7/7] add images on data site Memet Zx
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox