Fix integration script for non-core adapters

[matthewp]

What kind of changes does this PR include?

• Changes to the docs site code

Description

• Removes @astrojs/netlify and @astrojs/deno from docs generation as those integrations are no longer controlled by core. They will be documented in their own repository, like with any other 3rd party package.

Related Issue / Implementation PR

• Needed for Remove the deno adapter astro#8559
• Needed for Remove Netlify adapter from core astro#8574

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	c59505c
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/651477f64bebf900085d41ba
😎 Deploy Preview	https://deploy-preview-4741--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[matthewp]

From discussion in Discord, the outstanding thing here is to figure out what to do about the pages that are now excluded. Some options:

• Set up redirects to the new repository homes.
• Add a mdx file that explains that they are now maintained externally with a link.

[sarah11918]

Note to us to merge this when the affected repositories have been moved, and we'll make any necessary docs changes to content on our end at that time.

(E.g. if there is no page remaining to pull in, our content will simply not update and continue to show what's current, so we'll have to either remove manually on our end, or update manually to show a redirect etc.)

[sarah11918]

I'm approving the page text! This should wait for Chris to confirm some page generation questions I had.

[delucis]

I’d be in favour of minimal migration docs here once we know the new package name. Something along the lines of:

1. Uninstall @astrojs/deno
2. Install deno-astro-adapter (or whatever it ends up being called)
3. Update the import statement in astro.config.mjs to use the new package:

   - import deno from '@astrojs/deno';
   + import deno from 'deno-astro-adapter';

But I can understand if we’re reticent to provide any guidance or want to keep that somewhere else.

[sarah11918]

I do like this! Let's do it!

[matthewp]

I think we're going to want to merge this before they have released a new adapter (which we don't know when is going to happen). So would it be ok to go with this for now and update the guidance once that's out?

[matthewp]

The home for Netlify might be changing, so holding off on this one for now, putting back as a draft.

[matthewp]

Ok, this is ready for review again. This is cleaned up so that only Deno is removed from generation. Netlify is now maintained in https://github.com/withastro/adapters/tree/main/packages/netlify and the plan is that other adapters will be moved over. I'll update the script again when those are moved over.

[delucis]

Thanks @matthewp! Left a couple of notes.

Also underlining that these changes mean Deno will no longer show up in our integrations nav:

I think that was clear from our discussion, but might be worth us checking where and how we want to highlight its existence in the future, so that people who want it can still find it.

[sarah11918]

Following @delucis comment above re: now Deno doesn't show up on our list, I updated the SSR page with links to both the integrations directory on astro.build and to our official integrations guide page in docs.

[delucis]

Looks good — thanks @matthewp!