Replies: 3 comments
|
Important: it's easy to preserve old URLs to keep working as redirects to new paths, the trick is to add -permalink: /doc/en/lb4/Using-database-transactions.html
+permalink: /doc/en/lb4/data-access-guides-transactions.html
+redirect_from: /doc/en/lb4/Using-database-transactions.html |
0 replies
|
0 replies
|
Facing similar problem in #6085 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
At the moment, the documentation files in
docs/siteare using different ways for creating URL slugs (filename-like parts of the URL path).Most files use
Sentence-style.htmlformat, especially those on the first level (docs/site/{name}.md):https://github.com/strongloop/loopback-next/blob/ae6427322451c914ae54f44dbb656981e7fbbb81/docs/site/Application.md#L6
Nested files typically use
directory-lowercase-style.md, where the slug combines the path element with the title in all lowercase:https://github.com/strongloop/loopback-next/blob/ae6427322451c914ae54f44dbb656981e7fbbb81/docs/site/migration/datasources.md#L7
Some files use
_instead of-as the separator:https://github.com/strongloop/loopback-next/blob/ae6427322451c914ae54f44dbb656981e7fbbb81/docs/site/deployment/Deploying_to_ibm_cloud_kubernetes.md#L8
Personally, I'd like to use nested paths in URLs, e.g.
/doc/en/lb4/migration/models/overview.html. I encountered some issues with that approach the last time I tried it, but I didn't investigate them deeper.Let's discuss what URL style(s) we want to use in our docs and ideally come up with a single style to use consistently everywhere. @raymondfeng @hacksparrow @achrinza @strongloop/loopback-maintainers
All reactions