You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before the 2024 refresh (#359), the root and only tab used to have the path / and not /{repo_name}. The trailing /{repo_name} makes the URL look a bit odd in case we only have a single package. Here's a comparison between the two routing schemes:
# Before 2024 refresh
https://widgetbook.docs.page/guides/quick-start
# After 2024 refresh (redundant /widgetbook)
https://widgetbook.docs.page/widgetbook/guides/quick-start
This change makes sense in the following cases, but not in ours.
Yep this isn't ideal sorry - here's what happened:
We have custom domain support, in your case your docs pointed to docs.widgetbook.io. During our migration to the refresh we hit some issues upgrading our custom domain proxy which we didn't expect. We made the call to redirect custom domains to their vanity domain (:org.docs.page/:repo) as a temporary workaround whilst we upgrade the custom domain service. We didn't want to block the release on custom domains.
This is actively in progress, so we'll soon have docs.widgetbook.io back up and running.
Before the 2024 refresh (#359), the root and only tab used to have the path
/
and not/{repo_name}
. The trailing/{repo_name}
makes the URL look a bit odd in case we only have a single package. Here's a comparison between the two routing schemes:This change makes sense in the following cases, but not in ours.
Default domains
Organization with multiple repos
The text was updated successfully, but these errors were encountered: