Skip to content

Updating production from staging - #560

Open
ChronosSF wants to merge 14 commits into
masterfrom
vnext
Open

Updating production from staging#560
ChronosSF wants to merge 14 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 14 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>
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.

6 participants