[Experimental] Try out Astro docs deployment #41279
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This experimental PR gathers the
gh-pages
possible deployment of Astro docs migration PR.First of all, the generated website is created by running
npm run docs
from #41251 (done on the 12th of April). It created a_site
directory like it's already the case in ourmain
branch.Then, likely how we're already doing the
gh-pages
update:Then, you can checkout this branch locally and run
http-server
for instance.Impacts analysis
/examples/*
URLs are not generated but they haven't been generated for a whileComparison of the generated
/team/index.html
_astro
directory must be indocs/5.3/assets
(changed the configuration by using https://docs.astro.build/en/reference/configuration-reference/#buildassets)<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@docsearch/css@3">
and<link rel="stylesheet" href="/_astro/_slug_.C9dNs6d9.css">
in the<head>
; and current Bootstrap version has<link href="/docs/5.3/assets/css/docs.css" rel="stylesheet"><link href="/docs/5.3/assets/css/search.css" rel="stylesheet">
assets
directory that will be used by Astro to run everything. Files are not deferred, but handled directly by Astro as assets.<meta name="twitter:site" content="getbootstrap">
and<meta name="twitter:creator" content="getbootstrap">
should have a content equal to@getbootstrap
<body tabindex="0">
while our current website has a<body>
.<div class="position-fixed" aria-hidden="true"><input type="text" tabindex="-1"></div>
at the end of the file for/docs
URLs only. Astro doesn't have it.In Astro, the<footer>
is defined after the<script>
swhile in Bootstrap it's
Analysis: OK because everything is in the
assets
directory that will be used by Astro to run everything. Files are not deferred, but handled directly by Astro as assets.Before merging
sitemap.xml
that will be unused