Skip to content
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

chore: improve lighthouse score #1478

Merged
merged 6 commits into from
Jul 27, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/hydra/login-consent-flow.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,9 +29,9 @@ The flow itself works as follows:
4. The user's user agent follows the redirect and lands back at Ory OAuth2 & OpenID Connect. Next, Ory OAuth2 & OpenID Connect
redirects the user's user agent to the Consent Provider, hosted at - for example -
`http://consent-service/consent?consent_challenge=4567...`
5. The Consent Provider shows a user interface which asks the user if they would like to grant the OAuth 2.0 Client the
requested permissions ("OAuth 2.0 Scope"). You've probably seen this screen around, which is usually something similar to:
_"Would you like to grant Facebook Image Backup access to all your private and public images?"_.
5. The Consent Provider shows a user interface which asks the user if they would like to grant the OAuth 2.0 Client the requested
permissions ("OAuth 2.0 Scope"). You've probably seen this screen around, which is usually something similar to: _"Would you
like to grant Facebook Image Backup access to all your private and public images?"_.
6. The Consent Provider makes another REST request to Ory OAuth2 & OpenID Connect to let it know which permissions the user
authorized, and if the user authorized the request at all. The user can usually choose to not grant an application any access
to his/her personal data. In the response of that REST request, a redirect URL is included along the lines of
Expand Down
7 changes: 4 additions & 3 deletions docusaurus.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -78,8 +78,8 @@ const config = {
hideOnScroll: false,
logo: {
alt: "Ory",
src: `/docs/img/logo-docs.svg`,
srcDark: `/docs/img/logo-docs-dark.svg`,
src: `/docs/img/logos/logo-docs-2023-02-15.svg`,
srcDark: `/docs/img/logos/logo-docs-dark-2023-02-15.svg`,
href: `https://www.ory.sh`,
width: 63,
height: 32,
Expand Down Expand Up @@ -174,9 +174,10 @@ const config = {
],
logo: {
alt: "Ory logo in white",
src: "/docs/img/logo-ory-white.svg",
src: "/docs/img/logos/logo-ory-white-2022-11-04.svg",
href: "https://www.ory.sh/",
height: 80,
width: 130.7,
},
},
},
Expand Down
53 changes: 0 additions & 53 deletions src/config/hydra/config.js

This file was deleted.

208 changes: 0 additions & 208 deletions src/config/hydra/docusaurus.config.js

This file was deleted.

Loading
Loading