From d0b8485ddfd8dca1376ea0d417ce37282d092cd9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcus=20Otterstr=C3=B6m?= <35617441+MarcusOtter@users.noreply.github.com> Date: Sat, 31 Jul 2021 00:34:07 +0200 Subject: [PATCH] Ascii quotes (#928) --- docs/reference/api-reference.md | 10 +- docs/src/pages/blog/island-architecture.md | 2 +- .../pages/core-concepts/astro-components.md | 6 +- docs/src/pages/core-concepts/collections.md | 4 +- docs/src/pages/guides/deploy.md | 2 +- docs/src/pages/guides/styling.md | 96 +++++++++---------- docs/src/pages/reference/api-reference.md | 4 +- .../reference/configuration-reference.md | 2 +- 8 files changed, 63 insertions(+), 63 deletions(-) diff --git a/docs/reference/api-reference.md b/docs/reference/api-reference.md index b5f4f1bf1..9b0d82c9f 100644 --- a/docs/reference/api-reference.md +++ b/docs/reference/api-reference.md @@ -28,7 +28,7 @@ const data = Astro.fetchContent('../pages/post/*.md'); // returns an array of po ``` -`.fetchContent()` only takes one parameter: a relative URL glob of which local files you’d like to import. Currently only `*.md` files are supported. It’s synchronous, and returns an array of items of type: +`.fetchContent()` only takes one parameter: a relative URL glob of which local files you'd like to import. Currently only `*.md` files are supported. It's synchronous, and returns an array of items of type: ```js { @@ -113,9 +113,9 @@ When using the [Collections API](/core-concepts/collections), `createCollection( | `permalink` | `({ params }) => string` | **Required for URL Params.** Given a `param` object of `{ name: value }`, generate the final URL.\* | | `rss` | [RSS](/reference/api-reference#rss-feed) | Optional: generate an RSS 2.0 feed from this collection ([docs](/reference/api-reference#rss-feed)) | -_\* Note: don’t create confusing URLs with `permalink`, e.g. rearranging params conditionally based on their values._ +_\* Note: don't create confusing URLs with `permalink`, e.g. rearranging params conditionally based on their values._ -⚠️ `createCollection()` executes in its own isolated scope before page loads. Therefore you can’t reference anything from its parent scope. If you need to load data you may fetch or use async `import()`s within the function body for anything you need (that’s why it’s `async`—to give you this ability). If it wasn’t isolated, then `collection` would be undefined! Therefore, duplicating imports between `createCollection()` and your Astro component is OK. +⚠️ `createCollection()` executes in its own isolated scope before page loads. Therefore you can't reference anything from its parent scope. If you need to load data you may fetch or use async `import()`s within the function body for anything you need (that's why it's `async`—to give you this ability). If it wasn't isolated, then `collection` would be undefined! Therefore, duplicating imports between `createCollection()` and your Astro component is OK. #### RSS Feed @@ -143,7 +143,7 @@ export async function createCollection() { item: (item) => ({ title: item.title, description: item.description, - pubDate: item.pubDate + 'Z', // enforce GMT timezone (otherwise it’ll be different based on where it’s built) + pubDate: item.pubDate + 'Z', // enforce GMT timezone (otherwise it'll be different based on where it's built) /** (optional) add arbitrary XML to each */ customData: `${item.type} ${item.duration} @@ -156,7 +156,7 @@ export async function createCollection() { Astro will generate an RSS 2.0 feed at `/feed/[collection].xml` (for example, `/src/pages/$podcast.xml` would generate `/feed/podcast.xml`). -⚠️ Even though Astro will create the RSS feed for you, you’ll still need to add `` tags manually in your `` HTML: +⚠️ Even though Astro will create the RSS feed for you, you'll still need to add `` tags manually in your `` HTML: ```html "The general idea of an _“Islands”_ architecture is deceptively simple: Render HTML pages on the server, and inject placeholders or slots around highly dynamic regions. These placeholders/slots contain the server-rendered HTML output from their corresponding widget. They denote regions that can then be "hydrated" on the client into small self-contained widgets, reusing their server-rendered initial HTML."-Jason Miller +> "The general idea of an _"Islands"_ architecture is deceptively simple: Render HTML pages on the server, and inject placeholders or slots around highly dynamic regions. These placeholders/slots contain the server-rendered HTML output from their corresponding widget. They denote regions that can then be "hydrated" on the client into small self-contained widgets, reusing their server-rendered initial HTML."-Jason Miller To develop a better understanding of what Jason meant with his proposal, let's quickly explore the backdrop, before we explain 'Island Architecture' and how it is applied into Astro as our primary ethos. diff --git a/docs/src/pages/core-concepts/astro-components.md b/docs/src/pages/core-concepts/astro-components.md index a72c5121b..758b3fb07 100644 --- a/docs/src/pages/core-concepts/astro-components.md +++ b/docs/src/pages/core-concepts/astro-components.md @@ -34,7 +34,7 @@ An Astro component represents some snippet of HTML in your project. This can be CSS rules inside of a ` -
I’m a scoped style and only apply to this component
+
I'm a scoped style and only apply to this component

I have both scoped and global styles

``` @@ -52,7 +52,7 @@ To include every selector in a ` -
I’m a scoped style and only apply to this component
+
I'm a scoped style and only apply to this component

I have both scoped and global styles

``` @@ -66,7 +66,7 @@ We also automatically add browser prefixes using [Autoprefixer][autoprefixer]. B ## Supported Styling Options -Styling in Astro is meant to be as flexible as you’d like it to be! The following options are all supported: +Styling in Astro is meant to be as flexible as you'd like it to be! The following options are all supported: | Framework | Global CSS | Scoped CSS | CSS Modules | | :--------------- | :--------: | :--------: | :---------: | @@ -75,9 +75,9 @@ Styling in Astro is meant to be as flexible as you’d like it to be! The follow | `.vue` | ✅ | ✅ | ✅ | | `.svelte` | ✅ | ✅ | ❌ | -¹ _`.astro` files have no runtime, therefore Scoped CSS takes the place of CSS Modules (styles are still scoped to components, but don’t need dynamic values)_ +¹ _`.astro` files have no runtime, therefore Scoped CSS takes the place of CSS Modules (styles are still scoped to components, but don't need dynamic values)_ -All styles in Astro are automatically [**autoprefixed**](#cross-browser-compatibility), minified and bundled, so you can just write CSS and we’ll handle the rest ✨. +All styles in Astro are automatically [**autoprefixed**](#cross-browser-compatibility), minified and bundled, so you can just write CSS and we'll handle the rest ✨. --- @@ -112,7 +112,7 @@ Astro also supports [Sass][sass] out-of-the-box. To enable for each framework: - **Vue**: ` @@ -243,7 +243,7 @@ import Button from './Button.astro'; ``` -This is undesirable because now `