With the current docs directory setup, I'm making too many mistakes and have to manually address path changes and directory moves on deploy. This makes for a frustrating experience developing locally and shipping releases. With this PR, we're basically back to the same setup from v3—duplicating the dist directory into our docs directory. Not the most ideal, but very straightforward for me as the release manager.
* update docs path from docs/4.0/ to docs/4.1/
* bump version to 4.1.0
* Update redirects to work for 4.1 docs move
* Update docs version switcher to include latest and link to 4.0 docs
* re-run dist
* Update package-lock.json
* Update docs-navbar.html
1. Add `alt=""` for the Bootstrap logo
2. Replace the HTML entities with the unicode symbols
3. Refactor the badges to something that makes more sense to me
4. Change `Selenium Test Status` alt attribute to `Sauce Labs Test Status`
5. Use shields.io for the peerDependencies badge too
6. Add CSS and JS gzip size badges, shoutout to @ngryman
7. Add a few more trailing slashes to URLs
8. Change link to tooling setup to the website one
* use a trailing slash when possible
* use https when possible
* remove a few redirected links
* consistently use `https://popper.js.org/`
* fix `iconUrl` in nuget files
* change Jekyll Windows guide to the official one
* Update docs for old releases section in README
Hopefully not many folks are still in the process of transitioning to version 3.
* tweak for future-friendliness
* Remove remaining references to v4 Alpha
This commit removes the remaining refrences to the v4 Alpha website and replaces them with the
corresponding v4 Beta ones.
**Note:** We have to hard code the current docs version at some places. Wouldn't it be good to have a `/docs/latest/` redirect to solve this "issue" in the future?
* Don't update the domain in the CNAME file
