Add multiple cdn

[peng]

Description

Add build.assetsPrefix config docs if is object.

Related issues & labels (optional)

PR: withastro/astro#10189

Issues discussed: withastro/astro#9700 (comment)

Opened discussion: withastro/roadmap#818

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Feb 23, 2024 6:45pm

[astrobot-houston]

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any broken links you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[VoxelMC]

Hello! Thank you for submitting these wonderful Docs changes.
There are a few things to get out of the way first!

1. I see that this documents a currently proposed change! Once that change gets through scrutiny, it will be merged when appropriate :) (minor release day!)
2. In Astro Docs, we tend to write the en document first, merge it, then translate them. This way, it is less of a headache for the maintainers to check that every page is correct, and it's better for the translators to keep track of what is happening with the pages! You are more than welcome to PR the translations post-merge! I may be wrong about this; if I am, let me know (maintainers). Just letting you know before moving forward!
3. We may need to go through some iterations to ensure the documentation is consistent with current writing styles! I, and I am sure others, would love to work with you to make that happen.

Here's looking at getting that Astro PR merged and then this one, subsequently!

[VoxelMC]

Since this is documenting new behaviour, we will need to double check with core for accuracy!

[VoxelMC]

This review comment is more for overall edits.
You have done a great job of writing out what this new change brings! Quite frankly, it's pretty cool :)
I have suggested some changes, but if you feel like they are incorrect, feel free to ignore them or discuss with me how we can meet somewhere in the middle!

Once more, thank you for working on this!!!

[sarah11918]

Hi @peng - Thank you for contributing!

This will take a little bit of work to resolve properly, because in fact this is not the appropriate place to make changes to the configuration reference file, nor should any changes be made to other languages.

You should see at the top of this page when you edit it to tell you which file holds the source for this documentation:

Because this is also a feature / code change, the proper PR for this documentation is the same one you made your code changes in. That PR should also edit the above file and include documentation there, in proper JSDoc formatting. So, it's a little trickier because it must follow those syntax rules. You should look at other entries on the page and follow the model of how they are written.

Also, no changes should be made to any translated files. I'm assuming you do not speak all of these languages? 😄 We do not use any automated translations in our docs, and we have a system for our human translators, who are native speakers, to handle translations after a change is made to the English documentation. Most documentation contributions do require editing, so it is also inefficient to try to provide all languages up front before we have edited the English content.

So, this PR will eventually be closed. But, we can use this PR for some first edits, then you will know what to add to the other Astro PR and we can polish final documentation edits in that PR!

[sarah11918]

FYI - I removed the changes to the other languages so that I could remove our automated i18n label -- it will keep adding itself back as long as there is a change to a translated page, and then it's harder for me to label properly for triage! 😄

[sarah11918]

Just putting a block on this to make sure it doesn't get merged here. This content should move to the other linked Astro PR.

[peng]

@sarah11918 OK, I will open another PR.

[peng]

@VoxelMC @sarah11918 I opened another PR: #7183. Only en docs. Create by astro/src/@types/astro.ts file.