fix: update cloudflare integration guide

[jsparkdev]

Description (required)

update cloudflare integration guide

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/guides/integrations-guide/cloudflare.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	4a50970
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/6809ed7a20b59b0009033f27
😎 Deploy Preview	https://deploy-preview-11506--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.

[sarah11918]

Amazing updates, @jsparkdev ! Thank you so much for this PR! I appreciate the consistency, and love the definitions being turned into... definitions!

See my comments below for some specifics, which are mostly "I guess we're going to have to make some decisions and standardize throughout" 😅

You've identified some great improvements here, which are going to force us to do more work... but then have even greater improvements! 💪

[sarah11918]

This might be the only change I wouldn't necessarily make? We do commonly repeat the value within the description, maybe more often than not? So it's not a hard rule to follow to never refer to it within its own definition:

https://docs.astro.build/en/reference/configuration-reference/#compresshtml

https://docs.astro.build/en/reference/configuration-reference/#checkorigin

https://docs.astro.build/en/reference/configuration-reference/#markdowngfm

Admittedly, it's not standardized, and we can discuss our preferred way of doing this. We currently have a mix of:

• "to disable, set false"
• "to disable, set propertyName: false"
• "to disable, set propertyName to false"

We should probably make a docs Discussion to figure out how we want to standardize on this!

[jsparkdev]

Thanks for the good point!

[sarah11918]

Ugh, did GitHub eat my comment? Unresolving to make this easier to see on Talking and Doc'ing tomorrow, too!

[sarah11918]

Suggested change

	Determine whether to enable the Cloudflare runtime in development mode.
	Determines whether to enable the Cloudflare runtime in development mode.

We typically (although I just checked, not always! 😅 ) use this form of the verb.

My thinking is that a definition answers either:

"What is this?" when the point is to say what something is

• An array of allowed hosts
• The base path to deploy to

OR

"What does this do?" often with an assumed ["This"]:

• [This] Specifies the output target for builds
• [This] Enables security measures for an Astro website

I'm checking in config reference and of course I see right next to each other:

• Specify a mapping of redirects
• Specifies the output target for builds

So, clearly we have some work to do here, too! I see both in use on this page. (Enables, Determines... but then later Configure routes, Configure identical routes...

Let's make THIS page all verbs with the (s) for now, so that this one page is internally consistent, and we'll add this to our pile of "let's go through all the docs and standardize..." pile 😄

[jsparkdev]

Thanks for the great information!

[sarah11918]

I just "unresolved" the conversation for two reasons @jsparkdev 👍

1. I think there are more "no-s" verbs on this page we could standardize while we're here! Can you e.g. get the "Configure routes" while you're already here?
2. I'd like to use this comment tomorrow on Talking & Doc'ing, and this makes it easier to see. 😄

[ArmandPhilippot]

A tiny nit regarding a default, otherwise great job! 🙌🏽

[sarah11918]

OK, I think this looks great! And we can use it to update more going forward! Thank you again!

[yanthomasdev]

Good work @jsparkdev, I have just a small comment/nit for you!