* add prettier
* ci
* run prettier
* run prettier in CI
* run prettier --write
* ignore README.md
* specify googleAnalytics
* fmt
* npm run write-translations
* fmt
* ignore i18n json files
they're autogenerated and don't like being formatted
* post merge fixes & some updates
* post merge fixes
* Reorganize docs
* delete wasm-build-tools.mdx
* more small updates
* i hate versioned docs
* seems like I've got the traits of the certain owl who guards over the civilization when it comes to `;`
* just work please
* Update website/docs/concepts/components/lifecycle.mdx
Co-authored-by: Julius Lungys <32368314+voidpumpkin@users.noreply.github.com>
* little things
* post merge fixes
* npm update
Co-authored-by: Julius Lungys <32368314+voidpumpkin@users.noreply.github.com>
* some documentation fixes
* more fixes
* why it didn't work before is beyond me
* next redirect
* change 0.18 docs folder structure to make it inline with next
* move docs to /docs
now that home is its own page, docs should be under `/docs/`
* tag 0.19.0 version on website
function components are not part of `0.18.0` and even with the warning on
the introduction page many users still ask how they can access function
components or hooks.
The information and code blocks have fallen out of sync with the changes
on `master` so this is not even useful for users. One of the examples on
"Custom Hooks" page causes an exception in the rust markup so this issue
is resolved too and doesn't apply to the `next` version as the code
example is different.
If a user wants to learn about function components or hooks then they
can review the `next`/`master` version on yew.rs.
* checkout before artifact
* config for fork
* pass pull request number (again)
* worthless change to trigger build
* use comment url path
* let's play around with redirects
* trigger change
* redirects
* update config
* remove firebase.json from pull request
* remove redirects
* use an index page instead of redirects
* intro -> index
* revert unnecessary changes
* correct format
