Diff for withastro/docs/src/content/docs/en/concepts/why-astro.mdx since 2024-12-17

src/content/docs/en/concepts/why-astro.mdx CHANGED Edit Tailwind style section to change links and wording (#11279) • by Ariel K •
@@ -17,7 +17,7 @@ Some highlights include:
17
17
  - **[Server-first](/en/guides/on-demand-rendering/):** Moves expensive rendering off of your visitors' devices.
18
18
  - **[Zero JS, by default](/en/basics/astro-components/):** Less client-side JavaScript to slow your site down.
19
19
  - **[Content collections](/en/guides/content-collections/):** Organize, validate, and provide TypeScript type-safety for your Markdown content.
20
- - **[Customizable](/en/guides/integrations-guide/):** Tailwind, MDX, and hundreds of integrations to choose from.
20
+ - **[Customizable](/en/guides/integrations-guide/):** Partytown, MDX, and hundreds of integrations to choose from.
21
21
 
22
22
  ## Design Principles
23
23
 
src/content/docs/en/concepts/why-astro.mdx CHANGED Grammar corrections to why-astro.mdx (#12840) • by robertvsuch •
@@ -75,9 +75,9 @@ The `.astro` UI language is a superset of HTML: any valid HTML is valid Astro te
75
75
 
76
76
  We then made sure that you could also use your favorite UI component languages that you already know, and even reuse components you might already have. React, Preact, Svelte, Vue, Solid, and others, including web components, are all supported for authoring UI components in an Astro project.
77
77
 
78
- Astro was designed to be less complex than other UI frameworks and languages. One big reason for this is that Astro was designed to render on the server, not in the browser. That means that you don't need to worry about: hooks (React), stale closures (also React), refs (Vue), observables (Svelte), atoms, selectors, reactions, or derivations. There is no reactivity on the server, so all of that complexity melts away.
78
+ Astro was designed to be less complex than other UI frameworks and languages. One big reason for this is that Astro was designed to render on the server, not in the browser. That means that you don't need to worry about hooks (React), stale closures (also React), refs (Vue), observables (Svelte), atoms, selectors, reactions, or derivations. There is no reactivity on the server, so all of that complexity melts away.
79
79
 
80
- One of our favorite sayings is: **opt in to complexity.** We designed Astro to remove as much "required complexity" as possible from the developer experience, especially as you onboard for the first time. You can build a "Hello World" example website in Astro with just HTML and CSS. Then, when you need to build something more powerful, you can incrementally reach for new features and APIs as you go.
80
+ One of our favorite sayings is **opt in to complexity.** We designed Astro to remove as much "required complexity" as possible from the developer experience, especially as you onboard for the first time. You can build a "Hello World" example website in Astro with just HTML and CSS. Then, when you need to build something more powerful, you can incrementally reach for new features and APIs as you go.
81
81
 
82
82
  ### Developer-focused
83
83
 
src/content/docs/en/concepts/why-astro.mdx CHANGED New Ecosystem tab (#13571) • by Fred K. Schott •
@@ -17,7 +17,7 @@ Some highlights include:
17
17
  - **[Server-first](/en/guides/on-demand-rendering/):** Moves expensive rendering off of your visitors' devices.
18
18
  - **[Zero JS, by default](/en/basics/astro-components/):** Less client-side JavaScript to slow your site down.
19
19
  - **[Content collections](/en/guides/content-collections/):** Organize, validate, and provide TypeScript type-safety for your Markdown content.
20
- - **[Customizable](/en/guides/integrations-guide/):** Partytown, MDX, and hundreds of integrations to choose from.
20
+ - **[Customizable](/en/guides/integrations/):** Partytown, MDX, and hundreds of integrations to choose from.
21
21
 
22
22
  ## Design Principles
23
23