chore(docs): sync igniteui-xplat-docs Vnext (Mar → May 2026) #166
Open
Zneeky wants to merge 61 commits into
Open
chore(docs): sync igniteui-xplat-docs Vnext (Mar → May 2026) #166Zneeky wants to merge 61 commits into
igniteui-xplat-docs Vnext (Mar → May 2026) #166Zneeky wants to merge 61 commits into
Conversation
Replace manual edit/delete IgbButton blocks with IgbGridEditingActions (EditRow/DeleteRow/AddRow) and merge the Grid, TreeGrid, and HierarchicalGrid Blazor ComponentBlocks into a single block. Ported from igniteui-xplat-docs commit 416b6562 (Add corresponding code snippet for row editing actions topic, #1839). Co-authored-by: Mariela Tihova <mariela.tihova@gmail.com>
Remove the Blazor-only PlatformBlock that duplicated the WebComponents/React CSS parts example and drop the PlatformBlock wrapper so the styling documentation applies to all platforms. Ported from igniteui-xplat-docs commit 77ae9c59 (PR #1864). Co-authored-by: Mariela Tihova <mariela.tihova@gmail.com>
…ify HierarchicalGrid validation example - Merge the Blazor cancel-edit description into the WC/React block now that the same UnitsOnOrder/UnitsInStock example applies to all three. - Drop the Age/HireDate Blazor-specific paragraph. - Rewrite the HierarchicalGrid validation snippets (WebComponents webHierarchicalGridCellEdit -> webGridEditingEventsCellEdit; Blazor igRegisterScript "HandleCellEdit" -> "WebGridEditingEventsCellEdit") to validate UnitsOnOrder against UnitsInStock instead of Debut/LaunchDate. - Drop the now-redundant Blazor "validating two columns" paragraph. Ported from igniteui-xplat-docs commit 37f196b8 (PR #1851, "fix: cell-editing docs and snippets for Blazor and WC"). Co-authored-by: Mariela Tihova <mariela.tihova@gmail.com>
…ow and tweak border - Change the activeRow predicate from 'row.index === 0' (highlights only the first row) to 'row.index % 2 === 0' (highlights every other row) in the Blazor, WebComponents and React snippets. - Change the CSS rule from 'border: 2px solid #fc81b8' to 'border-top: 2px solid #fc81b8' so the highlight reads as a row divider rather than a full box. Ported from igniteui-xplat-docs commits ad4f86ae + 0296a788 (fix: add corresponding code snippets for conditional styling for React and WC). Co-authored-by: Mariela Tihova <MTihova@infragistics.com>
…with sample Change IgbColumn Field="Debut" from Filterable="true" + DisablePinning + DisableHiding to a simple Filterable="false" so the Configure Menu Features snippet matches what the live sample actually renders. Ported from igniteui-xplat-docs commit 8c22c2bb (fix(esf): Edit Configure Menu Features code snippet so that it matches the sample). Co-authored-by: Mariela Tihova <MTihova@infragistics.com>
…e packages - Simplify the intro paragraph and clarify that the language detection reads the root <html> lang attribute. Drop the list of built-in languages (no longer accurate now that translations live in a separate peer dependency). - Add a WebComponents snippet showing how to install igniteui-i18n-resources and register a bundle via igniteui-i18n-core's registerI18n(...) helper. - Reframe addResourceStrings as the escape hatch for languages outside the bundled set. - Soften the wording around the ResourceStrings override paragraph. Ported from igniteui-xplat-docs commits af489111, 29b3f69a, 9cb5e04b, 9f688e56, ebb027e1 (DockManager localization refresh, 2026-03-20..03-26). Co-authored-by: Galina Edinakova <gedinakova@infragistics.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
…test
Open the {PackageVerLatest} section with a Bug Fixes table covering the
new March service release (3229 Trial watermark on licensed Grids, 2754
IgbTabs/IgbSwitch interaction). The previous {PackageVerLatest} body
(Grids features, Breaking Changes, etc.) is now under a new
{PackageVerChanges-25-2-MAR} heading.
Per migration guidance, the de-link of "Row Paging / Filter Row / Load-Save
Layout / GroupBy Area / Cell Merging" in the historical Data Grid sections
is intentionally NOT ported — those linked pages still exist in docs-template.
Ported from igniteui-xplat-docs commits aa041d69, 5f917652, eec7614f and
the bug-fix portion of cf7060d8.
Co-authored-by: Deyan Kamburov <dkamburov@users.noreply.github.com>
Co-authored-by: Stamen Stoychev <sstoychev@infragistics.com>
Co-authored-by: Stamen Stoychev <SStoychev@infragistics.com>
…FEB, backfill 26-2-MAR
- New {PackageVerLatest} section documenting:
- Changed: DockManager bumped to igniteui-dockmanager@2.1.0 (with
minResizeWidth/minResizeHeight, paneFlyoutToggle event,
layoutChange detail); igniteui-webcomponents bumped to 7.1.0 with
new Splitter and Highlight components.
- New Features: AI-Assisted Development - Agent Skills shipped with
the igniteui-react package (components, customize-theme,
optimize-bundle-size).
- Demote the previous {PackageVerLatest} in docs-template to
{PackageVerChanges-26-2-FEB} so the version sequence matches xplat.
- Backfill the {PackageVerChanges-26-2-MAR} bug-fixes table from xplat
at commit 06b6851 (this section existed in xplat before our migration
window, but was missing from docs-template).
Per migration guidance, the de-linking edits in cf7060d8 (DataGrid /
Row Paging / Filter Row / Load-Save Layout / GroupBy Area / Cell Merging
/ Data Grid in the imports table) are NOT ported - those linked pages
still exist in docs-template.
The > [!Note] reformatting fix from eec7614f is also a no-op for this
file because docs-template already renders these admonitions as
<DocsAside type="note"> JSX components.
Ported from igniteui-xplat-docs commits aa041d69 (#1940), 5f917652
(#1946), eec7614f, plus partial cf7060d8 (#1982).
Co-authored-by: Deyan Kamburov <dkamburov@users.noreply.github.com>
Co-authored-by: Stamen Stoychev <sstoychev@infragistics.com>
Co-authored-by: Stamen Stoychev <SStoychev@infragistics.com>
The xplat diff for this file is a single typo fix in a Bug Fixes row
(overriden -> overridden, row 38668 IgxDataTooltipLayer). That row
lives in xplat's {PackageVerLatest} Bug Fixes table, which did NOT
exist in docs-template - docs-template's {PackageVerLatest} held the
26-1-JAN GA content (Charts enhancements, Angular 21 support).
Apply the same rename+backfill approach used for the React changelog:
- Backfill the {PackageVerLatest} Bug Fixes table from xplat at commit
06b6851 (with the typo already corrected to "overridden").
- Demote the prior docs-template {PackageVerLatest} content to
{PackageVerChanges-26-1-JAN} so the version sequence matches xplat.
Ported from igniteui-xplat-docs commit 4655d9c2 (fix typo), backfill
sourced from xplat reference commit 06b6851.
Co-authored-by: IGvaleries <vsuszynski@infragistics.com>
The xplat source for this file was effectively rewritten end-to-end across PRs #1963, #1975, and a follow-up docs sync. Port the new content into the .mdx, preserving the docs-template conventions: - New frontmatter (title/description/keywords/license/last_updated). - New intro framing the CLI as a standalone scaffold + MCP server tool. - Install section now covers npm and yarn, plus an `ig version` check. - Create a New Project split into "guided wizard" and "non-interactive" modes; new --template flag and per-framework template tables. - New arguments reference table for `ig new`. - Add a Component Template section reworked; the inline "> NOTE: Your routing file..." converted to <DocsAside type="note">. - Run the Application now uses `ig start`; Vite block clarified. - Brand-new AI Assistant Integration (MCP) section covering `ig mcp`, `npx -y igniteui-cli mcp`, and the `ig ai-config` quick-setup helper. Includes mcp.json snippets for VS Code, Cursor, Claude Desktop, Claude Code, and JetBrains. - Commands table rewritten and expanded with `ig upgrade-packages`, `ig mcp`, and `ig ai-config`. Converted HTML platform comments to <PlatformBlock for="...">, and the markdown admonition to <DocsAside>. Links preserved (.md targets unchanged). Ported from igniteui-xplat-docs commits 52228c2e (#1963), cf575cdf (#1975), and 10704024 (docs follow-up). Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com> Co-authored-by: Ivaylo Barakov <ibarakov@icloud.com> Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com>
…rade sections, shift Blazor headings
React (interactive CLI flow):
- Add a non-interactive 'ig new' command alternative with --template=top-nav.
- Replace the single CLI link with a pair of links: Step-by-Step Guide and CLI Overview.
- Promote "Package Installation" from H5 to H4 to match the surrounding hierarchy.
- Fix typo in the App.tsx comment (was "App.txs").
WebComponents (interactive CLI flow):
- Heading "Install Ignite UI CLI" -> "Using Ignite UI CLI" (the section already
covers more than installation).
- Add the same non-interactive 'ig new' alternative for WebComponents.
- Same dual-link replacement.
New shared sections (React, WebComponents):
- "Upgrade from Trial to Licensed" - documents 'ig upgrade-packages'.
- "AI-Assisted Development" - introduces Agent Skills, the CLI MCP and
Theming MCP servers, and 'ig ai-config'. Cross-links the new
ai/ai-assisted-development-overview.md, ai/cli-mcp.md, and
general-how-to-mcp-e2e.md pages (to be migrated next).
Heading rebalance:
- "{ProductName} Packages Overview" H1 -> H2 in both the WebComponents and
React blocks, so the H1 is only the top-level "Getting Started".
- Blazor section shifted up one level so it has its own H1
(Getting Started With ...), mirroring React/WC, with consistent H2 and
H3 subsections.
Frontmatter updated: refreshed description, dropped _language, cleared
mentionedTypes, added last_updated.
Ported from igniteui-xplat-docs commits 52228c2e (#1963) and cf575cdf (#1975).
Per migration policy: the source's added HTML schema/component-meta
comments (<!-- schema: Article, HowTo -->, etc.) are intentionally
omitted - they were docfx-specific metadata not used in docs-template.
Co-authored-by: Ivaylo Barakov <ibarakov@icloud.com>
Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com>
This page was substantially restructured in xplat-docs across six commits
(PR #1919 restructure, PR #1972 setup instructions, follow-up doc syncs,
and PR #1995 enabling Blazor + GH CLI). Port the new content end-to-end:
- Replace the "Approach 1: persistent IDE agent / Approach 2: download
and load" structure with a unified "Available Skills" + "Skill
Locations" + "Installing Skills" + "Theming MCP Server" layout.
- Add per-platform skill tables for WebComponents, React, Angular, and
Blazor (previously WC-only). Each lists the framework-specific skill
packages and their SKILL.md paths.
- New "Skill Locations" section enumerates the discovery directories
for each AI tool: General (.agents/skills/), GitHub Copilot, Claude,
Cursor, Gemini CLI/Antigravity, Junie (JetBrains), and Windsurf.
- "Installing Skills" now offers four options:
A. ig ai-config (with --assistants and --agents flags and an Angular
Schematics variant: ng generate @igniteui/angular-schematics:ai-config)
B. GitHub CLI: gh skill install/update IgniteUI/<repo> (per platform)
C. gemini skills install (user + workspace scope variants per platform)
D. npx skills add IgniteUI/{PackageCommon}
- Per-platform copy commands (cp / robocopy) for node_modules-shipped
skills, gated by PlatformBlock.
- Theming MCP Server section now points to the framework-specific
customize-theme SKILL.md path via PlatformBlock.
- Additional Resources cross-links the new ai-assisted-development-overview
and cli-mcp pages; Angular gets external infragistics.com links.
Converted source HTML platform comments to <PlatformBlock> and the
> [!NOTE] admonitions to <DocsAside type="note">. Schema HTML comments
omitted (docfx-only metadata, not used in docs-template). All GitHub
URLs use the {GithubLink} placeholder so they resolve per platform at
build time.
Ported from igniteui-xplat-docs commits a24b6ed2 (#1919), f1b848d4,
cde675a7, 8ac36c8c (#1972), 729347d1, and bd21bcf7 (#1995).
Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com>
Co-authored-by: Marina Stoyanova <Marina-L-Stoyanova@users.noreply.github.com>
Co-authored-by: Zdravko Kolev <zkolev@infragistics.com>
Co-authored-by: Konstantin Dinev <kdinev@infragistics.com>
Co-authored-by: georgianastasov <ggeorgianastasov@gmail.com>
… cross-link new pages Significant additions and refinements across six xplat commits: - Tighten the description and remove the redundant lead-paragraph flourish so it matches the new MCP-server framing. - Overview: collapse three paragraphs into two, then add a paragraph positioning Theming MCP as complementary to CLI MCP (with a React/WebComponents-gated link to the new end-to-end walkthrough). - New Angular-only "How version resolution works" subsection explaining npx detection of the locally-installed igniteui-theming and the behavior when no project is present. - "Other MCP Clients" reformatted from a Command/Arguments list to a single launch-command code block. - Heading rename: Customizing -> Customize AI Behavior with Project Rules (matches imperative style of nearby headings). - New Angular-only DocsAside after the compound-components note pointing to the `licensed` parameter for @infragistics/igniteui-angular consumers. - Section heading "Example Scenarios" -> "Common Workflows". - New Project Theme: Angular gets its own Sass example using @use 'igniteui-angular/theming' / core() / theme(...) mixins. - Brand-Exact Color Shades: inline Angular-only link to the Sass palettes reference on infragistics.com. - Troubleshooting "Platform not detected": use {PackageCommon} placeholder instead of the hard-coded `igniteui-react` example. - New Angular-only troubleshooting block "Generated Sass does not compile" with the `ng add igniteui-angular` remedy. - Additional Resources expanded: cross-links to the new general-how-to-mcp-e2e.md (React/WC), ai-assisted-development-overview.md, cli-mcp.md, and maker-framework.md pages. HTML platform comments converted to <PlatformBlock>. Schema HTML comment omitted (docfx-only). Em-dash -> hyphen stylistic conversions in the source diff are intentionally NOT ported here - they would touch a lot of unrelated text and the visual rendering is unchanged. Ported from igniteui-xplat-docs commits 331d90d3, bdbd1621, cde675a7, 7bc76c30 (#1971), 10704024, and bd21bcf7 (#1995). Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com> Co-authored-by: Stamen Stoychev <SStoychev@infragistics.com> Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com> Co-authored-by: Konstantin Dinev <kdinev@infragistics.com> Co-authored-by: georgianastasov <ggeorgianastasov@gmail.com>
…e AI toolchain New file - this is the top-level entry point for Ignite UI's AI tooling, introduced in xplat across multiple commits during April-May 2026. Covers all three independently usable layers: - Agent Skills (developer-owned instruction packages) - CLI MCP server (igniteui-cli) for project scaffolding + docs/API queries - Theming MCP server (igniteui-theming) for design tokens, palettes, contrast - MAKER MCP server (@igniteui/maker-mcp) - multi-agent orchestration Highlights: - "Configure the AI Toolchain" section centres on `npx igniteui-cli ai-config` with a DocsAside warning about the unpinned-version pitfall. - "What to Expect" documents the two terminal outputs (with/without Ignite UI installed in the project). - "Start the Servers" enumerates the manual start step in each supported AI client (VS Code, Cursor, Claude Code, JetBrains AI Assistant, Claude Desktop). - "Install Ignite UI and Add Skills Later" - per-framework install commands via PlatformBlock; Blazor gets a callout that ai-config is not yet wired and points at `gh skill install`. - "AI Toolchain at a Glance" comparison table. - Supported AI Clients table with per-client config file locations. - Step 1/2/3 setup walkthrough with VS Code and generic mcpServers JSON snippets. Conversions performed: - HTML platform comments -> <PlatformBlock>. - > [!NOTE] and > [!IMPORTANT] admonitions -> <DocsAside type="note"> and <DocsAside type="caution" title="Important">. - _description/_keywords/_license -> docs-template's quoted-string keys. - _language and namespace frontmatter fields dropped (docfx-only). - Schema HTML comment dropped (docfx-only). - Cross-links updated from .md to keep the existing docs-template convention (links to skills.md, cli-mcp.md, theming-mcp.md remain). Ported from igniteui-xplat-docs commits fd76a947, bdbd1621, 63648259, cde675a7, 7bc76c30 (#1971), 9381b41e (#1984), f365af61 (#1988), and bd21bcf7 (#1995). Co-authored-by: georgianastasov <ggeorgianastasov@gmail.com> Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com> Co-authored-by: Konstantin Dinev <kdinev@infragistics.com> Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com>
New file - documents the Ignite UI CLI MCP server that gives AI assistants
direct access to Ignite UI CLI scaffolding, component generation, project
modification, and documentation-aware workflows via the Model Context Protocol.
Content covers:
- Overview positioning CLI MCP next to Theming MCP (both connect to the
same AI client session).
- Example prompts ("Create a new project...", "Add a grid page...", etc.).
- Prerequisites: Node 18+, MCP-capable client, internet access, starting
point options (empty folder / CLI-scaffolded / existing project).
- "Choose a setup path" section formalising the three flows: CLI-first
(recommended), empty folder, existing project. Each path includes the
exact CLI commands and Angular Schematics equivalents.
- Per-platform 'ig new' command variants with Angular/React/WebComponents
template flags, plus matching `npx --package igniteui-cli igniteui new`
forms.
- Per-client setup guides with full mcp.json snippets: VS Code (servers),
Cursor (.cursor/mcp.json), Claude Desktop (per-OS path), Claude Code
(.mcp.json + `claude mcp add ...`), JetBrains AI Assistant, generic
STDIO command, and GitHub Copilot cloud agent with the {type, command,
args, tools} repo-level format.
- Available Tools table (list_components, get_doc, search_docs,
get_project_setup_guide, search_api, get_api_reference).
- Common Workflows table mapping scenarios to setup paths.
- Troubleshooting section covering npx/ig not recognized, MCP tools
missing after save, server start failures, wrong-folder context,
empty-folder pitfalls, and rejected GitHub configurations.
Conversions performed:
- HTML platform comments -> <PlatformBlock for="...">.
- > [!NOTE] admonitions -> <DocsAside type="note">.
- _description/_keywords/_license -> docs-template's quoted-string keys.
- _language and namespace frontmatter dropped (docfx-only).
- _canonicalLink retained (docs-template convention).
- Schema HTML comment dropped (docfx-only).
Ported from igniteui-xplat-docs commits fd76a947, bdbd1621, 63648259,
cde675a7, plus follow-on tweaks in 28a8aca8/19f17971/f9658faa/5476e2f5/
4eb094ae (all 'Update doc/en/components/ai/cli-mcp.md') and 262f796e
(docs build fix).
Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com>
Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com>
Co-authored-by: georgianastasov <ggeorgianastasov@gmail.com>
…page New file introducing the MAKER Framework MCP server (@igniteui/maker-mcp), a multi-agent AI orchestration server from Infragistics. Framework-agnostic - not specific to Angular/React/WC/Blazor and does not modify source files on its own. Content covers: - Overview: MAKER decomposes complex tasks into validated step plans using a first-to-ahead-by-K consensus vote across multiple AI agents. Based on Cognizant AI Lab's "Solving a million-step LLM task with zero errors". - How MAKER Works: planning phase (proposer + plan-voter), execution phase (executor + execution-voter), red-flag validation layer with custom IAIRedFlagValidator implementations. - Install: one-time GitHub Packages registry setup (`npm config set @IgniteUI:registry https://npm.pkg.github.com`) plus a PAT with read:packages scope in ~/.npmrc. - Connect to Your AI Client: full mcp.json snippets for VS Code, Claude Desktop, Cursor/Claude Code/JetBrains; STDIO transport across all. - Configure: env-var conventions (double-underscore separator), AI provider keys (OpenAI/Anthropic/Google), per-internal-client model selection for the four pipelines (Planning, PlanVoting, Execution, ExecutionVoting), external MCP server registration via indexed env vars (Executor__McpServers__0__*), and batchSize/k tuning guidance. - Available Tools: plan, execute, plan_and_execute. - Common Workflows: one-shot, inspect-before-execute, high-confidence critical (k=15), low-cost exploratory (k=3). - Supported Platforms: win-x64, osx-x64, osx-arm64, linux-x64; ARM Linux not yet packaged. MAKER_MCP_CACHE override documented. Conversions performed: - Frontmatter normalized to docs-template style (quoted keys, no _language/namespace). - HTML schema/cspell comments dropped (docfx-only). - No <PlatformBlock> needed - this file is platform-agnostic by design. - No DocsAside needed - source uses no [!NOTE]/[!IMPORTANT] admonitions. - last_updated retained but timestamp updated to reflect docs-template port date is not necessary; left as the source originally provided no trailing field, so it is omitted here. Ported from igniteui-xplat-docs commits 7bc76c30 (#1971, add-maker-to-ai-docs) and bd21bcf7 (#1995, Blazor + GH CLI follow-on). Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com> Co-authored-by: Konstantin Dinev <kdinev@infragistics.com>
… walkthrough
New file. The companion piece to ai/cli-mcp.md and ai/theming-mcp.md: a
single linear walkthrough that takes the reader from "empty folder" to a
themed, working Ignite UI app, using only chat prompts after step 2.
Step-by-step layout:
1. Start with Ignite UI CLI (global install or npx; guided or direct
mode; per-platform 'ig new' for React/WebComponents).
2. Connect CLI MCP and Theming MCP (full mcp.json snippets for VS Code's
'servers:' shape and the generic 'mcpServers:' shape for Cursor /
Claude Desktop / Claude Code / JetBrains).
3. Let the Assistant Review the Project.
4. Add a Real Feature Through Chat (Orders grid example with sample data,
filtering/sorting/paging follow-up).
5. Ask Documentation Questions in the Same Session.
6. Apply a Custom Theme (Theming MCP prompts).
7. Continue Iterating (alternate project + theming in one conversation).
Plus a "Topic Takeaways" closer and Related Topics cross-links.
Includes a "How CLI MCP and Theming MCP Divide Responsibilities" table at
the top that pins down which server owns which workflow.
Conversions:
- HTML platform comments -> <PlatformBlock> (React, WebComponents).
- _description / _keywords / _license -> docs-template's bare/quoted keys.
- _language and namespace frontmatter dropped (docfx-only).
- _canonicalLink retained (docs-template convention).
- No DocsAside needed; source has no markdown admonitions.
Fixed an odd source artifact: "Add or update {}components" -> "Add or
update {Platform} components" (the source token expansion was missing).
Ported from igniteui-xplat-docs commits 68da8b55, 63648259, 7a8854aa,
13929aa4, and a5aa9c75 (Simplify npx command usage).
Co-authored-by: georgianastasov <ggeorgianastasov@gmail.com>
…CLI interactive wizard
New file. Cross-linked from general-cli-overview, general-getting-started,
and ai/cli-mcp. Walks through the Ignite UI CLI's interactive 'ig' / 'ig new'
wizard step by step:
- Create a New Project
- Enter a project name
- Select a framework (React or WebComponents, gated by PlatformBlock)
- Select a project type (Ignite UI for React TS / Web Components TS)
- Select a project template (per-platform tables: Empty/Base/Top
Navigation for React; Empty/Base/Side Navigation for WebComponents)
- Select a theme (default pre-compiled CSS vs custom Sass palette)
- Complete or continue
- Add View ('ig add' interactive; direct 'ig add [template] [name]' form
with grid MyGrid example)
- Run the Application ('ig start')
Notes the limitation that step-by-step mode is interactive-only (no
scripted use) and points at Inquirer.js terminal-compat docs.
Conversions:
- The entire body is wrapped in <PlatformBlock for="React, WebComponents">
(matches the source which gates the whole file under those platforms).
- Inner per-platform variants for framework/type/template tables use
nested <PlatformBlock>.
- > [!NOTE] -> <DocsAside type="note">.
- Frontmatter normalized; docfx schema comment dropped.
Ported from igniteui-xplat-docs commit 52228c2e (#1963, feat: update cli
overview/getting started topics) and follow-up cf575cdf (#1975).
Co-authored-by: Ivaylo Barakov <ibarakov@icloud.com>
Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com>
…ts and React
New file. The Splitter was introduced in igniteui-webcomponents@7.1.0 (also
documented in the changelog migration earlier in this branch). It pairs a
resizable two-pane layout with collapse/expand controls, keyboard support,
and nested-splitter composition.
Sections covered:
- Overview + Example (Sample at /layouts/splitter/base, 520px).
- Getting Started: install instructions and registration (defineComponents
for WebComponents; npm install igniteui-react + IgrSplitter + CSS import
for React).
- Using {Platform} Splitter: 'start'/'end' slots with platform-gated HTML
and JSX examples.
- Orientation (horizontal default vs vertical).
- Pane Size and Constraints: StartSize/EndSize/min/max with examples.
- Collapsing and Resizing: DisableResize / DisableCollapse /
HideDragHandle / HideCollapseButtons; programmatic toggle('start')
with refs.
- Nested Splitters (second Sample at /layouts/splitter/nested).
- Events: WC uses igcResizeStart/igcResizing/igcResizeEnd; React uses
ResizeStart/Resizing/ResizeEnd. Event detail shape documented per
platform.
- Keyboard Navigation table (Arrow keys, Home/End, Ctrl + Arrow).
- Styling: CSS parts table + CSS custom property list + sample at
/layouts/splitter/styling.
- API References via <ApiRef pkg="core" types={["Splitter",
"SplitterResizeEventArgs"]} />.
Conversions performed to match docs-template conventions:
- HTML platform comments (<!-- WebComponents --> / <!-- React -->) ->
<PlatformBlock for="...">.
- Sample backtick syntax (`sample="..."`) -> <Sample src="..." height={N}
alt="..." />.
- Standalone API type backticks in API References -> <ApiRef> JSX.
- Inline `Splitter` references in body text -> <ApiLink type="Splitter" />
for consistency with neighbouring topics (e.g. tabs.mdx).
- mentionedTypes carried over from source frontmatter so the API search
index picks up Splitter and SplitterResizeEventArgs.
Ported from igniteui-xplat-docs commits e42211ea (docs(splitter): create
splitter topic) and 94a47688 (feat(splitter): enable topic for React;
add API maps for WC and React).
Co-authored-by: Bozhidara Pachilova <bozhidara.pp@gmail.com>
Co-authored-by: didimmova <d.dimova11@gmail.com>
…elog content
Mirror of the English Blazor changelog migration applied to the Japanese
translation. The xplat JP file received the same structural change as EN:
- New {PackageVerLatest} contains only the March SR bug fixes (2 rows:
3229 IgbGrid trial-watermark, 2754 IgbTabs / IgbSwitch state issue).
- New {PackageVerChanges-25-2-MAR} contains the 25.2 GA content
(IgbQueryBuilder intro, IgbGrid/Tree/Hierarchical/Pivot scroll perf,
PDF export, breaking change on data mutations, IgbThemeProvider, Badge,
Checkbox, Combo, Mask input, accessibility/styling enhancements,
and a large bug-fixes table).
- The previous JP {PackageVerLatest} content (Charts enhancements +
4-row IgbDataChart bug table) is demoted under a new
{PackageVerChanges-25-2-DEC} heading.
Translations preserved verbatim from xplat JP source. The "Fix typos and
improve clarity in changelog" tweaks from 3f7e236c are also captured.
Ported from igniteui-xplat-docs commits 51ac4e7e (docs(jp): sync JP
changelog files with EN changes) and 3f7e236c (typo fixes).
Co-authored-by: TomoyaWashio <148823993+TomoyaWashio@users.noreply.github.com>
…log content
Mirror of the English React changelog migration applied to the Japanese
translation:
- New {PackageVerLatest} contains the 26-2-MAR SR bug fixes (5 rows).
- New {PackageVerChanges-26-2-FEB} contains the full 26.2 GA content
({PackageCommon} new features incl. Copilot Skills + Chat, breaking
changes in Themes/Chat/Tooltip/Library, IgrGrid scroll perf, i18n
rewrite, PDF export, Popover API).
- Prior {PackageVerLatest} content (Charts enhancements + IgrDataChart
bug rows) is demoted under {PackageVerChanges-25-2-FEB}.
Translations preserved verbatim from xplat JP source.
Ported from igniteui-xplat-docs commits 51ac4e7e (jp sync) and 3f7e236c
(typo fix).
Co-authored-by: TomoyaWashio <148823993+TomoyaWashio@users.noreply.github.com>
… content Mirror of the JP changelog sync (commit 51ac4e7e) for the WC variant. Adds the new SR bug fixes table to PackageVerLatest and creates a new PackageVerChanges-26-1-FEB section with the full 26.1 GA content (charts bug fixes; AI skills; Themes/Chat/Tooltip/Library breaking changes; IgcGrid perf, i18n, PDF export, Popover API). The previous PackageVerLatest body is demoted to PackageVerChanges-25-2-DEC. Ported from igniteui-xplat-docs commit 51ac4e7e (docs(jp): sync JP changelog files with EN changes). Co-authored-by: Deyan Kamburov <dkamburov@users.noreply.github.com>
…tion, demote 26-1-JAN
Mirror of the English Angular changelog migration. New {PackageVerLatest}
contains a 7-row Bug Fixes table (IgxDataChart, IgxDataPieChart,
IgxDataTooltipLayer, Excel, etc.). Prior PackageVerLatest body
(Charts enhancements with DataPieChart additions) is demoted under a
new {PackageVerChanges-26-1-JAN} heading.
Ported from igniteui-xplat-docs commit 51ac4e7e (docs(jp): sync JP
changelog files with EN changes).
Co-authored-by: Deyan Kamburov <dkamburov@users.noreply.github.com>
…kages Mirror of the English dock-manager migration applied to JP. Same set of changes: - Simplified the intro paragraph; clarified language detection reads the root <html> lang attribute. - New WebComponents snippet showing the igniteui-i18n-resources peer dependency + registerI18n() flow. - Reframed addResourceStrings(...) as the escape hatch for languages outside the bundled set. - Softened the ResourceStrings property paragraph. Also fixed pre-existing structural issues in the JP file: - The previous "ローカライズ" heading was misplaced (above the ApiRef instead of above the localization content) and the localization content under "テーマ" was still in English. Restructured to: ## テーマ -> theme paragraph ## ローカライズ -> the new JP localization content ## API リファレンス -> ApiRef Ported from igniteui-xplat-docs commits 962756c1, 57ba6c86, and 7a507bf9 (dock-manager localization JP sync, 2026-03-26..03-31). Co-authored-by: Galina Edinakova <gedinakova@infragistics.com>
Japanese translation of the new Splitter component topic introduced in
igniteui-webcomponents@7.1.0. The JP source covers only the WebComponents
variant (the React/Angular variants were added on the EN side after the
JP file was first translated).
Sections mirror EN: Overview, Example, Usage (install + register +
slots), Orientation, Pane Size and Constraints, Collapsing and
Resizing (with programmatic toggle), Nested Splitters, Events,
Keyboard Navigation, Styling (CSS parts + custom properties), API
References, Additional Resources.
Conversions applied to match docs-template conventions:
- `sample="..."` backtick syntax -> <Sample src="..." height={N} alt="..." />.
- `Splitter` backtick references in body -> <ApiLink type="Splitter" />.
- "## API リファレンス" body backtick list -> <ApiRef pkg="core"
types={["Splitter"]} />.
- Frontmatter normalized to docs-template style (quoted keys, _language
removed).
Ported from igniteui-xplat-docs commit 95b8a931
([jp-sync] docs(jp/splitter): translate splitter topic to Japanese, #1943).
Co-authored-by: Stamen Stoychev <sstoychev@infragistics.com>
Co-authored-by: MonikaKirkova <monika_kirkova@abv.bg>
Co-authored-by: MonikaKirkova <47036441+MonikaKirkova@users.noreply.github.com>
Co-authored-by: Vasya Kacheshmarova <vasq1989@gmail.com>
Co-authored-by: Bozhidara Pachilova <35433937+ddaribo@users.noreply.github.com>
Japanese translation of the cross-agent Skills installation guide. The
JP source is one sync cycle behind EN: it covers WebComponents, React,
and Angular variants but not yet Blazor, and the install options are
A) installed npm package -> B) gemini skills CLI -> C) npx skills CLI
(the EN file has additional A) ig ai-config and B) GitHub CLI options
that were added in a later commit).
Mirror of EN sections: Available Skills (per-platform tables) -> Skill
Locations (Copilot, Claude, Cursor, Gemini CLI/Antigravity, Junie,
Windsurf) -> Installing Skills (3 options) -> Theming MCP Server ->
Additional Resources.
Conversions performed:
- HTML platform comments -> <PlatformBlock>.
- > [!NOTE] admonitions -> <DocsAside type="note">.
- _description/_keywords/_license -> docs-template's quoted-string keys.
- _language frontmatter dropped (docfx-only).
- All GitHub URLs use {GithubLink} placeholders for per-platform
resolution at build time.
Ported from igniteui-xplat-docs commit aa02fd20 ([jp-sync] Sync Japanese
AI MCP documentation with English changes from PR #1969, 2026-05-01).
Co-authored-by: jsakamotoIGJP <jsakamoto@infragistics.com>
Co-authored-by: ChronosSF <2188411+ChronosSF@users.noreply.github.com>
Japanese translation of the Theming MCP setup guide. Covers connection
to VS Code, Cursor, Claude Desktop, Claude Code, JetBrains, and generic
MCP clients; the full Available Tools reference; example prompts and
Common Workflows scenarios; troubleshooting; plus Angular-specific
guidance on version resolution and the licensed @infragistics/igniteui-
angular package.
Conversions performed:
- HTML platform comments -> <PlatformBlock for="...">.
- > [!NOTE] -> <DocsAside type="note">.
- Frontmatter normalized; _language and namespace dropped.
- Inline Angular link wrapper that lost its closing tag in the source
("[Sass を使用したテーマ設定](<a href=...>)") restored to a clean
markdown link.
Ported from igniteui-xplat-docs commit aa02fd20 ([jp-sync] Sync
Japanese AI MCP documentation with English changes from PR #1969).
Co-authored-by: Stamen Stoychev <SStoychev@infragistics.com>
Co-authored-by: Georgi Anastasov <48180072+georgianastasov@users.noreply.github.com>
Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com>
Co-authored-by: Zdravko Kolev <zkolev@infragistics.com>
Japanese translation of the AI-Assisted Development overview hub page. The JP source is one sync cycle behind EN: it documents the three-layer toolchain (Agent Skills + CLI MCP + Theming MCP) without the MAKER MCP layer, the ai-config quick-setup helper, or the "Configure the AI Toolchain" / "Start the Servers" / Install-and-add- later sections that landed later on the EN side. Sections covered: intro -> AI Toolchain at a Glance (table) -> Agent Skills -> CLI MCP Server -> Theming MCP Server -> Supported AI Clients (table) -> Setup walkthrough (Step 1 Load Skills, Step 2 Connect CLI MCP, Step 3 Connect Theming MCP optional) -> Additional Resources. Conversions performed: - HTML platform comments -> <PlatformBlock>. - Frontmatter normalized; _language and namespace dropped. - _canonicalLink retained. Ported from igniteui-xplat-docs commit aa02fd20 ([jp-sync] Sync Japanese AI MCP documentation with English changes from PR #1969). Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com> Co-authored-by: Georgi Anastasov <48180072+georgianastasov@users.noreply.github.com> Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com>
Japanese translation of the CLI MCP setup guide. Mirrors the EN structure: Overview -> Example Prompts -> Prerequisites -> Configure (canonical launch + setup-path picker for CLI-first/empty-folder/existing-project, plus per-platform 'ig new' command variants) -> per-client setup blocks (VS Code, Cursor, Claude Desktop, Claude Code, JetBrains, generic STDIO, GitHub Copilot cloud agent) -> Available Tools (six MCP tools with descriptions) -> Common Workflows -> Troubleshooting -> Additional Resources. Conversions performed: - HTML platform comments -> <PlatformBlock>. - > [!NOTE] -> <DocsAside type="note">. - Frontmatter normalized; _language and namespace dropped. - _canonicalLink retained. Ported from igniteui-xplat-docs commit aa02fd20 ([jp-sync] Sync Japanese AI MCP documentation with English changes from PR #1969). Co-authored-by: Georgi Anastasov <48180072+georgianastasov@users.noreply.github.com> Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com> Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com>
…MCP walkthrough
Japanese translation of the linear 7-step walkthrough from "empty folder"
to a themed, working {ProductName} app, using only chat prompts after
step 2. Mirrors the EN structure:
- CLI MCP and Theming MCP Responsibilities (table)
- What You Need
- Step 1: Start with Ignite UI CLI (global install / npx / guided / direct;
per-platform 'ig new' for React and WebComponents)
- Step 2: Connect CLI MCP and Theming MCP (mcp.json for VS Code 'servers'
shape + generic 'mcpServers' shape)
- Step 3: Let the Assistant Review the Project
- Step 4: Add a Real Feature Through Chat (Orders grid example)
- Step 5: Ask Documentation Questions in the Same Session
- Step 6: Apply a Custom Theme
- Step 7: Continue Iterating
- Topic Takeaways
- Related Topics
Conversions performed:
- HTML platform comments -> <PlatformBlock>.
- Frontmatter normalized; _language and namespace dropped.
- _canonicalLink retained.
Ported from igniteui-xplat-docs commit aa02fd20 ([jp-sync] Sync
Japanese AI MCP documentation with English changes from PR #1969).
Co-authored-by: Georgi Anastasov <48180072+georgianastasov@users.noreply.github.com>
Co-authored-by: Radoslav Mirchev <52001020+radomirchev@users.noreply.github.com>
Co-authored-by: RadoMirchev <radoslav.p.mirchev@gmail.com>
viktorkombov
added
🛠️ status: in-development
Update the Tabs snippets to the current API (EN + JP): - Simple declaration: tabs now use the `Label` property (or `label` slot) instead of the old WebComponents `<div slot="label">` for every tab. The Blazor snippet drops the obsolete Panel / IgbTabPanel model in favour of inline `<IgbTab Label="...">` with child content. The third tab keeps the `label` slot form to show both styles. - Disabled Tab snippets updated to the self-closing `label="..." disabled` form across WebComponents/Blazor/React. - New paragraph explaining tab text can be set via the `Label` property or the `label` slot, with remaining default-slot children rendered as the tab content. - Prefix / Suffix paragraph reworded to reference the `label` slot rather than a generic "default slot". Ported from igniteui-xplat-docs commit 95c26d8c. Co-authored-by: damyanpetev <damyanpetev@users.noreply.github.com>
…I ref EN + JP themes overview: - Add a Blazor-specific bundled-themes table (light + dark variants for Bootstrap, Material, Fluent, Indigo) pointing at the _content/IgniteUI.Blazor/themes/... stylesheet paths. - Wrap the "API References" section (the ConfigureTheme entry) in a React/WebComponents PlatformBlock - the ConfigureTheme runtime API is not available for Blazor, so the reference is hidden there. Converted the source HTML platform comments (<!-- Blazor -->, <!-- React, WebComponents -->) to <PlatformBlock> wrappers. Ported from igniteui-xplat-docs commit ab90e347. Co-authored-by: damyanpetev <damyanpetev@users.noreply.github.com>
viktorkombov
added
💥 status: in-test
viktorkombov
added
🛠️ status: in-development
…t flow
Port the AI-docs fixes from igniteui-xplat-docs PR #2010 across all four
AI pages.
ai-assisted-development-overview:
- Correct the CLI MCP server package name: @igniteui/mcp-server -> igniteui-cli.
- description uses npx igniteui-cli@latest ai-config.
- New Blazor note: ai-config detects the project via .csproj/.sln; the
IgniteUI.Blazor NuGet package need not be installed.
- "What to Expect" terminal output reworked into DocsAside notes,
platform-gated (Angular/React/WC mention npm install; Blazor omits it).
- Blazor "Add Skills Later" now uses npx igniteui-cli@latest ai-config
instead of gh skill install.
- CLI MCP Server section: launch command npx -y igniteui-cli mcp;
ai-config noted as the way to write client config.
- Step 1 split: Angular/React/WC pull skills from node_modules; Blazor
has them copied automatically by ai-config.
- Step 3: added the generic mcpServers JSON variant for non-VS Code clients.
cli-mcp:
- Replace "writes .vscode/mcp.json for VS Code" wording throughout with
the new "prompts you to choose which AI clients and agents to configure"
flow (Overview, setup-path picker, Common Workflows, Troubleshooting).
theming-mcp:
- detect_platform description notes Blazor projects have no package.json
and return generic.
- Prerequisites/Setup platform-gated: Angular/React/WC reference
igniteui-theming + package.json; Blazor references the IgniteUI.Blazor
NuGet package and notes npx fetches the MCP server directly.
- New Blazor block under "New Project Theme" about CSS custom property
output applied in wwwroot/css/app.css.
- "Platform not detected" troubleshooting platform-gated.
skills:
- New Blazor note after the ai-config flags table.
- Restructure Installing Skills: the node_modules manual-copy
instructions move directly under Option A inside an
Angular/React/WebComponents PlatformBlock (Blazor cp/robocopy variants
dropped - Blazor uses ai-config / gh skill); Option B (GitHub CLI) now
follows the manual-copy block.
- Option D npx skills command platform-gated (IgniteUI/{PackageCommon}
vs IgniteUI/igniteui-blazor).
HTML platform comments converted to <PlatformBlock>; markdown admonitions
to <DocsAside>. EN only - no JP sync for these exists in xplat yet.
Ported from igniteui-xplat-docs commits 066b9636, 1394241b, 9783cf16,
and 873fd1cb (PR #2010, ganastasov/ai-docs-fixes).
Co-authored-by: georgianastasov <ggeorgianastasov@gmail.com>
…roject creation Port igniteui-xplat-docs PR #2011 (mstoyanova/updating-ai-config-section). general-cli-overview: - Add `--assistants` and `--agents` rows to the `ig new` arguments table. - New "AI Configuration During Project Creation" section (React/WebComponents PlatformBlock) showing the interactive assistant/agent selection prompts that `ig new` displays after scaffolding, plus how to skip them (`--assistants none --agents none`) or pre-answer them non-interactively. - "Quick Setup with ig ai-config" rewritten: new intro, a version-pin DocsAside warning, and Interactive Mode / Non-Interactive Mode / Start the Servers subsections (with the per-client prompt listings and the --assistants/--agents flag table). - Commands table: `ig ai-config` row linked to the CLI wiki and reworded. - Code-block syntax aligned with the source: npm install -> bash; npm run dev / npx -y igniteui-cli mcp / ig mcp -> cmd. general-step-by-step-guide-using-cli: - New "Configure AI Tooling" step between "Select a theme" and "Complete or continue", showing the two wizard prompts and the non-interactive `--assistants`/`--agents` escape hatch, cross-linked to the CLI Overview anchor. HTML platform comments converted to <PlatformBlock>; admonition to <DocsAside>. EN only - no JP sync for PR #2011 exists in xplat yet. Ported from igniteui-xplat-docs commits 8e09d7ce, f181da5a, 9e9bab0d, 286eb84f, 79be0eca, bdcac9a7, 44fd8b8c, and ae855170 (PR #2011). Co-authored-by: Marina Stoyanova <Marina-L-Stoyanova@users.noreply.github.com> Co-authored-by: Konstantin Dinev <kdinev@infragistics.com>
…I References The EN splitter API References ApiRef listed SplitterResizeEventArgs alongside Splitter, but: - the igniteui-xplat-docs source splitter.md API References lists only `Splitter`, - the JP splitter.mdx already lists only `Splitter`, - the real type is named SplitterResizeEventArgsDetail (per xplat's apiMap), and being passed with the default kind="class" it would have generated an incorrect /classes/IgcSplitterResizeEventArgs URL. Align EN with the source and the JP file - API References now lists just Splitter.
…er type
Port three GitHub Copilot coding-agent PRs that landed together:
- PR #1999 (cb9ed33a) - RangeBarSeries
- PR #2003 (06fe0add) - MarkerSize property
- PR #2001 (b5270cd5) - Checkmark marker type
RangeBarSeries (en):
- chart-api.mdx: add RangeBarSeries to the Category Series table.
- chart-axis-types.mdx: add RangeBarSeries to CategoryYAxis and
NumericXAxis compatibility lists; mention it in the NumericXAxis
paragraph alongside BarSeries/StackedBarSeries.
- chart-performance.mdx: add Range Bar Chart entry to the Column Charts
performance row.
- types/bar-chart.mdx: add RangeBarSeries to frontmatter mentionedTypes,
insert a new "Range Bar Chart" section with the standard Range
prose + Sample at /charts/data-chart/range-bar-chart, and add
RangeBarSeries to the API References ApiLink list.
MarkerSize (en + jp chart-markers):
- New "Chart Marker Size" section with Blazor/React/WebComponents code
samples showing MarkerSize=30 on a ScatterLineSeries, a NaN-reset
example, the scatter-marker-options Sample, and a DocsAside note that
BubbleSeries radius is not affected by MarkerSize.
- Expanded mentionedTypes/keywords to include MarkerSize and the new
series base classes.
Checkmark marker type (en + jp chart-markers, en + jp changelogs):
- New "Chart Checkmark Marker Type" section explaining the new
MarkerType.Checkmark enum value, MarkerAutomaticBehavior.Checkmark,
and the SeriesViewer.CheckmarkMarkerTemplate customization hook.
- Changelogs: new Enhancements/Charts entries under {PackageVerLatest}
for all four platforms (en blazor / en react / en wc / en angular /
the four JP variants). EN changelogs additionally got the matching
RangeBarSeries enhancement entry. JP changelogs only got the Checkmark
entry - no JP sync for RangeBarSeries this round.
Conversions: HTML <br> -> <br /> in chart-api row; sample-backtick syntax
-> <Sample src="..." height={N} alt="..." />; > [!NOTE] -> <DocsAside
type="note"> (chart-markers); plain backticks kept for series/property
references in the new sections (matches existing docs-template style).
Ported from igniteui-xplat-docs PRs #1999, #2001, #2003.
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
FinancialChart does not expose a CategoryChart.ChartType property - it has a top-level ChartType. Rename the references in the topic body (the IgrApiLink label and the ZoomSliderType paragraph) and drop the duplicate FinancialChartType entry from the frontmatter mentionedTypes. Ported from igniteui-xplat-docs commit 602bed3b (fix(FinancialChart): Fixed wrong api links). Co-authored-by: Galina Edinakova <gedinakova@infragistics.com>
Indent the bullet list and the json code fence in the Claude Desktop section so they nest under their parent ordered-list items (1. and 2.) instead of breaking the list visually. Ported from igniteui-xplat-docs commit 05a06b40 (chore(*): fixing code snippet indentation). Co-authored-by: Konstantin Dinev <kdinev@infragistics.com>
… prop The IgxGridToolbarHiding equivalents on Web Components, React, and Blazor now expose a Prompt property alongside Title to set the filter-input placeholder inside the toolbar hiding dropdown. - Platform-gate the "Title only" prose paragraph to Angular and add a parallel React/Blazor/WebComponents paragraph that mentions both Title and Prompt with ApiLink references. - Add Prompt="Type here to search" (Blazor) / prompt="Type here to search" (WC + React) to every Grid/TreeGrid/HierarchicalGrid toolbar hiding snippet across the file (9 occurrences in total). HTML platform comments in the source were converted to <PlatformBlock>. Ported from igniteui-xplat-docs commit 273dd74f (PR #1636 - docs: include 'prompt' prop in markdown and snippets). Co-authored-by: Ivan Minchev <61944284+IMinchev64@users.noreply.github.com> Co-authored-by: Stamen Stoychev <chronos.stz@gmail.com>
- Replace the quoted "<link>" element reference with a backticked
`<link>` for consistency with the surrounding `<style>` reference.
- Rewrite the CSS sample to match the actual sample at
/interactions/chat/styling: target header, message-container,
message-sent, and message-header parts with the warn/gray-800 palette
instead of the prior primary-100 / border-radius / italic empty-state
example.
- Sample alt text platform-token-ized: "Web Components Chat Styling
Example" -> "{Platform} Chat Styling Example".
Ported from igniteui-xplat-docs commit eab7a367
(PR #1994 - docs(chat): add styling sample).
Co-authored-by: Adrian Petrov <99720888+adrianptrv@users.noreply.github.com>
The Razor code fence for the vertical divider example was using the React/lowercase form <igrDivider Vertical></igrDivider>; correct it to <IgbDivider vertical></IgbDivider> so the Razor snippet matches the actual Blazor API. Ported from igniteui-xplat-docs commit 2ff4a8d1 (PR #1829 - fix: fix code snippet for Divider topic). Co-authored-by: Mariela Tihova <mariela.tihova@gmail.com> Co-authored-by: Stamen Stoychev <chronos.stz@gmail.com>
…achable The earlier migration created four JP .mdx files but deliberately left them out of jp/toc.json (strict mirror of the older xplat JP toc). Users on the JP site had no navigation entry point to reach them. Add the missing entries, mirroring the EN toc structure: - AI section gains "エージェント ワークフロー" (ai/ai-assisted-development-overview.md), before Agent Skills. - AI section gains "CLI MCP" (ai/cli-mcp.md), after Agent Skills. - New React/WebComponents-targeted "操作方法" (How to) section after ライセンス with "CLI MCP と Theming MCP を使ったアプリのビルド" (general-how-to-mcp-e2e.md). Leaves the pre-existing Angular-only "操作方法" section alone. - Layouts section gains "スプリッター" (layouts/splitter.md), between Divider and Tile Manager. The new AI entries use the existing JP convention `exclude: ["Blazor"]`. The Splitter and the new How to section use `["Angular", "Blazor"]` (matching the EN entries and the actual page platform support).
Zneeky
added
❌ status: awaiting-test
The `RangeBarSeries` API class is not yet shipped, so its `<ApiLink>` references in the migrated docs resolve to 404s across Angular, React, Web Components, and Blazor. Strip all visible RangeBarSeries content (headings, prose, lists, samples, frontmatter mentionedTypes, API references, changelog enhancements) and leave a brief MDX comment in each affected file pointing to xplat-docs PR #1999 / cb9ed33a so the content can be restored once the API ships. MarkerSize and the `Checkmark` MarkerType from the same originating xplat commit (082241f) are kept — they only use backticked prose with no <ApiLink> references, so they have no broken-link impact. Affected files: - charts/types/bar-chart.mdx - charts/chart-api.mdx - charts/features/chart-axis-types.mdx - charts/features/chart-performance.mdx - general-changelog-dv.mdx - general-changelog-dv-react.mdx - general-changelog-dv-wc.mdx - general-changelog-dv-blazor.mdx
…ulti-column headers
…b.com/IgniteUI/docs-template into aahmedov/Xplat-docs-updates-migration
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
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.
Changes
AI / MCP toolchain (EN + JP)
ai-assisted-development-overviewhub,cli-mcpsetup guide,maker-framework(MAKER multi-agent orchestration),general-how-to-mcp-e2eend-to-end walkthrough,general-step-by-step-guide-using-cliinteractive-wizard page.ai/skillsfull rewrite for the cross-agent install flow (+ new Generate From Image Design skill);theming-mcpoverview refresh with Angular-specific guidance and cross-links;general/cli-overviewrewrite for new CLI features and MCP;general/getting-startedupdates for React/WC flows with new MCP + Upgrade sections.Layouts
Grids (
_shared)cell-editing— aligned Blazor snippet with WC, unified HierarchicalGrid validation example.conditional-cell-styling— every-other-row highlight + border tweak.excel-style-filtering— aligned Blazor Debut column with sample.row-actions— useIgbGridEditingActionsfor Blazor.Changelogs
PackageVerLatestsection, demoted 26-2-FEB, backfilled 26-2-MAR (EN + JP port of 26.2 GA + 26-2-MAR).Scheduling
date-range-picker— note that single-input mode is now editable.TOC
toc.json.