summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMathieu David <mathieudavid@mathieudavid.org>2016-02-22 18:01:36 +0100
committerMathieu David <mathieudavid@mathieudavid.org>2016-02-22 18:01:36 +0100
commit01c508572538776b317929d9c06f33b856dc921e (patch)
treee0f5aeb7eef5c6836b51f8b8467ad3832a5d26cf
parent9f17be2c32562fbde08a0bed1f47150d51200a5b (diff)
Add an entry about the favicon in the docsv0.0.9
-rw-r--r--book-example/src/format/theme/theme.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/book-example/src/format/theme/theme.md b/book-example/src/format/theme/theme.md
index 51f45f53..11018511 100644
--- a/book-example/src/format/theme/theme.md
+++ b/book-example/src/format/theme/theme.md
@@ -14,6 +14,7 @@ Here are the files you can override:
- ***book.js*** is mostly used to add client side functionality, like hiding / un-hiding the sidebar, changing the theme, ...
- ***highlight.js*** is the JavaScript that is used to highlight code snippets, you should not need to modify this.
- ***highlight.css*** is the theme used for the code highlighting
+- ***favicon.png*** the favicon that will be used
Generally, when you want to tweak the theme, you don't need to override all the files. If you only need changes in the stylesheet,
there is no point in overriding all the other files. Because custom files take precedence over built-in ones, they will not get updated with new fixes / features.