init: webflow oauth integration

[abvthecity]

Integrates oauth callback using webflow.

notes:

• new api route /api/fern-docs/oauth/webflow/callback is created to disambiguate from the ory and workos callback urls. this is important so that webflowclient is compiled separately from ory and workos, otherwise the edge function will eventually blow up in size (and fail to compile)
• new api route /api/fern-docs/oauth/ory/callback is created with a permanent redirect to it from /api/fern-docs/auth/callback. someone needs to reach out to rightbrain to update their actual callback urls, but this should work in the interim.

what's next:

• testing the oauth callback flow. the edge config is set for https://webflow-migration.docs.buildwithfern.com

what i'm not a fan of:

• theres some weird hackery magic going on in the ory-based oauth flow that needs to be reconsidered. @RohinBhargava i've added some TODO comments to indicate where.
• i'm not really sure what the error stuff does (if it does anything) and whether or not it is ory-specific. need to double check webflow's docs on oauth
• i actually think we have a really convoluted setup. we should really have a centralized auth.ferndocs.com for all the auth and oauth logic. Mainly because redirect urls are really really hard to change once they're set.
• the nice thing about vercel edge functions is that it has ultra low-latency, and runs globally. if we were to migrate to a central source of truth, we should consider using cloudflare workers.

[github-actions]

Playwright test results

 1 passed

Details

 1 test across 1 suite
 9 seconds
 6a16378

[github-actions]

PR Preview

• angellist.docs.withchima.com
• api-docs.codecombat.com
• api.dopt.com
• api.labelstud.io
• api.navipartner.com
• api.qdrant.tech
• apidocs.polytomic.com
• column.docs.withchima.com
• dev.documentation.sayari.com
• dev.hume.ai
• developer.balkan.id
• developer.devrev.ai
• developer.ideogram.ai
• developer.projectmanager.com
• developers.awork.com
• developers.beehiiv.com
• developers.gappify.com
• developers.upwardli.com
• docs-beta.projectmanager.com
• docs-next.scoutos.com
• docs.aiaplatform.com.au
• docs.airtop.ai
• docs.anterior.com
• docs.argolabs.ai
• docs.athenaintelligence.ai
• docs.balkanid.org
• docs.boundaryml.com
• docs.bytebot.ai
• docs.cable.tech
• docs.cartesia.ai
• docs.coactive.ai
• docs.cohere.com
• docs.conductorquantum.com
• docs.credal.ai
• docs.darwinbio.io
• docs.darwincloud.xyz
• docs.deeptune.com
• docs.fileforge.com
• docs.flagright.com
• docs.fluidstack.io
• docs.getkard.com
• docs.getscorecard.ai
• docs.givechariot.com
• docs.hellodata.ai
• docs.impiloplatform.com
• docs.instabase.com
• docs.joincandidhealth.com
• docs.kota.io
• docs.mavenagi.com
• docs.mercoa.com
• docs.monite.com
• docs.multion.ai
• docs.nominal.io
• docs.pier-finance.com
• docs.predictionguard.com
• docs.privategpt.dev
• docs.propexo.com
• docs.qlty.ai
• docs.qlty.us
• docs.reka.ai
• docs.revert.dev
• docs.rightbrain.ai
• docs.schematichq.com
• docs.scorecard.io
• docs.sphinxbio.com
• docs.stack-auth.com
• docs.subconscious.ai
• docs.superagent.sh
• docs.syndicate.io
• docs.trykeet.com
• docs.trypinnacle.app
• docs.usebridge.com
• docs.vellum.ai
• docs.withabound.com
• docs.withchima.com
• docs.withtime.ai
• documentation.sayari.com
• fern.assemblyai.com
• fern.ssoready.com
• gusto.docs.withchima.com
• help.getzep.com
• plantstore.dev
• reference.flatfile.com
• rippling.docs.withchima.com
• secure.docs.propexo.com
• www.intern.mavenagi.com
• www.plantstore.dev

[github-actions]

📦 Next.js Bundle Analysis for fern-platform-monorepo

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page	Size (compressed)
global	241.16 KB (🟢 -16.12 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

New Page Added

The following page was added to the bundle from the code in this PR:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/404	447 B	241.6 KB	69.03%

Two Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/dynamic/[host]/[[...slug]]	54.06 KB	295.22 KB	84.35% (🟢 -6.59%)
/static/[host]/[[...slug]]	54.06 KB	295.22 KB	84.35% (🟢 -6.59%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

[github-actions]

Playwright test results

 81 passed

Details

 81 tests across 3 suites
 1 minute, 16 seconds
 6a16378