docus plus should accept a basePath config option. This will make it easier to integrate docus-plus into an existing app.
Any page routes will be prefixed with that, meaning:
- /api-reference
- /changelog
- /doc-articles
- /api-resources
- (if landing is present)
The api and doc articles collections can add this prefix in the content.config.ts
This also mean that the landingspage should be optional. Only if index.yml exists in the content dir, should the landingspage be registrerd. Check the docus implementation pattern for that: https://github.com/nuxt-content/docus/blob/main/layer/modules/routing.ts (they handle this well!)
the basepath can be anything really as long as its url safe. So for example
The base path should have NO EFFECT on api routes or wll-known routes
It SHOULD have an effect on markdown routes, meaning
- /raw/doc-articles.md
- /raw/api-resources.md
But i think that will work automatically!
docus plus should accept a basePath config option. This will make it easier to integrate docus-plus into an existing app.
Any page routes will be prefixed with that, meaning:
The api and doc articles collections can add this prefix in the content.config.ts
This also mean that the landingspage should be optional. Only if index.yml exists in the content dir, should the landingspage be registrerd. Check the docus implementation pattern for that: https://github.com/nuxt-content/docus/blob/main/layer/modules/routing.ts (they handle this well!)
the basepath can be anything really as long as its url safe. So for example
The base path should have NO EFFECT on api routes or wll-known routes
It SHOULD have an effect on markdown routes, meaning
But i think that will work automatically!