This PR promotes the CSS, JS and FONTS files used by API reference to
the `static/css`, `static/js` and `static/fonts` directories
respectively. The intent is that for future releases, when generating
API reference docs, only the `index.html` and `navData.js` files need to
be copied from the generator tools.
Details of changes:
- `jquery-3.2.1.min.js` file is replaced by `jquery-3.3.1.min.js` to
align with the version used by Docsy. We can investigate in the future
whether this can be shared. Converging to the same version at least
can reduce the risks of compatibility.
- `jquery.scrollTo.min.js` moved to `static/js` file and renamed to
`jquery.scrollTo-2.1.2.min.js` so we know the version from file name.
- `scroll.js` moved to `static/js` and renamed to `scroll-apiref.js` to
siginify that it is used by API reference.
- A `README.md` file is added to `static/js` directory for describing
the purposes of the these files.
- `bootstrap.min.css` moved to `static/css` and renamed to
`bootstrap-4.3.1.min.css` so that it can be shared and its version can
be easily discovered.
- `font-awesome.min.css` moved to `static/css` and renamed to
`fontawesome-4.7.0.min.css` for the same reason.
- `stylesheet.css` moved to `static/css` and renamed to
`style_apiref.css` to siginify its purpose.
- A `README.md` file is added to `static/css` directory for describing
the purposes of the these files.
- FontAwesome fonts files moved to `static/fonts` so that they can be
shared across API reference versions.
- Current API reference (1.18) is modified to reference the relocated
files. Upstream generator change on the way
(kubernetes-sigs/reference-tools/#161).
Related: #22016, #22023, #22041, #22024, #22064
* Add Docsy, required packages and config
* Apply Docsy integration work to k8s website
This encompasses significant changes to the style system, layout files,
as well as changes to some of the static assets. To examine this work
and the iterations that were performed, the original repository can be
found at https://github.com/gearbox-built/kubernetes-hugo.git
* Address issues found in review
The styling and positioning of the header, footer, some shortcodes and
main container elements are improved. A new partial is added for
favicons. The sidebars, as well as inner table of contents, have been
altered for better positioning and rendering of content. Localization
has also been addressed.
* Enable announcements
The recent Black Lives Matter announcement surfaced issues which have
been addressed.
* Add new case study stylesheet
We will be adding a bunch of new case studies with an updated design (a lot of it is just simplified). I created this new file, and for the new case studies we will add
this updated code at the top from now on:
---
case_study_styles: true
cid: caseStudies
css: /css/new_case_studies.css
---
So just replacing the old css file with this one. Let me know if that is not going to work the way I think it will, thank you!
* update name
* update file name
* Removed multiple main tags from home page
Signed-off-by: chaitanyakaranam <chaitanya.karanam@yahoo.com>
* Removed multiple occurances of main in case-studies page
Signed-off-by: chaitanyakaranam <chaitanya.karanam@yahoo.com>
* Replaced css for main tag with .main-section class
Signed-off-by: ChaitanyaKaranam <karanam.krishna.25@gmail.com>
* Added main landmark role for all the pages
Signed-off-by: ChaitanyaKaranam <karanam.krishna.25@gmail.com>
* Force checks.
request-checks: true
Add shortcode, partial, and css so we can display an accouncement
site-wide.
Create a shortcode for use in content/en/ _index.html so
announcement is displayed on website landing page.
Create a partial for use in layouts/docs/baseof.html so
announcement is displaye on every page in '<url>/docs/home'
directory.
Add two values to config.toml: announcement (boolean) for toggling
display of announcement; announcement_message, which is the actual
message.
Signed-off-by: Aimee Ukasick <aimeeu.opensource@gmail.com>
* Fix docs home subnav link name
* change linkTitle to Home
* accept fix from master
* refactor docs home template
* bump
* test
* switch layout to basic
* swap in cards
* test card css
* add launch-cards and launch-card classes
* swap in content
* use different layout name to not affect user journeys
* revert file naming
* revert docsportal.html
* remove main, add kubeadm link
* documentation -> docs
* change kubeadm link
* kubeadm GA blog post
* Change file name and add post metadata
* Update CSS for blog post tables
* More formatting and wording changes
* Change build process to allow for displaying future blog posts
* Add links to command documentation
* Change blog post date and address PR feedback
* More wording updates
* update ol ul li bullet to disc
- update ol ul li bullet to disc
- move note out of list so that list numbers are correct
- fix typo
* futher clean-up
* Changed CSS property for browser consistency.
* Moved height property into tablet media query to fix issue on smaller screens.
* Add changed to two more .content files.
* Updated generated resources files, this time using Hugo extended.
* Add new Sass generation system
* Remove resources folder
* Add develop Sass command and sourcemaps
* Add Hugo version shortcode for use in docs
* Add OWNERS file to ./sass folder
* Add AnchorJS JavaScript
* Remove existing inpage_heading logic
* Remove underline from anchor tags
* Use single icon and add touch visibility
* Use paragraph link icon for AnchorJS
* Update Sass to use code formatting in docsContent headers
* Update header size coverage to H3-H6
Move the code of conduct page under /community
Add redirect
Use text from CNCF COC and note the revision we imported it at
Add note to top of imported file not to edit it directly
* [docs] Fix syntax formatting in HA-setup doc.
Attempts to fix an unformatted code block; whatever markdown parser is being used seems to have gotten tripped up, and as a result the inline `yaml` in the script is interpreted as bullet points... it looks [pretty yucky](http://jstu.art/sAjc). I'm wondering if this is something specific to the Hugo toolchain? Because GH itself recognizes the block as valid, even with the `none` syntax type.
If this doesn't trigger a CI build preview, I can test locally to verify.
* [css] Don't display ul/li bullets on UI 'tabs-nav' components.
* [docs] Revert HA docs changes.
This reverts commit f5cf5c7e4f.