Skip to content

Updating production from staging - #560

Open
ChronosSF wants to merge 50 commits into
masterfrom
vnext
Open

ChronosSF wants to merge 50 commits into
masterfrom
vnext

Conversation

@ChronosSF

Copy link
Copy Markdown
Member

Closes #

Checklist:

  • check topic's TOC/menu and paragraph headings
  • Include TOC topic labels in the topic content when it has a valuable update, is new, or is considered preview / beta
  • link to other topics using ./page.mdx or ../relative/path.mdx (.mdx extension required)
  • at the References section at the end of the topic add links to topics, samples, etc
  • reference API documentation instead of adding a section with API

  • use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
  • use spell checker tool (VS Code, Grammarly, Microsoft Editor)
  • add inline code blocks for the names of classes / tags / properties
  • add language descriptor for the code blocks
  • check if links function by running the check-api/mdx npm commands
  • check if sample is working and fully visible in the topic
  • check if sample is working and fully visible in the StackBlitz
  • check if code blocks match the code in StackBlitz demo
  • add or update meaningful llms.description metadata and run npm run check:llms-metadata


  • do not resolve requested changes (leave that to the reviewer)

Hristo313 and others added 30 commits August 28, 2026 15:41
…essibility-section

fix(docs): update the topics accessibility section rules
feat(grid-theming): refactor grid theming topics and add a grid theme building playground sample
- Add grids_templates/theming.mdx (new JP translation)
- Add 4 new Theming entries to components/toc.json
- Update Sample heights in hierarchical-grid.mdx, tree-grid.mdx, pivot-grid.mdx

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…R023/R029/R033/R034]

- hierarchical-grid.mdx: translate untranslated Sample alt text [R001]
- theming.mdx frontmatter: restore English component proper nouns in
  title/description/llms.description to match sibling topics and the
  {ComponentTitle} token, which always resolves to English [R005]
- theming.mdx: use English component names in the info aside, matching
  body prose convention [R009]
- theming.mdx: fix mistranslations and stiff phrasing - "color space",
  "popup chrome", "derivation roots", katakana "background" (which means
  a background process elsewhere in the JP docs), "Color is only half of
  a theme", and the "Try it" paragraph [R011/R014/R018/R020/R021/R029/R033]
- theming.mdx: unify okurigana and translate a leftover code comment
  [R022/R023/R034]

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- Use the established term ページネーター for paginator (was ページャー)
- Reword the theme-function aside for readability
- Restore the dropped 'tints' nuance in the $accent-color row
- Split the derivation sentence so the runtime clause reads clearly
- Replace the literal 'テーマの残り' with 'テーマの他の部分'
- Reword the CSS-only theming consequence sentence

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…93427390d37cb

[jp-sync] Sync JP docs: grid theming topics
docs(accessibility): update accessibility compliance documentation stucture and content
Co-authored-by: Stamen Stoychev <chronos.stz@gmail.com>
#535, #491 (#556)

* docs(jp): sync Angular JP docs with EN PRs #522, #438, #535, #491

Manual replay of the four failed "Sync Japanese Documentation (Angular)"
runs (33877005832, 34238718782, 34250163709, 34329511530). Each died in
the Copilot CLI step with transient_bad_request before doing any work;
the workflows have since been recompiled with gh-aw v0.88.7 in #555.

- chat: translate the `messages` row and the new bidirectional messages
  collection section (#438)
- theming-mcp: add the WCAG contrast note linking to the new
  Accessibility topic (#522)
- palettes: hsla() contrast variables in the CSS excerpt (#522)
- toc: add Themes > Accessibility; Button now points at
  inputs/button.mdx (#522, #491)
- retarget IgxButton links in dialog, time-picker, tooltip, roundness,
  material/bootstrap theming and the row-editing/search grid templates
  to the xplat-generated inputs/button page (#491, #535)
- remove the hand-authored button.mdx and layouts/avatar.mdx, superseded
  by the xplat-generated pages exactly as EN did (#491, #522)
- xplat jp toc: lift the Angular exclude on Button, Icon, Icon Button
  and Avatar and add Themes > Accessibility, mirroring the EN xplat toc
  so the Angular JP site gains the generated pages the Angular toc now
  references
- add the jp xplat themes/accessibility.mdx translation (target of the
  new toc entry and of the theming-mcp note)
- mirror the new button anatomy / do-don't images into jp/images, which
  the Angular build resolves per language via @xplat-images

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* docs(jp): sync xplat JP docs with EN PRs #522, #438, #535, #491

Manual replay of the four failed "Sync Japanese Documentation (xplat)"
runs (33877005838, 34238718784, 34250163990, 34329511576), which died in
the Copilot CLI step exactly like their Angular counterparts. Change set
is the EN diff under docs/xplat/src/content/en/ since the last successful
xplat sync (d346871), filtered to TOC-covered files per the workflow.

- inputs/button: re-mirror the rewritten EN topic (anatomy, getting
  started, usage/variants/states/layout/size/download/do-don't,
  properties, styling incl. Tailwind, accessibility, troubleshooting,
  dependencies, related, FAQ), reusing existing JP prose where EN kept it.
  The Getting Started link is split per platform like the JP badge and
  button-group pages, because the JP xplat toc still excludes
  general-getting-started.mdx for Angular (EN does not)
- inputs/button-group: Angular-specific PlatformBlocks throughout,
  {PackageCommon} install block, per-platform properties tables, API
  references and dependencies, new Related/FAQ content
- inputs/badge: {PackageCommon} install block, Angular import sentence,
  CSS variables table, troubleshooting/FAQ updates
- interactivity/accessibility-compliance: replace the Section 508 / WCAG
  matrices with the new standards, criteria, per-component documentation
  index (JP heading anchors), configuration, VPAT and FAQ sections
- interactivity/chat: Blazor MessageCreated guidance, per-platform
  property names, bidirectional messages collection section
- themes/overview: configureTheme variant argument, new Customizing with
  Sass section; themes/accessibility now anchors to it
- themes/palettes: runtime relative-color contrast, seed variables,
  --ig-wcag-* excerpt, contrast-level note
- ai/theming-mcp: WCAG contrast note

Not mirrored: the EN toc href fix for grids/grid/theming-grid.mdx (#535)
only corrected EN after a July file move (#355) that was never applied to
JP; JP still keeps the page at grids/theming-grid.mdx consistently.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* review: apply native check fixes (fix wording inconsistencies)

* review: apply native check fixes (reword literal "boundaries" translation in troubleshooting intros and known-limitations lead-in)

* review: apply native check fixes (reword literal "boundaries" translation in the Before You Start lead-in)

* review: apply native check fixes (restore accessibility anchors on carousel and tooltip links)

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: jsakamotoIGJP <jsakamoto@infragistics.com>
* docs(jp): sync switch topics translation (#546)

Sync Japanese documentation with English switch topic updates from
commit 5f68139 (feat(switch): update switch topics (#546)).

- components/inputs/switch.mdx: full translation of the reworked
  Switch topic (anatomy, getting started, usage, interaction states,
  styling, accessibility, troubleshooting, FAQ, related components).
- components/inputs/badge.mdx: updated Sample height (212 -> 250) for
  the outlined badge example, matching the English change.
- toc.json: removed the Angular exclude on the Switch entry and added
  updated: true, matching the English toc.json change.

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

* chore(toc): fix the jp toc as gh aw is bad at doing that

* Update Japanese terminology in switch documentation

* Fix typo in switch component documentation

* fix(*): fixing relative links for angular to point to the correct getting started topic

* fix(apilinks): fixing preceding errors with the same getting started issue

* docs(jp): add missing Angular JP images for switch anatomy and do/don't

---------

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: Stamen Stoychev <SStoychev@infragistics.com>
Co-authored-by: mkamiishi <mkamiishi@infragistics.com>
Co-authored-by: jsakamotoIGJP <jsakamoto@infragistics.com>
viktorkombov and others added 15 commits September 23, 2026 15:28
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sync docs/xplat/src/content/jp with the Virtual Scroll component topic
added in commit f02dd59 (#840).

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

[jp-sync] Sync Japanese docs: Virtual Scroll component topic
…20706d80aa9bdb

[jp-sync] Sync JP docs: Virtual Scroll component topic (Angular)
ChronosSF and others added 5 commits September 25, 2026 16:38
* feat(*): updating astro and astro/mdx versions

* chore(ci): update actions to Node 24 versions

These majors still declare a node20 runtime, which GitHub Actions has
deprecated in favor of node24:

- actions/checkout v4 -> v7
- actions/setup-node v4 -> v7
- actions/upload-artifact v4 -> v7
- actions/stale v9 -> v11

actions/github-script@v8 already runs on node24, and the gh-aw lock
files are generated with current pins, so both are left unchanged.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* feat(*): updating astro-components deps and clean-up

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
fix(ci): catch broken toc.json entries on every PR and after merges
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.

10 participants