Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Closes #
Checklist:
preview/beta./page.mdxor../relative/path.mdx(.mdxextension required)IgxSelectComponent,<igx-combo>code blocksfor the names of classes / tags / propertiescode blockscheck-api/mdxnpm commandsllms.descriptionmetadata and runnpm run check:llms-metadata