Files
awesome-copilot/website
github-actions[bot] e353a8cfb8 [bot] sync: CLI for Beginners — ch04 @-style imports + ch06 /mcp list (2026-07-10) (#2264)
* sync: update cli-for-beginners ch04 and ch06 from upstream

- Chapter 04: Add @-style imports section under Custom Instruction Files
  (released in v1.0.66, 2026-06-30). Users can now reference other files
  inside AGENTS.md or instruction files with @filepath syntax.

- Chapter 06: Add /mcp list to the Additional MCP Commands reference table.
  Released in v1.0.69-1 (2026-07-04), /mcp list shows currently attached MCP
  servers and can be run while Copilot is working. Also add /mcp auth command
  and update enable/disable descriptions to note session persistence.

- Bump lastUpdated to 2026-07-10 in both files.

Upstream commits: c559ab4953a0 (2026-07-09)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix: revert ch04 content changes, keep only date update

Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>

* Apply suggestion from @aaronpowell

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
2026-07-14 01:16:56 +00:00
..
2026-05-29 11:11:10 +10:00

Awesome GitHub Copilot website

Astro + Starlight site published to https://awesome-copilot.github.com/.

Local development

Run these from the repository root (they generate the data the site needs first):

npm run website:data    # generate public/data/*.json from repo content
npm run website:dev     # generate data + start the dev server
npm run website:build   # full production build

Accessibility

The website has an automated axe-core + Playwright audit. Run it locally with npm run website:a11y from the repository root, or run npm run a11y from website/ after building dist first.

CI blocks on critical and serious violations. Minor and moderate best-practice issues are reported as non-blocking.

Authoring conventions: resource cards use div[role="listitem"] wrappers, not <article>; only add role="list" to containers whose direct children are list items; do not nest interactive controls inside another focusable element; .btn-primary and ToC links must meet WCAG AA (4.5:1) contrast in both light and dark themes.

Social preview cards (LinkedIn, etc.)

Shared links render as large preview cards driven by Open Graph / Twitter meta tags. LinkedIn (and most platforms) read Open Graph — primarily og:image — while Twitter/X also uses twitter:card=summary_large_image. Most tags are produced automatically:

  • Starlight defaults emit og:title, og:description, og:url, og:type, og:site_name, and twitter:card=summary_large_image.
  • astro.config.mjs (global head) emits the shared image tags: og:image, og:image:width, og:image:height, og:image:alt, and twitter:image.
  • src/components/Head.astro adds twitter:title/description, og:image:secure_url, og:image:type, and twitter:image:alt.

Each page's title and description (StarlightPage frontmatter) flow into the card text, so keep them clear and benefit-focused.

The image-dimension invariant

og:image:width / og:image:height in astro.config.mjs describe public/images/social-image.png (currently 2400×1260, ~1.91:1). Crawlers use these dimensions to understand the image and may use them when selecting/rendering the preview. If you swap the image or add a per-page image override, update the full image set so every tag stays consistent: og:image, og:image:width, og:image:height, og:image:alt, and twitter:image (the last one matters because Head.astro derives og:image:secure_url from twitter:image first).

After deploying

LinkedIn caches scrapes aggressively. To force a refresh and confirm the card renders, run the changed URL through the LinkedIn Post Inspector. HTML output alone doesn't prove the live card — verify the deployed image returns HTTP 200 over HTTPS with Content-Type: image/png and no auth.