* Tame the footer and make the prev/next stand out
Originally the prev/next links looked like they were part of the header and were easy to miss. This makes it more obvious while at the same time making the header look more sleek.
* Move background color up a level in dom tree
* Allow all the click space
* Update mkdocs.yml
* Update mkdocs.yml
* Update mkdocs.yml
* bringing back the purple
* Revert "bringing back the purple"
This reverts commit a6af055288.
* Change language to reflect desired actions RE: KinD
* Overhaul of Getting Started
* lint fixes
* Change to Nav Serving title
* Small bug fix
* Richard's changes 👍
* changed the font weight for h4 tag to have distinctive style from bold text
* changed the font weight for h4 tag to have distinctive style from bold text
* changed the font weight for h4 tag to have distinctive style from bold text
* updated the font size h4 which can be easily distinguished in conmpare to bold text
* Updated the suggested changes
Co-authored-by: Evan Anderson <evana@vmware.com>
While going through the GitHub workflow for Knative documentation, The very first section is "Set up your local machine ", which contains the first point to create your fork of the knative/docs repo. So for the easy access, we can update the fork URL with the "fork" word and then can attach the knative/docs URL to the "knative/docs repo" which can be easy for the new contributors to easily access the repo.
* Incorporate static version of old docs in to site
Built via manual ./scripts/build.sh of website and then copied over.
Each release we get to delete one of these docs directories (and the
corresponding copy in build.sh) until they all disappear.
* Clean up built owners files
* Mv old-docs archived
* Mark archived/ dir as generated
Reran redirectredirects to generate redirects from the yaml metadata,
added them to the list of redirects, then ran them all through `sort |
uniq` to remove duplicated and put them in a nice order.
* Style tweaks for apiserversource
* Add reference for apiserversource
* Add reference page to mkdocs.yml
* Adding back because this PR should not touch containersource
* Apply suggestions from code review
Co-authored-by: Ali Ok <aliok@redhat.com>
* Apply feedback from review part 1
* Define PodSpecable and other tweaks
* Fix whitespace
Co-authored-by: Ali Ok <aliok@redhat.com>
* Added a new doc for covert from k8s deploy to knative service
* Address snneji's comments
* Added Kubernetes Deploy and Service Link
* added to navigation
Co-authored-by: Omer B <obensaadon@vmware.com>
* Add cookie warning to site
Imports the cookie warning from the old site. For simplicity,
this uses the same script from the old site in both places, so we
have to import jquery.
Note: this doesn't actually turn analytics on, but we now could do so.
* Tweak margins
* Add non-EU version
* include a section about disabling autotls for a namespace
* handle rename of namespace certificate controller
* handle rename of other net-* controllers
* Add net-istio webhook to spec.registry.override
container name `webhook` is duplicated with serving and net-istio. But
the example does not have net-istio's webhook so users hit an issue
like https://github.com/knative/operator/issues/519https://github.com/knative-sandbox/net-istio/pull/560 when we followed
it.
This patch adds the net-istio webhook to the doc.
* Remove white space
* Update docs/admin/install/operator/configuring-serving-cr.md
Co-authored-by: Ashleigh Brennan <abrennan@redhat.com>
* Fix to correct deploy name
Co-authored-by: Ashleigh Brennan <abrennan@redhat.com>
- Move dns docs to snippet (have to use include syntax because of
included macro, unfortunately)
- Update xip.io -> sslip.io in text
- Capitalize Service
- Fix some bad formatting in Operator install nearby
- Change "For these" -> "In these cases"
- Swap info to warning admonition style
- Remove "CAVEAT" and parenthetical reference to it
- Added much nicer "Knative provides" intro sentence
Looks like navigation.instant makes link anchors not work properly. I
don't think the feature really buys us anything, our search index isn't
_that_ big, so easiest to just disable it.
Chris Suszynski