-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
"cdk docs" opens on "index" and it's not very useful #129
Comments
@Doug-AWS, @RomainMuller and I are thinking that perhaps the right solution to this is to simply rename |
Hmm. Every AWS SDK (and every Sphinx project I've seen) uses this structure. I'll investigate. |
The real issue is that index.html contains an exploded table of contents, where every single topic page is listed. It wouldn't be so bad if it had just the 10 entries I have in index.rst: .. toctree:: |
I agree that this is /also/ an issue, but the experience we want is that when people open the root directory of the docs in their browser ( What happens if we rename |
@Doug-AWS if it makes more sense from your end to leave |
Not sure. The brazil build produces this experience. The index.html that brazil produces re-routes as you suggest in the HEAD section:
|
Add getting started and welcome in Java (and JavaScript). Rewrite "Getting Started" to detail the process of defining CDK apps without using `cdk init`. This is in order to improve the understanding of users when they onboard the CDK, which fixes #219. Fix TOC to include only two layers deep which fixes #129.
Add getting started and welcome in Java (and JavaScript). * Rewrite "Getting Started" to detail the process of defining CDK apps without using `cdk init`. This is in order to improve the understanding of users when they onboard the CDK, which fixes #219. * Fix TOC to include only two layers deep which fixes #129.
cdk docs
should open on "welcome.html" instead of "index.html"Also, it would be nice to be able to do "cdk docs getting-started" and it will open on "getting-started.html".
The text was updated successfully, but these errors were encountered: