Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modifying <head>: clarity and placement in the docs #1442

Merged
merged 11 commits into from
Aug 30, 2022
Merged

Conversation

Jutanium
Copy link
Contributor

TL;DR

  • Moves the Modifying <head> section into the Layouts section of /core-concepts/astro-pages
  • Clarifies that there is no special handling of the <head> tag

What kind of changes does this PR include?

  • New or updated content

Description

This addresses #1378.

The behavior of the <head> tag has little to do with the difference between JSX and Astro components. It does have to do with certain libraries within the React ecosystem, but that is not due to the JSX syntax. Documenting <head> makes more sense in the Layouts section of Astro Pages, because we recommend using the tag in a Layout, so I moved it there. (I could also see moving this to its own section within Astro Pages).

The section itself was unclear, as #1378 describes. Astro does not have any special handling of <head>, and I updated the wording to make that more clear.

@netlify
Copy link

netlify bot commented Aug 30, 2022

Deploy Preview for astro-docs-2 ready!

Name Link
🔨 Latest commit f13f93a
🔍 Latest deploy log https://app.netlify.com/sites/astro-docs-2/deploys/630e7c387f2c8800084348c1
😎 Deploy Preview https://deploy-preview-1442--astro-docs-2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Dan Jutan added 5 commits August 30, 2022 17:07
@sarah11918
Copy link
Member

LGTM @Jutanium! Great call!

@Jutanium Jutanium merged commit dc625de into main Aug 30, 2022
@Jutanium Jutanium deleted the modifying-head branch August 30, 2022 21:20
trueberryless added a commit to trueberryless/withastro-docs that referenced this pull request Oct 21, 2024
yanthomasdev added a commit that referenced this pull request Nov 4, 2024
* update translation #1442

* update translation #1434

* update translation #1510

* update translation #1538

* Update src/content/docs/de/basics/astro-pages.mdx

* Update src/content/docs/de/basics/astro-pages.mdx

* Update src/content/docs/de/basics/astro-pages.mdx

* Update src/content/docs/de/basics/astro-pages.mdx

* Update src/content/docs/de/basics/astro-pages.mdx

* update translation #1638

* update translation #2091

* update translation #2133

* update translation #2409

* update translation #2371

* update translation #4610

* update translation #5128

* update translation #5205

* update translation #5240

* update translation #5364

* update translation #5765

* update translation #6267

* remove paragraph where I cant find when it was deleted in original version

* update translation #6620

* update translation #8495

* update translation #8573

* update translation #9336

* update translation #9336 2/2

didnt save file locally, so git didnt add

* fix all visual differences by comparing manually against original english version

* fix broken links in `astro-pages.mdx`

* Breaking changes to other files! fixing links which link to the �stro-pages.mdx file

* but now...

* Update src/content/docs/de/basics/astro-pages.mdx

Co-authored-by: Max <[email protected]>

* Update src/content/docs/de/basics/astro-pages.mdx

Co-authored-by: Max <[email protected]>

* Update src/content/docs/de/basics/astro-pages.mdx

Co-authored-by: Max <[email protected]>

* revert Update markdown-content.mdx

@lunaria-track:src/content/docs/de/basics/astro-pages.mdx

---------

Co-authored-by: Max <[email protected]>
Co-authored-by: Yan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants