You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hexo configuration documentation claims that skip_render setting contains "Paths that will be copied to public raw, without being rendered". As far as I understand this implies those files will be deployed as they are, not that they will be ignored.
The provided example, copied/pasted bellow, suggest the same:
skip_render: "mypage/**/*"
# will output `source/mypage/index.html` and `source/mypage/code.js` without altering them.
→ In this example, source/mypage/index.html will be deployed and then it should be included in the sitemap.
Not sure what would be the best approach to address this, but it seems to me files matched by the skip_render setting shouldn't be excluded from the generated sitemap (or at list a subset of them, such as .html files for example).
Best
The text was updated successfully, but these errors were encountered:
Hi there,
Hexo configuration documentation claims that
skip_render
setting contains "Paths that will be copied to public raw, without being rendered". As far as I understand this implies those files will be deployed as they are, not that they will be ignored.The provided example, copied/pasted bellow, suggest the same:
→ In this example,
source/mypage/index.html
will be deployed and then it should be included in the sitemap.Not sure what would be the best approach to address this, but it seems to me files matched by the
skip_render
setting shouldn't be excluded from the generated sitemap (or at list a subset of them, such as.html
files for example).Best
The text was updated successfully, but these errors were encountered: