Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build sitemaps #51

Merged
merged 14 commits into from
Aug 8, 2018
Merged

Build sitemaps #51

merged 14 commits into from
Aug 8, 2018

Conversation

jckr
Copy link
Contributor

@jckr jckr commented Jun 14, 2018

When a user runs ocular build-docs to generate a mdRoutes.js file based on the contents of their /src/docs folder, this will now also create a sitemap.xml file based on these files.

In other words, if the user puts their markdown files in /src/docs, ocular can not only generate a dynamic routes js file but also the corresponding sitemap.xml document so search engines can index the contents of these pages.

Copy link
Collaborator

@ibgreen ibgreen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks very promising!

@@ -13,6 +13,7 @@ ocular build-docs
```

in the CLI and this will create a mdRoutes file based on the contents of the __/src/docs/__ folder. Each markdown (.md) file will become an entry in the table of content, grouped hierarchically by folders.
If you have a BASEURL file in your src folder, which contains the url of the your documentation file, ocular build-docs will also generate a sitemap (__sitemap.xml__) based on these files.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or are using a Github project type

jckr and others added 7 commits August 7, 2018 16:48
…in jsRoutes. (#56)

Previously, jsRoutes was taken as is - there was no reprocessing at all. All routes that needed to appear in the table of contents had to be in mdRoutes. The issue there is that mdRoutes mixed 2 kind of routes - those with documentations (as intended) and those with standalone components.
With this PR, we can go back to a model where mdRoutes contains only routes with markdown files (and can easily be generated instead of manually created)
@jckr jckr merged commit 4b5588b into master Aug 8, 2018
@xintongxia xintongxia deleted the build-sitemaps branch October 9, 2019 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants