Sitemap generator #27
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
build/sitemap.js
Outdated
| function filter (contents, done) { | ||
| var pages = contents.filter(function (item) { | ||
| var pathToFile = path.join(inputDir, item) | ||
| return fs.statSync(pathToFile).isDirectory() |
There was a problem hiding this comment.
|
Just a note, but we'll need to extend this to play nicely with sub pages. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This little script just helps google to index the site.
I see this tool becoming more sophisticated over time and becoming an XML file with images etc. But this is the first iteration.
npm run build:sitemapSearches the
/pagesdir for folder names, excludes any folder called 'home' and creates a file/dist/sitemap.txtwith the most simple content a sitemap can have: