Skip to content

[jp-sync] Sync JP Angular docs: Avatar topic moved to layouts/ (PR #450) - #496

Open
github-actions[bot] wants to merge 2 commits into
vnextfrom
jp-sync/avatar-xplat-topic-pr450-cc02dc2a6107cc35
Open

[jp-sync] Sync JP Angular docs: Avatar topic moved to layouts/ (PR #450)#496
github-actions[bot] wants to merge 2 commits into
vnextfrom
jp-sync/avatar-xplat-topic-pr450-cc02dc2a6107cc35

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Original author: Ivan Minchev 61944284+IMinchev64@users.noreply.github.com

Syncs the Japanese Angular documentation with the changes introduced in PR #450 ("feat(docs): update avatar xplat topic").

Changes Synced

English (source) Japanese (updated) Change
components/avatar.mdx components/avatar.mdx Removed (mirrors EN deletion)
components/layouts/avatar.mdx components/layouts/avatar.mdx Created — full Japanese translation of the new comprehensive Avatar topic
components/toc.json components/toc.json Updated Avatar href from avatar.mdxlayouts/avatar.mdx
components/list.mdx components/list.mdx Updated 2 avatar links to layouts/avatar.mdx
components/stepper.mdx components/stepper.mdx Updated avatar link to layouts/avatar.mdx
components/themes/misc/angular-material-theming.mdx components/themes/misc/angular-material-theming.mdx Updated avatar link to ../../layouts/avatar.mdx
components/themes/misc/bootstrap-theming.mdx components/themes/misc/bootstrap-theming.mdx Updated avatar link to ../../layouts/avatar.mdx
components/tooltip.mdx components/tooltip.mdx Updated 2 avatar links to layouts/avatar.mdx

Summary

The Avatar component documentation was restructured: the old components/avatar.mdx was removed and replaced with a new comprehensive components/layouts/avatar.mdx topic that includes anatomy, variants, shape, size, do/don't guidance, properties table, styling (CSS variables, Sass theming, Tailwind), accessibility, troubleshooting, and FAQ sections. All cross-references to the Avatar topic in related JP docs (list, stepper, tooltip, theming pages, TOC) were updated accordingly.

Generated by Sync Japanese Documentation (Angular) · 166.7 AIC · ⌖ 10.8 AIC · ⊞ 7.4K ·

- Remove components/avatar.mdx (mirrors EN removal)
- Add components/layouts/avatar.mdx (new comprehensive avatar topic, translated to Japanese)
- Update components/toc.json: Avatar href changed from avatar.mdx to layouts/avatar.mdx
- Update components/list.mdx: avatar links updated to layouts/avatar.mdx
- Update components/stepper.mdx: avatar link updated to layouts/avatar.mdx
- Update components/themes/misc/angular-material-theming.mdx: avatar link updated
- Update components/themes/misc/bootstrap-theming.mdx: avatar link updated
- Update components/tooltip.mdx: avatar links updated to layouts/avatar.mdx

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

@jsakamotoIGJP jsakamotoIGJP left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in this PR

  • Refined the Japanese translation for better accuracy and consistency with existing JP topics.
  • The JP images folder was missing the Avatar assets, so I copied them from the EN folder without modification. I verified this with npm run angular:dev:jp and concluded that reusing the same images in JP causes no problem.

Blocker

@ChronosSF As the CI check also detected, the link to the Badge component on the Avatar page returns 404 Not Found. On the EN side, the Badge topic has already been revised and its URL path moved from /badge to /inputs/badge, but that change has not yet been applied to the JP side.

Please DO NOT MERGE this into vnext until the EN Badge changes are also applied to JP. In fact, the Badge and Avatar revisions need to land in vnext at the same time, because the Badge page also links to the Avatar page. The two pages reference each other using the new URL paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant