-
Notifications
You must be signed in to change notification settings - Fork 690
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
[proposal] move _all_ examples from GitHub to netlify #1619
Comments
I'd like to see about moving more to netlify for all the docs, having everything versioned in there should fix the problem. I'd expect the master version to point to latest and all others would be tagged in the proper release. |
I'd be down with that. Now I understand how to do redirects doing a |
I think this would be a great move, showing users the examples front and center. Removing confusion = always 👍 I agree with Steve as well, having versioned docs would be nice to have, it does require some minor rework of the current docs structure though. Your solution Dave to only build the website based on the latest release should also work nicely, I think it would require a few manual steps for each release (point to the right branch in Netlify and run a manual build after release). That's a quick thing though, and we can most likely trigger something using webhooks though, to hopefully remove those manual steps. |
I very much like the idea of versioned docs, and in my mind the docs include the examples. |
Updates projectcontour#1619 Migrate the getting started section of the README to projectcontour.io/getting-started. Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Migrate the getting started section of the README to projectcontour.io/getting-started. Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Migrate the getting started section of the README to projectcontour.io/getting-started. Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Take a first pass through the /docs/ directory any move any documents which are not specific to a release. Also remove a few outdated docs like tls.md and zenhub.md. Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Migrate the getting started section of the README to projectcontour.io/getting-started. Signed-off-by: Dave Cheney <[email protected]>
Updates #1619 Migrate the getting started section of the README to projectcontour.io/getting-started. Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Take a first pass through the /docs/ directory any move any documents which are not specific to a release. Also remove a few outdated docs like tls.md and zenhub.md. Signed-off-by: Dave Cheney <[email protected]>
Updates #1619 Take a first pass through the /docs/ directory any move any documents which are not specific to a release. Also remove a few outdated docs like tls.md and zenhub.md. Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Signed-off-by: Dave Cheney <[email protected]>
Updates #1619 Signed-off-by: Dave Cheney <[email protected]>
Updates projectcontour#1619 Enables strict mode and fix strict mode failures. Signed-off-by: Dave Cheney <[email protected]>
Fixes projectcontour#1619 For 1.0 the plan of record is to keep the examples on GitHub. This is due to the difficulty in doing directory index style static resources from projectcontour.io. To support this weave the name of the current github release through the website. Note that at the present, in the rc.2 timeframe, this will break a lot of links so this PR is targeted for 1.0 (or shortly after) which will bring the guides, resources, and release documentation in line with the latest released tag on GitHub. Signed-off-by: Dave Cheney <[email protected]>
Moving to 1.0 final because of the circular dependency on a latest release version > 0.15.x |
Updates projectcontour#1619 Enables strict mode and fix strict mode failures. Signed-off-by: Dave Cheney <[email protected]>
Updates #1619 Enables strict mode and fix strict mode failures. Signed-off-by: Dave Cheney <[email protected]>
Fixes projectcontour#1619 For 1.0 the plan of record is to keep the examples on GitHub. This is due to the difficulty in doing directory index style static resources from projectcontour.io. To support this weave the name of the current github release through the website. Note that at the present, in the rc.2 timeframe, this will break a lot of links so this PR is targeted for 1.0 (or shortly after) which will bring the guides, resources, and release documentation in line with the latest released tag on GitHub. Signed-off-by: Dave Cheney <[email protected]>
Fixes projectcontour#1619 For 1.0 the plan of record is to keep the examples on GitHub. This is due to the difficulty in doing directory index style static resources from projectcontour.io. To support this weave the name of the current github release through the website. Note that at the present, in the rc.2 timeframe, this will break a lot of links so this PR is targeted for 1.0 (or shortly after) which will bring the guides, resources, and release documentation in line with the latest released tag on GitHub. Signed-off-by: Dave Cheney <[email protected]>
Fixes projectcontour#1619 For 1.0 the plan of record is to keep the examples on GitHub. This is due to the difficulty in doing directory index style static resources from projectcontour.io. To support this weave the name of the current github release through the website. Note that at the present, in the rc.2 timeframe, this will break a lot of links so this PR is targeted for 1.0 (or shortly after) which will bring the guides, resources, and release documentation in line with the latest released tag on GitHub. Signed-off-by: Dave Cheney <[email protected]>
Fixes projectcontour#1619 For 1.0 the plan of record is to keep the examples on GitHub. This is due to the difficulty in doing directory index style static resources from projectcontour.io. To support this weave the name of the current github release through the website. Note that at the present, in the rc.2 timeframe, this will break a lot of links so this PR is targeted for 1.0 (or shortly after) which will bring the guides, resources, and release documentation in line with the latest released tag on GitHub. Signed-off-by: Dave Cheney <[email protected]>
Fixes #1619 For 1.0 the plan of record is to keep the examples on GitHub. This is due to the difficulty in doing directory index style static resources from projectcontour.io. To support this weave the name of the current github release through the website. Note that at the present, in the rc.2 timeframe, this will break a lot of links so this PR is targeted for 1.0 (or shortly after) which will bring the guides, resources, and release documentation in line with the latest released tag on GitHub. Signed-off-by: Dave Cheney <[email protected]>
A perennial problem for users who start with GitHub rather than projectcontour.io is they are using our
:master
branch. This means they can get a broken or unstable expirience, eg. #1615This sort of go worse when we move the README from recommending
:master
to the:latest
release, moving the Quickstart yaml further from the experience of git pull && kubectl apply. #1484Some possible solutions I can think of:
release-whatever
, this should mean the quickstart and the documentation in GitHub match up. With the write kind of url hacking this could remove the requirement to updatesite/_redirects
on each release. The downside of this is it'll probably screw up every single PR pushed to the site because GitHub will base the PR on the release branch, not the master branch.site/examples
directory. This would mean changing netlify to pull from the latest release branch, not master so the example changes are not updated until we cut a release.The text was updated successfully, but these errors were encountered: