diff --git a/.github/skills/astro-child-config/SKILL.md b/.github/skills/astro-child-config/SKILL.md
new file mode 100644
index 0000000000..ebe620d820
--- /dev/null
+++ b/.github/skills/astro-child-config/SKILL.md
@@ -0,0 +1,326 @@
+---
+name: astro-child-config
+description: "Reference guide for creating or updating an Astro child site under `docs/{lib}/` in this monorepo. Covers `astro.config.ts` structure, `package.json` scripts (dev/build/preview × en/jp), `IGDOCS_PLATFORMS` registration in `src/platform.ts`, language-aware path selection (`DOCS_LANG` env), `tsconfig.json`, `content.config.ts`, the `createDocsSite()` integration helper, port allocation, base paths, multi-language source folder mapping (e.g. `DOCS_LANG=jp` → `ja/` folder), and per-platform conventions (jQuery vs Angular vs xplat). Use when an agent needs to add a new docs library, add a new language to an existing library, or audit a child config for missing scripts/platform entries."
+user-invocable: true
+---
+
+# AI Agent Guide — Configuring an Astro Child Repo
+
+## Context
+
+This monorepo contains a top-level `docs-template` package and several Astro child sites under `docs/{lib}/`:
+
+| Library | Path | Pattern |
+|---|---|---|
+| jQuery | `docs/jquery/` | DocFX-imported MDX, env-driven lang switching, `DOCS_LANG=jp` → `ja/` folder |
+| Angular | `docs/angular/` | Hand-authored MDX, lang folders: `en`, `jp`, `kr` (literal) |
+| xplat | `docs/xplat/` | Generated MDX; **platform** + **lang** dual-axis (Angular/React/WC/Blazor × en/jp) |
+
+All three share the same shell:
+
+- Use `createDocsSite()` from `docs-template/integration` for site assembly
+- Register their nav identity in `IGDOCS_PLATFORMS` (`src/platform.ts`)
+- Mount their content via `source.docsDir` (env-scoped glob loader)
+- Use `cross-env DOCS_ENV=...` and `DOCS_LANG=...` for build configuration
+
+This skill explains how to set up a new child site or add a new language to an existing one.
+
+---
+
+## When to Use This Skill
+
+| Situation | Use this skill? |
+|---|---|
+| Creating a new `docs/{newlib}/` site | **Yes** |
+| Adding `kr` (or another lang) to an existing site | **Yes** |
+| Site's nav/footer is broken (missing platform entry) | **Yes** |
+| Re-allocating ports because of conflicts | **Yes** |
+| Renaming a published library (production base path) | **Yes** |
+| Editing content of a single MDX page | No — edit the file directly |
+| Configuring sidebar order | No — edit `toc.json` directly |
+| Migrating new DocFX content | See `docfx-to-mdx-migration` skill first |
+
+---
+
+## Required Files for a New Child Site
+
+```
+docs/{newlib}/
+├── astro.config.ts # site config (this skill)
+├── package.json # dev/build/preview scripts (this skill)
+├── tsconfig.json # extends astro/tsconfigs/strict
+├── public/web.config # IIS routing (Infragistics CDN)
+├── src/
+│ ├── content.config.ts # re-exports docs-template/content
+│ ├── env.d.ts # `/// `
+│ └── content/{lang}/
+│ ├── topics/ # MDX content
+│ ├── environment.json # `{environment:Foo}` token values
+│ └── images/ # (optional) image assets
+└── toc.json # sidebar (en) — non-en lives at src/content/toc.json
+```
+
+---
+
+## Step 1 — Register the Library in `src/platform.ts`
+
+`IGDOCS_PLATFORMS` is the source of truth for nav/footer/product-links. Every (library × language) combo needs an entry.
+
+Open [src/platform.ts](src/platform.ts) and add entries. **Each entry needs a unique `devPort`**:
+
+```ts
+export const IGDOCS_PLATFORMS = {
+ // ... existing entries ...
+ NewLib: {
+ lang: 'en', label: 'NewLib', key: 'newlib', devPort: 4336, // unique port
+ base: '/docs-newlib', // production URL path
+ title: 'Ignite UI for NewLib',
+ description: 'Component documentation for Ignite UI for NewLib.',
+ },
+ NewLibJP: { // mandatory if you support jp
+ lang: 'jp', label: 'NewLib', key: 'newlib', devPort: 4346, // +10 from en port (convention)
+ base: '/docs-newlib', // same base — JP domain handles the lang prefix at infra level
+ title: 'Ignite UI for NewLib',
+ description: 'Component documentation for Ignite UI for NewLib.',
+ },
+};
+```
+
+### Port allocation convention
+
+| Range | Purpose |
+|---|---|
+| 4321 | xplat (default Astro port; selects platform via `PLATFORM` env) |
+| 4331–4335 | en sites (Angular 4331, React 4332, WC 4333, Blazor 4334, jQuery 4335) |
+| 4336+ | new libraries (en) |
+| 4341–4345 | jp counterparts (`+10` from en) |
+| 4346+ | new libraries (jp) |
+
+Pick the next free port in the appropriate range.
+
+### `getNavConfig()` switch — also in `src/platform.ts`
+
+If your library needs a custom navbar (most do), find the `getNavConfig()` function and add a `case 'newlib':` arm. Without this entry the navbar/footer will render empty — a common bug that masquerades as "site is broken".
+
+---
+
+## Step 2 — Write `docs/{newlib}/astro.config.ts`
+
+The minimal pattern (mirrors [docs/jquery/astro.config.ts](docs/jquery/astro.config.ts)):
+
+```ts
+// @ts-check
+import mdx from '@astrojs/mdx';
+import path from 'node:path';
+import { createDocsSite, type DocsMode } from 'docs-template/integration';
+import { IGDOCS_PLATFORMS, type NavLang } from 'docs-template/platform';
+
+// ── Build mode and language ──────────────────────────────────────────────────
+const docsEnv = process.env.DOCS_ENV || process.env.NODE_ENV || 'development';
+const docsLang = (process.env.DOCS_LANG || 'en') as NavLang;
+
+if (docsEnv !== 'development' && docsEnv !== 'staging' && docsEnv !== 'production') {
+ throw new Error(`[astro.config] Invalid DOCS_ENV "${docsEnv}". Expected one of: "development", "staging", "production".`);
+}
+const mode: DocsMode = docsEnv;
+
+// ── Site URL ─────────────────────────────────────────────────────────────────
+const PROD_HOST = 'https://www.infragistics.com';
+const STAGING_HOST = 'https://staging.infragistics.com';
+
+const platformKey = docsLang === 'jp' ? 'NewLibJP' : 'NewLib';
+const { base, devPort } = IGDOCS_PLATFORMS[platformKey];
+const site = mode === 'production' ? `${PROD_HOST}${base}`
+ : mode === 'staging' ? `${STAGING_HOST}${base}`
+ : `http://localhost:${devPort}`;
+
+// ── Source paths ─────────────────────────────────────────────────────────────
+// If your jp source folder is named differently (e.g. 'ja' for DocFX-style imports):
+const contentLangDir = docsLang === 'jp' ? 'ja' : docsLang;
+const docsDir = path.resolve(`./src/content/${contentLangDir}/topics`);
+const tocPath = docsLang === 'jp'
+ ? path.resolve('./src/content/toc.json') // non-en convention
+ : path.resolve('./toc.json'); // en convention
+
+export default createDocsSite({
+ site,
+ base: mode !== 'development' ? base : undefined,
+ title: 'Ignite UI for NewLib',
+ description: 'Component and API reference docs for Ignite UI for NewLib.',
+ platform: 'newlib',
+ navLang: docsLang,
+ mode,
+ productLinks: Object.values(IGDOCS_PLATFORMS)
+ .filter(p => p.lang === docsLang)
+ .map(({ label, key, base: b }) => ({
+ label,
+ href: mode === 'production' ? `${PROD_HOST}${b}` : `${STAGING_HOST}${b}`,
+ platform: key,
+ })),
+ source: { tocPath, docsDir },
+ starlight: {},
+ image: { service: { entrypoint: 'astro/assets/services/noop' } },
+ integrations: [mdx()],
+ vite: {
+ resolve: {
+ alias: { '@': path.resolve('./src') },
+ },
+ },
+});
+```
+
+### Variant: hand-authored content (Angular pattern)
+
+If your `jp` folder is literally `jp/` (not `ja/`), drop the `contentLangDir` mapping:
+
+```ts
+const docsDir = path.resolve(`./src/content/${docsLang}`); // jp/ ja/ kr/ — folder name == DOCS_LANG
+```
+
+See [docs/angular/astro.config.ts](docs/angular/astro.config.ts) for the full hand-authored pattern (also runs `generateGridTopics()` as a pre-build step).
+
+### Variant: dual-axis platform × lang (xplat pattern)
+
+If your library generates output for multiple **platforms** (Angular/React/WC/Blazor) AND multiple langs, follow [docs/xplat/astro.config.ts](docs/xplat/astro.config.ts). Key differences:
+
+- Resolves `PLATFORM` from env or `.platform.json`
+- Uses `LANG_CODE` instead of `DOCS_LANG`
+- Mounts content from `./generated/{platform}/{lang}/`
+- Adds a Vite plugin for `{Token}` substitution from `docConfig.json` (must run **before** MDX compile, otherwise `{Token}` is parsed as JSX expression)
+
+---
+
+## Step 3 — Write `docs/{newlib}/package.json`
+
+Match the script matrix from [docs/jquery/package.json](docs/jquery/package.json). For each language, you need `dev:{lang}`, `build:{lang}`, `build-staging:{lang}`, `build-production:{lang}`, `preview:{lang}`:
+
+```json
+{
+ "name": "newlib-docs",
+ "type": "module",
+ "version": "1.0.0",
+ "scripts": {
+ "dev": "astro dev --port 4336",
+ "dev:en": "cross-env DOCS_ENV=development DOCS_LANG=en astro dev --port 4336",
+ "dev:jp": "cross-env DOCS_ENV=development DOCS_LANG=jp astro dev --port 4336",
+
+ "build:en": "cross-env DOCS_ENV=production DOCS_LANG=en NODE_OPTIONS=--max-old-space-size=4096 astro build --outDir=../../dist/newlib",
+ "build:jp": "cross-env DOCS_ENV=production DOCS_LANG=jp NODE_OPTIONS=--max-old-space-size=4096 astro build --outDir=../../dist/newlib-jp",
+ "build": "cross-env NODE_OPTIONS=--max-old-space-size=4096 astro build",
+
+ "build-staging:en": "cross-env DOCS_ENV=staging NODE_ENV=production DOCS_LANG=en NODE_OPTIONS=--max-old-space-size=4096 astro build --outDir=../../dist/newlib",
+ "build-staging:jp": "cross-env DOCS_ENV=staging NODE_ENV=production DOCS_LANG=jp NODE_OPTIONS=--max-old-space-size=4096 astro build --outDir=../../dist/newlib-jp",
+
+ "build-production:en": "cross-env NODE_ENV=production DOCS_LANG=en NODE_OPTIONS=--max-old-space-size=4096 astro build --outDir=../../dist/newlib",
+ "build-production:jp": "cross-env NODE_ENV=production DOCS_LANG=jp NODE_OPTIONS=--max-old-space-size=4096 astro build --outDir=../../dist/newlib-jp",
+
+ "preview:en": "cross-env DOCS_LANG=en astro preview --outDir=../../dist/newlib --port 4336",
+ "preview:jp": "cross-env DOCS_LANG=jp astro preview --outDir=../../dist/newlib-jp --port 4336",
+
+ "astro": "astro"
+ },
+ "engines": { "node": ">=22.12.0" },
+ "dependencies": {
+ "@astrojs/mdx": "^5.0.0",
+ "@astrojs/starlight": "^0.38.3",
+ "astro": "^6.1.6",
+ "docs-template": "file:../../",
+ "sharp": "^0.34.2"
+ },
+ "devDependencies": {
+ "cross-env": "^7.0.3",
+ "js-yaml": "^4.1.1",
+ "sass-embedded": "^1.98.0"
+ }
+}
+```
+
+### Convention rules for scripts
+
+- **Always `cross-env`** for env vars — works on Windows + macOS + Linux.
+- **`DOCS_ENV` is the canonical mode flag**; `NODE_ENV` is only set for legacy Vite behavior.
+- **Do NOT set `NODE_ENV=staging`** — Vite derives `import.meta.env.DEV` from it and sets it `false`, breaking dev features.
+- **`outDir` is per-lang** — e.g. `../../dist/newlib` for en, `../../dist/newlib-jp` for jp. Otherwise the en build is overwritten.
+- **`NODE_OPTIONS=--max-old-space-size=4096`** for builds. Without this, large MDX trees OOM on Windows.
+- **`dev:{lang}` uses the same port** — only one lang can run at a time.
+
+---
+
+## Step 4 — Wire Up the Top-Level `package.json`
+
+Add scripts that delegate to the child:
+
+```json
+{
+ "scripts": {
+ "newlib:dev:en": "npm run dev:en --prefix docs/newlib",
+ "newlib:dev:jp": "npm run dev:jp --prefix docs/newlib",
+ "newlib:build:en": "npm run build:en --prefix docs/newlib",
+ "newlib:build:jp": "npm run build:jp --prefix docs/newlib"
+ }
+}
+```
+
+---
+
+## Step 5 — `tsconfig.json` and `content.config.ts`
+
+```jsonc
+// docs/newlib/tsconfig.json
+{
+ "extends": "astro/tsconfigs/strict",
+ "include": [".astro/types.d.ts", "**/*"],
+ "exclude": ["dist"]
+}
+```
+
+```ts
+// docs/newlib/src/content.config.ts
+export { collections } from 'docs-template/content';
+```
+
+The re-exported `collections` from [src/content-helper.ts](src/content-helper.ts) reads `DOCS_SOURCE_PATH` (set by `createDocsSite()`) and creates a glob loader scoped to that single language directory. **No need to exclude other languages** — they are simply never included.
+
+---
+
+## Step 6 — Validation Checklist
+
+Before opening a PR for a new child site, verify:
+
+- [ ] Each `(lib, lang)` pair has an entry in `IGDOCS_PLATFORMS` with a unique `devPort`
+- [ ] `getNavConfig()` in `src/platform.ts` has a `case '{key}':` arm
+- [ ] `astro.config.ts` reads `DOCS_LANG` and selects the correct platform key
+- [ ] `package.json` has all script variants (dev/build/build-staging/build-production/preview × langs)
+- [ ] `dist/{lib}-{lang}` is the per-lang output (no en/jp collision)
+- [ ] `cross-env` is used everywhere (Windows compatibility)
+- [ ] `environment.json` exists at `src/content/{lang}/environment.json`
+- [ ] `toc.json` location matches `tocPath` in astro.config (en at `./toc.json`, non-en at `./src/content/toc.json` per convention)
+- [ ] Top-level `package.json` has delegating scripts
+
+---
+
+## Common Pitfalls
+
+### Empty navbar / footer
+
+The page renders but with no nav. Cause: missing `case '{key}':` in `getNavConfig()` in [src/platform.ts](src/platform.ts).
+
+### Site loads but jp content shows en pages
+
+Cause: `astro.config.ts` is not threading `DOCS_LANG` into `docsDir`. Check that `path.resolve('./src/content/${contentLangDir}/topics')` actually swaps with the env value.
+
+### `EMFILE: too many open files` on Windows during dev
+
+Transient on Windows when many terminals/processes are open. Close other Node processes and retry. If chronic, lower the `Vite` watch concurrency or split content into smaller collections.
+
+### Two languages overwrite each other in `dist/`
+
+Cause: missing per-lang `--outDir` in build scripts. Fix: `--outDir=../../dist/{lib}-{lang}`.
+
+### `import.meta.env.DEV` is `false` in dev mode
+
+Cause: `NODE_ENV=staging` was set somewhere upstream. Use `DOCS_ENV=staging` and leave `NODE_ENV` unset (or `development`).
+
+### Sidebar shows raw `{environment:ProductName}` literals
+
+`toc.json` is JSON, not MDX — `remark-docfx` never sees it. Resolution happens at sidebar-build time inside [src/sidebar.ts](src/sidebar.ts), which reads `environment.json` (same lookup as `remark-docfx`) for the active `DOCS_ENV`. If your sidebar still shows raw `{environment:Foo}` text, check that `environment.json` exists alongside the docs dir and contains the key for your active environment. Do **not** statically rewrite tokens in `toc.json` — keep them dynamic.
diff --git a/.github/skills/docfx-to-mdx-migration/SKILL.md b/.github/skills/docfx-to-mdx-migration/SKILL.md
new file mode 100644
index 0000000000..e77836523d
--- /dev/null
+++ b/.github/skills/docfx-to-mdx-migration/SKILL.md
@@ -0,0 +1,252 @@
+---
+name: docfx-to-mdx-migration
+description: "Reference guide for migrating DocFX-style documentation (`.md` files with `NN_` prefixed folders, `%%Token%%` placeholders, `.html` cross-references, HTML tables, DocFX `` blocks) into Astro/Starlight-compatible MDX in this repo. Covers the 11-step pipeline (`scripts/migrate-jquery-pipeline.mjs`), individual scripts, dynamic environment.json token resolution at runtime (remark-docfx for MDX, sidebar.ts for toc.json), BOM handling for Japanese sources, git rename-detection workflow, and how to migrate a new library or new language. Use when an agent is asked to migrate a new docs source, run/extend the migration pipeline, debug pipeline output, or add a new fixer step."
+user-invocable: true
+---
+
+# AI Agent Guide — Migrating DocFX Docs to Astro/Starlight MDX
+
+## Context
+
+This repo serves multiple Starlight sites built from MDX content. Source content originally exported from DocFX needs systematic transformation to compile under Astro v6 + `@astrojs/mdx` + Starlight.
+
+DocFX inputs that **cannot** be served as-is:
+
+| DocFX feature | MDX requirement |
+|---|---|
+| `NN_Topic-Name.md` (numeric prefix for ordering) | Slugified file/folder names (no leading digits) |
+| `%%Token%%` placeholders | `{environment:Token}` (resolved by `remark-docfx`) |
+| `` blocks | YAML frontmatter with `title:` and `slug:` |
+| `.html` cross-references | Slug-based routes (no extension) |
+| HTML `
` (no colspan/rowspan) | Markdown pipe tables |
+| Pseudo-HTML tags like ``, ``, `` | Escaped to `<color>` etc. |
+| Bare `{` and `}` in prose | `{` / `}` (MDX parses `{` as JSX) |
+| BOM at file start (Japanese sources) | Stripped on read, optionally re-added on write |
+
+Authoritative pipeline doc: [scripts/MIGRATION.md](scripts/MIGRATION.md). This skill is the **how-to-think-about-migration** companion.
+
+---
+
+## When to Use This Skill
+
+| Situation | Use this skill? |
+|---|---|
+| Migrating a new DocFX source folder into `docs/{lib}/src/content/...` | **Yes** |
+| Adding a new language (e.g. `kr`) to an already-migrated library | **Yes** |
+| Debugging "Files changed: 0" output from a fixer script | **Yes** |
+| Adding a new fixer step to the pipeline | **Yes** |
+| Fixing a single MDX parse error in 1 file | No — edit the file directly |
+| Updating sidebar order for already-migrated content | No — edit `toc.json` directly |
+| Resolving `` / `` props | No — see the `api-link` skill |
+
+---
+
+## Step 1 — Set Up Source Layout BEFORE Running the Pipeline
+
+Pipeline expects this layout:
+
+```
+docs/{lib}/src/content/{lang}/topics/ ← MDX content goes here (initially .md)
+docs/{lib}/src/content/{lang}/environment.json ← token values
+docs/{lib}/src/content/{lang}/images/ ← images (optional, fixer locates them)
+docs/{lib}/toc.json (en) OR docs/{lib}/src/content/toc.json (non-en)
+```
+
+For non-English languages, the legacy DocFX folder may use a different code than `DOCS_LANG`:
+
+| `DOCS_LANG` env | Folder name on disk |
+|---|---|
+| `en` | `en/` |
+| `jp` | `ja/` (ISO 639-1, matches DocFX export) |
+| `kr` | `kr/` |
+
+The astro-child config translates `DOCS_LANG=jp` → `ja/` folder. See the `astro-child-config` skill.
+
+### Git rename detection (critical for non-English imports)
+
+If you are importing renamed `.md` → `.mdx` files into git, do it as a **2-commit sequence**:
+
+1. **Pure rename commit**: only path changes, no content edits. Stage as renames so git history is preserved:
+ ```bash
+ git config diff.renameLimit 3000 # default 400 is too low for >1000 files
+ git mv # OR git add -A after mv (git auto-detects 100% similarity)
+ git commit -m "Rename: → (.md → .mdx)"
+ ```
+2. **Pipeline commit**: run the migration pipeline, then commit the content changes on top. This way `git log --follow` works correctly.
+
+---
+
+## Step 2 — Run the Pipeline
+
+The orchestrator runs all 12 steps in order:
+
+```bash
+# Dry-run first
+node scripts/migrate-jquery-pipeline.mjs --topics=docs/{lib}/src/content/{lang}/topics --toc=docs/{lib}/{toc-path}
+
+# Apply
+node scripts/migrate-jquery-pipeline.mjs --apply --topics=... --toc=...
+```
+
+**Always restore the working tree to the post-rename state before re-running**, because the pipeline is **not idempotent** for all steps. If you need to re-run, restore with:
+
+```bash
+rm -rf docs/{lib}/src/content/{lang}/topics
+git checkout HEAD -- docs/{lib}/src/content/{lang}/topics
+```
+
+### Pipeline order and rationale
+
+| Step | Script | Why this order |
+|---|---|---|
+| 1 | `gen-jquery-toc` | Reads `NN_` prefixes for ordering — **must run before rename** |
+| 2 | `convert-docfx-tokens` | `%%Token%%` → `{environment:Token}` in content; `%%Token%%` → `{environment:Token}` in `toc.json` (kept dynamic) |
+| 3 | `convert-html-tables` | HTML tables → markdown pipe tables (skips colspan/rowspan; those are handled at build time) |
+| 4 | `fix-html-links` | `.html` → `.mdx` using `"fileName"` from metadata blocks. **Must run before rename** (uses original filenames) |
+| 5 | `rename-jquery-topics` | Strip `NN_`, slugify, update `toc.json` and inline links |
+| 6 | `fix-pseudo-html` | Escape ``, curly braces. Always writes (no `--apply` flag) |
+| 7 | `fix-all-mdx` | 11 fixers + per-file `compile()` validation |
+| 8 | `fix-broken-images` | Locate moved/renamed images; rewrites paths |
+| 9 | `fix-internal-links` | Resolve old-style flat names → slugified absolute paths; **remaps file-path slugs to frontmatter slugs** |
+| 10 | `add-slugs-to-toc` | Read `slug:` from each MDX, inject into `toc.json` so sidebar resolves without per-file reads |
+| 11 | `validate-mdx` | Compile every file with `@mdx-js/mdx`; report grouped errors |
+
+---
+
+## Step 3 — Common Pitfalls
+
+### 3a. BOM (UTF-8 byte order mark) breaks frontmatter regexes
+
+Japanese DocFX exports often have BOM (`\uFEFF`) at byte 0. A regex like `/^---/` will not match because the file starts with `\uFEFF---`.
+
+**Fix in any new script that reads MDX files**:
+
+```js
+const raw = fs.readFileSync(file, 'utf-8');
+const bom = raw.charCodeAt(0) === 0xFEFF ? '\uFEFF' : '';
+const text = bom ? raw.slice(1) : raw;
+// ... process `text` ...
+fs.writeFileSync(file, bom + result, 'utf-8');
+```
+
+Files in this repo that already do this: [scripts/fix-pseudo-html.mjs](scripts/fix-pseudo-html.mjs), [scripts/fix-all-mdx.mjs](scripts/fix-all-mdx.mjs), [scripts/add-slugs-to-toc.mjs](scripts/add-slugs-to-toc.mjs), [src/sidebar.ts](src/sidebar.ts), [src/llms.ts](src/llms.ts).
+
+### 3b. "Files changed: 0" but the change should have applied
+
+Common cause: the script compares `content !== content_at_some_intermediate_step` instead of `content !== src` (original disk content). If a transform produces output identical to an intermediate snapshot, the file is **not** written even though it differs from disk.
+
+Always compare write-decision against the **original disk content** captured before any in-memory mutation. See [scripts/fix-all-mdx.mjs](scripts/fix-all-mdx.mjs) for the post-fix history of this exact bug.
+
+### 3c. Frontmatter `slug:` vs file-path slug
+
+Starlight routes by the **frontmatter `slug:` value**, not by file path. A file at `general-and-getting-started/deployment-guide.mdx` with `slug: deployment-guide` is served at `/deployment-guide`, not `/general-and-getting-started/deployment-guide`.
+
+`fix-internal-links` builds a `filePathSlug → frontmatterSlug` map and remaps every resolved link. Any new link-fixer must do the same, or links will 404 in the rendered site.
+
+### 3d. `{environment:Foo}` tokens — **always keep dynamic**
+
+Environment tokens (e.g. `{environment:demosBaseUrl}`, `{environment:sassApiUrl}`) are resolved at **build time per environment** — each of dev / staging / production gets its own value from `environment.json`. Do **not** statically rewrite them to literal strings; doing so hard-codes one environment's URL and breaks the others.
+
+Three resolution sites exist, all backed by the shared helper [src/env-tokens.ts](src/env-tokens.ts):
+
+1. **MDX body**: [src/plugins/remark-docfx.ts](src/plugins/remark-docfx.ts) — visits `text`, `link`, `image`, `code`, `html` and `mdxJsxFlowElement`/`mdxJsxTextElement` (string-literal attribute values) nodes.
+2. **`toc.json`**: [src/sidebar.ts](src/sidebar.ts) — resolves on the raw TOC text before parsing, so `name`, `href`, `slug`, badge text all get values from the active `DOCS_ENV`.
+3. **Frontmatter**: [src/content-helper.ts](src/content-helper.ts) — resolves `title`, `description`, `keywords` in the schema preprocessor (used for the SEO `` and breadcrumbs; the visible page H1 comes from the body `# Heading`, see below).
+
+**Page H1 convention — body heading is canonical:**
+
+This repo overrides Starlight's `PageTitle` component ([src/components/overrides/PageTitle.astro](src/components/overrides/PageTitle.astro)) to suppress the auto-generated `
` from the frontmatter `title`. The visible H1 is the **body `# Heading`** in every MDX file (the convention across all child sites — angular, xplat, jquery). Migration scripts must therefore *preserve* the body H1, not strip it. Frontmatter `title` is still used by Starlight for the `` tag, breadcrumb, and sidebar fallback label.
+
+**Form rules — body vs frontmatter vs toc.json:**
+
+| Location | Required form | Why |
+|---|---|---|
+| MDX body prose | `\{environment:Foo\}` (backslash-escaped) | MDX parses bare `{` as JSX expression; `\{` tells MDX to emit a literal `{` in the text node, which the runtime resolver then matches |
+| MDX JSX attribute string-literal values (e.g. `data-src="…"`) | `{environment:Foo}` (raw braces) | Inside a quoted JSX attribute value `{` is a literal char — no escaping needed |
+| YAML frontmatter (`title:`, `description:`, …) | `{environment:Foo}` (raw braces) | YAML treats `{` as a literal char; frontmatter is resolved by `src/content-helper.ts` (used by Starlight for the H1 and breadcrumbs) |
+| `toc.json` | `{environment:Foo}` (raw braces) | JSON parses `{` only at the start of objects, never inside string values |
+
+The runtime regex in [src/env-tokens.ts](src/env-tokens.ts) (`ENV_TOKEN_RE`) matches all three forms (`{…}`, `\{…\}`, and `{…}`) for backward compatibility with legacy content. New content should use the form for its location per the table above.
+
+`scripts/convert-docfx-tokens.mjs` enforces this split: frontmatter gets raw braces, body gets `\{…\}`. Any new fixer that touches MDX must preserve this split — `fix-pseudo-html.mjs`, `fix-all-mdx.mjs` and `fix-internal-links.mjs` all skip both `\{environment:…\}` and the legacy `{environment:…}` forms.
+
+Both layers look up `environment.json` in this order:
+```
+{docsDir}/en/environment.json
+{docsDir}/environment.json
+{docsDir}/../environment.json
+{docsDir}/../en/environment.json
+```
+Token values come from `data[DOCS_ENV]` (with fallback to `data.production`).
+
+If you ever feel tempted to write a script that resolves tokens to literals: don't. Add a runtime resolver (using `loadEnvValues()` + `resolveEnvTokens()` from `src/env-tokens.ts`) wherever the token is being rendered as a literal instead.
+
+### 3e. Rename-detection on subsequent commits
+
+Once renames are in commit 1, commit 2 (the pipeline output) will be partially detected as renames if `diff.renameLimit` is large enough AND if no files changed by >50% similarity. Some heavily-rewritten files will show as `delete`+`add`. That is acceptable — `git log --follow` still uses the rename info from commit 1.
+
+---
+
+## Step 4 — Migrating a New Library
+
+```bash
+# Place source files under docs/{newlib}/src/content/en/topics
+# Place environment.json under docs/{newlib}/src/content/en/environment.json
+# Set up astro child config (see the `astro-child-config` skill)
+
+TOPICS=docs/{newlib}/src/content/en/topics
+TOC=docs/{newlib}/toc.json
+
+node scripts/migrate-jquery-pipeline.mjs --apply --topics=$TOPICS --toc=$TOC
+```
+
+If the new library uses a different folder layout (no `NN_` prefixes, no `%%Token%%`, etc.), specific steps become no-ops automatically — but **gen-jquery-toc** will still need adapting if your toc generation rules differ.
+
+---
+
+## Step 5 — Migrating a New Language to an Existing Library
+
+```bash
+# 1. Drop translated source under docs/{lib}/src/content/{ja,kr,...}/topics
+# 2. Add environment.json under same parent folder
+# 3. Confirm the astro child config supports the lang (see `astro-child-config` skill)
+
+TOPICS=docs/{lib}/src/content/{lang}/topics
+TOC=docs/{lib}/src/content/toc.json # non-en uses src/content/toc.json by convention
+
+node scripts/migrate-jquery-pipeline.mjs --apply --topics=$TOPICS --toc=$TOC
+```
+
+Because Japanese sources may have BOM, watch for it in any custom fixer you add (see 3a).
+
+---
+
+## Step 6 — Adding a New Fixer Step
+
+1. Create `scripts/{your-fixer}.mjs`. Follow the pattern of [scripts/fix-internal-links.mjs](scripts/fix-internal-links.mjs):
+ - Accept `--apply` (dry-run by default), `--topics=`, `--toc=` flags
+ - Walk MDX files via `fs.readdirSync(..., { withFileTypes: true })`
+ - Strip BOM on read; re-add on write
+ - Print `Results:` summary at end
+2. Add to [scripts/migrate-jquery-pipeline.mjs](scripts/migrate-jquery-pipeline.mjs) at the appropriate position (note that pre-rename steps must use original filenames; post-rename steps must use slugs).
+3. Document the step in [scripts/MIGRATION.md](scripts/MIGRATION.md).
+
+> **Do not add a runtime MDX rewriter that mutates source files at build time.** The repo previously had a `normalizeMdxDir()` call in `astro.config.ts` (and a `src/normalize-mdx.ts` module) that ran on every dev-server start and re-applied a `{` → `{` escape, repeatedly corrupting frontmatter and body env tokens. All MDX transformation belongs in the migration pipeline (one-time, idempotent) or in remark/rehype plugins (in-memory at compile time, never written to disk).
+
+---
+
+## Quick Reference: Script Command Map
+
+| Goal | Script |
+|---|---|
+| Generate `toc.json` from file tree | `gen-jquery-toc.mjs` |
+| Convert `%%Token%%` → `{environment:Token}` (MDX + toc) | `convert-docfx-tokens.mjs` |
+| Convert HTML tables to pipe tables | `convert-html-tables.mjs` |
+| Fix `.html` cross-references | `fix-html-links.mjs` |
+| Strip `NN_` prefixes, slugify | `rename-jquery-topics.mjs` |
+| Escape pseudo-HTML / curly braces | `fix-pseudo-html.mjs` |
+| Fix orphaned tags, anchors, etc. + validate | `fix-all-mdx.mjs` |
+| Fix broken image paths | `fix-broken-images-all.mjs` |
+| Resolve old-style links → frontmatter slugs | `fix-internal-links.mjs` |
+| Inject slugs into `toc.json` | `add-slugs-to-toc.mjs` |
+| Compile-validate every MDX | `validate-mdx.mjs` |
diff --git a/docs/jquery/astro.config.ts b/docs/jquery/astro.config.ts
index 26c532a2bc..233714b2bf 100644
--- a/docs/jquery/astro.config.ts
+++ b/docs/jquery/astro.config.ts
@@ -3,7 +3,6 @@ import mdx from '@astrojs/mdx';
import path from 'node:path';
import { createDocsSite, type DocsMode } from 'docs-template/integration';
import { IGDOCS_PLATFORMS, type NavLang } from 'docs-template/platform';
-import { normalizeMdxDir } from 'docs-template/normalize-mdx';
// ── Build mode and language ──────────────────────────────────────────────────
// DOCS_ENV: 'development' | 'staging' | 'production' (preferred, default: 'development')
@@ -41,9 +40,6 @@ const tocPath = docsLang === 'jp'
? path.resolve('./src/content/toc.json')
: path.resolve('./toc.json');
-// ── Pre-process: normalize legacy DocFX MDX files to Astro/Starlight format ──
-normalizeMdxDir(docsDir);
-
// https://astro.build/config
export default createDocsSite({
site,
diff --git a/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-directives.mdx b/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-directives.mdx
index 98ada355eb..f3e9e88e6a 100644
--- a/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-directives.mdx
+++ b/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-directives.mdx
@@ -4,14 +4,15 @@ slug: angularjs-directives
---
# AngularJS Directives
+
## In This Group of Topics
### Introduction
-The {environment:ProductName}® directives for AngularJS allow you to take advantage of the data binding and declarative view programming when using {environment:ProductName}® controls in Angular apps. In the [{environment:ProductName} GitHub repository](https://github.com/IgniteUI/igniteui-angularjs) you can always find the latest source and samples.
+The \{environment:ProductName\}® directives for AngularJS allow you to take advantage of the data binding and declarative view programming when using \{environment:ProductName\}® controls in Angular apps. In the [\{environment:ProductName\} GitHub repository](https://github.com/IgniteUI/igniteui-angularjs) you can always find the latest source and samples.
### Topics
-- [Using {environment:ProductName} with AngularJS](/using-ignite-ui-with-angularjs.mdx) - This topic contains an overview using the {environment:ProductName} directives for AngularJS.
-- [Conditional and Advanced Templating with AngularJS](/conditional-and-advanced-templating-with-angularjs.mdx) - This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the {environment:ProductName} directives for AngularJS.
-- [AngularJS Samples](/angularjs-samples.mdx) - This topic contains samples using the {environment:ProductName} directives for AngularJS.
\ No newline at end of file
+- [Using \{environment:ProductName\} with AngularJS](/using-ignite-ui-with-angularjs.mdx) - This topic contains an overview using the \{environment:ProductName\} directives for AngularJS.
+- [Conditional and Advanced Templating with AngularJS](/conditional-and-advanced-templating-with-angularjs.mdx) - This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the \{environment:ProductName\} directives for AngularJS.
+- [AngularJS Samples](/angularjs-samples.mdx) - This topic contains samples using the \{environment:ProductName\} directives for AngularJS.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-samples.mdx b/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-samples.mdx
index e15e668e21..d4ea7afbe8 100644
--- a/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-samples.mdx
+++ b/docs/jquery/src/content/en/topics/angularjs-directives/angularjs-samples.mdx
@@ -6,7 +6,7 @@ slug: angularjs-samples
# AngularJS Samples
## Topic Overview
-This topic covers samples with {environment:ProductFamilyName} directives for AngularJS.
+This topic covers samples with \{environment:ProductFamilyName\} directives for AngularJS.
### In this topic
@@ -40,8 +40,8 @@ This topic contains the following sections:
### Requirements
In order to run this sample, you need to have:
-- The required {environment:ProductName} JavaScript and CSS files
-- The {environment:ProductFamilyName} AngularJS directives
+- The required \{environment:ProductName\} JavaScript and CSS files
+- The \{environment:ProductFamilyName\} AngularJS directives
### Grid Sample
This sample will demonstrate how we can use `igGrid` with AngularJS.
@@ -50,7 +50,7 @@ This sample will demonstrate how we can use `igGrid` with AngularJS.
The following is a preview of the final result.
#### Details
@@ -76,7 +76,7 @@ This sample will demonstrate how we can use `igTileManager` with AngularJS.
The following is a preview of the final result.
#### Details
@@ -128,7 +128,7 @@ This sample demonstrates how `AngularJS` directives are used to instantiate `igL
The following is a preview of the final result.
#### Details
@@ -141,7 +141,7 @@ This sample demonstrates how `AngularJS` directives are used to instantiate `igD
The following is a preview of the final result.
#### Details
@@ -151,5 +151,5 @@ This sample demonstrates how to link together the Data Chart and Zoombar Control
### Related Content
The following topics provide additional information related to this one:
-- [Using {environment:ProductFamilyName} with AngularJS](/using-ignite-ui-with-angularjs.mdx) - This topic contains an overview using the {environment:ProductFamilyName} directives for AngularJS.
-- [Conditional and Advanced Templating with AngularJS](/conditional-and-advanced-templating-with-angularjs.mdx) - This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the {environment:ProductFamilyName} directives for AngularJS.
\ No newline at end of file
+- [Using \{environment:ProductFamilyName\} with AngularJS](/using-ignite-ui-with-angularjs.mdx) - This topic contains an overview using the \{environment:ProductFamilyName\} directives for AngularJS.
+- [Conditional and Advanced Templating with AngularJS](/conditional-and-advanced-templating-with-angularjs.mdx) - This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the \{environment:ProductFamilyName\} directives for AngularJS.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/angularjs-directives/conditional-and-advanced-templating-with-angularjs.mdx b/docs/jquery/src/content/en/topics/angularjs-directives/conditional-and-advanced-templating-with-angularjs.mdx
index 9ccc986f54..7c16e59035 100644
--- a/docs/jquery/src/content/en/topics/angularjs-directives/conditional-and-advanced-templating-with-angularjs.mdx
+++ b/docs/jquery/src/content/en/topics/angularjs-directives/conditional-and-advanced-templating-with-angularjs.mdx
@@ -2,20 +2,23 @@
title: "Conditional and Advanced Templating with AngularJS"
slug: conditional-and-advanced-templating-with-angularjs
---
+
+# Conditional and Advanced Templating with AngularJS
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
#Conditional and Advanced Templating with AngularJS
##Topic Overview
-This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the {environment:ProductName} directives for AngularJS.
+This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the \{environment:ProductName\} directives for AngularJS.
### Required background
The following lists the concepts, topics, and articles required as a prerequisite to understanding this topic.
- Topics
- - [Using {environment:ProductName} with AngularJS](/using-ignite-ui-with-angularjs.mdx)
+ - [Using \{environment:ProductName\} with AngularJS](/using-ignite-ui-with-angularjs.mdx)
- [Infragistics Templating Engine](../06_Infragistics-Templating-Engine/01_igTemplating Overview.mdx)
- Concepts
@@ -41,7 +44,7 @@ This topic contains the following sections:
## Introduction
-As {environment:ProductName} controls use [Infragistics Templating Engine](../06_Infragistics-Templating-Engine/01_igTemplating Overview.mdx) by default to handle templating, there are a few characteristics that must be taken into account when creating {environment:ProductName} controls in an Angular app, more specifically when doing so declaratively. The templating engine supports both common substitution using a `${property}` notation, as well as **conditional and iterative operations** that using double curly braces (e.g. `{{condition / loop}}` ). The latter is however in direct conflict with Angular’s [expression](https://docs.angularjs.org/guide/expression) evaluation as it uses the same syntax for bindings and therefore would recognize such templates and attempt to parse them. That is usually not a desired effect as it is likely to cause exceptions due to syntax and context differences. Even without errors, it might change the template’s markup that is otherwise intended for evaluation at within a control’s rendering process. This topic provides a few alternatives for using complex templates declaratively as well as methods to customize the entire templating handling with different engines.
+As \{environment:ProductName\} controls use [Infragistics Templating Engine](../06_Infragistics-Templating-Engine/01_igTemplating Overview.mdx) by default to handle templating, there are a few characteristics that must be taken into account when creating \{environment:ProductName\} controls in an Angular app, more specifically when doing so declaratively. The templating engine supports both common substitution using a `${property}` notation, as well as **conditional and iterative operations** that using double curly braces (e.g. `{{condition / loop}}` ). The latter is however in direct conflict with Angular’s [expression](https://docs.angularjs.org/guide/expression) evaluation as it uses the same syntax for bindings and therefore would recognize such templates and attempt to parse them. That is usually not a desired effect as it is likely to cause exceptions due to syntax and context differences. Even without errors, it might change the template’s markup that is otherwise intended for evaluation at within a control’s rendering process. This topic provides a few alternatives for using complex templates declaratively as well as methods to customize the entire templating handling with different engines.
### Context and Scope
@@ -105,11 +108,11 @@ The templates works as expected because nested elements under the parent are rem
### External Templates
-The easiest way to avoid conflicts would be to define templates outside the `ng-app` directive but that would mean the template can no longer be part of the {environment:ProductName} directive options. Nonetheless, an external template can often have a desired effect. For example you can increase readability of your code or share templates between controls. Either way, the directives need to be able to find that template for control initialization and to do that you use a scope method.
+The easiest way to avoid conflicts would be to define templates outside the `ng-app` directive but that would mean the template can no longer be part of the \{environment:ProductName\} directive options. Nonetheless, an external template can often have a desired effect. For example you can increase readability of your code or share templates between controls. Either way, the directives need to be able to find that template for control initialization and to do that you use a scope method.
### Using a Scope Method
-A function defined in the angular scope can be used to provide the template value via option evaluation. It can perform both complex tasks for initialization or simply provide access to a template defined somewhere in the document. While some controls provide the choice to supply either the template itself or the id by which it can be found( e.g. the `igDataChart`), the {environment:ProductName} directives will register the `getHtml()` function in your scope for the rest:
+A function defined in the angular scope can be used to provide the template value via option evaluation. It can perform both complex tasks for initialization or simply provide access to a template defined somewhere in the document. While some controls provide the choice to supply either the template itself or the id by which it can be found( e.g. the `igDataChart`), the \{environment:ProductName\} directives will register the `getHtml()` function in your scope for the rest:
**In JavaScript:**
```js
@@ -177,13 +180,13 @@ While the Infragistics Templating Engine is used by default, it is not by any me
```
-To use this feature jsRender script must be referenced on the page. Note that this **does not affect other controls**, their templates would still be handled by the {environment:ProductName} engine by default and follow the default syntax. As jsRender uses double curly braces even more extensively, the same techniques to avoid conflicts with Angular apply as described so far. Even more so, as substitution of a single property (e.g. `template="{{>UnitPrice}}"`) without any additional markup or formatting will be recognized as an expression to evaluate even for options nested within a directive.
+To use this feature jsRender script must be referenced on the page. Note that this **does not affect other controls**, their templates would still be handled by the \{environment:ProductName\} engine by default and follow the default syntax. As jsRender uses double curly braces even more extensively, the same techniques to avoid conflicts with Angular apply as described so far. Even more so, as substitution of a single property (e.g. `template="{{>UnitPrice}}"`) without any additional markup or formatting will be recognized as an expression to evaluate even for options nested within a directive.
-**Related Sample:** [JsRender Integration]({environment:NewSamplesUrl}/grid/jsrender-integration)
+**Related Sample:** [JsRender Integration](\{environment:NewSamplesUrl\}/grid/jsrender-integration)
### Overriding the Templating Function
-In advanced scenarios where other customization options are exhausted it is also possible to override the main templating function with your own. This is only possible in **{environment:ProductName} version 14.1 and later**. The `tmpl` is the main function of the Infragistics Templating Engine and is defined globally under the `$.ig` namespace object. This function is called by all relevant {environment:ProductName} controls and it receives both the template and data object:
+In advanced scenarios where other customization options are exhausted it is also possible to override the main templating function with your own. This is only possible in **\{environment:ProductName\} version 14.1 and later**. The `tmpl` is the main function of the Infragistics Templating Engine and is defined globally under the `$.ig` namespace object. This function is called by all relevant \{environment:ProductName\} controls and it receives both the template and data object:
**In JavaScript:**
```js
@@ -199,7 +202,7 @@ The templating process at this point may be handled in any number of ways – fr
If you want to use Angular’s syntax there are two options that handle evaluation of expressions in html – the compile and interpolate services. The string output requirement of the templating function essentially excludes the [`$compile`](https://docs.angularjs.org/api/ng/service//$compile) service as an option for custom templating (as compiled and linked templates still won’t have the time to activate). The [`$interpolate`](https://docs.angularjs.org/api/ng/service//$interpolate) service, however, immediately evaluates any expressions in the markup and directly substitutes their values. Creating such templating solution still requires a `$scope` reference accessible from the global function and also matching the passed data item in the angular app scope so it can be evaluated, but it is possible to execute logic from scope methods on every render.
->**Note:** Keep in mind that overriding the templating function applies to every active {environment:ProductName} control in the application, so if other controls have templates the new function should be able to handle those as well. Changing templating engines also usually means templates for all controls must change to match the new syntax.
+>**Note:** Keep in mind that overriding the templating function applies to every active \{environment:ProductName\} control in the application, so if other controls have templates the new function should be able to handle those as well. Changing templating engines also usually means templates for all controls must change to match the new syntax.
## Related Content
@@ -207,7 +210,7 @@ If you want to use Angular’s syntax there are two options that handle evaluati
The following topics provide additional information related to this topic.
-- [Using different template engines with {environment:ProductName} controls](http://www.infragistics.com/community/blogs/marina_stoyanova/archive/2014/05/30/using-different-template-engines-with-ignite-ui-controls.aspx)
+- [Using different template engines with \{environment:ProductName\} controls](http://www.infragistics.com/community/blogs/marina_stoyanova/archive/2014/05/30/using-different-template-engines-with-ignite-ui-controls.aspx)
- [jsRender Integration](/controls/iggrid/features/jsrender-integration.mdx)
### Samples
diff --git a/docs/jquery/src/content/en/topics/angularjs-directives/using-ignite-ui-with-angularjs.mdx b/docs/jquery/src/content/en/topics/angularjs-directives/using-ignite-ui-with-angularjs.mdx
index 065ccc70d5..cfb4faae00 100644
--- a/docs/jquery/src/content/en/topics/angularjs-directives/using-ignite-ui-with-angularjs.mdx
+++ b/docs/jquery/src/content/en/topics/angularjs-directives/using-ignite-ui-with-angularjs.mdx
@@ -1,21 +1,24 @@
---
-title: "Using {environment:ProductName} with AngularJS"
+title: "Using {environment:ProductName} with AngularJS"
slug: using-ignite-ui-with-angularjs
---
+
+# Using \{environment:ProductName\} with AngularJS
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
-#Using {environment:ProductName} with AngularJS
+#Using \{environment:ProductName\} with AngularJS
##Topic Overview
-This topic contains an overview using the {environment:ProductName} directives for AngularJS.
+This topic contains an overview using the \{environment:ProductName\} directives for AngularJS.
### Required background
The following lists the concepts, topics, and articles required as a prerequisite to understanding this topic.
- Topics
- - [{environment:ProductName} Overview](/igniteui-for-jquery-overview.mdx)
+ - [\{environment:ProductName\} Overview](/igniteui-for-jquery-overview.mdx)
- Concepts
- [AngularJS Conceptual Overview](https://docs.angularjs.org/guide/concepts)
@@ -32,7 +35,7 @@ This topic contains the following sections:
- [Scope Options](#scope-options)
- [Events](#events)
- [Options Evaluation](#options-evaluation)
-- [**Creating Angular app with {environment:ProductName}**](#creating-angular-app)
+- [**Creating Angular app with \{environment:ProductName\}**](#creating-angular-app)
- [Requirements](#requirements)
- [Steps](#steps)
- [**Data Binding**](#data-binding)
@@ -48,15 +51,15 @@ This topic contains the following sections:
## Introduction
-The [{environment:ProductName}® directives for AngularJS](https://github.com/IgniteUI/igniteui-angularjs) allow you to take advantage of data binding and declarative programming when using {environment:ProductName}® controls in AngularJS apps.
+The [\{environment:ProductName\}® directives for AngularJS](https://github.com/IgniteUI/igniteui-angularjs) allow you to take advantage of data binding and declarative programming when using \{environment:ProductName\}® controls in AngularJS apps.
-The directives are available as a separate module called `'igniteui-directives'` in the *igniteui-angular.js* file. They extend Angular with HTML markers that enable initialization and binding of {environment:ProductName} controls in the context (scope) provided by AngularJS.
+The directives are available as a separate module called `'igniteui-directives'` in the *igniteui-angular.js* file. They extend Angular with HTML markers that enable initialization and binding of \{environment:ProductName\} controls in the context (scope) provided by AngularJS.
->**Note:** Directives are registered dynamically based on the loaded {environment:ProductName} widgets. Therefore, you should make sure only the proper scripts are loaded on the page (and preferably avoid loading unused widgets).
+>**Note:** Directives are registered dynamically based on the loaded \{environment:ProductName\} widgets. Therefore, you should make sure only the proper scripts are loaded on the page (and preferably avoid loading unused widgets).
## Directives
-As Angular provides a very flexible syntax for writing directives and normalizes different declarative approaches to a single behavior, there are multiple ways you can initialize a control and its options. You have a number of different options available to you to initialize an {environment:ProductName} control in an Angular application. You may use a custom tag element ``, attributes like `
` or a class name `
`. Each of these approaches will match the control directive and produce the same result. Stated another way, the following definitions all work to initialize an `igRating` control:
+As Angular provides a very flexible syntax for writing directives and normalizes different declarative approaches to a single behavior, there are multiple ways you can initialize a control and its options. You have a number of different options available to you to initialize an \{environment:ProductName\} control in an Angular application. You may use a custom tag element ``, attributes like `<div data-control-name>` or a class name `<div class="control-name">`. Each of these approaches will match the control directive and produce the same result. Stated another way, the following definitions all work to initialize an `igRating` control:
**In HTML:**
@@ -66,12 +69,12 @@ As Angular provides a very flexible syntax for writing directives and normalizes
```
-For readability, best practices recommend using tags and attributes over classes. Even though Angular normalizes other delimiters, it’s also recommended for {environment:ProductName} Angular directives the control names to be lower case and dash-delimited.
+For readability, best practices recommend using tags and attributes over classes. Even though Angular normalizes other delimiters, it’s also recommended for \{environment:ProductName\} Angular directives the control names to be lower case and dash-delimited.
## Options
-All options provided for a directive are intended for the {environment:ProductName} widget that it will create, therefore all applicable options can be found under the [{environment:ProductName} API reference](https://www.igniteui.com/help/api/2025.1/). There are two mutually-exclusive ways to define options – declaratively in the View or as an object in the Scope.
+All options provided for a directive are intended for the \{environment:ProductName\} widget that it will create, therefore all applicable options can be found under the [\{environment:ProductName\} API reference](https://www.igniteui.com/help/api/2025.1/). There are two mutually-exclusive ways to define options – declaratively in the View or as an object in the Scope.
### Declarative Options
@@ -132,11 +135,11 @@ app.controller('treeController',
};
}]);
```
-These options may seem familiar to you as they are simply using the [{environment:ProductName} API](https://www.igniteui.com/help/api/2025.1/ui.igtree) in the controller as there is no need for AngularJS to normalize them from the view.
+These options may seem familiar to you as they are simply using the [\{environment:ProductName\} API](https://www.igniteui.com/help/api/2025.1/ui.igtree) in the controller as there is no need for AngularJS to normalize them from the view.
### Events
-Although standard methods of [handling {environment:ProductName} events](/general-and-getting-started/using-events-in-igniteui-for-jquery.mdx) are still available, directives can also bind handlers that are defined declaratively as an attribute with `event-` prefix. The name of the event still follows the same naming convention as options - **lower case and dash-delimited**. For example, the following code listing shows how to declare the event of the `igVideoPlayer`:
+Although standard methods of [handling \{environment:ProductName\} events](/general-and-getting-started/using-events-in-igniteui-for-jquery.mdx) are still available, directives can also bind handlers that are defined declaratively as an attribute with `event-` prefix. The name of the event still follows the same naming convention as options - **lower case and dash-delimited**. For example, the following code listing shows how to declare the event of the `igVideoPlayer`:
**In HTML:**
```html
@@ -151,7 +154,7 @@ function ($scope) {
}
}]);
```
->**Note:** Keep in mind there are many user interaction-related events in the {environment:ProductName} controls are not raised when the controls are manipulated through the API. The directives use API methods to achieve data binding. For example, the event of the `igCombo` control is not raised because a change was made to the `ngModel` to which it was bound.
+>**Note:** Keep in mind there are many user interaction-related events in the \{environment:ProductName\} controls are not raised when the controls are manipulated through the API. The directives use API methods to achieve data binding. For example, the event of the `igCombo` control is not raised because a change was made to the `ngModel` to which it was bound.
### Options Evaluation
@@ -173,20 +176,20 @@ By dividing it by 10:

-## Creating Angular app with {environment:ProductName}
+## Creating Angular app with \{environment:ProductName\}
### Requirements
-When considering the required resources the same requirements and options apply as described in the [Using JavaScript Resources in {environment:ProductName}](/general-and-getting-started/deployment-guide-javascript-resources.mdx) documentation in addition to loading the {environment:ProductName} Angular directives module afterwards. This means that along with some styles the application would also need to include:
+When considering the required resources the same requirements and options apply as described in the [Using JavaScript Resources in \{environment:ProductName\}](/general-and-getting-started/deployment-guide-javascript-resources.mdx) documentation in addition to loading the \{environment:ProductName\} Angular directives module afterwards. This means that along with some styles the application would also need to include:
- [jQuery](http://www.jquery.com/) 1.7 and later
- [jQuery UI](http://jqueryui.com/) 1.8 and later
- [AngularJS](http://www.angularjs.org/) 1.0 and later
-- [{environment:ProductName}](http://www.igniteui.com/) 13.1 and later
+- [\{environment:ProductName\}](http://www.igniteui.com/) 13.1 and later
### Steps
-1. Begin by including the [{environment:ProductName} theme and structural](/general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) files:
+1. Begin by including the [\{environment:ProductName\} theme and structural](/general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) files:
**In HTML:**
```html
@@ -205,7 +208,7 @@ When considering the required resources the same requirements and options apply
```
-3. Include {environment:ProductName} and the directives module. Preferably use a custom download, but you can also [include {environment:ProductName} in any available way](/general-and-getting-started/deployment-guide-javascript-resources.mdx).
+3. Include \{environment:ProductName\} and the directives module. Preferably use a custom download, but you can also [include \{environment:ProductName\} in any available way](/general-and-getting-started/deployment-guide-javascript-resources.mdx).
**In HTML:**
```html
@@ -246,7 +249,7 @@ When considering the required resources the same requirements and options apply
## Data Binding
-Besides providing initialization integration, one of the main benefits of the {environment:ProductName} directives for AngularJS is data binding support. The directives automatically assign AngularJS watchers to the sources provided at initialization, so the only requirement to enable data binding is to set the `dataSource` option or `data-source` attribute to the desired property from the scope:
+Besides providing initialization integration, one of the main benefits of the \{environment:ProductName\} directives for AngularJS is data binding support. The directives automatically assign AngularJS watchers to the sources provided at initialization, so the only requirement to enable data binding is to set the `dataSource` option or `data-source` attribute to the desired property from the scope:
**In HTML:**
```html
@@ -285,7 +288,7 @@ The other main group are controls that cannot edit their information (mostly con
## Templates
-Many {environment:ProductName} controls support templates that are by default handled by the [Infragistics Templating Engine](../06_Infragistics-Templating-Engine/01_igTemplating Overview.mdx). The {environment:ProductName}® Templating Engine is a JavaScript library used to apply a content template to a set of HTML elements. It supports conditional logic and nested templates. The engine uses a `${property}` notation for substitution of the corresponding property values in the data provided. For example, wrapping column values in additional markup for styling and formatting:
+Many \{environment:ProductName\} controls support templates that are by default handled by the [Infragistics Templating Engine](../06_Infragistics-Templating-Engine/01_igTemplating Overview.mdx). The \{environment:ProductName\}® Templating Engine is a JavaScript library used to apply a content template to a set of HTML elements. It supports conditional logic and nested templates. The engine uses a `${property}` notation for substitution of the corresponding property values in the data provided. For example, wrapping column values in additional markup for styling and formatting:
**In HTML:**
```html
@@ -325,7 +328,7 @@ app.controller('gridController',
### Setting Templates Declaratively
-The templating engine uses double curly braces for **conditional templates** (e.g. `{{if condition}}` ), which are also used by Angular for expression evaluation. Therefore, using such templates in declarative initialization **can cause conflicts**. For more information on how you can provide conditional templates declaratively or customize the templating process refer to the [Conditional and Advanced Templating with AngularJS](/conditional-and-advanced-templating-with-angularjs.mdx) topic.
+The templating engine uses double curly braces for **conditional templates** (e.g. `{{if condition}}` ), which are also used by Angular for expression evaluation. Therefore, using such templates in declarative initialization **can cause conflicts**. For more information on how you can provide conditional templates declaratively or customize the templating process refer to the [Conditional and Advanced Templating with AngularJS](/conditional-and-advanced-templating-with-angularjs.mdx) topic.
**Related:** [igGrid sample](http://igniteui.github.io/igniteui-angularjs/samples/igGrid.html)
@@ -362,7 +365,7 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [{environment:ProductName} directives for AngularJS samples](http://igniteui.github.io/igniteui-angularjs/)
-- [All {environment:ProductName} control samples]({environment:SamplesUrl})
+- [\{environment:ProductName\} directives for AngularJS samples](http://igniteui.github.io/igniteui-angularjs/)
+- [All \{environment:ProductName\} control samples](\{environment:SamplesUrl\})
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/aspnet-mvc-landingpage.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/aspnet-mvc-landingpage.mdx
index 59575bb4e0..aab96cbd1e 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/aspnet-mvc-landingpage.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/aspnet-mvc-landingpage.mdx
@@ -1,10 +1,9 @@
---
-title: "{environment:ProductNameMVC}"
+title: "{environment:ProductNameMVC}"
slug: asp.net-mvc-landingpage
---
-# {environment:ProductNameMVC}
-
+# \{environment:ProductNameMVC\}
- [Infragistics Excel Engine](/excel-engine/win-infragistics-excel-engine.mdx)
- [Infragistics Document Engine](/document-engine/win-infragistics-document-engine.mdx)
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/api-overview.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/api-overview.mdx
index f3a5a8eb66..257387d1c7 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/api-overview.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/api-overview.mdx
@@ -4,6 +4,7 @@ slug: documentengine-api-overview
---
# API Overview
+
This section lists each namespace that is relevant to the code library. We also give you several key classes that you will be using while programming with this code library. The namespaces and classes on this page link directly into our API documentation.
> **Note:** Unless otherwise noted, the unit for all properties in the Infragistics.Documents assembly is Points.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/getting-started-with-infragistics-document-engine.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/getting-started-with-infragistics-document-engine.mdx
index f5eb091ec0..a9c9074f60 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/getting-started-with-infragistics-document-engine.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/getting-started-with-infragistics-document-engine.mdx
@@ -6,7 +6,6 @@ slug: documentengine-getting-started-with-infragistics-document-engine
# Getting Started with Infragistics Document Engine
-
The Infragistics Document Engine™ is a large assembly containing multiple namespaces with several interfaces in each. If you are new to the Documents assembly, we can completely understand the potential to get a little overwhelmed at the sheer size of the assembly. For this reason, we've added a quick start topic that will guide you through the shortest route that you need to take in order to understand the Infragistics Document Engine and create a simple report of your own.
Since report writing is a linear process, you can use the following road map to help you understand the Document Engine's Document Object Model.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/welcome-to-infragistics-document-engine.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/welcome-to-infragistics-document-engine.mdx
index a9cd95860f..1dbf79f1a6 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/welcome-to-infragistics-document-engine.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/welcome-to-infragistics-document-engine.mdx
@@ -5,7 +5,6 @@ slug: documentengine-welcome-to-infragistics-document-engine
# Welcome to Infragistics Document Engine
-
The Infragistics Document Engine™ is a complete, self-contained code library, allowing you to generate exceptional reports in both Portable Document Format (PDF) and XML Paper Specification (XPS) format. Infragistics Document Engine's Document Object Model (DOM) is simple enough to get up and running quickly, yet complex enough to give you the customizability that Infragistics products are known for. Using the DOM, you can effectively create a report, add a section, add some text, and publish the report -- all in a mere four lines of code.
## [Report Elements](DocumentEngine-Report-Elements.html "Discusses the Report elements available in the Infragistics Document Engine.")
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/win-infragistics-document-engine.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/win-infragistics-document-engine.mdx
index f327262772..cd67bf6ded 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/win-infragistics-document-engine.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/win-infragistics-document-engine.mdx
@@ -5,7 +5,6 @@ slug: win-infragistics-document-engine
# Infragistics Document Engine
-
The Infragistics Document Engine is the purveyor of fine, business reports in both Portable Document Format (PDF) and XML Paper Specification (XPS) file formats. Use the complete Document Object Model (DOM) to handle any report scenario imaginable. The Infragistics Document Engine includes support for report information, preferences, and security. There is also an extensive Graphics object to add color and personality to your reports.
Click the links below to access important information about the Infragistics Document Engine.
@@ -14,4 +13,4 @@ Click the links below to access important information about the Infragistics Doc
- [Getting Started with Infragistics Document Engine](DocumentEngine-Getting-Started-with-Infragistics-Document-Engine.html "getting started with infragistics document engine"): Once you have a basic understanding of the Infragistics Document Engine, this topic will help you start using the code library. This topic is a quick walkthrough of the objects you need to create in order to produce a full report.
- [Writing Reports](DocumentEngine-Writing-Reports.html "writing reports with document engine"): This section is the meat of the Infragistics Document Engine help. You will be shown the details of each report and graphic element. These topics are in the form of conceptual walkthroughs, as most elements are quite hefty and contain many features!
- [Deploying Infragistics Document Engine](DocumentEngine-Deploying-Infragistics-Document-Engine.html "deploying document engine"): If your application uses the Infragistics Document Engine, refer to this topic for a list of the Infragistics .NET assemblies that you need to redistribute as part of your application.
-- [API Overview](DocumentEngine-API-Overview.html "api overview for document engine"): This topic lists the namespaces and classes that you will be working with while programming with the Infragistics Excel Engine. The namespaces and classes listed in this topic link conveniently into the "API Reference Guide" section of the {environment:ProductName} help.
\ No newline at end of file
+- [API Overview](DocumentEngine-API-Overview.html "api overview for document engine"): This topic lists the namespaces and classes that you will be working with while programming with the Infragistics Excel Engine. The namespaces and classes listed in this topic link conveniently into the "API Reference Guide" section of the \{environment:ProductName\} help.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/known-issues.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/known-issues.mdx
index 9ea2bde5a8..8a638ffbaf 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/known-issues.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/known-issues.mdx
@@ -2,6 +2,9 @@
title: "Known Issues and Limitations (Infragistics Document Engine)"
slug: documentengine-known-issues
---
+
+# Known Issues and Limitations (Infragistics Document Engine)
+
g
# Known Issues and Limitations (Infragistics Document Engine)
@@ -20,14 +23,14 @@ The following table summarizes the known issues and limitations for the Infragis
## Infragistics Document Engine
Issue | Description | Status
---|---|---
-Namespace conflict | Using the NetAdvantage® for ASP.NET and {environment:ProductName}™ documents’ assemblies together causes namespace conflict exceptions. | 
+Namespace conflict | Using the NetAdvantage® for ASP.NET and \{environment:ProductName\}™ documents’ assemblies together causes namespace conflict exceptions. | 
## Known Issues and Limitations Details
-Using the Infragistics ASP.NET and {environment:ProductName} documents’ assemblies together causes namespace conflict exceptions.
+Using the Infragistics ASP.NET and \{environment:ProductName\} documents’ assemblies together causes namespace conflict exceptions.
### Workaround
-Reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from {environment:ProductName} in your application. The documents’ libraries within these assemblies are the same and can be used to replace one another.
+Reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from \{environment:ProductName\} in your application. The documents’ libraries within these assemblies are the same and can be used to replace one another.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/layout-elements.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/layout-elements.mdx
index 0348a16b11..5db84807d8 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/layout-elements.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/layout-elements.mdx
@@ -4,6 +4,7 @@ slug: documentengine-advanced-layout-elements
---
# Advanced Layout Elements
+
Advanced layout elements are elements that you don't necessarily need in order to write a complete report. These elements will help you accomplish specific tasks related to your report's layout.
Click the links below to learn more about advanced layout elements.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/rotator.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/rotator.mdx
index 0ff6b2b686..bd7fe1dfd6 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/rotator.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/rotator.mdx
@@ -5,7 +5,6 @@ slug: documentengine-rotator
# Rotator
-
The Rotator element rotates its content either 90 degrees clockwise or 90 degrees counter-clockwise. Content is rotated counter-clockwise by default, but by setting the Backward property to True, you can rotate the content clockwise. The Rotator element should be used when all you need to do is simply rotate content at a 90 degree angle. If you need to rotate content at a 45 degree angle or any other angle, you need to use the Site element. For more information on the Site element, see Site.
In the image to the right, you see two Text elements inside of Rotator elements. The first Rotator element rotates the text 90 degrees clockwise by setting the Backward property to True. A Stretcher element was also necessary as the text was left-aligned. The second Rotator element is the exact opposite of the first.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/site.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/site.mdx
index 91c1c2e0cf..0a52a3d429 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/site.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/site.mdx
@@ -4,6 +4,7 @@ slug: documentengine-site
---
# Site
+
The Site element affords you the ultimate customizability in placing layout elements on a page. Using the Site element, you can place elements using their x- and y-coordinates, and even rotate them to any angle.
The Site element doesn't have unique properties that make it different from other layout elements; instead, each method that adds content elements contains two overloads. These overloads allow you to place each layout element separately wherever you chose.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/stretcher.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/stretcher.mdx
index 3334a995e7..44028a1a1f 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/stretcher.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/advanced/stretcher.mdx
@@ -4,6 +4,7 @@ slug: documentengine-stretcher
---
# Stretcher
+
The `Stretcher` element is a non-visible layout element whose only purpose is to stretch content to the end of a page. Normally, a layout element will resize to fit the content it encapsulates. This may be an undesired effect if the layout element includes a background color or image. When you call the `AddStretcher` method off a layout element, that element will stretch to the end of the page, even if its content does not. The two images below show how an element with its background color set to `LightSteelBlue` would look like without and with a Stretcher element.
Without Stretcher | With Stretcher
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/report/element.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/report/element.mdx
index a6a5dc18bd..83d96fa0cb 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/report/element.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/report/element.mdx
@@ -6,7 +6,6 @@ slug: documentengine-report-element
# Report Element
-
The Report element is the top-level object that defines the entire report. You must add all content to a report by way of a Section element. Most layout elements use methods to create additional and nested layout elements; this is the same for the Report element, but you can add only one layout element type, the Section element, to the Report element. An easier way to understand this concept would be to visualize it as an object model diagram. For example, a report's layout can be as simple as the following tree:
- Report
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/section/section.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/section/section.mdx
index c6a271f1f7..2101e3a404 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/section/section.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/section/section.mdx
@@ -4,6 +4,7 @@ slug: documentengine-section
---
# Section
+
The Section element is the only element that you can add to the Report element. Through the Section element, you can manipulate page numbering and your document's look and feel through stationery and decorations, among other things.
Click the links below to find out more about the Section element.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/segment.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/segment.mdx
index a35747c7ce..3ab77c06ea 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/segment.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/layout/segment.mdx
@@ -6,7 +6,6 @@ slug: documentengine-segment
# Segment
-
The Segment element is aptly named for the several complete segments (or pages) of content it can produce. Similar to the Section element, the Segment element can have different header/footer combinations for each individual page (as long as the number of pages does not exceed the number of headers/footers, see the Segment Headers and Footers section below for more information). But, unlike the Section element, you can't set a Segment's size; Segments depend on the size of their containing Section element. The Segment and Section elements both have an [AddStretcher](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Segment.ISegment~AddStretcher.html "Link to the Web API Reference Guide to the AddStretcher member.") method to stretch content on individual pages; however, the Segment element also has the [Stretch](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Segment.ISegment~Stretch.html "Link to the Web API Reference Guide to the Stretch member.") property to stretch all content on every page.
The Segment element is very similar in function to the Section, Band, and Group elements. Refer to the table below for the main differences between these four elements.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/navigation/table-of-contents.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/navigation/table-of-contents.mdx
index 526069486c..19dd4bcb23 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/navigation/table-of-contents.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/navigation/table-of-contents.mdx
@@ -4,6 +4,7 @@ slug: documentengine-table-of-contents
---
# Table of Contents
+
Creating a table of contents (TOC) is much simpler than most would think. If you've already been writing reports with the Infragistics Document Engine™, you may already be halfway on the way to writing a table of contents. The TOC element creates a table of contents based on the structure of your report; so it is important that you build your report properly in order to take advantage of the TOC element.
The Text element exposes a [Heading](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Text.IText~Heading.html "Link to the Web API Reference Guide to the Heading member.") property, which can be set to the [TextHeading](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.TextHeading.html "Link to the Web API Reference Guide to the TextHeading member.") enumeration. Some of the values of this enumeration are H1, H2, H3, and so on. When you set the heading of a Text element, you are letting the TOC element know how to generate the table of contents. The [ITOC](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.TOC.ITOC.html "Link to the Web API Reference Guide to the ITOC interface.") interface includes an [AddLevel](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.TOC.ITOC~AddLevel.html "Link to the Web API Reference Guide to the AddLevel member.") method, which you can use in conjunction with the different headings. The first level that you add to the table of contents corresponds to the first level of headings, or H1. Adding another level to the table of contents will correspond to H2, continuing on to the final heading, H9. Therefore, if you label your headings properly, you won't have to do much extra work to generate a table of contents.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/content.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/content.mdx
index 924fe76c57..0db4077e40 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/content.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/content.mdx
@@ -4,6 +4,7 @@ slug: documentengine-pattern-content
---
# Pattern Content
+
Pattern content includes elements that can all be styled through the use of patterns. These patterns apply styles to grids, tables, trees, etc. by creating pattern objects and then applying them to their associated element. These elements mostly rely on some source of data to fill them.
Click the links below to learn about the pattern content that is available to you.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/text.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/text.mdx
index b23f1cb86e..7a7753cec8 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/text.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/text.mdx
@@ -4,6 +4,7 @@ slug: documentengine-text
---
# Text
+
The Text element adds highly customized paragraph content to your reports. The Text element includes several text-specific properties that will make your content stand out no matter what the occasion. Several of these properties can be found in the [report graphics](DocumentEngine-Report-Graphics.html "Explains the graphic items available for reports created using document engine.") section, but there are a few properties that are specific to text:
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/trees.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/trees.mdx
index 321670f88b..44e3cfb9e1 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/trees.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/pattern/trees.mdx
@@ -4,6 +4,7 @@ slug: documentengine-trees
---
# Trees
+
The Tree element is useful for displaying hierarchical relationships by showing how parent nodes, especially the root node, own their child nodes and all nodes beneath them in the hierarchy. The Tree element's object model consists of a main tree object with a [Root](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Tree.ITree~Root.html "Link to the Web API Reference Guide to the Root member.") property to identify the root node of the tree. Once you've gotten a reference to the root node (which is of type [INode](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Tree.INode.html "Link to the Web API Reference Guide to the INode interface.") ), you can call the [AddNode](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Tree.INode~AddNode.html "Link to the Web API Reference Guide to the AddNode member.") method off the INode interface to add additional nodes to the tree. You can add as many or as few nodes as you like, but there will only be one root node.
As with all [pattern content](DocumentEngine-Pattern-Content.html "Explains the pattern content items available in the document engine."), you can implement style changes by adding patterns to the following tree elements:
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/content.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/content.mdx
index 54c81d71fe..7294548a47 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/content.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/content.mdx
@@ -4,6 +4,7 @@ slug: documentengine-quick-content
---
# Quick Content
+
When all you need is the bare minimum. Quick content allows you to quickly add report material through method calls. For example, call the `AddQuickText` method and pass your text as the argument; that's all you need to do to add simple text to a layout element.
Click the links below to learn about the light-weight, quick content elements.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/table.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/table.mdx
index 3d7fbd5665..d4b6248bcf 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/table.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/table.mdx
@@ -6,7 +6,6 @@ slug: documentengine-quick-table
# Quick Table
-
The Quick Table element is definitely the heaviest of the light-weight [Quick Content](DocumentEngine-Quick-Content.html "Explains the quick content items available in the document engine.") elements only because a table naturally contains several elements. You can add the following elements to the Quick Table element:
- Column
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/text.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/text.mdx
index 197d9da9ac..4402cb0083 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/text.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/elements/quick/text.mdx
@@ -6,7 +6,6 @@ slug: documentengine-quick-text
# Quick Text
-
The Quick Text element is the simplest of the [Quick Content](DocumentEngine-Quick-Content.html "Explains the quick content that's available in the document engine.") elements in that you do not need to customize the element at all. The Quick Text element was designed in such a way that all you need to do is pass a string to the AddQuickText method to quickly add text to your report. Of course, you can also get a reference to the element and modify a few standard properties such as [Alignment](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.QuickText.IQuickText~Alignment.html "Link to the Web API Reference Guide to the Alignment member.") , [Brush](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.QuickText.IQuickText~Brush.html "Link to the Web API Reference Guide to the Brush member.") , and [Font](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.QuickText.IQuickText~Font.html "Link to the Web API Reference Guide to the Font member.") ; but if you need a full-fledged Text element, see [Text](DocumentEngine-Text.html "Explains the Text element available in the document engine.") for more information. The basic use-case for the Quick Text element is to add default text (Arial, 12pt) with no regard to its placement or appearance.

diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/graphics/shapes.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/graphics/shapes.mdx
index c5572285c5..fa4e200eb8 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/graphics/shapes.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/document-engine/writing/graphics/shapes.mdx
@@ -4,6 +4,7 @@ slug: documentengine-shapes
---
# Shapes
+
The Site element is an intriguing element that can place objects anywhere in its binding rectangle as well as rotate them. Another feature that makes the Site element very useful is the [Shapes](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Shapes.IShapes.html "Link to the Web API Reference Guide to the IShapes interface.") factory. Just as the name implies, the Shapes factory allows you to produce numerous kinds of shapes and add them to the Site element.
You can easily access each shape off the Shapes object by calling a method specific to that shape (e.g., to add a rectangle, call the [AddRetangle](Infragistics.Web.Documents.Reports~Infragistics.Documents.Reports.Report.Shapes.IShapes~AddRectangle.html "Link to the Web API Reference Guide to the AddRectangle member.") method). The method will return a reference to the newly created shape and you can set that reference to a new shape object.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/api-overview.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/api-overview.mdx
index 329b93072e..2e6cac2e57 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/api-overview.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/api-overview.mdx
@@ -4,6 +4,7 @@ slug: excelengine-api-overview
---
# API Overview
+
This section lists each namespace that is relevant to the code library. We also give you several key classes that you will be using while programming with this code library. The namespaces and classes on this page link directly into our API documentation.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/add-document-properties-to-a-workbook.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/add-document-properties-to-a-workbook.mdx
index 1a2d6b7009..f022016205 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/add-document-properties-to-a-workbook.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/add-document-properties-to-a-workbook.mdx
@@ -6,7 +6,6 @@ slug: excelengine-add-document-properties-to-a-workbook
# Add Document Properties to a Workbook
-
Associated with each workbook file are various properties that provide information about its content. These properties include the following pieces of information:
- Author
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/adding-shapes-to-a-worksheet.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/adding-shapes-to-a-worksheet.mdx
index 1218e1ebf1..f235a43ad8 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/adding-shapes-to-a-worksheet.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/adding-shapes-to-a-worksheet.mdx
@@ -6,7 +6,6 @@ slug: excelengine-adding-shapes-to-a-worksheet
# Adding Shapes to a Worksheet
-
## Before You Begin
One of the great things about the Infragistics.Documents.Excel assembly is the ability to add images and shapes to your worksheet. As in Microsoft® Excel®, you can place an image on a worksheet, position it where you want, and even group it with other shapes on the same worksheet. Using a shape is a simple process of creating the shape, setting anchors which determine where it will be positioned on the worksheet, and adding it to the worksheet.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/list-of-supported-built-in-functions.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/list-of-supported-built-in-functions.mdx
index b1e130307d..0fd102a19f 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/list-of-supported-built-in-functions.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/list-of-supported-built-in-functions.mdx
@@ -3,7 +3,6 @@ title: "List of Supported Built-in Functions"
slug: excelengine-list-of-supported-built-in-functions
---
-
# List of Supported Built-in Functions
## Introduction
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/merge-cells.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/merge-cells.mdx
index 4954f9ca3b..1002acf664 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/merge-cells.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/merge-cells.mdx
@@ -4,6 +4,7 @@ slug: excelengine-merge-cells
---
# Merge Cells
+
Aside from setting the value or format of cells, you can also merge cells to make two or more cells appear as one. If you merge cells, they must be in a rectangular region. When part of a merged region, each cell in the region will have the same value and cell format; also, they will all be associated with the same [`WorksheetMergedCellsRegion`](Infragistics.Web.Documents.Excel~Infragistics.Documents.Excel.WorksheetMergedCellsRegion.html "Link to the Web API Reference Guide to the WorksheetMergedCellsRegion member.") object, accessible from their [`AssociatedMergedCellsRegion`](Infragistics.Web.Documents.Excel~Infragistics.Documents.Excel.WorksheetCell~AssociatedMergedCellsRegion.html "Link to the Web API Reference Guide to the WorksheetMergedCellsRegion member.") property. The `WorksheetMergedCellsRegion` object will also have the same value and cell format as the cells. Setting the value (or cell format) of the region or any cell in the region will change the value of all cells and the region. If you unmerge cells, because the merged region was removed from the worksheet, all of the previously merged cells will retain the shared cell format they had before they were unmerged. However, only the top-left cell of the region will retain the shared value.
The following code demonstrates how to merge some cells and set the value and format of the merged cells region.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/moving-a-worksheet-within-an-excel-workbook.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/moving-a-worksheet-within-an-excel-workbook.mdx
index f859bd74f0..edaca1c40c 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/moving-a-worksheet-within-an-excel-workbook.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/using/moving-a-worksheet-within-an-excel-workbook.mdx
@@ -4,6 +4,7 @@ slug: excelengine-moving-a-worksheet-within-an-excel-workbook
---
# Moving a Worksheet within an Excel Workbook
+
In certain cases you might need to move a worksheet to a particular index position in the owning Excel® workbook’s worksheets collection.
Considering, you have three worksheets in an Excel Workbook, you can place worksheet3 in the first position, using the [`MoveToIndex`](Infragistics.Web.Documents.Excel~Infragistics.Documents.Excel.Worksheet~MoveToIndex.html "Link to the Web API Reference Guide to the MoveToIndex method.") method of the [`Worksheet`](Infragistics.Web.Documents.Excel~Infragistics.Documents.Excel.Worksheet.html "Link to the Web API Reference Guide to the Worksheet class.") class.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/win-infragistics-excel-engine.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/win-infragistics-excel-engine.mdx
index 02414e2ba6..7bcd75d447 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/win-infragistics-excel-engine.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/excel-engine/win-infragistics-excel-engine.mdx
@@ -15,7 +15,7 @@ Click the links below to access important information about the Infragistics Exc
- [Deploying the Infragistics Excel Engine](ExcelEngine-Deploying-the-Infragistics-Excel-Engine.html "deploying the infragistics excel engine"): If your application uses the Infragistics Excel Engine, refer to this topic for a list of the Infragistics .NET assemblies that you need to redistribute as part of your application.
-- [API Overview](ExcelEngine-API-Overview.html "api overview for excel engine"): This topic lists the namespaces and classes that you will be working with while programming with the Infragistics Excel Engine. The namespaces and classes listed in this topic link conveniently into the "API Reference Guide" section of the {environment:ProductName} help.
+- [API Overview](ExcelEngine-API-Overview.html "api overview for excel engine"): This topic lists the namespaces and classes that you will be working with while programming with the Infragistics Excel Engine. The namespaces and classes listed in this topic link conveniently into the "API Reference Guide" section of the \{environment:ProductName\} help.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-known-issues.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-known-issues.mdx
index 48485b16eb..9c27277b82 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-known-issues.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-known-issues.mdx
@@ -1,14 +1,13 @@
---
-title: "Wrappers Known Issues and Limitations ({environment:ProductNameMVC})"
+title: "Wrappers Known Issues and Limitations ({environment:ProductNameMVC})"
slug: aspnet-mvc-wrappers-known-issues
---
-# Wrappers Known Issues and Limitations ({environment:ProductNameMVC})
-
+# Wrappers Known Issues and Limitations (\{environment:ProductNameMVC\})
## Known Issues and Limitations Summary
-The following table summarizes the known issues and limitations of the {environment:ProductNameMVC}. Detailed explanations of some of the issues and the existing workarounds are provided after the summary table.
+The following table summarizes the known issues and limitations of the \{environment:ProductNameMVC\}. Detailed explanations of some of the issues and the existing workarounds are provided after the summary table.
Legend: |
@@ -17,7 +16,7 @@ Legend: |
 | No known workaround
 | No known workaround, fix planned
-### {environment:ProductNameMVC}
+### \{environment:ProductNameMVC\}
Issue | Description | Status
@@ -59,9 +58,9 @@ When [`AutoGenerateLayouts`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.GridModel
### MVC Loader not functioning correctly in an MVC Razor Layout View
-The {environment:ProductNameMVC} Loader cannot initialize before the controls in an actual View when it is included in an ASP.NET MVC Razor Layout View.
+The \{environment:ProductNameMVC\} Loader cannot initialize before the controls in an actual View when it is included in an ASP.NET MVC Razor Layout View.
-{environment:ProductNameMVC} do not produce the proper Loader code when the Loader is included in a layout page in an ASP.NET MVC Razor application. They use the regular jQuery `$(function() { })` (document.ready) syntax. This happens only for ASP.NET MVC Razor applications. In MVC ASPX Views with master pages this problem does not occur.
+\{environment:ProductNameMVC\} do not produce the proper Loader code when the Loader is included in a layout page in an ASP.NET MVC Razor application. They use the regular jQuery `$(function() { })` (document.ready) syntax. This happens only for ASP.NET MVC Razor applications. In MVC ASPX Views with master pages this problem does not occur.
The reason for this is that layout Views are processed and executed after the particular View is rendered and the Loader has no chance to initialize prior to View rendering.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-mobile-known-issues.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-mobile-known-issues.mdx
index bc4371647a..d712c466ee 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-mobile-known-issues.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/igniteui-for-mvc-mobile-known-issues.mdx
@@ -1,14 +1,13 @@
---
-title: "Mobile Wrappers Known Issues and Limitations ({environment:ProductNameMVC})"
+title: "Mobile Wrappers Known Issues and Limitations ({environment:ProductNameMVC})"
slug: aspnet-mvc-mobile-wrappers-known-issues
---
-# Mobile Wrappers Known Issues and Limitations ({environment:ProductNameMVC})
-
+# Mobile Wrappers Known Issues and Limitations (\{environment:ProductNameMVC\})
## Known Issues and Limitations Summary
-The following table summarizes the known issues and limitations of the {environment:ProductNameMVC} mobile.
+The following table summarizes the known issues and limitations of the \{environment:ProductNameMVC\} mobile.
Legend: |
--------|---------
@@ -17,7 +16,7 @@ Legend: |
 | No known workaround, fix planned
-### {environment:ProductName} ASP.NET MVC Mobile Wrappers (mobile)
+### \{environment:ProductName\} ASP.NET MVC Mobile Wrappers (mobile)
Issue | Description | Status
------|-------------|--------
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/mvcscaffolding/mvc-scaffolding.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/mvcscaffolding/mvc-scaffolding.mdx
index 7a73f5f478..a2691eeefe 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/mvcscaffolding/mvc-scaffolding.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/mvcscaffolding/mvc-scaffolding.mdx
@@ -1,14 +1,14 @@
---
-title: "{environment:ProductNameMVC} Scaffolder Visual Studio extension"
+title: "{environment:ProductNameMVC} Scaffolder Visual Studio extension"
slug: mvc-scaffolding
---
-# {environment:ProductNameMVC} Scaffolder Visual Studio extension
+# \{environment:ProductNameMVC\} Scaffolder Visual Studio extension
### Introduction
-With the 2015.2 Release, we introduce the **{environment:ProductNameMVC}** Scaffolder Extension.
+With the 2015.2 Release, we introduce the **\{environment:ProductNameMVC\}** Scaffolder Extension.
It allows the developer to easily generate MVC wrapper widget declarations, as well as related Controller action methods.
This saves a lot of time for manual setup, referencing and coding.
@@ -28,7 +28,7 @@ In order to take advantage of the Scaffolding mechanism, just follow the steps o
3. Click on the "Add" menu item and then on "New Scaffolder Item..." option.
This set of steps is demonstrated in the screenshot below:

-4. Next, you will be prompted to choose the type of Scaffolding item you want - this can be an "{environment:ProductName} View" or an "{environment:ProductName} Controller with View".
+4. Next, you will be prompted to choose the type of Scaffolding item you want - this can be an "\{environment:ProductName\} View" or an "\{environment:ProductName\} Controller with View".
These selection options are demonstrated in the screenshot below:

The difference between these two options is that one adds a simple View, whereas the other one creates a View, along with a controller.
@@ -38,7 +38,7 @@ In the second and last tab, you can choose which properties to enable in the com
This is demonstrated in the screenshot below:

6. Once we are done with the settings for the component that we are adding, we click on the "Add" button. This automatically adds a view, containing the widget wrapper definition, along with all the settings that we have enabled.
-You can further customize it, add or remove properties and methods, as you would normally do in a standard view, containing an {environment:ProductName} widget wrapper.
+You can further customize it, add or remove properties and methods, as you would normally do in a standard view, containing an \{environment:ProductName\} widget wrapper.
###Prerequisites
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/using-ignite-ui-tag-helpers.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/using-ignite-ui-tag-helpers.mdx
index 79e4a15a80..ea487478c7 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/using-ignite-ui-tag-helpers.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/using-ignite-ui-tag-helpers.mdx
@@ -1,13 +1,13 @@
---
-title: "Using {environment:ProductNameASPNETCore} Tag Helpers"
+title: "Using {environment:ProductNameASPNETCore} Tag Helpers"
slug: tag-helpers
---
-# Using {environment:ProductNameASPNETCore} Tag Helpers
+# Using \{environment:ProductNameASPNETCore\} Tag Helpers
## Topic Overview
-This topic demonstrates how to configure {environment:ProductNameASPNETCore}™ components by using the Tag Helpers syntax introduced in the new ASP.NET Core 1.0
+This topic demonstrates how to configure \{environment:ProductNameASPNETCore\}™ components by using the Tag Helpers syntax introduced in the new ASP.NET Core 1.0
### In this topic
@@ -19,7 +19,7 @@ This topic contains the following sections:
## Adding Tag Helpers to scope of the view
-To add all {environment:ProductName} Tag Helpers to the current view scope, the @addTagHelper directive is used:
+To add all \{environment:ProductName\} Tag Helpers to the current view scope, the @addTagHelper directive is used:
```csharp
@using Infragistics.Web.Mvc
@@ -143,5 +143,5 @@ and by using Tag Helpers:
```
## Related Content
-- [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html)
+- [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html)
- [Adding Controls to an MVC Project](../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx)
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/using-igniteui-controls-in-aspnet-core-project.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/using-igniteui-controls-in-aspnet-core-project.mdx
index 410a09c9cd..a58a999a9f 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/using-igniteui-controls-in-aspnet-core-project.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/using-igniteui-controls-in-aspnet-core-project.mdx
@@ -1,13 +1,13 @@
---
-title: "Using {environment:ProductNameASPNETCore}"
+title: "Using {environment:ProductNameASPNETCore}"
slug: mvc-aspnet-core3
---
-# Using {environment:ProductNameASPNETCore}
+# Using \{environment:ProductNameASPNETCore\}
## Topic Overview
-This topic explains how to get started with {environment:ProductNameASPNETCore}™ components in an ASP.NET Core Web Application built for .NET 7.
+This topic explains how to get started with \{environment:ProductNameASPNETCore\}™ components in an ASP.NET Core Web Application built for .NET 7.
### In this topic
@@ -23,19 +23,19 @@ This topic contains the following sections:
With the ASP.NET Core most modules are now wrapped as NuGet packages. This allows you to retrieve and use only the specific modules you need for your application, without having to depend on a common assembly. All dependencies of the specific module will be restored out of the box.
-As such our new {environment:ProductNameASPNETCore} built on top of ASP.NET Core will also ship as a NuGet package. When you are installing the product make sure to include the NuGet packages module that will create a local feed for you to install the required packages from. For more information, please refer to the topic: [Using {environment:ProductName} NuGet packages](/general-and-getting-started/using-ignite-ui-nuget-packages.mdx).
+As such our new \{environment:ProductNameASPNETCore\} built on top of ASP.NET Core will also ship as a NuGet package. When you are installing the product make sure to include the NuGet packages module that will create a local feed for you to install the required packages from. For more information, please refer to the topic: [Using \{environment:ProductName\} NuGet packages](/general-and-getting-started/using-ignite-ui-nuget-packages.mdx).
Control's declaration follows the same syntax as the previous MVC versions. You can refer to the following topic for more information and examples: [Adding Controls to an MVC Project](../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx)
### Using online private feed
-You can also install Infragistics Web MVC NuGet package using the Infragistics hosted NuGet server. Checkout [Installing {environment:ProductNameMVC} packages from the online private feed](../01_General-and-Getting-Started/18_Using_Ignite_UI_NuGet_Packages.mdx#privateFeedInstallation) topic for more information.
+You can also install Infragistics Web MVC NuGet package using the Infragistics hosted NuGet server. Checkout [Installing \{environment:ProductNameMVC\} packages from the online private feed](../01_General-and-Getting-Started/18_Using_Ignite_UI_NuGet_Packages.mdx#privateFeedInstallation) topic for more information.
## Configuring the igUpload Middleware for file upload handling
In the old ASP.NET in order to handle more robust file uploading capabilities as multiple file uploads, large file uploads and reporting of the progress of an upload you would have to implement an HttpModule and/or HttpHandler in order to plug into the HTTP Request process.
ASP.NET Core introduces a new request pipeline built around a new middleware definition.
-The {environment:ProductNameASPNETCore} file upload fully utilizes the new middleware definition model and can be directly plugged into the pipeline.
+The \{environment:ProductNameASPNETCore\} file upload fully utilizes the new middleware definition model and can be directly plugged into the pipeline.
There are two middleware modules - one for handling uploads and one for receiving commands from the client and returning status feedback to the client.
In order to add them to the pipeline they need to be include in the Configure method of the Startup.cs class before the MVC module.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/understanding-infragistics-word-library/word-understanding-infragistics-word-library.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/understanding-infragistics-word-library/word-understanding-infragistics-word-library.mdx
index 599003fb0f..c8aa873375 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/understanding-infragistics-word-library/word-understanding-infragistics-word-library.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/understanding-infragistics-word-library/word-understanding-infragistics-word-library.mdx
@@ -4,6 +4,7 @@ slug: word-understanding-infragistics-word-library
---
# Understanding Infragistics Word Library
+
The topics in this section will give you a better idea of why you would want to use Word Library in your applications.
Click the links below to gain an overview of the Word Library.
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/using-infragistics-word-library/word-headers-footers-and-page-numbers.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/using-infragistics-word-library/word-headers-footers-and-page-numbers.mdx
index 27ca572ebd..c7b15bcf1b 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/using-infragistics-word-library/word-headers-footers-and-page-numbers.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/using-infragistics-word-library/word-headers-footers-and-page-numbers.mdx
@@ -4,6 +4,7 @@ slug: word-headers-footers-and-page-numbers
---
# Headers Footers and Page Numbers
+
Using the Infragistics® Word library you can create headers and footers that may be as simple as a document title and a page number to images, multiple paragraphs, tables and hyperlinks.
The following screenshots depicts a Word document created with text and image in the `Header`:
diff --git a/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/word-infragistics-word-library.mdx b/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/word-infragistics-word-library.mdx
index 178968e93d..87c4a2a377 100644
--- a/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/word-infragistics-word-library.mdx
+++ b/docs/jquery/src/content/en/topics/asp-net-mvc/word-library/word-infragistics-word-library.mdx
@@ -4,6 +4,7 @@ slug: word-infragistics-word-library
---
# Infragistics Word Library
+
This section contains valuable information about Word Library, ranging from what the Word Library does and why you would want to use it in your application, to step-by-step procedures on how to accomplish a common task.
Click the links below to access important information about the Word Library.
@@ -15,7 +16,7 @@ In this section you'll find any information that will help you to better underst
In this section, you'll find short, useful topics with sample code snippets that demonstrate how to perform specific tasks with the Word Library.
## [Word API Overview](Word-API-Overview.html "api overview for Word Library")
-This topic lists the namespaces and classes that you will be working with while programming with the Word Library. The namespaces and classes listed in this topic link conveniently into the "API Reference Guide" section of the {environment:ProductName} help.
+This topic lists the namespaces and classes that you will be working with while programming with the Word Library. The namespaces and classes listed in this topic link conveniently into the "API Reference Guide" section of the \{environment:ProductName\} help.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/accessibility-compliance.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/accessibility-compliance.mdx
index 4375146d46..aad91610cb 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/accessibility-compliance.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/accessibility-compliance.mdx
@@ -5,7 +5,6 @@ slug: igbulletgraph-accessibility-compliance
# Accessibility Compliance (igBulletGraph)
-
## Topic Overview
#### Purpose
@@ -25,7 +24,7 @@ The following topics are prerequisites to understanding this topic:
#### Introduction
-All of the {environment:ProductName}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. The table below contains the specific rules of Subpart 1194.22 that pertain to the control. Also, detailed is how the igBulletGraph control complies with each of these rules.
+All of the \{environment:ProductName\}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. The table below contains the specific rules of Subpart 1194.22 that pertain to the control. Also, detailed is how the igBulletGraph control complies with each of these rules.
In some cases, to meet the requirements of each accessibility rule, you may need to interact with the control by setting a specific property, but in other cases, the control performs these tasks for you.
@@ -47,7 +46,7 @@ Rules | Rule text | How we comply
The following topic provides additional information related to this topic.
-- [Accessibility Compliance](//general-and-getting-started/accessibility-compliance.mdx): This topic provides reference information for the accessibility compliance of all controls in the {environment:ProductName} product.
+- [Accessibility Compliance](//general-and-getting-started/accessibility-compliance.mdx): This topic provides reference information for the accessibility compliance of all controls in the \{environment:ProductName\} product.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/to-an-html-page.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/to-an-html-page.mdx
index 224ea9a6b8..85ae9387ec 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/to-an-html-page.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/to-an-html-page.mdx
@@ -2,6 +2,9 @@
title: "Adding igBulletGraph to an HTML Page"
slug: igbulletgraph-adding-to-an-html-page
---
+
+# Adding igBulletGraph to an HTML Page
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Adding igBulletGraph to an HTML Page
@@ -49,11 +52,11 @@ The following table summarizes the requirements for using the `igBulletGraph` co
| | | |
| --- | --- | --- |
| Required Resources | Description | What you need to do… |
-| jQuery and jQuery UI JavaScript resources | {environment:ProductName}™ is built on top of the following frameworks: [jQuery](http://jquery.com/) [jQuery UI](http://jqueryui.com/) | Add script references to both libraries in the `` section of your page. |
-| General *igBulletGraph* JavaScript Resources | The *igBulletGraph* control depends on functionality distributed across several files in the {environment:ProductName} Library. You can load the required resources in one of the following ways: Use the Infragistics® Loader (*igLoader*™). You only need to include a script reference to *igLoader* on your page. Load the required resources manually. You need to use the dependencies listed in the table below. Load the two combined files, containing the logic for all data visualization controls from the {environment:ProductName} package - *infragistics.core.js*, *infragistics.dv.js* and *infragistics.encoding.js* (optional). The following table lists the {environment:ProductName} library dependencies related to the *igBulletGraph* control. These resources need to be referred to explicitly if you chose not to use *igLoader* or the combined files. JS Resource | Description |
-| *infragistics.util.js*, *infragistics.util.jquery.js* | {environment:ProductName} utilities | |
+| jQuery and jQuery UI JavaScript resources | \{environment:ProductName\}™ is built on top of the following frameworks: [jQuery](http://jquery.com/) [jQuery UI](http://jqueryui.com/) | Add script references to both libraries in the `` section of your page. |
+| General *igBulletGraph* JavaScript Resources | The *igBulletGraph* control depends on functionality distributed across several files in the \{environment:ProductName\} Library. You can load the required resources in one of the following ways: Use the Infragistics® Loader (*igLoader*™). You only need to include a script reference to *igLoader* on your page. Load the required resources manually. You need to use the dependencies listed in the table below. Load the two combined files, containing the logic for all data visualization controls from the \{environment:ProductName\} package - *infragistics.core.js*, *infragistics.dv.js* and *infragistics.encoding.js* (optional). The following table lists the \{environment:ProductName\} library dependencies related to the *igBulletGraph* control. These resources need to be referred to explicitly if you chose not to use *igLoader* or the combined files. JS Resource | Description |
+| *infragistics.util.js*, *infragistics.util.jquery.js* | \{environment:ProductName\} utilities | |
| *infragistics.ext_core.js*, *infragistics.ext_collections.js*, *infragistics.ext_ui.js*, *infragistics.dv_jquerydom.js*, *infragistics.dv_core.js*, *infragistics.dv_geometry.js* A shared library for data visualization components | | |
-| *infragistics.ui.widget.js* | Base igWidget for all {environment:ProductName} widgets. | |
+| *infragistics.ui.widget.js* | Base igWidget for all \{environment:ProductName\} widgets. | |
| *infragistics.bulletgraph.js* | The *igBulletGraph* control | |
| *infragistics.ui.bulletgraph.js* | The *igBulletGraph* widget | |
@@ -335,4 +338,4 @@ The following topics provide additional information related to this topic.
The following sample provides additional information related to this topic.
-- [Basic Configuration]({environment:SamplesUrl}/bullet-graph/basic-configuration): This sample demonstrates a simple configuration of the `igBulletGraph` control.
\ No newline at end of file
+- [Basic Configuration](\{environment:SamplesUrl\}/bullet-graph/basic-configuration): This sample demonstrates a simple configuration of the `igBulletGraph` control.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/using-the-mvc-helper.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/using-the-mvc-helper.mdx
index 8fed8bd5cd..5494280611 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/using-the-mvc-helper.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/adding/using-the-mvc-helper.mdx
@@ -2,6 +2,9 @@
title: "Adding igBulletGraph to an ASP.NET MVC application"
slug: igbulletgraph-adding-using-the-mvc-helper
---
+
+# Adding igBulletGraph to an ASP.NET MVC application
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Adding igBulletGraph to an ASP.NET MVC application
@@ -24,7 +27,7 @@ The following table lists the concepts and topics required as a prerequisite to
- ASP.NET MVC HTML Helpers
- Topics
- - [Adding Controls to an MVC Project](../../../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx): This topic explains how to get started with {environment:ProductName}™ components in an ASP.NET MVC application.
+ - [Adding Controls to an MVC Project](../../../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx): This topic explains how to get started with \{environment:ProductName\}™ components in an ASP.NET MVC application.
- [*igBulletGraph* Overview](/igbulletgraph-overview.mdx): This topic provides conceptual information about the `igBulletGraph` control including its main features, minimum requirements, and user functionality.
@@ -149,7 +152,7 @@ Add the ASP.NET MVC helper to the body of your ASP.NET page.
**2. Instantiate the *igBulletGraph* control** configuring its basic rendering options.
-Instantiate the `igBulletGraph` control. As with all {environment:ProductNameMVC} controls, you must call the Render method to render the HTML and JavaScript to the View.
+Instantiate the `igBulletGraph` control. As with all \{environment:ProductNameMVC\} controls, you must call the Render method to render the HTML and JavaScript to the View.
**In ASPX:**
@@ -287,7 +290,7 @@ The following topics provide additional information related to this topic.
The following sample provides additional information related to this topic.
-- [MVC Initialization]({environment:SamplesUrl}/bullet-graph/mvc-initialization): This sample demonstrates how to use the ASP.NET MVC helper for the bullet graph.
+- [MVC Initialization](\{environment:SamplesUrl\}/bullet-graph/mvc-initialization): This sample demonstrates how to use the ASP.NET MVC helper for the bullet graph.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/api-links.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/api-links.mdx
index 8bcb6aa0d1..df6a36c7c0 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/api-links.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/api-links.mdx
@@ -2,6 +2,9 @@
title: "jQuery and MVC API Links (igBulletGraph)"
slug: igbulletgraph-api-links
---
+
+# jQuery and MVC API Links (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
#jQuery and MVC API Links (igBulletGraph)
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/comparative-ranges.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/comparative-ranges.mdx
index 66bfedf1e0..d1aae03fa3 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/comparative-ranges.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/comparative-ranges.mdx
@@ -2,6 +2,9 @@
title: "Configuring Comparative Ranges (igBulletGraph)"
slug: igbulletgraph-configuring-comparative-ranges
---
+
+# Configuring Comparative Ranges (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Comparative Ranges (igBulletGraph)
@@ -262,7 +265,7 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Range Settings]({environment:SamplesUrl}/bullet-graph/range-settings): This sample demonstrates setting comparative ranges in the `igBulletGraph` control.
+- [Range Settings](\{environment:SamplesUrl\}/bullet-graph/range-settings): This sample demonstrates setting comparative ranges in the `igBulletGraph` control.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/scale/the-scale.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/scale/the-scale.mdx
index 536c7ba8f3..329f87b31c 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/scale/the-scale.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/scale/the-scale.mdx
@@ -2,6 +2,9 @@
title: "Configuring the Scale (igBulletGraph)"
slug: igbulletgraph-configuring-the-scale
---
+
+# Configuring the Scale (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring the Scale (igBulletGraph)
@@ -271,7 +274,7 @@ Setting the minimum and maximum values implicitly defines all values within the

-Having the scales’ range defined also enables the positioning of the other value-based visual elements on the scale, namely the performance bar, comparative ranges, comparative marker, and the performance bar. Note that because these elements are value-based, when the scale’s range changes (i.e. when either its minimum or maximum value (or both) changes), these visual elements are re-positioned spatially together with the scale’s values keeping their position on the scale. (To see this effect in action, refer to the [Range Settings]({environment:SamplesUrl}/bullet-graph/range-settings) sample.)
+Having the scales’ range defined also enables the positioning of the other value-based visual elements on the scale, namely the performance bar, comparative ranges, comparative marker, and the performance bar. Note that because these elements are value-based, when the scale’s range changes (i.e. when either its minimum or maximum value (or both) changes), these visual elements are re-positioned spatially together with the scale’s values keeping their position on the scale. (To see this effect in action, refer to the [Range Settings](\{environment:SamplesUrl\}/bullet-graph/range-settings) sample.)
### Property settings
@@ -750,9 +753,9 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Tick Marks Settings]({environment:SamplesUrl}/bullet-graph/tick-marks-settings) This sample demonstrates the supported tickmarks configuration of the `igBulletGraph` control.
+- [Tick Marks Settings](\{environment:SamplesUrl\}/bullet-graph/tick-marks-settings) This sample demonstrates the supported tickmarks configuration of the `igBulletGraph` control.
-- [Scale Labeling Settings]({environment:SamplesUrl}/bullet-graph/scale-labeling-settings): This sample demonstrates the supported scale labeling configurations of the `igBulletGraph` control.
+- [Scale Labeling Settings](\{environment:SamplesUrl\}/bullet-graph/scale-labeling-settings): This sample demonstrates the supported scale labeling configurations of the `igBulletGraph` control.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-background.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-background.mdx
index e6f5afb5ba..615a24ee5b 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-background.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-background.mdx
@@ -2,6 +2,9 @@
title: "Configuring the Background (igBulletGraph)"
slug: igbulletgraph-configuring-the-background
---
+
+# Configuring the Background (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring the Background (igBulletGraph)
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-comparative-marker.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-comparative-marker.mdx
index ab57520e97..dad9ffc95b 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-comparative-marker.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-comparative-marker.mdx
@@ -2,6 +2,9 @@
title: "Configuring the Comparative Marker (igBulletGraph)"
slug: igbulletgraph-configuring-the-comparative-marker
---
+
+# Configuring the Comparative Marker (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring the Comparative Marker (igBulletGraph)
@@ -241,9 +244,9 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Performance Bar Settings]({environment:SamplesUrl}/bullet-graph/performance-bar-settings): This sample demonstrates configuring the performance (actual value) bar, the comparative measure (target value) marker, and the dimension of the scale of the `igBulletGraph` control.
+- [Performance Bar Settings](\{environment:SamplesUrl\}/bullet-graph/performance-bar-settings): This sample demonstrates configuring the performance (actual value) bar, the comparative measure (target value) marker, and the dimension of the scale of the `igBulletGraph` control.
-- [Basic Configuration]({environment:SamplesUrl}/bullet-graph/basic-configuration): This sample demonstrates a simple configuration of the `igBulletGraph` control.
+- [Basic Configuration](\{environment:SamplesUrl\}/bullet-graph/basic-configuration): This sample demonstrates a simple configuration of the `igBulletGraph` control.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-performance-bar.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-performance-bar.mdx
index 6940de5d6f..ef82fcd1b1 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-performance-bar.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-performance-bar.mdx
@@ -2,6 +2,9 @@
title: "Configuring the Performance Bar (igBulletGraph)"
slug: igbulletgraph-configuring-the-performance-bar
---
+
+# Configuring the Performance Bar (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring the Performance Bar (igBulletGraph)
@@ -233,7 +236,7 @@ This topic explains, with code examples, how to configure the comparative measur
The following samples provide additional information related to this topic.
-- [Performance Bar Settings]({environment:SamplesUrl}/bullet-graph/performance-bar-settings): This sample demonstrates configuring the performance (actual value) bar, the comparative measure (target value) marker, and the dimension of the scale of the `igBulletGraph` control.
+- [Performance Bar Settings](\{environment:SamplesUrl\}/bullet-graph/performance-bar-settings): This sample demonstrates configuring the performance (actual value) bar, the comparative measure (target value) marker, and the dimension of the scale of the `igBulletGraph` control.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-tooltips.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-tooltips.mdx
index 31f137fcb5..22992804b9 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-tooltips.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-tooltips.mdx
@@ -2,6 +2,9 @@
title: "Configuring the Tooltips (igBulletGraph)"
slug: igbulletgraph-configuring-the-tooltips
---
+
+# Configuring the Tooltips (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring the Tooltips (igBulletGraph)
@@ -372,7 +375,7 @@ While the first `igBulletGraph` used for visualizing the Development Task and ha
In the sample's context, even though these tasks are executed simultaneously at the course of three weeks, initially more time has been spent on development. This is demonstrated by the progress bars’ placement amongst the three different ranges (“Low, “Medium” and “High”), that represent the level of confidence for delivering the needed results.
## Related Content
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-visual-elements.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-visual-elements.mdx
index 0c645e976d..d701d48cac 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-visual-elements.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/elements/the-visual-elements.mdx
@@ -6,7 +6,6 @@ slug: igbulletgraph-configuring-the-visual-elements
# Configuring the Visual Elements (igBulletGraph)
-
## In This Group of Topics
### Introduction
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/the-orientation-and-direction.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/the-orientation-and-direction.mdx
index d0b603a413..afba1bae0d 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/the-orientation-and-direction.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/configuring/the-orientation-and-direction.mdx
@@ -2,6 +2,9 @@
title: "Configuring the Orientation and Direction (igBulletGraph)"
slug: igbulletgraph-configuring-the-orientation-and-direction
---
+
+# Configuring the Orientation and Direction (igBulletGraph)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring the Orientation and Direction (igBulletGraph)
@@ -198,7 +201,7 @@ $('#igBulletGraph').igBulletGraph({
The following samples provide additional information related to this topic.
-- [Vertical Orientation]({environment:SamplesUrl}/bullet-graph/vertical-orientation): This sample demonstrates how to change the orientation of the bullet graph and how to invert the scale.
+- [Vertical Orientation](\{environment:SamplesUrl\}/bullet-graph/vertical-orientation): This sample demonstrates how to change the orientation of the bullet graph and how to invert the scale.
diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/igbulletgraph.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/igbulletgraph.mdx
index a3737e6caa..da3017b809 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/igbulletgraph.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/igbulletgraph.mdx
@@ -9,7 +9,7 @@ slug: igbulletgraph
The topics in this group cover the `igBulletGraph`™ control and its use.
-The `igBulletGraph` control is an {environment:ProductName}™ control which allows for visualizing data in the form of a bullet graph. Linear by design, it provides a simple and concise view of a primary measure or measures compared against a scale and, optionally, some other measure.
+The `igBulletGraph` control is an \{environment:ProductName\}™ control which allows for visualizing data in the form of a bullet graph. Linear by design, it provides a simple and concise view of a primary measure or measures compared against a scale and, optionally, some other measure.

diff --git a/docs/jquery/src/content/en/topics/controls/igbulletgraph/overview.mdx b/docs/jquery/src/content/en/topics/controls/igbulletgraph/overview.mdx
index 8bcd8e35b4..66caa5c135 100644
--- a/docs/jquery/src/content/en/topics/controls/igbulletgraph/overview.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igbulletgraph/overview.mdx
@@ -2,6 +2,9 @@
title: "igBulletGraph Overview"
slug: igbulletgraph-overview
---
+
+# igBulletGraph Overview
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igBulletGraph Overview
@@ -50,7 +53,7 @@ This topic contains the following sections:
#### igBulletGraph summary
-The `igBulletGraph` control is an **{environment:ProductName}**™ control which allows for visualizing data in the form of a bullet graph. Linear by design, it provides a simple and concise view of a primary measure or measures compared against a scale and, optionally, some other measure.
+The `igBulletGraph` control is an **\{environment:ProductName\}**™ control which allows for visualizing data in the form of a bullet graph. Linear by design, it provides a simple and concise view of a primary measure or measures compared against a scale and, optionally, some other measure.

@@ -71,7 +74,7 @@ Each of the [visual elements](./00_igBulletGraph_Overview.mdx#configurable-visua
### Animated transitions
-The igBulletGraph control provides built-in support for animation by its property. The animation effect occurs on loading the control as well as when the value of any of its properties is changed. By default, animated transitions are disabled. Providing a value in milliseconds for the transitionDuration property of the control determines the timeframe for swiping the control into view by smoothly visualizing all its visual elements through a slide effect (from bottom-left to top-right). Setting the value to 0 disables the animated transition. For a sample, demonstrating the animation transition effect, see the [Animated Transitions]({environment:SamplesUrl}/bullet-graph/animated-transitions) sample.
+The igBulletGraph control provides built-in support for animation by its property. The animation effect occurs on loading the control as well as when the value of any of its properties is changed. By default, animated transitions are disabled. Providing a value in milliseconds for the transitionDuration property of the control determines the timeframe for swiping the control into view by smoothly visualizing all its visual elements through a slide effect (from bottom-left to top-right). Setting the value to 0 disables the animated transition. For a sample, demonstrating the animation transition effect, see the [Animated Transitions](\{environment:SamplesUrl\}/bullet-graph/animated-transitions) sample.
### Support for tooltips
@@ -589,7 +592,7 @@ The following picture demonstrates a `igBulletGraph` displayed with default sett
## Requirements
-The `igBulletGraph` control is a jQuery UI widget and, therefore, depends on the jQuery and jQuery UI libraries. References to these resources are needed nevertheless, in spite of the use of pure jQuery or {environment:ProductNameMVC}. The *Infragistics.Web.Mvc* assembly is required when the control is used in the context of ASP.NET MVC.
+The `igBulletGraph` control is a jQuery UI widget and, therefore, depends on the jQuery and jQuery UI libraries. References to these resources are needed nevertheless, in spite of the use of pure jQuery or \{environment:ProductNameMVC\}. The *Infragistics.Web.Mvc* assembly is required when the control is used in the context of ASP.NET MVC.
In order for the bullet graph to display the performance value(s), the property has to be set.
@@ -616,9 +619,9 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Basic Configuration]({environment:SamplesUrl}/bullet-graph/basic-configuration): This sample demonstrates a simple configuration of the igBulletGraph control.
+- [Basic Configuration](\{environment:SamplesUrl\}/bullet-graph/basic-configuration): This sample demonstrates a simple configuration of the igBulletGraph control.
-- [Animated Transitions]({environment:SamplesUrl}/bullet-graph/animated-transitions): This sample demonstrates animated transitions between different sets of settings in the igBulletGraph control.
+- [Animated Transitions](\{environment:SamplesUrl\}/bullet-graph/animated-transitions): This sample demonstrates animated transitions between different sets of settings in the igBulletGraph control.
### Resource
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/annotations-and-interactions/datatooltip.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/annotations-and-interactions/datatooltip.mdx
index 6ac20acf7c..9f8d970bbd 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/annotations-and-interactions/datatooltip.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/annotations-and-interactions/datatooltip.mdx
@@ -1,6 +1,7 @@
---
title: "Chart Data Tooltip"
---
+
# Chart Data Tooltip
In {ProductName}, the data tooltip of the `igCategoryChart` displays values and titles of series as well as legend badges of series in a tooltip. In addition, it provides many configuration properties of the `igDataLegend` for filtering series rows and values columns, styling, and formatting values. This tooltip type updates while moving the mouse inside of the plot area of the `igCategoryChart`.
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/axis-labels.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/axis-labels.mdx
index baaeaebf5a..1732a941c0 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/axis-labels.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/axis-labels.mdx
@@ -3,7 +3,7 @@ title: "Configuring Axis Label"
slug: igcategorychart-axis-label
---
-# Configuring Axis Label
+# Configuring Axis Label
The igCategoryChart control allows you full control over configuring, formatting and styling the labels displayed on your chart. By default, you do not need to explicitly set the labels. The Category Chart will use the first appropriate string property that it finds within the data you provided and will use that for the labels.
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-axes.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-axes.mdx
index ad7d5c4beb..26b399d2e9 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-axes.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-axes.mdx
@@ -5,7 +5,6 @@ slug: categorychart-axes
# Axes
-
In the igCategoryChart control, an Axis provides base properties for specifying appearance of axis main lines, gridlines, tickmarks, titles, stripes, and axis labels.
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-configuring-axis-titles.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-configuring-axis-titles.mdx
index f5aef96088..3de4ced8be 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-configuring-axis-titles.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/axes/categorychart-configuring-axis-titles.mdx
@@ -4,6 +4,7 @@ slug: categorychart-configuring-axis-titles
---
# Axis Titles
+
The axis title feature of the igCategoryChart control allows you to add contextual information to the x and y axes of the chart.
### In this topic
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-accessibility-compliance.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-accessibility-compliance.mdx
index 65235cada9..497d51b524 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-accessibility-compliance.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-accessibility-compliance.mdx
@@ -5,7 +5,6 @@ slug: igcategorychart-accessibility-compliance
# Accessibility Compliance (igCategoryChart)
-
##Topic Overview
@@ -28,7 +27,7 @@ The following topics are prerequisite to understanding this topic:
### Introduction
-All of the {environment:ProductName}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also detailed is how the `igCategoryChart` control complies with each rule.
+All of the \{environment:ProductName\}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also detailed is how the `igCategoryChart` control complies with each rule.
To meet the requirements each accessibility rule, in some cases, you may need to interact with the control by to setting a specific property, but in other cases the control does the work for you.
@@ -55,4 +54,4 @@ The following table summarizes the accessibility compliance features of the igCa
The following topic provide additional information related to this topic.
-- [**Accessibility Compliance**](//general-and-getting-started/accessibility-compliance.mdx): Provides reference information for accessibility compliance of all {environment:ProductName} controls.
\ No newline at end of file
+- [**Accessibility Compliance**](//general-and-getting-started/accessibility-compliance.mdx): Provides reference information for accessibility compliance of all \{environment:ProductName\} controls.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-api-overivew.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-api-overivew.mdx
index 9642549d01..be3710db41 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-api-overivew.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-api-overivew.mdx
@@ -2,6 +2,9 @@
title: "jQuery and MVC API Reference Links (igCategoryChart)"
slug: categorychart-api-overview
---
+
+# jQuery and MVC API Reference Links (igCategoryChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# jQuery and MVC API Reference Links (igCategoryChart)
@@ -10,7 +13,7 @@ import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
## Topic Overview
### Purpose
-This topic provides links to the API documentation for jQuery and {environment:ProductNameMVC} class for `igCategoryChart`™ control.
+This topic provides links to the API documentation for jQuery and \{environment:ProductNameMVC\} class for `igCategoryChart`™ control.
### Required Background
@@ -25,7 +28,7 @@ The following topics are prerequisite to understanding this topic:
### Introduction
-The `igCategoryChart` is built as a jQuery UI widget with an accompanying {environment:ProductNameMVC}. For more information about each API, follow the links to the API documentation given below.
+The `igCategoryChart` is built as a jQuery UI widget with an accompanying \{environment:ProductNameMVC\}. For more information about each API, follow the links to the API documentation given below.
### API documents reference summary
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-datalegend.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-datalegend.mdx
index d0343d9991..dfa92d4064 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-datalegend.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-datalegend.mdx
@@ -1,6 +1,7 @@
---
title: "Data Legend"
---
+
# Data Legend
The `igDataLegend` is a component that works much like the `Legend`, but it shows values of series and provides many configuration properties for filtering series rows and values columns, styling and formatting values. This legend updates when moving the mouse inside of the plot area of the `igCategoryChart` and has a persistent state that remembers the last hovered point when the user's mouse pointer exits the plot area. It displays this content using a set of three type of rows and four types of columns.
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-overview.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-overview.mdx
index 14b01537fa..11231a6889 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-overview.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-overview.mdx
@@ -3,7 +3,7 @@ title: "Overview"
slug: categorychart-overview
---
-# Overview
+# Overview
### About igCategoryChart
diff --git a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-styling.mdx b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-styling.mdx
index b2b783cf52..296f0dcee2 100644
--- a/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-styling.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcategorychart/categorychart-styling.mdx
@@ -5,7 +5,6 @@ slug: categorychart-styling
# Styling igCategoryChart
-
## Topic Overview
@@ -22,7 +21,7 @@ This topic demonstrates how to apply styles and themes to the `igCategoryChart`
**Topics**
-- [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx): General information and a procedure for updating styles and themes in {environment:ProductName}™ library.
+- [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx): General information and a procedure for updating styles and themes in \{environment:ProductName\}™ library.
**External Resources**
@@ -62,9 +61,9 @@ The `igCategoryChart` uses the jQuery UI CSS Framework for the purposes of apply
To customize a theme, you can use the ThemeRoller tool. This jQuery UI tool facilitates the creation of custom themes that are compatible with the jQuery UI widgets. Many prebuilt themes are available for download and use in your website. The `igCategoryChart` control supports the use of ThemeRoller themes.
-Detailed information for using themes with {environment:ProductName} library is available in the [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) topic.
+Detailed information for using themes with \{environment:ProductName\} library is available in the [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) topic.
-Note: The base theme of {environment:ProductName} is not necessary for charts and you may safely omit it on pages only containing charts.
+Note: The base theme of \{environment:ProductName\} is not necessary for charts and you may safely omit it on pages only containing charts.
## Themes Summary
@@ -81,7 +80,7 @@ A summary of the `igCategoryChart` control’s available themes.
IG Theme
Path: `{IG CSS root}/themes/Infragistics/`
File: `infragistics.theme.css`
-
This theme defines general visual features for all {environment:ProductName} controls. Detailed information for using the IG theme is available in the Styling and Theming in {environment:ProductName} topic.
+
This theme defines general visual features for all \{environment:ProductName\} controls. Detailed information for using the IG theme is available in the Styling and Theming in \{environment:ProductName\} topic.
@@ -179,7 +178,7 @@ Demonstrate how to modify the default IG Chart styles with your preferred settin
1. Copy the default chart CSS file.
- **Copy the CSS file, with the default chart styles (`infragistics.ui.chart.css`), from the {environment:ProductName} installation folder to the themes folder of your web site or application.**
+ **Copy the CSS file, with the default chart styles (`infragistics.ui.chart.css`), from the \{environment:ProductName\} installation folder to the themes folder of your web site or application.**
For instance, if you have a folder `Content/themes` in your web site or application where keep the CSS files used by the application, then make a copy of the default chart CSS file mentioned above in `Content/themes/MyChartTheme/ig.ui.chart.custom.css`.
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/accessibility-compliance.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/accessibility-compliance.mdx
index 04b7a271ea..fe2734e039 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/accessibility-compliance.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/accessibility-compliance.mdx
@@ -5,14 +5,13 @@ slug: igcombo-accessibility-compliance
# Accessibility Compliance (igCombo)
-
##igCombo Accessibility Compliance
###Introduction
-All of the {environment:ProductName}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973.
+All of the \{environment:ProductName\}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973.
To meet the requirements each accessibility rule, in some cases, you may need to interact with the control by to setting a specific property, but in other cases the control does the work for you.
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/binding/cascading.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/binding/cascading.mdx
index 1184dc8a69..f1a52daa7a 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/binding/cascading.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/binding/cascading.mdx
@@ -5,7 +5,6 @@ slug: igcombo-cascading
# Creating Cascading igCombos
-
##Topic Overview
@@ -225,7 +224,7 @@ The following is the full code that was created for this sample to demonstrate w
The following samples provide additional information related to this topic.
-- [Cascading Combo]({environment:SamplesUrl}/combo/cascading-combos): This sample demonstrates three cascading `igCombo` controls.
+- [Cascading Combo](\{environment:SamplesUrl\}/combo/cascading-combos): This sample demonstrates three cascading `igCombo` controls.
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/binding/data-binding.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/binding/data-binding.mdx
index 6bb2f2fe27..fd1623d3c2 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/binding/data-binding.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/binding/data-binding.mdx
@@ -5,7 +5,6 @@ slug: igcombo-data-binding
# Binding igCombo to Data Overview
-
## Topic Overview
@@ -79,7 +78,7 @@ The following lists the supported data sources and some basic specifics for thei
## Binding to data sources to overview
-In most cases, you will use the `dataSource` or `dataSourceUrl` options of the `igCombo` to bind to data. This option provides your data to the `igDataSource` which can handle the various supported data formats. The one main exception to using this option is when the `igCombo` is instantiated using a SELECT element. The `igCombo` will inherit the data and options of its base SELECT element in this case. In ASP.NET MVC, supplying an `IQueryable` to the {environment:ProductNameMVC} facilitates the serialization of the data from the server and passes it to the client with the View. Once the page is received by the browser, the `dataSource` option of the `igCombo` is set for client-side operation.
+In most cases, you will use the `dataSource` or `dataSourceUrl` options of the `igCombo` to bind to data. This option provides your data to the `igDataSource` which can handle the various supported data formats. The one main exception to using this option is when the `igCombo` is instantiated using a SELECT element. The `igCombo` will inherit the data and options of its base SELECT element in this case. In ASP.NET MVC, supplying an `IQueryable` to the \{environment:ProductNameMVC\} facilitates the serialization of the data from the server and passes it to the client with the View. Once the page is received by the browser, the `dataSource` option of the `igCombo` is set for client-side operation.
### Class diagram for binding to data sources
@@ -249,7 +248,7 @@ Following is a conceptual overview of the process:
**d. (ASP.NET MVC) Call DataBind() and Render().**
- When instantiating the {environment:ProductNameMVC} `Combo`, call the DataBind method to bind to the data and call the Render method last after all other options have been configured. This is the method that renders the HTML and JavaScript necessary to instantiate the `igCombo` on the client
+ When instantiating the \{environment:ProductNameMVC\} `Combo`, call the DataBind method to bind to the data and call the Render method last after all other options have been configured. This is the method that renders the HTML and JavaScript necessary to instantiate the `igCombo` on the client
**In ASPX:**
@@ -272,7 +271,7 @@ Online Combo binding examples
The combo easily binds to a JavaScript array or JSON data. This sample contains a basic example of client-side binding.
### HTML Binding
@@ -280,14 +279,14 @@ The combo easily binds to a JavaScript array or JSON data. This sample contains
igCombo can bind directly to an HTML SELECT element.
## Related Topics
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/binding/to-data.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/binding/to-data.mdx
index 570d01fa19..217f61ab15 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/binding/to-data.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/binding/to-data.mdx
@@ -5,20 +5,19 @@ slug: igcombo-binding-to-data
# Binding igCombo to Data
-
##In This Group of Topics
### Introduction
-The topics in this group explain how to bind {environment:ProductName}® combo control to data.
+The topics in this group explain how to bind \{environment:ProductName\}® combo control to data.
### Topics
- [Binding igCombo to Data Overview](/igcombo-data-binding.mdx): This topic discusses the different ways to data bind the `igCombo` control as well as other details related to data binding.
-- [Binding Cascading igCombo Controls to Data](/igcombo-cascading.mdx): The topics in this group explain how to bind cascading {environment:ProductName} combo control to data.
+- [Binding Cascading igCombo Controls to Data](/igcombo-cascading.mdx): The topics in this group explain how to bind cascading \{environment:ProductName\} combo control to data.
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/angularjs-support.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/angularjs-support.mdx
index 6f33ab6fd1..d4e8f20520 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/angularjs-support.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/angularjs-support.mdx
@@ -21,18 +21,18 @@ This topic contains the following sections:
The following is a preview of the final result.
### Requirements
In order to run this sample, you need to have:
-- The required {environment:ProductName} JavaScript and CSS files
-- The {environment:ProductFamilyName} AngularJS directives
+- The required \{environment:ProductName\} JavaScript and CSS files
+- The \{environment:ProductFamilyName\} AngularJS directives
### Details
In the sample we have listed 20 products. Using the AngularJS ng-repeat we loop through the data source records and for each of these products we create an input and bind it to the ProductName. In this way when we edit something in the input, the change is immediately reflected in the data source. Above the product names there are two `igCombo` controls with similar options. They are bound to the data source with the products. Also they are bound to a value from the controller (combo.value1) which stores the selected product id. On the left side of the `igCombo` controls we have an input which is bound to the same value (combo.value1). We can edit the inputs holding the product names, select a value from any `igCombo` or edit the selected product id - the two-way binding will update the `igCombo` controls and the input with the corresponding values instantly.
### Related Content
The following topics provide additional information related to this topic:
-- [Using {environment:ProductFamilyName} with AngularJS](../../../10_AngularJS Directives/00_Using_Ignite_UI_with_AngularJS.mdx) - This topic contains an overview using the {environment:ProductFamilyName} directives for AngularJS.
-- [Conditional and Advanced Templating with AngularJS](../../../10_AngularJS Directives/01_Conditional_and_Advanced_Templating_with_AngularJS.mdx) - This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the {environment:ProductFamilyName} directives for AngularJS.
\ No newline at end of file
+- [Using \{environment:ProductFamilyName\} with AngularJS](../../../10_AngularJS Directives/00_Using_Ignite_UI_with_AngularJS.mdx) - This topic contains an overview using the \{environment:ProductFamilyName\} directives for AngularJS.
+- [Conditional and Advanced Templating with AngularJS](../../../10_AngularJS Directives/01_Conditional_and_Advanced_Templating_with_AngularJS.mdx) - This topic explains how to use conditional templates and use advanced templating methods to customize controls created with the \{environment:ProductFamilyName\} directives for AngularJS.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/asp-net-mvc.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/asp-net-mvc.mdx
index 54e22e045d..d89d616f12 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/asp-net-mvc.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/asp-net-mvc.mdx
@@ -10,11 +10,11 @@ This topic shows how to use the igCombo in a basic ASP.NET MVC scenario.
### Purpose
-The {environment:ProductNameMVC} Combo is instantiated in a View. In addition, the `ComboDataSourceAction` attribute is used to process the remote request for the collection of employees as well as process the remote filtering parameters. Finally, you can see how the combo is used in a form to update a field in the model.
+The \{environment:ProductNameMVC\} Combo is instantiated in a View. In addition, the `ComboDataSourceAction` attribute is used to process the remote request for the collection of employees as well as process the remote filtering parameters. Finally, you can see how the combo is used in a form to update a field in the model.
#### Concepts
-- Using {environment:ProductNameMVC} Combo
+- Using \{environment:ProductNameMVC\} Combo
### In this topic
@@ -41,7 +41,7 @@ The following screenshot is a preview of the final result.
To complete the procedure, you need an ASP.NET MVC Project with the following:
-- The required {environment:ProductName} JavaScript and CSS files
+- The required \{environment:ProductName\} JavaScript and CSS files
- The Infragistics.Web.Mvc.dll assembly referenced
### Overview
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-auto-suggest.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-auto-suggest.mdx
index 23235e2f2e..375365919e 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-auto-suggest.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-auto-suggest.mdx
@@ -2,6 +2,9 @@
title: "Configuring Auto-Suggest (igCombo)"
slug: igcombo-configure-auto-suggest
---
+
+# Configuring Auto-Suggest (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Auto-Suggest (igCombo)
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-remote-filtering.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-remote-filtering.mdx
index b4d04d9d79..9a54cc45dc 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-remote-filtering.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-remote-filtering.mdx
@@ -2,6 +2,9 @@
title: "Configuring Remote Filtering (igCombo)"
slug: igcombo-configure-remote-filtering
---
+
+# Configuring Remote Filtering (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Remote Filtering (igCombo)
@@ -63,7 +66,7 @@ The table below lists the configurable behaviors of the `igCombo` control.
| Configurable behavior | Behavior details | Configuration properties |
| --- | --- | --- |
| Remote filtering with OData | OData provides a way to filter the combo when the data source has a very large amount of records. The igCombo control internally handles sending the proper requests for filtered results from the service. | |
-| Remote filtering with the ASP.NET MVC | The {environment:ProductNameMVC} Combo provides the API to setup server-side filtering when binding to collections of business objects. | ComboDataSourceAction |
+| Remote filtering with the ASP.NET MVC | The \{environment:ProductNameMVC\} Combo provides the API to setup server-side filtering when binding to collections of business objects. | ComboDataSourceAction |
##Configure OData list filtering
@@ -132,7 +135,7 @@ Following is a conceptual overview of the process:
2. Configure the data source
- Set the dataSource option to the URL of the OData service. In the case of the {environment:ProductName} OData service, JSONP is used to avoid cross-domain restrictions of the browser. This is format is requested by passing a callback parameter in the OData request URI.
+ Set the dataSource option to the URL of the OData service. In the case of the \{environment:ProductName\} OData service, JSONP is used to avoid cross-domain restrictions of the browser. This is format is requested by passing a callback parameter in the OData request URI.
**In HTML:**
@@ -148,7 +151,7 @@ Following is a conceptual overview of the process:
3. Configure the response data key
- The data is returned from OData in a specific schema. If you are accessing an OData v1 service, this key is typically ‘d’. The {environment:ProductName} service is OData v2 and the response key is ‘d.results’.
+ The data is returned from OData in a specific schema. If you are accessing an OData v1 service, this key is typically ‘d’. The \{environment:ProductName\} service is OData v2 and the response key is ‘d.results’.
**In HTML:**
@@ -232,9 +235,9 @@ $("#comboTarget").igCombo({
###ASP.NET MVC list filtering configuration details
-The {environment:ProductNameMVC} `Combo` primarily functions to render the necessary jQuery and HTML on the client while being able to configure the behaviors in C# or Visual Basic.NET.
+The \{environment:ProductNameMVC\} `Combo` primarily functions to render the necessary jQuery and HTML on the client while being able to configure the behaviors in C# or Visual Basic.NET.
-The other part of the {environment:ProductNameMVC} is to facilitate remote operations to the server. This is the case with `igCombo` control where you can decorate an `ActionResult` method with the `ComboDataSourceAction` attribute and the helper can facilitate the server-side querying of the data source and return the appropriate data to the client.
+The other part of the \{environment:ProductNameMVC\} is to facilitate remote operations to the server. This is the case with `igCombo` control where you can decorate an `ActionResult` method with the `ComboDataSourceAction` attribute and the helper can facilitate the server-side querying of the data source and return the appropriate data to the client.
###ASP.NET MVC list filtering configuration property settings
@@ -244,7 +247,7 @@ The table below maps the desired configuration to property settings. The propert
| In order to… | Use this property: | And set it to… |
| --- | --- | --- |
-| Configure remote filtering with the {environment:ProductNameMVC} helper | , , , , ComboDataSourceAction | IQueryable object, string URL to ComboDataSourceAction, remote, filter, Attribute used to decorate filtering request ActionResult method |
+| Configure remote filtering with the \{environment:ProductNameMVC\} helper | , , , , ComboDataSourceAction | IQueryable object, string URL to ComboDataSourceAction, remote, filter, Attribute used to decorate filtering request ActionResult method |
For detailed information about these properties, refer to their listing
@@ -258,7 +261,7 @@ in the property reference section:
#### Introduction
-This example shows how to enable remote filtering with the {environment:ProductNameMVC}. In this configuration, and action method is defined for data filtering operations. The `igCombo` control is bound to data on the server and when a filtering operation occurs on the client, the request for filtered data is sent to the action method.
+This example shows how to enable remote filtering with the \{environment:ProductNameMVC\}. In this configuration, and action method is defined for data filtering operations. The `igCombo` control is bound to data on the server and when a filtering operation occurs on the client, the request for filtered data is sent to the action method.
#### Requirements
@@ -266,7 +269,7 @@ To complete the procedure, you need the following:
- an ASP.NET MVC application
- `Infragistics.Web.Mvc.dll` assembly referenced in your project
-- A `Combo` control bound to data through the {environment:ProductNameMVC}
+- A `Combo` control bound to data through the \{environment:ProductNameMVC\}
#### Overview
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-selection.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-selection.mdx
index b6f81912d1..a9ed0f5953 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-selection.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configure-selection.mdx
@@ -2,6 +2,9 @@
title: "Configuring Selection (igCombo)"
slug: igcombo-configure-selection
---
+
+# Configuring Selection (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Selection (igCombo)
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configuring.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configuring.mdx
index 860e0dd57b..f44c2d723e 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configuring.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/configuring.mdx
@@ -5,13 +5,12 @@ slug: igcombo-configuring
# Configuring igCombo
-
##In This Group of Topics
### Introduction
-The topics in this group explain how to configure {environment:ProductName}® combo control.
+The topics in this group explain how to configure \{environment:ProductName\}® combo control.
### Topics
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/grouping.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/grouping.mdx
index 4efc2de5d4..8051d6432b 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/grouping.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/grouping.mdx
@@ -2,6 +2,9 @@
title: "Configuring Grouping (igCombo)"
slug: igCombo-grouping
---
+
+# Configuring Grouping (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Grouping (igCombo)
@@ -72,4 +75,4 @@ $(".selector").igCombo({
### Samples
The following samples provide additional information related to this topic.
-- [Grouping with header and footer templates]({environment:SamplesUrl}/combo/grouping):This sample demonstrates how grouping can be used with Header and Footer templates efficiently.
+- [Grouping with header and footer templates](\{environment:SamplesUrl\}/combo/grouping):This sample demonstrates how grouping can be used with Header and Footer templates efficiently.
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/knockoutjs-support.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/knockoutjs-support.mdx
index 0177b9a40b..101629e298 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/knockoutjs-support.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/knockoutjs-support.mdx
@@ -2,6 +2,9 @@
title: "Configuring Knockout Support (igCombo)"
slug: igcombo-knockoutjs-support
---
+
+# Configuring Knockout Support (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Knockout Support (igCombo)
@@ -206,7 +209,7 @@ Using the Knockout [`disabled`](http://knockoutjs.com/documentation/disable-bind
The following topics provide additional information related to this topic.
-- [Knockout Support (Editors)](../../igEditors/Config/02_Configuring Knockout Support (Editors).mdx): This topic explains how to configure {environment:ProductName} editor controls to bind to View-Model objects managed by the [Knockout library](http://knockoutjs.com/).
+- [Knockout Support (Editors)](../../igEditors/Config/02_Configuring Knockout Support (Editors).mdx): This topic explains how to configure \{environment:ProductName\} editor controls to bind to View-Model objects managed by the [Knockout library](http://knockoutjs.com/).
- [Migrating to the New Combo](../02_igCombo_Migrating_To_The_New_Combo.mdx#ko_changes): This topic aims to help with migration from old combo to the new one. The document includes the changes in the Knockout integration of the igCombo.
@@ -218,10 +221,10 @@ The following samples provide additional information related to this topic.
- The sample below demonstrates how to bind igCombo to data managed by KO data bindings. Binding an array to combo's drop-down and model property to the combo selected items is implemented.
->**Note:** The Knockout extensions do not work with the {environment:ProductNameMVC}.
+>**Note:** The Knockout extensions do not work with the \{environment:ProductNameMVC\}.
### Resources
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/load-on-demand.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/load-on-demand.mdx
index a243c56efe..a5531a44f1 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/load-on-demand.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/load-on-demand.mdx
@@ -2,6 +2,9 @@
title: "Configuring Load-on-Demand (igCombo)"
slug: igcombo-load-on-demand
---
+
+# Configuring Load-on-Demand (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Load-on-Demand (igCombo)
@@ -175,11 +178,11 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Load-on-Demand]({environment:SamplesUrl}/combo/load-on-demand):This sample demonstrates how to use the combo box load-on-demand and paging functionality using a remote OData data source.
+- [Load-on-Demand](\{environment:SamplesUrl\}/combo/load-on-demand):This sample demonstrates how to use the combo box load-on-demand and paging functionality using a remote OData data source.
-- [Virtualization]({environment:SamplesUrl}/combo/virtualization):This sample demonstrates how enabling UI virtualization allows the `igCombo` control to quickly and efficiently render large amounts of data in the combo.
+- [Virtualization](\{environment:SamplesUrl\}/combo/virtualization):This sample demonstrates how enabling UI virtualization allows the `igCombo` control to quickly and efficiently render large amounts of data in the combo.
-- [Filtering]({environment:SamplesUrl}/combo/filtering):This sample demonstrates how the dropdown list of the `igCombo` control can be filtered based off of the input value. The auto-suggest and auto-complete functionalities are also supported.
+- [Filtering](\{environment:SamplesUrl\}/combo/filtering):This sample demonstrates how the dropdown list of the `igCombo` control can be filtered based off of the input value. The auto-suggest and auto-complete functionalities are also supported.
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/optimize-performance.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/optimize-performance.mdx
index 9cfaf5fea8..95095d654b 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/optimize-performance.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/optimize-performance.mdx
@@ -2,6 +2,9 @@
title: "Optimizing Performance (igCombo)"
slug: igcombo-optimize-performance
---
+
+# Optimizing Performance (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Optimizing Performance (igCombo)
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/typescript-support.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/typescript-support.mdx
index f940c198ac..e4a03da8e0 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/configuring/typescript-support.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/configuring/typescript-support.mdx
@@ -29,8 +29,8 @@ The following screenshot is a preview of the final result.
### Requirements
In order to run this sample, you need to have:
-- The required {environment:ProductName} JavaScript and CSS files
-- The required {environment:ProductName} TypeScript definitions
+- The required \{environment:ProductName\} JavaScript and CSS files
+- The required \{environment:ProductName\} TypeScript definitions
### Overview
This topic takes you step-by-step toward creating a TypeScript class, data source and `igCombo`.
@@ -138,4 +138,4 @@ $(function () {
### Related Content
The following topic provides additional information related to this topic:
-- [Using {environment:ProductName} with TypeScript](Using-Ignite-UI-with-TypeScript.html) - This topic contains an overview for using the {environment:ProductName} type definitions for TypeScript.
\ No newline at end of file
+- [Using \{environment:ProductName\} with TypeScript](Using-Ignite-UI-with-TypeScript.html) - This topic contains an overview for using the \{environment:ProductName\} type definitions for TypeScript.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/getting-started.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/getting-started.mdx
index 6ea1f2acf8..35407850c2 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/getting-started.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/getting-started.mdx
@@ -5,7 +5,6 @@ slug: igcombo-getting-started
# Adding igCombo
-
##Topic Overview
@@ -19,8 +18,8 @@ The `igCombo`™ can be configured to run using jQuery or ASP.NET MVC. This help
You need to first read the following topics:
-- [Using JavaScript Resources in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
-- [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
+- [Using JavaScript Resources in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
+- [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
##Create a basic igCombo implementation
@@ -70,7 +69,7 @@ Following is a conceptual overview of the process:
```
- Instantiate the `igCombo`. In jQuery, you can use the document ready JavaScript event to instantiate the combo. In ASP.NET MVC, use the {environment:ProductNameMVC} to bind to an `IQueryable` datasource.
+ Instantiate the `igCombo`. In jQuery, you can use the document ready JavaScript event to instantiate the combo. In ASP.NET MVC, use the \{environment:ProductNameMVC\} to bind to an `IQueryable` datasource.
**In HTML:**
@@ -165,7 +164,7 @@ Following is a conceptual overview of the process:
**d. (ASP.NET MVC) Call Render().**
- When instantiating the {environment:ProductNameMVC} `Combo`, call the Render method last after all other options have been configured. This is the method that renders the HTML and JavaScript necessary to instantiate the `igCombo` on the client
+ When instantiating the \{environment:ProductNameMVC\} `Combo`, call the Render method last after all other options have been configured. This is the method that renders the HTML and JavaScript necessary to instantiate the `igCombo` on the client
**In ASPX:**
@@ -218,7 +217,7 @@ The following table lists the code examples provided below.
| --- | --- |
| Example | Description |
| Basic jQuery Implementation | Shows how to bind to data and set basic options in jQuery |
-| Basic ASP.NET MVC Implementation | Shows how to bind to data and set basic options using the {environment:ProductNameMVC} |
+| Basic ASP.NET MVC Implementation | Shows how to bind to data and set basic options using the \{environment:ProductNameMVC\} |
###Code Example: Basic jQuery implementation
@@ -262,7 +261,7 @@ The code below demonstrates how to create and configure the `igCombo` control us
###Code Example: Basic ASP.NET MVC implementation
-The code below demonstrates how to create and configure the {environment:ProductNameMVC} `Combo` control with the following parameters:
+The code below demonstrates how to create and configure the \{environment:ProductNameMVC\} `Combo` control with the following parameters:
| Property | Value |
@@ -311,8 +310,8 @@ public class DefaultController : Controller{
Following are some other topics you may find useful.
-- [Using JavaScript Resources in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
-- [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
+- [Using JavaScript Resources in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
+- [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/igcombo.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/igcombo.mdx
index 67cf83f166..6d28702d35 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/igcombo.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/igcombo.mdx
@@ -5,7 +5,6 @@ slug: igcombo-igcombo
# igCombo
-
##Introduction
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/jquery-and-asp-net-mvc-helper-api-links.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/jquery-and-asp-net-mvc-helper-api-links.mdx
index 7f7d8abfb5..6e1433f9d5 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/jquery-and-asp-net-mvc-helper-api-links.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/jquery-and-asp-net-mvc-helper-api-links.mdx
@@ -2,6 +2,9 @@
title: "jQuery and MVC API Links (igCombo)"
slug: igcombo-jquery-and-asp-net-mvc-helper-api-links
---
+
+# jQuery and MVC API Links (igCombo)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# jQuery and MVC API Links (igCombo)
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/keyboard-navigation.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/keyboard-navigation.mdx
index 55cadccdb3..a24b19562c 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/keyboard-navigation.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/keyboard-navigation.mdx
@@ -3,6 +3,8 @@ title: "Keyboard Navigation (igCombo)"
slug: igCombo-keyboard-navigation
---
+# Keyboard Navigation (igCombo)
+
#Keyboard Navigation (igCombo)
##Topic overview
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/known-limitations.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/known-limitations.mdx
index 15efb19d07..6890ca53bb 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/known-limitations.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/known-limitations.mdx
@@ -6,7 +6,6 @@ slug: igcombo-known-limitations
# Known Issues and Limitations (igCombo)
-
##Known Issues and Limitations Summary
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/migrating-to-the-new-combo.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/migrating-to-the-new-combo.mdx
index 2e02dd6e15..5089e806b6 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/migrating-to-the-new-combo.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/migrating-to-the-new-combo.mdx
@@ -2,6 +2,9 @@
title: "Migrating to the new combo"
slug: igcombo-migrating-to-the-new-combo
---
+
+# Migrating to the new combo
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Migrating to the new combo
@@ -56,7 +59,7 @@ dataBindOnOpen|Used to delay data binding to when the drop down is opened.|This
text|Used to set custom text in combo input on initialization|This option is not supported. To set initial selection use option [initialSelectedItems](#initialSelectedItems).
clearSelectionOnBlur|Used to preserve selected items on blur when the text input didn't match the selected items text.| This option is not supported.
valueKeyType textKeyType|Used to specify the data type behind the value/text data|These options are not supported. The type of value and text fields from the data source will be used.
-parentCombo cascadingDataSources parentComboKey|Used to setup cascading functionality|These options are not supported. Internal cascading functionality is no longer supported. It can be achieved through changing related combo data sources on current combo's selection changed event. [See sample]({environment:SamplesUrl}/combo/cascading-combos)
+parentCombo cascadingDataSources parentComboKey|Used to setup cascading functionality|These options are not supported. Internal cascading functionality is no longer supported. It can be achieved through changing related combo data sources on current combo's selection changed event. [See sample](\{environment:SamplesUrl\}/combo/cascading-combos)
*We tried hard to ensure behavioral parity between the old and new combo, but some things we could not complete for 15.1. If these behaviors are crucial to your solution, and you want to upgrade to 15.1, please contact us.
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/overview.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/overview.mdx
index e26467eadd..ff166b314b 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/overview.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/overview.mdx
@@ -5,7 +5,6 @@ slug: igcombo-overview
# igCombo Overview
-
##Topic Overview
@@ -36,11 +35,11 @@ The table below lists the required background you need for fully understanding t
You need to first read the following topics:
-- [{environment:ProductName} Overview](//igniteui-for-jquery-overview.mdx)
+- [\{environment:ProductName\} Overview](//igniteui-for-jquery-overview.mdx)
-- [Using JavaScript Resources in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
+- [Using JavaScript Resources in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
-- [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
+- [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
- [igGrid/igDataSource Architecture Overview](/iggrid/igdatasource-architecture-overview.mdx), The Data Source Control section
@@ -67,7 +66,7 @@ The table below briefly explains the main features of the `igCombo`.
| Keyboard navigation | Users can easily and quickly navigate through items or change the selected/highlighted items thanks to the rich keyboard navigation that igCombo supports. |
| Load-on-Demand | The igCombo control supports Load-on-Demand feature. Enabling Load-on-Demand significantly reduces the bandwidth and processing overhead on both the server and the client. |
| Highlighting | When a user type a text in igCombo input the matching results in the dropdown items are displayed with a visual highlighting of the matching text. |
-| {environment:ProductNameMVC} | You can use managed .NET code to configure the {environment:ProductNameMVC} Combo control. |
+| \{environment:ProductNameMVC\} | You can use managed .NET code to configure the \{environment:ProductNameMVC\} Combo control. |
### Virtualization
@@ -82,7 +81,7 @@ Virtualization allows the `igCombo` control to bind to hundreds of items while k
#### Related Sample
-- [igCombo Virtualization]({environment:SamplesUrl}/combo/virtualization)
+- [igCombo Virtualization](\{environment:SamplesUrl\}/combo/virtualization)
### Auto-Complete
@@ -120,7 +119,7 @@ The `igCombo` control supports single and multiple selection. With multiple sele
#### Related Sample
-- [igCombo Multiple selection]({environment:SamplesUrl}/combo/selection-and-checkboxes)
+- [igCombo Multiple selection](\{environment:SamplesUrl\}/combo/selection-and-checkboxes)
### Load-on-Demand
@@ -131,7 +130,7 @@ If Load-on-Demand is enabled, the user should first be able to see a scrollbar i
#### Related Sample
-- [Load-On-Demand]({environment:SamplesUrl}/combo/load-on-demand)
+- [Load-On-Demand](\{environment:SamplesUrl\}/combo/load-on-demand)
### Keyboard navigation
@@ -143,12 +142,12 @@ Experience by saving time and allowing the end-user to easily and quickly naviga
#### Related Sample
-- [Keyboard navigation]({environment:SamplesUrl}/combo/keyboard-navigation)
+- [Keyboard navigation](\{environment:SamplesUrl\}/combo/keyboard-navigation)
-### {environment:ProductNameMVC}
+### \{environment:ProductNameMVC\}
-You can use the ASP.NET MVC Helper to use managed code languages to configure the {environment:ProductNameMVC} `Combo` control. You can create re-usable Views or ViewModels in your ASP.NET MVC applications to interface with the combo. You can also bind to an IQueryable object in ASP.NET and the helper will generate the JSON data for the `igCombo` control to use on the client.
+You can use the ASP.NET MVC Helper to use managed code languages to configure the \{environment:ProductNameMVC\} `Combo` control. You can create re-usable Views or ViewModels in your ASP.NET MVC applications to interface with the combo. You can also bind to an IQueryable object in ASP.NET and the helper will generate the JSON data for the `igCombo` control to use on the client.
### Related Topics
@@ -159,7 +158,7 @@ You can use the ASP.NET MVC Helper to use managed code languages to configure th
#### Related Sample
-- [{environment:ProductNameMVC} Combo]({environment:SamplesUrl}/combo/aspnet-mvc-helper)
+- [\{environment:ProductNameMVC\} Combo](\{environment:SamplesUrl\}/combo/aspnet-mvc-helper)
##Minimum Requirements
@@ -168,7 +167,7 @@ You can use the ASP.NET MVC Helper to use managed code languages to configure th
###Introduction
-The `igCombo` control is a jQuery UI Widget and therefore is dependent upon the jQuery core and jQuery UI JavaScript libraries. In addition, there are several {environment:ProductName}™ JavaScript resources that the `igCombo` control uses for shared functionality and data binding. These JavaScript references are required whether the `igCombo` control is used in a pure JavaScript context or in ASP.NET MVC. When using the `igCombo` in ASP.NET MVC, the Infragistics.Web.Mvc assembly is required to configure the `igCombo` with .NET languages.
+The `igCombo` control is a jQuery UI Widget and therefore is dependent upon the jQuery core and jQuery UI JavaScript libraries. In addition, there are several \{environment:ProductName\}™ JavaScript resources that the `igCombo` control uses for shared functionality and data binding. These JavaScript references are required whether the `igCombo` control is used in a pure JavaScript context or in ASP.NET MVC. When using the `igCombo` in ASP.NET MVC, the Infragistics.Web.Mvc assembly is required to configure the `igCombo` with .NET languages.
###Requirements
@@ -178,12 +177,12 @@ The table below lists the requirements for the `igCombo` control.
| Requirement | Description |
| --- | --- |
-| jQuery and jQuery UI JavaScript resources | {environment:ProductName} is built on top of these frameworks: [jQuery](http://jquery.com) (The required jQuery version for igCombo is 1.8.3) [jQuery UI](http://jqueryui.com/) (The required jQuery UI version for igCombo is 1.9.2) |
-| Shared {environment:ProductName} JavaScript resources | There are several shared JavaScript resources in {environment:ProductName} that most widgets use: infragistics.util.js infragistics.util.jquery.js |
+| jQuery and jQuery UI JavaScript resources | \{environment:ProductName\} is built on top of these frameworks: [jQuery](http://jquery.com) (The required jQuery version for igCombo is 1.8.3) [jQuery UI](http://jqueryui.com/) (The required jQuery UI version for igCombo is 1.9.2) |
+| Shared \{environment:ProductName\} JavaScript resources | There are several shared JavaScript resources in \{environment:ProductName\} that most widgets use: infragistics.util.js infragistics.util.jquery.js |
| igDataSource JavaScript Resources | The igCombo uses the igDataSource internally for data operations: infragistics.dataSource.js |
| igTemplating JavaScript Resources | The igCombo uses the igTemplating internally for the rendering of items. infragistics.templating.js |
| igCombo JavaScript resources | The JavaScript file for the igCombo widget: infragistics.ui.combo.js |
-| IG Theme | This theme contains custom visual styles created especially for {environment:ProductName} |
+| IG Theme | This theme contains custom visual styles created especially for \{environment:ProductName\} |
| Base Theme | The base theme contains styles that primarily define the form and function for each widget. |
@@ -217,7 +216,7 @@ The following table lists the supported data sources and some basic specifics fo
### Binding to data sources overview
-In most cases, you will use the `dataSource` or `dataSourceUrl` options of the `igCombo` to bind to data. This option provides your data to the `igDataSource` which can handle the various data formats that are supported. The one main exception to using this option is when the `igCombo` is instantiated using a SELECT element. The `igCombo` inherits the data and options of its base SELECT element in this case. In ASP.NET MVC, supplying an IQueryable to the {environment:ProductNameMVC} Helper facilitates the serialization of the data from the server and passes it to the client with the View. Once the page is received by the browser, the `dataSource` option of the `igCombo` is set for client-side operation.
+In most cases, you will use the `dataSource` or `dataSourceUrl` options of the `igCombo` to bind to data. This option provides your data to the `igDataSource` which can handle the various data formats that are supported. The one main exception to using this option is when the `igCombo` is instantiated using a SELECT element. The `igCombo` inherits the data and options of its base SELECT element in this case. In ASP.NET MVC, supplying an IQueryable to the \{environment:ProductNameMVC\} Helper facilitates the serialization of the data from the server and passes it to the client with the View. Once the page is received by the browser, the `dataSource` option of the `igCombo` is set for client-side operation.
##Template Use and Selection
@@ -258,11 +257,11 @@ The table below maps some of your possible needs to the appropriate templates.
Following are some other topics you may find useful.
-- [{environment:ProductName} Overview](//igniteui-for-jquery-overview.mdx)
+- [\{environment:ProductName\} Overview](//igniteui-for-jquery-overview.mdx)
-- [Using JavaScript Resources in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
+- [Using JavaScript Resources in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-resources.mdx)
-- [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
+- [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
- [igGrid/igDataSource Architecture Overview](/iggrid/igdatasource-architecture-overview.mdx)
diff --git a/docs/jquery/src/content/en/topics/controls/igcombo/using-themes.mdx b/docs/jquery/src/content/en/topics/controls/igcombo/using-themes.mdx
index 215cc0866c..44c9df1c2f 100644
--- a/docs/jquery/src/content/en/topics/controls/igcombo/using-themes.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igcombo/using-themes.mdx
@@ -5,7 +5,6 @@ slug: igcombo-using-themes
# Styling igCombo
-
##Using Themes
@@ -20,7 +19,7 @@ To customize a theme, you can use ThemeRoller. ThemeRoller is a tool provided by
The information you need to customize the jQuery UI theme for the `igCombo` is covered in the following topics:
-- [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
+- [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
##Related Topics
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/accessibility-compliance.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/accessibility-compliance.mdx
index 71ffc5034a..e127897753 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/accessibility-compliance.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/accessibility-compliance.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-accessibility-compliance
# Accessibility Compliance (igDataChart)
-
##Topic Overview
@@ -28,7 +27,7 @@ The following topics are prerequisite to understanding this topic:
### Introduction
-All of the {environment:ProductName}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also detailed is how the `igDataChart` control complies with each rule.
+All of the \{environment:ProductName\}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also detailed is how the `igDataChart` control complies with each rule.
To meet the requirements each accessibility rule, in some cases, you may need to interact with the control by to setting a specific property, but in other cases the control does the work for you.
@@ -57,7 +56,7 @@ The following table summarizes the accessibility compliance features of the igDa
The following topics provide additional information related to this topic.
-- [**Accessibility Compliance**](//general-and-getting-started/accessibility-compliance.mdx): Provides reference information for accessibility compliance of all {environment:ProductName} controls.
+- [**Accessibility Compliance**](//general-and-getting-started/accessibility-compliance.mdx): Provides reference information for accessibility compliance of all \{environment:ProductName\} controls.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/adding.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/adding.mdx
index cc2e6f2da7..73be5a9ef3 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/adding.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/adding.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-adding
# Adding igDataChart
-
## Topic Overview
### Purpose
@@ -23,9 +22,9 @@ The following table lists the materials required as a prerequisite to understand
**Topics**
-- [{environment:ProductName} Overview](//igniteui-for-jquery-overview.mdx): General information on the {environment:ProductName}™ library.
+- [\{environment:ProductName\} Overview](//igniteui-for-jquery-overview.mdx): General information on the \{environment:ProductName\}™ library.
-- [Using JavaScript Resources in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-resources.mdx): This topic provides general guidance on adding required JavaScript resources to use controls from the {environment:ProductName} library.
+- [Using JavaScript Resources in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-resources.mdx): This topic provides general guidance on adding required JavaScript resources to use controls from the \{environment:ProductName\} library.
- [igDataChart Overview](/overview/igdatachart-overview.mdx): This topic provides conceptual information about the `igDataChart`™ control including its main features, minimum requirements for using charts and user functionality.
@@ -90,13 +89,13 @@ The following steps demonstrate how to add an `igDataChart` control to a web pag
Add the jQuery, jQueryUI and Modernizr JavaScript resources to a folder named `Scripts` in your web site or web application.
- Add the {environment:ProductName} CSS files to a folder named `Content/ig` in your web site or web application (see the [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) topic for details).
+ Add the \{environment:ProductName\} CSS files to a folder named `Content/ig` in your web site or web application (see the [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) topic for details).
- Add the {environment:ProductName} JavaScript files to a folder named `Scripts/ig` in your web site or web application (see the [Using JavaScript Resouces in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-resources.mdx) topic for details).
+ Add the \{environment:ProductName\} JavaScript files to a folder named `Scripts/ig` in your web site or web application (see the [Using JavaScript Resouces in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-resources.mdx) topic for details).
**Use igLoader in JavaScript**
- The `igLoader`™ control is the recommended way to load JavaScript and CSS resources required by the {environment:ProductName} library controls. First the `igLoader` script must be included in the page:
+ The `igLoader`™ control is the recommended way to load JavaScript and CSS resources required by the \{environment:ProductName\} library controls. First the `igLoader` script must be included in the page:
**In HTML:**
@@ -122,7 +121,7 @@ The following steps demonstrate how to add an `igDataChart` control to a web pag
**Use MVC Loader**
- The `Infragistics.Web.Mvc` assembly must be referenced in your ASP.NET MVC project and the corresponding namespace must be referenced in your view. For details, see [Using JavaScript Resources in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-resources.mdx) but for clarity the code to reference the namespace is given here.
+ The `Infragistics.Web.Mvc` assembly must be referenced in your ASP.NET MVC project and the corresponding namespace must be referenced in your view. For details, see [Using JavaScript Resources in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-resources.mdx) but for clarity the code to reference the namespace is given here.
**In ASPX:**
@@ -156,7 +155,7 @@ The following steps demonstrate how to add an `igDataChart` control to a web pag
**ASP.NET Example**
- For ASP.NET MVC no container elements are needed because {environment:ProductNameMVC} adds the required markup automatically.
+ For ASP.NET MVC no container elements are needed because \{environment:ProductNameMVC\} adds the required markup automatically.
3. Add data source.
@@ -252,7 +251,7 @@ The following steps demonstrate how to add an `igDataChart` control to a web pag
**ASP.NET example**
- The code below instantiates and sets the main features of the `igDataChart` using the {environment:ProductNameMVC} DataChart provided in the `Infragistics.Web.Mvc` assembly. The data model is associated with the control with the DataChart(Model) call and the rest of the calls act similarly to the HTML example.
+ The code below instantiates and sets the main features of the `igDataChart` using the \{environment:ProductNameMVC\} DataChart provided in the `Infragistics.Web.Mvc` assembly. The data model is associated with the control with the DataChart(Model) call and the rest of the calls act similarly to the HTML example.
**In ASPX:**
@@ -469,7 +468,7 @@ The following topics provide additional information related to this topic.
- [Binding igDataChart to Data](/igdatachart-databinding.mdx): Shows how to bind data from various data sources to a chart control. This includes JavaScript arrays, JSON, WCF service. Shows how a big volume of data can be data bound to a chart control.
-- [jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): References to the jQuery API reference of `igDataChart` and contains a reference table with all {environment:ProductNameMVC} properties with code snippets.
+- [jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): References to the jQuery API reference of `igDataChart` and contains a reference table with all \{environment:ProductNameMVC\} properties with code snippets.
- [Styling igDataChart](/styling/igdatachart-styling-themes.mdx): Demonstrates how to use the `igDataChart`™ control to apply styles and themes.
@@ -479,9 +478,9 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Bar and Column Series]({environment:SamplesUrl}/data-chart/bar-and-column-series): Demonstrates how bar and column charts can be implemented using the `igDataChart` control.
+- [Bar and Column Series](\{environment:SamplesUrl\}/data-chart/bar-and-column-series): Demonstrates how bar and column charts can be implemented using the `igDataChart` control.
-- [Composite Chart]({environment:SamplesUrl}/data-chart/composite-chart): This sample demonstrates how to configure a composite chart with two Y-axes with different range and two different data series types: column and line series.
+- [Composite Chart](\{environment:SamplesUrl\}/data-chart/composite-chart): This sample demonstrates how to configure a composite chart with two Y-axes with different range and two different data series types: column and line series.
### Resources
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/api-links.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/api-links.mdx
index 7fb27e94f7..b37c1657a2 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/api-links.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/api-links.mdx
@@ -2,6 +2,9 @@
title: "jQuery and MVC API Reference Links (igDataChart)"
slug: igdatachart-api-links
---
+
+# jQuery and MVC API Reference Links (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# jQuery and MVC API Reference Links (igDataChart)
@@ -10,7 +13,7 @@ import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
##Topic Overview
### Purpose
-This topic provides links to the API documentation for jQuery and {environment:ProductNameMVC} class for `igDataChart`™ control.
+This topic provides links to the API documentation for jQuery and \{environment:ProductNameMVC\} class for `igDataChart`™ control.
### Required Background
@@ -25,7 +28,7 @@ The following topics are prerequisite to understanding this topic:
### Introduction
-The `igDataChart` is built as a jQuery UI widget with an accompanying {environment:ProductNameMVC}. For more information about each API, follow the links to the API documentation given below.
+The `igDataChart` is built as a jQuery UI widget with an accompanying \{environment:ProductNameMVC\}. For more information about each API, follow the links to the API documentation given below.
### API documents reference summary
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts-in-aspnet-mvc.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts-in-aspnet-mvc.mdx
index 1306748706..39b80512a0 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts-in-aspnet-mvc.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts-in-aspnet-mvc.mdx
@@ -5,7 +5,6 @@ slug: animating-charts-in-asp.net-mvc
# Animating Charts in ASP.NET MVC(igDataChart)
-
##Topic Overview
@@ -298,7 +297,7 @@ Step-by-step instructions for creating a simple web page with an animated column
The following topics provide additional information related to this topic.
-- [Animating Charts in HTML and JavaScript](/igdatachart-animating-html.mdx) : Demonstrates how to: create an HTML view; use JavaScript to add data dynamically to a column chart; and animate data changes using the Motion Framework for charts in the {environment:ProductName} library.
+- [Animating Charts in HTML and JavaScript](/igdatachart-animating-html.mdx) : Demonstrates how to: create an HTML view; use JavaScript to add data dynamically to a column chart; and animate data changes using the Motion Framework for charts in the \{environment:ProductName\} library.
### Samples
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts.mdx
index 24157471d8..1d84e6ecde 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/charts.mdx
@@ -5,11 +5,10 @@ slug: igdatachart-animating-charts
# Animating Charts (Motion Framework for Charts)
-
##Topic overview
### Introduction
-The Infragistics® Motion Framework™ is a framework for animating data changes in {environment:ProductName}™ chart controls.
+The Infragistics® Motion Framework™ is a framework for animating data changes in \{environment:ProductName\}™ chart controls.
### Topics
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/html.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/html.mdx
index 026f99d23c..639b5cd176 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/html.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/html.mdx
@@ -5,13 +5,12 @@ slug: igdatachart-animating-html
# Animating Charts in HTML and JavaScript (igDataChart)
-
##Topic Overview
### Purpose
-This topic explains how to create an HTML view and use JavaScript to add data dynamically to a column chart and use the Motion Framework for charts in the {environment:ProductName} library to animate data changes.
+This topic explains how to create an HTML view and use JavaScript to add data dynamically to a column chart and use the Motion Framework for charts in the \{environment:ProductName\} library to animate data changes.
### Required background
@@ -239,7 +238,7 @@ You can experiment by creating a different kind of change in the data source lik
The following topics provide additional information related to this topic.
-- [Animating Charts in ASP.NET MVC(igDataChart)](./02_Animating Charts in ASP.NET MVC.mdx): This topic explains how to create an MVC view and use jQuery to add data dynamically to a column chart by an AJAX POST request and use the Motion Framework for charts in the {environment:ProductName} library to animate data changes.
+- [Animating Charts in ASP.NET MVC(igDataChart)](./02_Animating Charts in ASP.NET MVC.mdx): This topic explains how to create an MVC view and use jQuery to add data dynamically to a column chart by an AJAX POST request and use the Motion Framework for charts in the \{environment:ProductName\} library to animate data changes.
### Samples
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/motion-framework.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/motion-framework.mdx
index 39cd8bdf16..45b1ac3e38 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/motion-framework.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/animating/motion-framework.mdx
@@ -2,6 +2,9 @@
title: "Infragistics Motion Framework for Charts Overview (igDataChart)"
slug: igdatachart-motion-framework
---
+
+# Infragistics Motion Framework for Charts Overview (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Infragistics Motion Framework for Charts Overview (igDataChart)
@@ -33,7 +36,7 @@ The Infragistics Motion Framework tells the story of your data in a way that all
Motion Framework works on the principle that data is being fed, either continually or in batches, to a chart control that invokes the appropriate API method whenever data changes to render a fully customizable animated visual representation of your data.
-The Motion Framework allows developers using the {environment:ProductName} chart controls, to increase the visual appeal of, and imply trends or other meaning behind the data.
+The Motion Framework allows developers using the \{environment:ProductName\} chart controls, to increase the visual appeal of, and imply trends or other meaning behind the data.
##Chart Animation Configuration Summary
@@ -62,7 +65,7 @@ A catalog of the Infragistics Motion Network supported configurable chart animat
The following sample demonstrates how to use the Motion Framework™ with igDataChart to build highly engaging visualizations and provide smooth playback of changes in data over time.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-intervals.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-intervals.mdx
index 10ed68d9e1..d7786eac98 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-intervals.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-intervals.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-configuring-axis-intervals
# Configuring Axis Intervals (igDataChart)
-
##Topic Overview
@@ -47,7 +46,7 @@ The Major and Minor intervals feature of the `igDataChart` control allows you to
The following example is configurable `igDataChart` control, using NumericX and Y axes, where the following options can be set - Interval, MinorInterval, MajorStroke and MinorStroke.
@@ -145,7 +144,7 @@ This sample illustrates how the `igDataChart` control, with the axis major and m
will be displayed as a result of the usage of the following settings - MinorInterval, MinorStroke, MinorStrokeThickness, Interval, MajorStroke and MajorStrokeThickness.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-title.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-title.mdx
index 3cad12eb58..1d557794e8 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-title.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/axis-title.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-axis-title
# Configuring the Axis Title (igDataChart)
-
##Topic Overview
@@ -116,7 +115,7 @@ The following topic provides additional information related to this topic:
The following sample provides additional information related to this topic.
-- [Axis Title]({environment:SamplesUrl}/data-chart/axis-title) : The axis title feature of the `igDataChart` control allows you to add information about the chart’s axis.
+- [Axis Title](\{environment:SamplesUrl\}/data-chart/axis-title) : The axis title feature of the `igDataChart` control allows you to add information about the chart’s axis.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/chart-titles-and-subtitles.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/chart-titles-and-subtitles.mdx
index 031851be9e..b5cc5ee551 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/chart-titles-and-subtitles.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/chart-titles-and-subtitles.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-chart-titles-and-subtitles
# Configuring the Chart Title and Subtitle (igDataChart)
-
##Topic Overview
@@ -90,7 +89,7 @@ Following are a chart title settings' table and an example that implements this
- [Chart Title and Subtitle]({environment:SamplesEmbedUrl}/data-chart/chart-title)
+ [Chart Title and Subtitle](\{environment:SamplesEmbedUrl\}/data-chart/chart-title)

diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/configuring.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/configuring.mdx
index 850bbe83b4..10d6a34e31 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/configuring.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/configuring.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-configuring
# Configuring igDataChart
-
##In This Group of Topics
@@ -16,7 +15,7 @@ This is a group of topics explaining how to configure the various aspects of the
### Topics
-- [Animating Charts (Motion Framework for Charts)](/animating/igdatachart-animating-charts.mdx): The Infragistics® Motion Framework™ is a framework for animating data changes in {environment:ProductName}™ chart controls.
+- [Animating Charts (Motion Framework for Charts)](/animating/igdatachart-animating-charts.mdx): The Infragistics® Motion Framework™ is a framework for animating data changes in \{environment:ProductName\}™ chart controls.
- [Configuring the Navigation Features (igDataChart)](/igdatachart-configuring-navigation-features.mdx): This topic explains, with code examples, how to configure navigation features of the `igDataChart`™ control and how to use its API to define the position and size of the visible portion of the chart.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datalegend.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datalegend.mdx
index 7227d53b54..cad12ae5bf 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datalegend.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datalegend.mdx
@@ -1,6 +1,7 @@
---
title: "Chart Data Legend"
---
+
# Chart Data Legend
The `igDataLegend` is a component that works much like the `Legend`, but it shows values of series and provides many configuration properties for filtering series rows and values columns, styling and formatting values. This legend updates when moving the mouse inside of the plot area of the `igDataChart` and has a persistent state that remembers the last hovered point when the user's mouse pointer exits the plot area. It displays this content using a set of three type of rows and four types of columns.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datatooltip.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datatooltip.mdx
index d0d7cf09d4..583508b550 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datatooltip.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/datatooltip.mdx
@@ -1,6 +1,7 @@
---
title: "Chart Data Tooltip"
---
+
# Chart Data Tooltip
The `DataToolTipLayer` displays values and titles of series as well as legend badges of series in a tooltip. In addition, it provides many configuration properties of the `igDataLegend` for filtering series rows and values columns, styling, and formatting values. This tooltip type updates while moving the mouse inside of the plot area of the `igCategoryChart`, `igFinancialChart`, and `igDataChart` components.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/callout-layer.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/callout-layer.mdx
index e0157c65de..f1c51a4e77 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/callout-layer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/callout-layer.mdx
@@ -5,7 +5,6 @@ slug: hoverinteractions-callout-layer
# Configuring the Callout Layer (igDataChart)
-
## Topic Overview
### Purpose
@@ -106,4 +105,4 @@ $(function () {
The following samples provide additional information related to this topic.
-- [Callouts Layers]({environment:SamplesUrl}/data-chart/callout-layer): This sample demonstrates using the Callout annotation layer in the `igDataChart`
+- [Callouts Layers](\{environment:SamplesUrl\}/data-chart/callout-layer): This sample demonstrates using the Callout annotation layer in the `igDataChart`
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-highlight-layer.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-highlight-layer.mdx
index cba038bb3a..7e75a7b1a4 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-highlight-layer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-highlight-layer.mdx
@@ -69,7 +69,7 @@ This sample demonstrates the Category Highlight Layer that targets a category ax
The sample options pane allows you to edit the properties of the Category Highlight Layer, such as changing the color of the highlight, outline, thickness and more.
@@ -101,7 +101,7 @@ The following samples provide additional information related to this topic.
- [Hover Interactions – Crosshair Layer](./03_HoverInteractions_Crosshair_Layer.mdx#example): This sample demonstrates the Crosshair Layer that provides crossing lines that meet at the actual value of every series that they are targeting. The sample options pane allows you to edit the properties of the layer, such as changing the thickness of the crosshair.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-item-highlight-layer.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-item-highlight-layer.mdx
index 94021b867b..26c93abb2d 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-item-highlight-layer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-item-highlight-layer.mdx
@@ -66,7 +66,7 @@ useInterpolation | bool | This property specifies if the highlight band should s
This sample demonstrates the Category Item Highlight Layer that highlights items in a series that use a category axis either by drawing a banded shape at their position or by rendering a marker at their position.The sample options pane allows you to edit the properties of the Category Item Highlight Layer, such as changing the color of the highlight, outline, thickness and more.
@@ -101,7 +101,7 @@ The following samples provide additional information related to this topic.
- [Hover Interactions – Crosshair Layer](./03_HoverInteractions_Crosshair_Layer.mdx#example): This sample demonstrates the Crosshair Layer that provides crossing lines that meet at the actual value of every series that they are targeting. The sample options pane allows you to edit the properties of the layer, such as changing the thickness of the crosshair.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-tooltip-layer.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-tooltip-layer.mdx
index 9dbf9dfc79..6a1ca26e88 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-tooltip-layer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/category-tooltip-layer.mdx
@@ -70,7 +70,7 @@ This sample demonstrates the Category Tooltip Layer that displays grouped toolti
The sample options pane allows you to edit the properties of the layer, such as changing the position of the tooltip.
@@ -104,7 +104,7 @@ The following samples provide additional information related to this topic.
- [Hover Interactions – Crosshair Layer](./03_HoverInteractions_Crosshair_Layer.mdx#example): This sample demonstrates the Crosshair Layer that provides crossing lines that meet at the actual value of every series that they are targeting. The sample options pane allows you to edit the properties of the layer, such as changing the thickness of the crosshair.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/common-properties.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/common-properties.mdx
index ee2ee7eb55..75d6099b57 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/common-properties.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/common-properties.mdx
@@ -137,14 +137,14 @@ Following is the code used in this implementation
The following samples provide additional information related to this topic.
-- [Hover Interactions – Category Highlight Layer]({environment:SamplesUrl}/data-chart/category-highlight-layer): This sample demonstrates the Category Highlight Layer that targets a category axis, or all category axes in the `igDataChart`™ control. The sample options pane allows you to edit the properties of the Category Highlight Layer, such as changing the color of the highlight, outline, thickness and more.
+- [Hover Interactions – Category Highlight Layer](\{environment:SamplesUrl\}/data-chart/category-highlight-layer): This sample demonstrates the Category Highlight Layer that targets a category axis, or all category axes in the `igDataChart`™ control. The sample options pane allows you to edit the properties of the Category Highlight Layer, such as changing the color of the highlight, outline, thickness and more.
-- [Hover Interactions – Category Item Highlight Layer]({environment:SamplesUrl}/data-chart/category-item-highlight-layer): This sample demonstrates the Category Item Highlight Layer that highlights items in a series that use a category axis either by drawing a banded shape at their position or by rendering a marker at their position.The sample options pane allows you to edit the properties of the Category Item Highlight Layer, such as changing the color of the highlight, outline, thickness and more.
+- [Hover Interactions – Category Item Highlight Layer](\{environment:SamplesUrl\}/data-chart/category-item-highlight-layer): This sample demonstrates the Category Item Highlight Layer that highlights items in a series that use a category axis either by drawing a banded shape at their position or by rendering a marker at their position.The sample options pane allows you to edit the properties of the Category Item Highlight Layer, such as changing the color of the highlight, outline, thickness and more.
-- [Hover Interactions – Category Tooltip Layer]({environment:SamplesUrl}/data-chart/category-tooltip-layer): This sample demonstrates the Category Tooltip Layer that displays grouped tooltips for series that use a category axis. The sample options pane allows you to edit the properties of the layer, such as changing the position of the tooltip.
+- [Hover Interactions – Category Tooltip Layer](\{environment:SamplesUrl\}/data-chart/category-tooltip-layer): This sample demonstrates the Category Tooltip Layer that displays grouped tooltips for series that use a category axis. The sample options pane allows you to edit the properties of the layer, such as changing the position of the tooltip.
-- [Hover Interactions – Crosshair Layer]({environment:SamplesUrl}/data-chart/crosshair-layer): This sample demonstrates the Crosshair Layer that provides crossing lines that meet at the actual value of every series that they are targeting. The sample options pane allows you to edit the properties of the layer, such as changing the thickness of the crosshair.
+- [Hover Interactions – Crosshair Layer](\{environment:SamplesUrl\}/data-chart/crosshair-layer): This sample demonstrates the Crosshair Layer that provides crossing lines that meet at the actual value of every series that they are targeting. The sample options pane allows you to edit the properties of the layer, such as changing the thickness of the crosshair.
-- [Hover Interactions – Item Tooltip Layer]({environment:SamplesUrl}/data-chart/item-tooltip-layer): This sample demonstrates the Item Tooltip Layer that displays tooltips for all target series individually. The sample options pane allows you to edit the properties of the layer, such as changing the transition duration.
+- [Hover Interactions – Item Tooltip Layer](\{environment:SamplesUrl\}/data-chart/item-tooltip-layer): This sample demonstrates the Item Tooltip Layer that displays tooltips for all target series individually. The sample options pane allows you to edit the properties of the layer, such as changing the transition duration.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/crosshair-layer.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/crosshair-layer.mdx
index 66ff2a4b0c..6091f4f35b 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/crosshair-layer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/crosshair-layer.mdx
@@ -5,7 +5,6 @@ slug: hoverinteractions-crosshair-layer
# Configuring the Crosshair Layer (igDataChart)
-
## Topic Overview
### Purpose
@@ -88,7 +87,7 @@ This sample demonstrates the Crosshair Layer that provides crossing lines that m
The sample options pane allows you to edit the properties of the layer, such as changing the thickness of the crosshair.
@@ -122,7 +121,7 @@ The following samples provide additional information related to this topic.
- [Hover Interactions – Item Tooltip Layer](./04_HoverInteractions_Item_Tooltip_Layer.mdx#example): This sample demonstrates the Item Tooltip Layer that displays tooltips for all target series individually. The sample options pane allows you to edit the properties of the layer, such as changing the transition duration.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/final-value-layer.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/final-value-layer.mdx
index 4ce6a1f1c4..36d5328a6c 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/final-value-layer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/final-value-layer.mdx
@@ -5,7 +5,6 @@ slug: hoverinteractions-final-value-layer
# Configuring the Final Value Layer (igDataChart)
-
## Topic Overview
### Purpose
@@ -87,4 +86,4 @@ $(function () {
The following samples provide additional information related to this topic.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/final-value-layer): This sample demonstrates using the Final Value annotation layer in the `igDataChart`.
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/final-value-layer): This sample demonstrates using the Final Value annotation layer in the `igDataChart`.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/item-tooltip-layer.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/item-tooltip-layer.mdx
index 0c843c56e2..4b336b3157 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/item-tooltip-layer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/hover-interactions/item-tooltip-layer.mdx
@@ -5,7 +5,6 @@ slug: hoverinteractions-item-tooltip-layer
# Configuring the Item Tooltip Layer (igDataChart)
-
## Topic Overview
### Purpose
@@ -70,7 +69,7 @@ This sample demonstrates the Item Tooltip Layer that displays tooltips for all t
The sample options pane allows you to edit the properties of the layer, such as changing the transition duration.
@@ -104,4 +103,4 @@ The following samples provide additional information related to this topic.
- [Hover Interactions – Crosshair Layer](./03_HoverInteractions_Crosshair_Layer.mdx#example): This sample demonstrates the Crosshair Layer that provides crossing lines that meet at the actual value of every series that they are targeting. The sample options pane allows you to edit the properties of the layer, such as changing the thickness of the crosshair.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
\ No newline at end of file
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/igchart-transitions-in-animations.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/igchart-transitions-in-animations.mdx
index 7dd4164248..58c5aa0c68 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/igchart-transitions-in-animations.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/igchart-transitions-in-animations.mdx
@@ -5,7 +5,6 @@ slug: igchart-transitions-in-animations
# Transitions In Animations
-
##Topic Overview
@@ -45,7 +44,7 @@ This topic contains the following sections:
### Overview
-This feature allows you to animate the series as it loads a new data source. The available animation differs depending on the type of series involved. For example, the `columnSeries` animates by rising from the x-axis, a `lineSeries` animates by drawing from the y-axis. Refer to the following sample to see how the different series animate visually, [Transition Animation]({environment:SamplesUrl}/data-chart/transition-animation) and [Transition Animation (Financial)](./08_igChart_Transitions_In_Animations.mdx#transition-example).
+This feature allows you to animate the series as it loads a new data source. The available animation differs depending on the type of series involved. For example, the `columnSeries` animates by rising from the x-axis, a `lineSeries` animates by drawing from the y-axis. Refer to the following sample to see how the different series animate visually, [Transition Animation](\{environment:SamplesUrl\}/data-chart/transition-animation) and [Transition Animation (Financial)](./08_igChart_Transitions_In_Animations.mdx#transition-example).
Enable animated transitions by setting the `isTransitionInEnabled` property to “`true`”.
@@ -119,7 +118,7 @@ The transition type is configured by setting the `transitionInMode` property to
The following example demonstrates how to enable and change transition in animations for the financial chart:
##Related Content
@@ -139,4 +138,4 @@ and bind it to data.
The following samples provide additional information related to this topic.
-- [Transition Animation]({environment:SamplesUrl}/data-chart/transition-animation): This sample demonstrates the animation feature that is displayed at the chart initialization.
\ No newline at end of file
+- [Transition Animation](\{environment:SamplesUrl\}/data-chart/transition-animation): This sample demonstrates the animation feature that is displayed at the chart initialization.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/knockoutjs-support.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/knockoutjs-support.mdx
index c9974d07fb..72f041d584 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/knockoutjs-support.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/knockoutjs-support.mdx
@@ -2,6 +2,9 @@
title: "Configuring Knockout Support (igDataChart)"
slug: igdatachart-knockoutjs-support
---
+
+# Configuring Knockout Support (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Knockout Support (igDataChart)
@@ -159,10 +162,10 @@ The control can be bound to a non-observable array and object fields, but doing
This example demonstrates the igDataChart control reacting to changes in the data source by the Knockout View-Model. Note that the chart is updated without having to re-bind the control. By default, the sample shows the market revenue and expenses for the first 10 days of the month. You can add/remove days and move items along the chart and observe money flow on the market changing accordingly.
->**Note:** The Knockout extensions do not work with the {environment:ProductNameMVC}.
+>**Note:** The Knockout extensions do not work with the \{environment:ProductNameMVC\}.
##Related Content
@@ -180,7 +183,7 @@ The following topics provide additional information related to this topic.
- [Configuring Knockout Support (igCombo)](//igcombo/configuring/configuring.mdx): This topic explains how to configure the `igCombo` control to bind to View-Model objects managed by the Knockout library.
-- [Configuring Knockout Support (igEditors)](../../igEditors/Config/02_Configuring Knockout Support (Editors).mdx): This topic explains how to configure {environment:ProductName} editor controls to bind to View-Model objects using the Knockout library.
+- [Configuring Knockout Support (igEditors)](../../igEditors/Config/02_Configuring Knockout Support (Editors).mdx): This topic explains how to configure \{environment:ProductName\} editor controls to bind to View-Model objects using the Knockout library.
- [Configuring Knockout Support (igTree)](//igtree/knockoutjs-support.mdx): This topic explains how to configure the `igTree` control to bind to View-Model objects managed by the Knockout library.
@@ -189,7 +192,7 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Bind igDataChart with KnockoutJS]({environment:SamplesUrl}/data-chart/bind-data-chart-with-ko): The sample demonstrates binding `igDataChart` with Knockout View-Model, using Infragistics Knockout extension for the control.
+- [Bind igDataChart with KnockoutJS](\{environment:SamplesUrl\}/data-chart/bind-data-chart-with-ko): The sample demonstrates binding `igDataChart` with Knockout View-Model, using Infragistics Knockout extension for the control.
### Resources
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/navigation-features.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/navigation-features.mdx
index 5c05b4a2df..63e22ff588 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/navigation-features.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/navigation-features.mdx
@@ -2,6 +2,9 @@
title: "Configuring the Navigation Features (igDataChart)"
slug: igdatachart-configuring-navigation-features
---
+
+# Configuring the Navigation Features (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring the Navigation Features (igDataChart)
@@ -70,7 +73,7 @@ Setting the visible portion of the chart|Set the coordinates and size of the vis
This sample demonstrates various navigation methods available in the jQuery chart. Panning and zooming through the control’s content can be performed using built-in keyboard navigation (Arrows, Page Up/Down, Home key), built-in mouse navigation (Shift + mouse drag, mouse scroll, mouse down + mouse drag), and the overview plus detail pane, as well as from code-behind using the control's window position and scale properties.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/series-highlighting.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/series-highlighting.mdx
index e2404c3b13..5b04500135 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/series-highlighting.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/series-highlighting.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-series-highlighting
# Configuring the Series Highlighting (igDataChart)
-
##Topic Overview
@@ -77,13 +76,13 @@ The following table summarizes the properties used for series highlighting. Thes
This sample demonstrates the series highlighting feature on different series types by configuring the `isHighlightingEnabled` and `highlightingTransitionDuration` series properties.
## Events
@@ -144,7 +143,7 @@ The following table summarizes the properties of the `assigningCategoryMarke
The following example shows the usage of the `assigningCategoryStyle` event to change the highlighting feature to fade non highlighting columns instead of changing the highlighting column.
- [Custom Series Highlighting]({environment:SamplesEmbedUrl}/data-chart/custom-series-highlighting)
+ [Custom Series Highlighting](\{environment:SamplesEmbedUrl\}/data-chart/custom-series-highlighting)

diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polygon-series.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polygon-series.mdx
index 3e3e2c1196..d3d4e5cfd4 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polygon-series.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polygon-series.mdx
@@ -99,4 +99,4 @@ With the above data and chart, the following result is generated:
### Samples
-- [Scatter Polygon Series]({environment:SamplesUrl}/data-chart/polygon): This sample demonstrates how you can display polygonal data in the `igDataChart` control.
\ No newline at end of file
+- [Scatter Polygon Series](\{environment:SamplesUrl\}/data-chart/polygon): This sample demonstrates how you can display polygonal data in the `igDataChart` control.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polyline-series.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polyline-series.mdx
index e506154bb8..64ce05ea76 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polyline-series.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/shape-series/polyline-series.mdx
@@ -100,4 +100,4 @@ With the above data and chart, the following result is generated:
### Samples
-- [Scatter Polyline Series]({environment:SamplesUrl}/data-chart/polyline): This sample demonstrates how you can display polyline data in the `igDataChart` control.
\ No newline at end of file
+- [Scatter Polyline Series](\{environment:SamplesUrl\}/data-chart/polyline): This sample demonstrates how you can display polyline data in the `igDataChart` control.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/timexaxis.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/timexaxis.mdx
index 8cb61674fd..6844bbb8cf 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/timexaxis.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/configuring/timexaxis.mdx
@@ -208,4 +208,4 @@ The following topic provides additional information related to this topic:
### Samples
The following sample provides additional information related to this topic.
-- [Data Chart - Time X-Axis with Axis Breaks]({environment:SamplesUrl}/data-chart/time-x-axis): This sample demonstrates the Time X-Axis with axis breaks in the `igDataChart` control.
\ No newline at end of file
+- [Data Chart - Time X-Axis with Axis Breaks](\{environment:SamplesUrl\}/data-chart/time-x-axis): This sample demonstrates the Time X-Axis with axis breaks in the `igDataChart` control.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/databinding.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/databinding.mdx
index 4bddf72518..571bdd3a75 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/databinding.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/databinding.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-databinding
# Binding igDataChart to Data
-
##Topic Overview
@@ -96,7 +95,7 @@ Each data source has different requirements for data binding to the `igDataSourc
### Data sources summary
-The data binding of the `igDataChart` control is identical to that of the other controls in the {environment:ProductName}™ library. The way to bind data is by either by assigning a data source to the `dataSource` option or by providing a URL in the `dataSourceUrl` if data is provided by a web or WCF service.
+The data binding of the `igDataChart` control is identical to that of the other controls in the \{environment:ProductName\}™ library. The way to bind data is by either by assigning a data source to the `dataSource` option or by providing a URL in the `dataSourceUrl` if data is provided by a web or WCF service.
##Binding to a JavaScript Array
@@ -195,7 +194,7 @@ The following steps demonstrate how to bind the `igDataChart` control to a JavaS
This is a basic example of the data chart bound to JSON data:
##Binding to an IQueryable<T> in ASP.NET MVC
@@ -215,7 +214,7 @@ This example demonstrates how to bind the `igDataChart` control to an XML string
### Introduction
-This procedure demonstrates how to bind a list of data objects from a backend controller method to a data chart using the ASP.NET helper provided in the {environment:ProductName} library.
+This procedure demonstrates how to bind a list of data objects from a backend controller method to a data chart using the ASP.NET helper provided in the \{environment:ProductName\} library.
### Prerequisites
@@ -234,7 +233,7 @@ to that array.
### Steps
-The following steps demonstrate how to instantiate and bind an `igDataChart` control in ASP.NET MVC by providing a list of data objects to a strongly typed view and use {environment:ProductNameMVC} DataChart.
+The following steps demonstrate how to instantiate and bind an `igDataChart` control in ASP.NET MVC by providing a list of data objects to a strongly typed view and use \{environment:ProductNameMVC\} DataChart.
1. Define the data model.
@@ -259,7 +258,7 @@ The following steps demonstrate how to instantiate and bind an `igDataChart` con
Add the logic to a controller method in order to instantiate an array of `StockMarketDataPoint` objects. This place to add custom logic that gets data from the data base.
- Note that the list of `StockMarketDataPoint` objects is converted to an IQueryable<StockMarketDataPoint> before submitting to the view. This can alternatively be done in the {environment:ProductNameMVC} call in the view, but the implementation provided here is cleaner.
+ Note that the list of `StockMarketDataPoint` objects is converted to an IQueryable<StockMarketDataPoint> before submitting to the view. This can alternatively be done in the \{environment:ProductNameMVC\} call in the view, but the implementation provided here is cleaner.
**In C#:**
@@ -457,7 +456,7 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Binding High Volume Data]({environment:SamplesUrl}/data-chart/binding-high-volume-data): This sample demonstrates a large number of records bound to an `igDataChart`.
+- [Binding High Volume Data](\{environment:SamplesUrl\}/data-chart/binding-high-volume-data): This sample demonstrates a large number of records bound to an `igDataChart`.
### Resources
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/known-issues.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/known-issues.mdx
index c349e71345..2d6dfd2c84 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/known-issues.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/known-issues.mdx
@@ -2,6 +2,9 @@
title: "Known Issues and Limitations (igDataChart)"
slug: igdatachart-known-issues
---
+
+# Known Issues and Limitations (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Known Issues and Limitations (igDataChart)
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/landing-page.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/landing-page.mdx
index 05389b4fd1..310cb2e551 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/landing-page.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/landing-page.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-landing-page
# igDataChart
-
##In This Group of Topics
@@ -46,7 +45,7 @@ The topics in this section provide detailed information regarding the `igDataCha
- [Accessibility Compliance (igDataChart)](/igdatachart-accessibility-compliance.mdx): This topic explains `igDataChart` accessibility features and provides advice how to achieve accessibility compliance for pages containing charts.
-- [jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): This topic provides links to the API documentation for jQuery and {environment:ProductNameMVC} class for `igDataChart` control.
+- [jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): This topic provides links to the API documentation for jQuery and \{environment:ProductNameMVC\} class for `igDataChart` control.
- [Known Issues and Limitations (igDataChart)](/igdatachart-known-issues.mdx): This topic lists all known issues and limitations in the `igDataChart` control.
@@ -59,6 +58,6 @@ The topics in this section provide detailed information regarding the `igDataCha
The following topics provide additional information related to this topic.
-- [{environment:ProductName} Overview](//igniteui-for-jquery-overview.mdx): This topic provides general information about the {environment:ProductName}™ library.
+- [\{environment:ProductName\} Overview](//igniteui-for-jquery-overview.mdx): This topic provides general information about the \{environment:ProductName\}™ library.
- [igPieChart Overview](/igpiechart/overview.mdx): This topic provides conceptual information about the `igPieChart`™ control including its main features, minimum requirements, and user functionality.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/hoverinteractions-hover-interactions-overview.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/hoverinteractions-hover-interactions-overview.mdx
index 4412887455..02d67984bb 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/hoverinteractions-hover-interactions-overview.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/hoverinteractions-hover-interactions-overview.mdx
@@ -157,7 +157,7 @@ The following samples provide additional information related to this topic.
- [Hover Interactions – Item Tooltip Layer](../04_Configuring/04_Hover Interactions/04_HoverInteractions_Item_Tooltip_Layer.mdx#example): This sample demonstrates the Item Tooltip Layer that displays tooltips for all target series individually. The sample options pane allows you to edit the properties of the layer, such as changing the transition duration.
-- [Hover Interactions – Multiple Layers]({environment:SamplesUrl}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
+- [Hover Interactions – Multiple Layers](\{environment:SamplesUrl\}/data-chart/multiple-layers): This sample demonstrates how multiple layers interact within the `igDataChart` control. This sample displays the Item Tooltip Layer, the Crosshair layer and the Category Highlight Layer.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/overview.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/overview.mdx
index f1dd437ada..fa1d0c5d4c 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/overview.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/overview.mdx
@@ -2,6 +2,9 @@
title: "Overview (igDataChart)"
slug: igdatachart-overview
---
+
+# Overview (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Overview (igDataChart)
@@ -25,9 +28,9 @@ The following table lists the materials required as a prerequisite to understand
**Topics**
-- [{environment:ProductName} Overview](///igniteui-for-jquery-overview.mdx)
+- [\{environment:ProductName\} Overview](///igniteui-for-jquery-overview.mdx)
-General information on the {environment:ProductName}™ library.
+General information on the \{environment:ProductName\}™ library.
### In This Topic
@@ -109,7 +112,7 @@ The following table displays the supported chart types.
### Minimum requirements summary
-The `igDataChart` control is a jQuery UI widget and therefore depends on the jQuery and jQuery UI libraries. The Modernzr library is also used internally for detecting browser and device capabilities. The control uses several {environment:ProductName}™ shared resources for functionality and data binding. References to these resources are needed nevertheless, in spite of pure jQuery or {environment:ProductNameMVC} being used. The `Infragistics.Web.Mvc` assembly is required when the control is used in the context of ASP.NET MVC.
+The `igDataChart` control is a jQuery UI widget and therefore depends on the jQuery and jQuery UI libraries. The Modernzr library is also used internally for detecting browser and device capabilities. The control uses several \{environment:ProductName\}™ shared resources for functionality and data binding. References to these resources are needed nevertheless, in spite of pure jQuery or \{environment:ProductNameMVC\} being used. The `Infragistics.Web.Mvc` assembly is required when the control is used in the context of ASP.NET MVC.
### Minimum requirements summary chart
@@ -119,17 +122,17 @@ The following table summarizes the requirements for using the `igDataChart` cont
| Requirement | Description |
| --- | --- |
| HTML5 canvas API | The functionality of the charting library is based on the HTML5 Canvas tag and its related API. Any web browser that supports these will be able to render and display charts generated by the igDataChart control. No other HTML5 features are required for the operation of the igDataChart control. The topic [Canvas Element: Support](http://en.wikipedia.org/wiki/Canvas_element#Support) from [Wikipedia™](http://en.wikipedia.org/wiki/Main_Page) details which versions of the most popular desktop and mobile web browsers support the HTML5 Canvas API. |
-| jQuery and jQuery UI JavaScript resources | {environment:ProductName} is built on top of these frameworks: [jQuery](http://docs.jquery.com/Main_Page) [jQuery UI](http://jqueryui.com/) |
+| jQuery and jQuery UI JavaScript resources | \{environment:ProductName\} is built on top of these frameworks: [jQuery](http://docs.jquery.com/Main_Page) [jQuery UI](http://jqueryui.com/) |
| Modernizr | The Modernizr library is used by the igDataChart to detect browser and device capabilities. It is not mandatory and if not included the control will behave as if it works in a normal desktop environment with HTML5 compatible browser. [Modernizr](http://modernizr.com/docs/) |
-| General charting JavaScript resources | The charting functionality of the {environment:ProductName} library is distributed across several files depending on the series type. In case you wish to include resources manually, you need to use the dependencies listed in the following tables. JS Resource |
-| infragistics.util.js, infragistics.util.jquery.js | {environment:ProductName} utilities |
+| General charting JavaScript resources | The charting functionality of the \{environment:ProductName\} library is distributed across several files depending on the series type. In case you wish to include resources manually, you need to use the dependencies listed in the following tables. JS Resource |
+| infragistics.util.js, infragistics.util.jquery.js | \{environment:ProductName\} utilities |
| infragistics.datasource.js | The igDataSource control. |
| infragistics.ext_core.js, infragistics.ext_collections.js, infragistics.ext_ui.js, infragistics.dv_jquerydom.js, infragistics.dv_core.js, infragistics.dv_geometry.js, infragistics.datachart_core.js | Data visualization core functionality |
| infragistics.dvcommonwidget.js | Chart and map common widget |
| infragistics.ui.chart.js | Chart UI widget |
| infragistics.legend.js, infragistics.ui.chartlegend.js | Chart legend functionality and UI widget |
| infragistics.dv_opd.js | Chart Overview Plus Detail Pane functionality |
-| infragistics.ui.widget.js | Base igWidget for all {environment:ProductName} widgets. |
+| infragistics.ui.widget.js | Base igWidget for all \{environment:ProductName\} widgets. |
</td>
</tr>
@@ -141,7 +144,7 @@ The following table summarizes the requirements for using the `igDataChart` cont
<tr>
<td>IG theme</td>
- <td>This theme contains custom visual styles created for the {environment:ProductName} library. It is contained in the following file:
</td>
</tr>
<tr>
@@ -152,7 +155,7 @@ The following table summarizes the requirements for using the `igDataChart` cont
</table>
->**Note:**To learn about the different ways to reference JavaScript resources in {environment:ProductName}, see the [Using JavaScript Resources in {environment:ProductName}](///general-and-getting-started/deployment-guide-javascript-resources.mdx) topic.
+>**Note:**To learn about the different ways to reference JavaScript resources in \{environment:ProductName\}, see the [Using JavaScript Resources in \{environment:ProductName\}](///general-and-getting-started/deployment-guide-javascript-resources.mdx) topic.
##Main Features
@@ -183,7 +186,7 @@ The legend is a visual panel that shows an icon and a title for each data series

-Legends are implemented with a separate control from the {environment:ProductName} library called `igChartLegend` and require a separate div element on the page. The div element is referred in each series object so that it is included in the legend. The `igChartLegend` is a very simple control covered in the topic referred below.
+Legends are implemented with a separate control from the \{environment:ProductName\} library called `igChartLegend` and require a separate div element on the page. The div element is referred in each series object so that it is included in the legend. The `igChartLegend` is a very simple control covered in the topic referred below.
### Composite charts
@@ -306,13 +309,13 @@ Contains basic information about the related `igPieChart` control for displaying
The following samples provide additional information related to this topic.
-- [JSON Binding]({environment:SamplesUrl}/data-chart/json-binding): This sample shows how the `igDataChart` binds to JSON data.
+- [JSON Binding](\{environment:SamplesUrl\}/data-chart/json-binding): This sample shows how the `igDataChart` binds to JSON data.
-- [Bar and Column Series]({environment:SamplesUrl}/data-chart/bar-and-column-series): Demonstrates how bar and column charts can be implemented using the `igDataChart` control.
+- [Bar and Column Series](\{environment:SamplesUrl\}/data-chart/bar-and-column-series): Demonstrates how bar and column charts can be implemented using the `igDataChart` control.
- [Chart Navigation](../04_Configuring/10_igDataChart_Configuring_Navigation_Features.mdx#example): Demonstrates user interaction with a chart including zoom, panning, dragging, and how these can be controlled from the API.
-- [Binding Real-Time Data]({environment:SamplesUrl}/data-chart/binding-real-time-data): Demonstrates how real-time data can by dynamically bound to a data chart.
+- [Binding Real-Time Data](\{environment:SamplesUrl\}/data-chart/binding-real-time-data): Demonstrates how real-time data can by dynamically bound to a data chart.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/series-types.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/series-types.mdx
index bfcdb933bc..f63f69f55c 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/series-types.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/series-types.mdx
@@ -2,6 +2,9 @@
title: "Series Types (igDataChart)"
slug: igdatachart-series-types
---
+
+# Series Types (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Series Types (igDataChart)
@@ -188,7 +191,7 @@ Composite charts plot at least two data series that either use different axis ra
This sample demonstrates how to configure a composite chart with two Y-axes with different range and two different data series types: column and line series.
There are no specific settings for creating composite charts but rather you can mix different series types and use multiple axes.
@@ -201,7 +204,7 @@ The following topics provide additional information related to this topic.
- [Adding igDataChart](/igdatachart-adding.mdx): This topic demonstrates how to add the igDataChart control to a web page and bind it to data.
-- [](/igdatachart-api-links.mdx)[jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): This topic provides links to the API documentation for jQuery and {environment:ProductNameMVC} class for `igDataChart`
+- [](/igdatachart-api-links.mdx)[jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): This topic provides links to the API documentation for jQuery and \{environment:ProductNameMVC\} class for `igDataChart`
### Samples
@@ -209,20 +212,20 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Bar and Column Series]({environment:SamplesUrl}/data-chart/bar-and-column-series): This sample demonstrates creating bar and column series charts.
+- [Bar and Column Series](\{environment:SamplesUrl\}/data-chart/bar-and-column-series): This sample demonstrates creating bar and column series charts.
-- [Category Series]({environment:SamplesUrl}/data-chart/category-series): This sample demonstrates creating category series charts.
+- [Category Series](\{environment:SamplesUrl\}/data-chart/category-series): This sample demonstrates creating category series charts.
-- [Composite Chart]({environment:SamplesUrl}/data-chart/composite-chart): This sample demonstrates creating a composite chart.
+- [Composite Chart](\{environment:SamplesUrl\}/data-chart/composite-chart): This sample demonstrates creating a composite chart.
-- [Financial Series]({environment:SamplesUrl}/data-chart/financial-series): This sample demonstrates creating financial (or “candlestick”) charts.
+- [Financial Series](\{environment:SamplesUrl\}/data-chart/financial-series): This sample demonstrates creating financial (or “candlestick”) charts.
-- [Polar Series]({environment:SamplesUrl}/data-chart/polar-series): This sample demonstrates creating polar charts.
+- [Polar Series](\{environment:SamplesUrl\}/data-chart/polar-series): This sample demonstrates creating polar charts.
-- [Radial Series]({environment:SamplesUrl}/data-chart/radial-series): This sample demonstrates creating radial charts.
+- [Radial Series](\{environment:SamplesUrl\}/data-chart/radial-series): This sample demonstrates creating radial charts.
-- [Range Category Series]({environment:SamplesUrl}/data-chart/range-category-series): This sample demonstrates creating range category charts.
+- [Range Category Series](\{environment:SamplesUrl\}/data-chart/range-category-series): This sample demonstrates creating range category charts.
-- [Scatter Series]({environment:SamplesUrl}/data-chart/scatter-series): This sample demonstrates creating scatter (or “XY series) charts.
+- [Scatter Series](\{environment:SamplesUrl\}/data-chart/scatter-series): This sample demonstrates creating scatter (or “XY series) charts.
-- [Stacked Series]({environment:SamplesUrl}/data-chart/stacked-series): This sample demonstrates creating Stacked series charts (XY charts).
\ No newline at end of file
+- [Stacked Series](\{environment:SamplesUrl\}/data-chart/stacked-series): This sample demonstrates creating Stacked series charts (XY charts).
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/visual-elements.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/visual-elements.mdx
index 24c21d591e..f9ae194959 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/overview/visual-elements.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/overview/visual-elements.mdx
@@ -2,6 +2,9 @@
title: "Configurable Visual Elements (igDataChart)"
slug: igdatachart-visual-elements
---
+
+# Configurable Visual Elements (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configurable Visual Elements (igDataChart)
@@ -119,13 +122,13 @@ This sample configures several of the elements, available in the `igDataChart` c
Chart elements such as axis, labels, grid lines, grid stripes, zoom bars, series, trend lines, indicators and crosshairs are all available to enhance the control's presentation.
In addition to the settings above, the sample below demonstrates both enabling the default tooltip for the Chart’s series and configuring a custom tooltip template for the "United States" series.
##Related Content
@@ -137,7 +140,7 @@ The following topics provide additional information related to this topic.
- [Adding igDataChart](/igdatachart-adding.mdx): This topic demonstrates how to create add the `igDataChart`™ control and bind it to data.
-- [](/igdatachart-api-links.mdx)[jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): This topic provides links to the API documentation for jQuery and {environment:ProductNameMVC} class for `igDataChart`™ control.
+- [](/igdatachart-api-links.mdx)[jQuery and MVC API Reference Links (igDataChart)](/igdatachart-api-links.mdx): This topic provides links to the API documentation for jQuery and \{environment:ProductNameMVC\} class for `igDataChart`™ control.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/series-requirements.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/series-requirements.mdx
index 68d06f1c87..89ba6a9505 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/series-requirements.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/series-requirements.mdx
@@ -6,7 +6,6 @@ slug: igdatachart-series-requirements
# Series Requirements
-
The `igDataChart`™ control supports a number of various series, and some of these series require specific axis types and data mapping in order for them to render correctly on the chart plot area.
### Overview
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/styling/the-chart-series.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/styling/the-chart-series.mdx
index 19a9d07f39..9c4f9f12cb 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/styling/the-chart-series.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/styling/the-chart-series.mdx
@@ -2,6 +2,9 @@
title: "Styling the Chart Series (igDataChart)"
slug: igdatachart-styling-the-chart-series
---
+
+# Styling the Chart Series (igDataChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Styling the Chart Series (igDataChart)
@@ -55,7 +58,7 @@ The linear gradient effect is achieved, by setting the type of the
- [Chart Fill Gradients]({environment:SamplesEmbedUrl}/data-chart/chart-fill-gradients)
+ [Chart Fill Gradients](\{environment:SamplesEmbedUrl\}/data-chart/chart-fill-gradients)
@@ -66,7 +69,7 @@ The following sample defines the chart configuration needed to achieve that effe
With the drop-shadow effect, the series appear as if casting a shadow.
@@ -224,9 +227,9 @@ The following topics provide additional information related to this topic.
- [Styling igDataChart](/igdatachart-styling-themes.mdx): This topic demonstrates how to apply styles and themes to the `igDataChart` control.
-- [Styling and Theming in {environment:ProductName}](///general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
+- [Styling and Theming in \{environment:ProductName\}](///general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
-General information and a procedure for updating styles and themes in {environment:ProductName}™ library.
+General information and a procedure for updating styles and themes in \{environment:ProductName\}™ library.
diff --git a/docs/jquery/src/content/en/topics/controls/igdatachart/styling/themes.mdx b/docs/jquery/src/content/en/topics/controls/igdatachart/styling/themes.mdx
index 3d8246952e..e047e00d3f 100644
--- a/docs/jquery/src/content/en/topics/controls/igdatachart/styling/themes.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdatachart/styling/themes.mdx
@@ -5,7 +5,6 @@ slug: igdatachart-styling-themes
# Styling igDataChart
-
##Topic Overview
@@ -22,7 +21,7 @@ This topic demonstrates how to apply styles and themes to the `igDataChart`™ c
**Topics**
-- [Styling and Theming in {environment:ProductName}](///general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx): General information and a procedure for updating styles and themes in {environment:ProductName}™ library.
+- [Styling and Theming in \{environment:ProductName\}](///general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx): General information and a procedure for updating styles and themes in \{environment:ProductName\}™ library.
**External Resources**
@@ -66,9 +65,9 @@ The `igDataChart` uses the jQuery UI CSS Framework for the purposes of applying
To customize a theme, you can use the ThemeRoller tool. This jQuery UI tool facilitates the creation of custom themes that are compatible with the jQuery UI widgets. Many prebuilt themes are available for download and use in your website. The `igDataChart` control supports the use of ThemeRoller themes.
-Detailed information for using themes with {environment:ProductName} library is available in the [Styling and Theming in {environment:ProductName}](///general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) topic.
+Detailed information for using themes with \{environment:ProductName\} library is available in the [Styling and Theming in \{environment:ProductName\}](///general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx) topic.
-Note: The base theme of {environment:ProductName} is not necessary for charts and you may safely omit it on pages only containing charts.
+Note: The base theme of \{environment:ProductName\} is not necessary for charts and you may safely omit it on pages only containing charts.
##Themes Summary
@@ -85,7 +84,7 @@ A summary of the `igDataChart` control’s available themes.
IG Theme
Path: `{IG CSS root}/themes/Infragistics/`
File: `infragistics.theme.css`
-
This theme defines general visual features for all {environment:ProductName} controls. Detailed information for using the IG theme is available in the Styling and Theming in {environment:ProductName} topic.
+
This theme defines general visual features for all \{environment:ProductName\} controls. Detailed information for using the IG theme is available in the Styling and Theming in \{environment:ProductName\} topic.
@@ -236,7 +235,7 @@ Demonstrate how to modify the default IG Chart styles with your preferred settin
1. Copy the default chart CSS file.
- **Copy the CSS file, with the default chart styles (`infragistics.ui.chart.css`), from the {environment:ProductName} installation folder to the themes folder of your web site or application.**
+ **Copy the CSS file, with the default chart styles (`infragistics.ui.chart.css`), from the \{environment:ProductName\} installation folder to the themes folder of your web site or application.**
For instance, if you have a folder `Content/themes` in your web site or application where keep the CSS files used by the application, then make a copy of the default chart CSS file mentioned above in `Content/themes/MyChartTheme/ig.ui.chart.custom.css`.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/accessibility-compliance.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/accessibility-compliance.mdx
index ab290ecb0f..4b8c7bb92d 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/accessibility-compliance.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/accessibility-compliance.mdx
@@ -24,7 +24,7 @@ The following topics are prerequisite to understanding this topic:
### Introduction
-All of the {environment:ProductName}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also, detailed information about how the grid control complies with each rule is represented.
+All of the \{environment:ProductName\}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also, detailed information about how the grid control complies with each rule is represented.
To meet the requirements of each accessibility rule, in some cases you may need to interact with the control by to setting a specific property, but in other cases the control does the work for you.
@@ -49,7 +49,7 @@ Rules | Rule Text | How We Comply
The following topics provide additional information related to this topic:
-- [Accessibility Compliance](//general-and-getting-started/accessibility-compliance.mdx): Provides reference information for accessibility compliance of all {environment:ProductName} controls.
+- [Accessibility Compliance](//general-and-getting-started/accessibility-compliance.mdx): Provides reference information for accessibility compliance of all \{environment:ProductName\} controls.
- [***igDialog* Overview**](./00_igDialog Overview.mdx): The topic introduces the user to the `igDialog` control’s main features.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/adding-igdialog.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/adding-igdialog.mdx
index 70abdff652..b3ca625cc3 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/adding-igdialog.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/adding-igdialog.mdx
@@ -2,6 +2,9 @@
title: "Adding igDialog"
slug: adding-igdialog
---
+
+# Adding igDialog
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Adding igDialog
@@ -10,7 +13,7 @@ import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
This procedure guides you through the process of adding an `igDialog` control to a web page. The `igDialog` is configured so that all of the header buttons are enabled – such as buttons for minimize, maximize, pin and close.
-You have the option of instantiating the control in several ways. This topic demonstrates the typical jQuery UI method, the jQuery method (by using attributes) and instantiating the control using the {environment:ProductNameMVC} Dialog.
+You have the option of instantiating the control in several ways. This topic demonstrates the typical jQuery UI method, the jQuery method (by using attributes) and instantiating the control using the \{environment:ProductNameMVC\} Dialog.
### Preview
@@ -60,7 +63,7 @@ The recommended approach to instantiating the `igDialog` control is to use the l
```
-> **Note:** If you are using {environment:ProductNameMVC} Dialog, remember to reference the ***Infragistics.Web.Mvc*** dll into your project.
+> **Note:** If you are using \{environment:ProductNameMVC\} Dialog, remember to reference the ***Infragistics.Web.Mvc*** dll into your project.
### 2. Instantiate igDialog
@@ -107,7 +110,7 @@ The following code demonstrates how to initialize `igDialog` control, with full
});
```
-If you want to use the `igDialog` with TypeScript, you can instantiate it using the code above. You just need to include the reference paths to the {environment:ProductFamilyName} and jQuery type definitions for TypeScript:
+If you want to use the `igDialog` with TypeScript, you can instantiate it using the code above. You just need to include the reference paths to the \{environment:ProductFamilyName\} and jQuery type definitions for TypeScript:
**In TypeScript:**
```typescript
@@ -118,11 +121,11 @@ If you want to use the `igDialog` with TypeScript, you can instantiate it using
>**Note:** This is needed for TypeScript versions prior to 1.5 so the compiler could include the dependencies in the program during compilation. In 1.5 and newer versions they can be defined in a separate tsconfig.json file. For more information see the [tsconfig.json wiki page](https://github.com/Microsoft/TypeScript/wiki/tsconfig.json)
-> More information on how to use the {environment:ProductName} definitions for TypeScript can be found in ["Using {environment:ProductName} with TypeScript" topic](using-ignite-ui-with-typescript.html).
+> More information on how to use the \{environment:ProductName\} definitions for TypeScript can be found in ["Using \{environment:ProductName\} with TypeScript" topic](using-ignite-ui-with-typescript.html).
- **Razor Initialization**
- It’s important to know that the {environment:ProductNameMVC} Dialog is not like the other controls where it is expected that it will render the HTML, along with the JavaScript code that initializes the control. Because the `igDialog` content can be any HTML markup, you need to define the markup first, and then the {environment:ProductNameMVC} will define all the configurations of the control.
+ It’s important to know that the \{environment:ProductNameMVC\} Dialog is not like the other controls where it is expected that it will render the HTML, along with the JavaScript code that initializes the control. Because the `igDialog` content can be any HTML markup, you need to define the markup first, and then the \{environment:ProductNameMVC\} will define all the configurations of the control.
- Define `DIV` HTML placeholder
@@ -134,7 +137,7 @@ If you want to use the `igDialog` with TypeScript, you can instantiate it using
```
- {environment:ProductNameMVC} code:
+ \{environment:ProductNameMVC\} code:
**In C#:**
@@ -152,25 +155,25 @@ If you want to use the `igDialog` with TypeScript, you can instantiate it using
)
```
-> **Note**: When you want to set identifier of the {environment:ProductNameMVC} Dialog, you have three different options. For more information see the [Property Reference](./03_API Reference/00_igDialog Property Reference.mdx) topic. If the defined HTML placeholder has the same ID as in the sample above – `igDialog1`, then you can use one of the following:
+> **Note**: When you want to set identifier of the \{environment:ProductNameMVC\} Dialog, you have three different options. For more information see the [Property Reference](./03_API Reference/00_igDialog Property Reference.mdx) topic. If the defined HTML placeholder has the same ID as in the sample above – `igDialog1`, then you can use one of the following:
> `Dialog.ContentJquerySelector("#igDialog1")` – defines the selector – the same as it is supposed to be in the jQuery.
-> `Dialog.ContentID("igDialog1")` – defines the selector without the #, which will be rendered automatically by the {environment:ProductNameMVC}.
+> `Dialog.ContentID("igDialog1")` – defines the selector without the #, which will be rendered automatically by the \{environment:ProductNameMVC\}.
> `Dialog.ID(“igDialog1”)` – the same as the `ContentID(“igDialog1”)`
-> **Note**: If you want to define the HTML DIV Placeholder code using the {environment:ProductNameMVC}, then the Dialog Helper suggests the following method. Assume that you want to achieve the same effect as defining an DIV HTML placeholder, then use: `Dialog.ContentHTML("
igDialog Content
")`
+> **Note**: If you want to define the HTML DIV Placeholder code using the \{environment:ProductNameMVC\}, then the Dialog Helper suggests the following method. Assume that you want to achieve the same effect as defining an DIV HTML placeholder, then use: `Dialog.ContentHTML("
igDialog Content
")`
- **Instantiate in AngularJS**
The following example demonstrates how to declare a Dialog Window with an AngularJS directive:
-> More information on how to use the {environment:ProductName} directives for AngularJS can be found in ["Using {environment:ProductName} with AngularJS" topic](../../10_AngularJS Directives/00_Using_Ignite_UI_with_AngularJS.mdx).
+> More information on how to use the \{environment:ProductName\} directives for AngularJS can be found in ["Using \{environment:ProductName\} with AngularJS" topic](../../10_AngularJS Directives/00_Using_Ignite_UI_with_AngularJS.mdx).
## Destroy igDialog
@@ -204,4 +207,4 @@ The following topics provide additional information related to this topic:
The following sample provide additional information related to this topic:
-- [Icons]({environment:SamplesUrl}/dialog-window/icons): This sample demonstrates you how to show `igDialog` icons.
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons): This sample demonstrates you how to show `igDialog` icons.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/css-classes-reference.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/css-classes-reference.mdx
index e43cad5080..0ee12a23b4 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/css-classes-reference.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/css-classes-reference.mdx
@@ -2,6 +2,9 @@
title: "CSS Classes Reference (igDialog)"
slug: igdialog-css-classes-reference
---
+
+# CSS Classes Reference (igDialog)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# CSS Classes Reference (igDialog)
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/event-reference.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/event-reference.mdx
index f8d17358c1..ece749ef7d 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/event-reference.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/event-reference.mdx
@@ -2,6 +2,9 @@
title: "Event Reference (igDialog)"
slug: igdialog-event-reference
---
+
+# Event Reference (igDialog)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Event Reference (igDialog)
@@ -56,7 +59,7 @@ $("#igDialog1").igDialog({
The following example shows how this is done and it also demonstrates the use of the jQuery's [`on`](http://api.jquery.com/on/) method to attach an event handler to a selected element:
### Attaching Event Handlers in MVC
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/method-reference.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/method-reference.mdx
index d5b03425e7..a19f33b6ca 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/method-reference.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/method-reference.mdx
@@ -2,6 +2,9 @@
title: "Method Reference (igDialog)"
slug: igdialog-method-reference
---
+
+# Method Reference (igDialog)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Method Reference (igDialog)
@@ -58,7 +61,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
- [API and Events](./02_igDialog Event Reference.mdx#attaching-handlers-jquery): This sample demonstrates how to handle events in the Dialog Window control and API usage.
-- [Modal Dialog]({environment:SamplesUrl}/dialog-window/modal-dialog): This sample shows you how to create a modal dialog.
+- [Modal Dialog](\{environment:SamplesUrl\}/dialog-window/modal-dialog): This sample shows you how to create a modal dialog.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/property-reference.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/property-reference.mdx
index 235c0df907..927520b113 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/property-reference.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/api-reference/property-reference.mdx
@@ -2,6 +2,9 @@
title: "Property Reference (igDialog)"
slug: igdialog-property-reference
---
+
+# Property Reference (igDialog)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Property Reference (igDialog)
@@ -73,16 +76,16 @@ The following table summarizes the purpose and functionality of the `igDialog` c
## MVC Method Reference
-The following table summarizes the purpose and functionality of * {environment:ProductNameMVC} * `Dialog`. Most of the methods correspond to the jQuery properties except for and . There are additional MVC methods that don’t have corresponding igDialog properties, such as: [`ContentJquerySelector`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html), [`ContentID`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentID.html), [`ID`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ID.html), [`ContentHTML`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogWrapper~ContentHTML.html).
+The following table summarizes the purpose and functionality of * \{environment:ProductNameMVC\} * `Dialog`. Most of the methods correspond to the jQuery properties except for and . There are additional MVC methods that don’t have corresponding igDialog properties, such as: [`ContentJquerySelector`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html), [`ContentID`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentID.html), [`ID`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ID.html), [`ContentHTML`](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogWrapper~ContentHTML.html).
| | | | |
| --- | --- | --- | --- |
| Property | Parameter Type | Values (**Default Value**) | Description |
-| [ContentJquerySelector](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html) | string | “#igDialog1” | This property defines the selector for the {environment:ProductNameMVC} Dialog. This selector should be the same as the selector when the jQuery-only widget is created. For example, if your HTML placeholder has the id “igDialog1”, then the value of [ContentJquerySelector](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html) should be “#igDialog”. Then, the {environment:ProductNameMVC} will render following code: $(“#igDialog”).igDialog(); |
-| [ContentID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentID.html) | string | “igDialog1” | This property defines the selector for the {environment:ProductNameMVC} Dialog. In contrast to the [ContentJquerySelector](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html) property, you only need to pass the id of the HTML placeholder, without the #, and the {environment:ProductNameMVC} will render it automatically. If your value in the [ContentID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentID.html) is “igDialog”, then the result will be the same as in the previous property: $(“#igDialog”).igDialog(); |
-| [ID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ID.html) | string | “igDialog1” | This property defines the selector for the {environment:ProductNameMVC} Dialog. It’s absolutely equivalent to the [ContentID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogWrapper~ContentID.html) property – it accepts the same format for the parameter and renders the same code. |
-| [ContentHTML](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentHTML.html) | string | “<div id="igDialog1”> igDialog Content </div>” | This property allows you to define the HTML placeholder of the {environment:ProductNameMVC} Dialog. This HTML code will then become the content of the igDialog. |
+| [ContentJquerySelector](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html) | string | “#igDialog1” | This property defines the selector for the \{environment:ProductNameMVC\} Dialog. This selector should be the same as the selector when the jQuery-only widget is created. For example, if your HTML placeholder has the id “igDialog1”, then the value of [ContentJquerySelector](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html) should be “#igDialog”. Then, the \{environment:ProductNameMVC\} will render following code: $(“#igDialog”).igDialog(); |
+| [ContentID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentID.html) | string | “igDialog1” | This property defines the selector for the \{environment:ProductNameMVC\} Dialog. In contrast to the [ContentJquerySelector](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentJquerySelector.html) property, you only need to pass the id of the HTML placeholder, without the #, and the \{environment:ProductNameMVC\} will render it automatically. If your value in the [ContentID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentID.html) is “igDialog”, then the result will be the same as in the previous property: $(“#igDialog”).igDialog(); |
+| [ID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ID.html) | string | “igDialog1” | This property defines the selector for the \{environment:ProductNameMVC\} Dialog. It’s absolutely equivalent to the [ContentID](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogWrapper~ContentID.html) property – it accepts the same format for the parameter and renders the same code. |
+| [ContentHTML](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ContentHTML.html) | string | “<div id="igDialog1”> igDialog Content </div>” | This property allows you to define the HTML placeholder of the \{environment:ProductNameMVC\} Dialog. This HTML code will then become the content of the igDialog. |
| [Container](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~Container.html) | string | “#idContainer” “.classContainer” | Gets or sets the HTML container element for the igDialog. By default the parent form of the original target element is used and if that parent is unavailable, then the HTML body object is used. Note that if the CSS container property “position” is not set, its value is "static", then the position value is set to "relative". |
| [State](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~State.html) | string | **DialogState.Opened** DialogState.Closed DialogState.Minimized DialogState.Maximized | This property allows you to set and get the state of the dialog. |
| [Pinned](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~Pinned.html) | bool? | true **false** | Gets or sets the pinned state of the dialog. |
@@ -94,7 +97,7 @@ The following table summarizes the purpose and functionality of * {environm
| [EnableHeaderFocus](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogWrapper~EnableHeaderFocus.html) | bool? | **true** false | Gets or sets the ability to adjust the state of the header to be in focused or not-focused state. This property works only if the [trackFocus](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~TrackFocus.html) property is enabled. |
| [TabIndex](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogWrapper~TabIndex.html) | int? | **0** | Gets or sets the value for the tabIndex attribute applied to the igDialog main HTML element. |
| [ZIndex](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~ZIndex.html) | int? | **1000** | Gets or sets the value of the zIndex applied to the igDialog main HTML element. |
-| [EnableDblclick](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~EnableDblclick.html) | bool? | true false | Gets or sets the action that will occur if the igDialog header is double clicked. If the value is “false,” the window will not be affected by mouse double click. Contrastingly, it will react if the value is “true”. The “auto” state means that the igDialog will only be affected by double click if there is maximize icon in the header. “Auto” is the default state, but you cannot change it dynamically through the {environment:ProductNameMVC}. |
+| [EnableDblclick](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~EnableDblclick.html) | bool? | true false | Gets or sets the action that will occur if the igDialog header is double clicked. If the value is “false,” the window will not be affected by mouse double click. Contrastingly, it will react if the value is “true”. The “auto” state means that the igDialog will only be affected by double click if there is maximize icon in the header. “Auto” is the default state, but you cannot change it dynamically through the \{environment:ProductNameMVC\}. |
| [Height](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~Height.html) | string | 100 “100px” “2em” “100%” | Gets or sets the initial height of the dialog in pixels for the normal state. Note that if “%” is used, then the size of the window browser object is used and it only takes effect when the igDialog is opening. |
| [Width](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~Width.html) | string | **300** “300px” “2em” “100%” | Gets or sets the initial width of the dialog in pixels for the normal state. Note that if “%” is used, then the size of the window browser object is used and it only takes effect when the igDialog is opening. |
| [MinHeight](Infragistics.Web.Mvc~Infragistics.Web.Mvc.DialogModel~MinHeight.html) | string | **100** “100px” “2em” “100%” | Gets or sets the minimal height of the dialog in the normal state. |
@@ -139,15 +142,15 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Basic Usage]({environment:SamplesUrl}/dialog-window/basic-usage): This sample shows you how to configure the `igDialog` height, width and state.
+- [Basic Usage](\{environment:SamplesUrl\}/dialog-window/basic-usage): This sample shows you how to configure the `igDialog` height, width and state.
- [API and Events](./02_igDialog Event Reference.mdx#attaching-handlers-jquery): This sample demonstrates how to handle events in the Dialog Window control and API usage.
-- [ASP.NET MVC Basic Usage]({environment:SamplesUrl}/dialog-window/aspnet-mvc-helper): This example demonstrates how you can utilize the ASP.NET MVC helper for the Dialog Window.
+- [ASP.NET MVC Basic Usage](\{environment:SamplesUrl\}/dialog-window/aspnet-mvc-helper): This example demonstrates how you can utilize the ASP.NET MVC helper for the Dialog Window.
-- [Modal Dialog]({environment:SamplesUrl}/dialog-window/modal-dialog): This sample shows you how to create a modal dialog.
+- [Modal Dialog](\{environment:SamplesUrl\}/dialog-window/modal-dialog): This sample shows you how to create a modal dialog.
-- [Loading External Page]({environment:SamplesUrl}/dialog-window/loading-external-page): This sample demonstrates how to load external content from a URL.
+- [Loading External Page](\{environment:SamplesUrl\}/dialog-window/loading-external-page): This sample demonstrates how to load external content from a URL.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/animations.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/animations.mdx
index 0f53b3fdaf..a69468a75d 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/animations.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/animations.mdx
@@ -2,6 +2,9 @@
title: "igDialog Animations"
slug: igdialog-animations
---
+
+# igDialog Animations
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Animations
@@ -71,7 +74,7 @@ $("#dialog").igDialog({
### Example with MVC
-The code below demonstrates how set the animations for the {environment:ProductNameMVC} Dialog:
+The code below demonstrates how set the animations for the \{environment:ProductNameMVC\} Dialog:
**In C#:**
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/external-page.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/external-page.mdx
index 0ed051a62e..c9f3c8bddb 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/external-page.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/external-page.mdx
@@ -2,6 +2,9 @@
title: "igDialog External Page"
slug: igdialog-external-page
---
+
+# igDialog External Page
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog External Page
@@ -84,7 +87,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Loading External Page]({environment:SamplesUrl}/dialog-window/loading-external-page): This sample demonstrates how to load external content from a URL.
+- [Loading External Page](\{environment:SamplesUrl\}/dialog-window/loading-external-page): This sample demonstrates how to load external content from a URL.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/header-and-footer.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/header-and-footer.mdx
index 340b020d46..06d217b3fe 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/header-and-footer.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/header-and-footer.mdx
@@ -2,6 +2,9 @@
title: "igDialog Header and Footer"
slug: igdialog-header-and-footer
---
+
+# igDialog Header and Footer
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Header and Footer
@@ -119,7 +122,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Icons]({environment:SamplesUrl}/dialog-window/icons): The sample that shows you how to show `igDialog` icons.
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons): The sample that shows you how to show `igDialog` icons.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/maximize-and-minimize.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/maximize-and-minimize.mdx
index e87c41bcf1..e2435f880d 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/maximize-and-minimize.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/maximize-and-minimize.mdx
@@ -2,6 +2,9 @@
title: "igDialog Maximize and Minimize"
slug: igdialog-maximize-and-minimize
---
+
+# igDialog Maximize and Minimize
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Maximize and Minimize
@@ -202,7 +205,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Icons]({environment:SamplesUrl}/dialog-window/icons): The sample that shows you how to show `igDialog` icons.
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons): The sample that shows you how to show `igDialog` icons.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/modal-state.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/modal-state.mdx
index 40e4a0a7c7..4ad0cf13b1 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/modal-state.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/modal-state.mdx
@@ -2,6 +2,9 @@
title: "igDialog Modal State"
slug: igdialog-modal-state
---
+
+# igDialog Modal State
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Modal State
@@ -90,7 +93,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Modal Dialog]({environment:SamplesUrl}/dialog-window/modal-dialog) : This sample shows you how to create a modal `igDialog`.
+- [Modal Dialog](\{environment:SamplesUrl\}/dialog-window/modal-dialog) : This sample shows you how to create a modal `igDialog`.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/multiple-dialogs.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/multiple-dialogs.mdx
index dec5c9132a..942e66da4b 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/multiple-dialogs.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/multiple-dialogs.mdx
@@ -2,6 +2,9 @@
title: "igDialog Multiple Dialogs"
slug: igdialog-multiple-dialogs
---
+
+# igDialog Multiple Dialogs
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Multiple Dialogs
@@ -45,7 +48,7 @@ You can show multiple `igDialog` widgets on a single page and they will appear p
What the control does automatically is it detects the first HTML placeholder and initializes the first dialog widget at the bottom. Respectively, the last `igDialog` HTML placeholder will be for the top widget. The `igDialog` exposes API methods that grant access to the top dialogs and the ability to move dialogs to the top level if they are not there already.
-> **Note:** You cannot achieve this functionality using {environment:ProductNameMVC} Dialog.
+> **Note:** You cannot achieve this functionality using \{environment:ProductNameMVC\} Dialog.
### Code
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/pin.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/pin.mdx
index f00203077b..060c941540 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/pin.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/pin.mdx
@@ -2,6 +2,9 @@
title: "igDialog Pin"
slug: igdialog-pin
---
+
+# igDialog Pin
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Pin
@@ -163,7 +166,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Icons]({environment:SamplesUrl}/dialog-window/icons): The sample that shows you how to show `igDialog` icons.
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons): The sample that shows you how to show `igDialog` icons.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/position.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/position.mdx
index 3a6a83faf5..a20f9939a3 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/position.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/position.mdx
@@ -2,6 +2,9 @@
title: "igDialog Position"
slug: igdialog-position
---
+
+# igDialog Position
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Position
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/show-and-hide.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/show-and-hide.mdx
index ec9a109f82..e4afa5f0a6 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/configuring/show-and-hide.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/configuring/show-and-hide.mdx
@@ -2,6 +2,9 @@
title: "igDialog Show and Hide"
slug: igdialog-show-and-hide
---
+
+# igDialog Show and Hide
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Show and Hide
@@ -126,7 +129,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Basic Usage]({environment:SamplesUrl}/dialog-window/basic-usage): This sample shows you how to configure the `igDialog` height, width and state.
+- [Basic Usage](\{environment:SamplesUrl\}/dialog-window/basic-usage): This sample shows you how to configure the `igDialog` height, width and state.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/known-issues.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/known-issues.mdx
index f73803884a..e03c176ab9 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/known-issues.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/known-issues.mdx
@@ -2,6 +2,9 @@
title: "Known Issues and Limitations (igDialog)"
slug: igdialog-known-issues
---
+
+# Known Issues and Limitations (igDialog)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Known Issues and Limitations (igDialog)
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/overview.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/overview.mdx
index cb39eb8c94..7c521a4100 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/overview.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/overview.mdx
@@ -2,6 +2,9 @@
title: "igDialog Overview"
slug: igdialog-overview
---
+
+# igDialog Overview
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDialog Overview
@@ -103,7 +106,7 @@ The main functionality is that a window has the ability to show and hide itself.
**Related Samples:**
-- [Basic Usage]({environment:SamplesUrl}/dialog-window/basic-usage)
+- [Basic Usage](\{environment:SamplesUrl\}/dialog-window/basic-usage)
### Maximize and Minimize
@@ -115,7 +118,7 @@ You can maximize and minimize the `igDialog` by using the appropriate buttons. T
**Related Samples:**
-- [Icons]({environment:SamplesUrl}/dialog-window/icons)
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons)
### Pin
@@ -127,7 +130,7 @@ The `igDialog` can be pinned the to the parent container at its top left edge. T
**Related Samples:**
-- [Icons]({environment:SamplesUrl}/dialog-window/icons)
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons)
### Drag
@@ -135,7 +138,7 @@ You can drag and drop the `igDialog`. The only property that needs to be modifie
**Related Samples:**
-- [**Basic Usage**]({environment:SamplesUrl}/dialog-window/basic-usage)
+- [**Basic Usage**](\{environment:SamplesUrl\}/dialog-window/basic-usage)
### Resize
@@ -143,7 +146,7 @@ You can drag and drop the `igDialog`. The only property that needs to be modifie
**Related Samples:**
-- [Basic Usage]({environment:SamplesUrl}/dialog-window/basic-usage)
+- [Basic Usage](\{environment:SamplesUrl\}/dialog-window/basic-usage)
### Position
@@ -167,7 +170,7 @@ The `igDialog` control proposes properties for modifying the footer and header a
**Related Samples:**
-- [Icons]({environment:SamplesUrl}/dialog-window/icons)
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons)
### Keyboard support
@@ -179,7 +182,7 @@ You can close the `igDialog` using the “ESC” key. The only property that nee
**Related Samples:**
-- [Basic Usage]({environment:SamplesUrl}/dialog-window/basic-usage)
+- [Basic Usage](\{environment:SamplesUrl\}/dialog-window/basic-usage)
### Modal state
@@ -191,7 +194,7 @@ When `igDialog` is in modal state, the page in the background is hidden and disa
**Related Samples:**
-- [Modal Dialog]({environment:SamplesUrl}/dialog-window/modal-dialog)
+- [Modal Dialog](\{environment:SamplesUrl\}/dialog-window/modal-dialog)
### Multiple dialogs
@@ -211,7 +214,7 @@ The `igDialog` can have an entire page as content. For more information on how t
**Related Samples:**
-- [Loading External Page]({environment:SamplesUrl}/dialog-window/loading-external-page)
+- [Loading External Page](\{environment:SamplesUrl\}/dialog-window/loading-external-page)
### Animations
@@ -258,7 +261,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Basic Usage]({environment:SamplesUrl}/dialog-window/basic-usage): This sample shows you how to configure the `igDialog` height, width and state.
+- [Basic Usage](\{environment:SamplesUrl\}/dialog-window/basic-usage): This sample shows you how to configure the `igDialog` height, width and state.
diff --git a/docs/jquery/src/content/en/topics/controls/igdialog/styling-and-theming.mdx b/docs/jquery/src/content/en/topics/controls/igdialog/styling-and-theming.mdx
index c6b9977b7f..cd1d859ecf 100644
--- a/docs/jquery/src/content/en/topics/controls/igdialog/styling-and-theming.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdialog/styling-and-theming.mdx
@@ -82,7 +82,7 @@ The following topics provide additional information related to this topic:
The following samples provide additional information related to this topic:
-- [Icons]({environment:SamplesUrl}/dialog-window/icons): This sample demonstrates you how to show `igDialog` icons.
+- [Icons](\{environment:SamplesUrl\}/dialog-window/icons): This sample demonstrates you how to show `igDialog` icons.
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/accessibility-compliance.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/accessibility-compliance.mdx
index 922669ce6a..a58203052b 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/accessibility-compliance.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/accessibility-compliance.mdx
@@ -2,6 +2,9 @@
title: "Accessibility Compliance (igDoughnutChart)"
slug: igdoughnutchart-accessibility-compliance
---
+
+# Accessibility Compliance (igDoughnutChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Accessibility Compliance (igDoughnutChart)
@@ -25,7 +28,7 @@ The following topics are prerequisites to understanding this topic:
### Introduction
-All of the {environment:ProductName}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also, detailed is how the `igDoughnutChart` control complies with each of these rules.
+All of the \{environment:ProductName\}™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. Table 1 contains the specific rules of Subpart 1194.22 that pertain to the control. Also, detailed is how the `igDoughnutChart` control complies with each of these rules.
In some cases, to meet the requirements of each accessibility rule, you may need to interact with the control by setting a specific property, but in other cases, the control performs these tasks for you.
@@ -46,7 +49,7 @@ Rules | Rule text | How we comply
### Topics
The following topic provides additional information related to this topic.
-- [Accessibility Compliance](//general-and-getting-started/accessibility-compliance.mdx): This topic provides reference information for the accessibility compliance of all controls in the {environment:ProductName} product.
+- [Accessibility Compliance](//general-and-getting-started/accessibility-compliance.mdx): This topic provides reference information for the accessibility compliance of all controls in the \{environment:ProductName\} product.
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/adding.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/adding.mdx
index e4e7479ec2..bb031244cd 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/adding.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/adding.mdx
@@ -15,7 +15,7 @@ This is a group of topics demonstrating how to add the `igDoughnutChart`™ cont
- [Adding *igDoughnutChart* to an HTML Page](/igdoughnutchart-adding-to-an-html-page.mdx): This topic explains how to add the `igDoughnutChart` to an HTML page.
-- [Adding *igDoughnutChart* to an ASP.NET MVC Application](/igdoughnutchart-adding-using-the-mvc-helper.mdx): This topic walks through instantiating an `igDoughnutChart` in an ASP.NET MVC application using {environment:ProductNameMVC}.
+- [Adding *igDoughnutChart* to an ASP.NET MVC Application](/igdoughnutchart-adding-using-the-mvc-helper.mdx): This topic walks through instantiating an `igDoughnutChart` in an ASP.NET MVC application using \{environment:ProductNameMVC\}.
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/to-an-html-page.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/to-an-html-page.mdx
index ea6d586cbf..a05bc9ffd4 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/to-an-html-page.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/to-an-html-page.mdx
@@ -15,7 +15,7 @@ This topic explains how to add the `igDoughnutChart`™ to an HTML page.
The following topics are prerequisites to understanding this topic:
-- [Adding Required Resources Manually](///general-and-getting-started/adding-the-required-resources-for-igniteui-for-jquery.mdx): This topic provides general guidance on adding required JavaScript resources to use controls from the {environment:ProductName} library.
+- [Adding Required Resources Manually](///general-and-getting-started/adding-the-required-resources-for-igniteui-for-jquery.mdx): This topic provides general guidance on adding required JavaScript resources to use controls from the \{environment:ProductName\} library.
- [*igDoughnutChart* Overview](/igdoughnutchart-overview.mdx): This topic provides an overall look at the `igDoughnutChart` control.
@@ -49,13 +49,13 @@ The following table summarizes the requirements for using the `igDoughnutChart`
| | | |
| --- | --- | --- |
| Required Resources | Description | What you need to do… |
-| jQuery and jQuery UI JavaScript resources | {environment:ProductName}™ is built on top of the following frameworks: [jQuery](http://jquery.com/) [jQuery UI](http://jqueryui.com/) | Add script references to both libraries in the `` section of your page. |
+| jQuery and jQuery UI JavaScript resources | \{environment:ProductName\}™ is built on top of the following frameworks: [jQuery](http://jquery.com/) [jQuery UI](http://jqueryui.com/) | Add script references to both libraries in the `` section of your page. |
| igDoughnutChart CSS resource files | Uses the styles from the following CSS file for rendering various elements of the control:, <IG CSS root>/structure/modules/infragistics.ui.html5.css, <IG CSS root>/structure/modules/infragistics.ui.shared.css, <IG CSS root>/structure/modules/infragistics.ui.chart.css | |
-| General `igDoughnutChart` JavaScript Resources | The igDoughnutChart control depends on functionality distributed across several files in the {environment:ProductName} Library. Load the required resources in one of the following ways: Using the Infragistics® Loader (igLoader™). You only need to include a script reference to igLoader on your page. Loading the required resources manually. You need to use the dependencies listed in the table below. Loading the two combined files, containing the logic for all data visualization controls from the {environment:ProductName} package: infragistics.core.js and infragistics.dv.js. The following table lists the {environment:ProductName} library dependences related to the igDoughnutChart control. Refer to these resources explicitly if not to using igLoader or the combined files. JS Resource | Description |
-| infragistics.util.js, infragistics.util.jquery.js | {environment:ProductName} utilities | |
+| General `igDoughnutChart` JavaScript Resources | The igDoughnutChart control depends on functionality distributed across several files in the \{environment:ProductName\} Library. Load the required resources in one of the following ways: Using the Infragistics® Loader (igLoader™). You only need to include a script reference to igLoader on your page. Loading the required resources manually. You need to use the dependencies listed in the table below. Loading the two combined files, containing the logic for all data visualization controls from the \{environment:ProductName\} package: infragistics.core.js and infragistics.dv.js. The following table lists the \{environment:ProductName\} library dependences related to the igDoughnutChart control. Refer to these resources explicitly if not to using igLoader or the combined files. JS Resource | Description |
+| infragistics.util.js, infragistics.util.jquery.js | \{environment:ProductName\} utilities | |
| infragistics.datasource.js | Data source framework | |
| infragistics.templating.js | Template engine (igTemplate™) | |
-| infragistics.ui.widget.js | Base igWidget for all {environment:ProductName} widgets. | |
+| infragistics.ui.widget.js | Base igWidget for all \{environment:ProductName\} widgets. | |
| infragistics.ext_core.js,, infragistics.ext_collections.js,, infragistics.ext_ui.js,, infragistics.dv_jquerydom.js,, infragistics.dv_core.js,, infragistics.dv_geometry.js Data visualization core functionality | | |
| infragistics.datachart_core.js Common chart visualization functionality | | |
| infragistics.dv_interactivity.js | Provides support for user interaction such as panning, zooming, dragging, etc. | |
@@ -63,7 +63,7 @@ The following table summarizes the requirements for using the `igDoughnutChart`
| infragistics.doughnutchart.js | Doughnut chart visualization logic | |
| infragistics.legend.js | Common chart code for legend functionality | |
| infragistics.dvcommonwidget.js | Chart and map common widget | |
-| infragistics.ui.chartlegend.js | The igChartLegend™ control is common to all {environment:ProductName} chart controls | |
+| infragistics.ui.chartlegend.js | The igChartLegend™ control is common to all \{environment:ProductName\} chart controls | |
| infragistics.ui.basechart.js | Common code for chart widgets | |
| infragistics.ui.chart.js | `igDataChart` widget UI code | |
| infragistics.ui.doughnutchart.js | The `igDoughnutChart` widget UI code | |
@@ -74,7 +74,7 @@ The following table summarizes the requirements for using the `igDoughnutChart`
<tr>
<td>IG Theme(Optional)</td>
- <td>This theme contains the visual styles for the {environment:ProductName} library. The theme file is:<IG CSS root>/themes/Infragistics/infragistics.theme.css</td>
+ <td>This theme contains the visual styles for the \{environment:ProductName\} library. The theme file is:<IG CSS root>/themes/Infragistics/infragistics.theme.css</td>
<td></td>
</tr>
</tbody>
@@ -307,13 +307,13 @@ Follow these steps to add an `igDoughnutChart` to an HTML page.
The following topics provide additional information related to this topic.
-- [Adding *igDoughnutChart* to an ASP.NET MVC Application](/igdoughnutchart-adding-using-the-mvc-helper.mdx): This topic walks through instantiating an `igDoughnutChart` in an ASP.NET MVC application using {environment:ProductNameMVC}.
+- [Adding *igDoughnutChart* to an ASP.NET MVC Application](/igdoughnutchart-adding-using-the-mvc-helper.mdx): This topic walks through instantiating an `igDoughnutChart` in an ASP.NET MVC application using \{environment:ProductNameMVC\}.
-- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the {environment:ProductNameMVC} for it.
+- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the \{environment:ProductNameMVC\} for it.
### Samples
The following sample provides additional information related to this topic.
-- [Bind to JSON]({environment:SamplesUrl}/doughnut-chart/bind-json): This is a basic example of the doughnut chart bound to JSON data.
\ No newline at end of file
+- [Bind to JSON](\{environment:SamplesUrl\}/doughnut-chart/bind-json): This is a basic example of the doughnut chart bound to JSON data.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/using-the-mvc-helper.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/using-the-mvc-helper.mdx
index 5e4c72bcc6..5cb5758bee 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/using-the-mvc-helper.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/adding/using-the-mvc-helper.mdx
@@ -2,6 +2,9 @@
title: "Adding igDoughnutChart to an ASP.NET MVC Application"
slug: igdoughnutchart-adding-using-the-mvc-helper
---
+
+# Adding igDoughnutChart to an ASP.NET MVC Application
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Adding igDoughnutChart to an ASP.NET MVC Application
@@ -10,7 +13,7 @@ import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
### Purpose
-This topic walks through using {environment:ProductNameMVC} to instantiate an ™ in an ASP.NET MVC application.
+This topic walks through using \{environment:ProductNameMVC\} to instantiate an ™ in an ASP.NET MVC application.
### Required background
@@ -22,7 +25,7 @@ The following table lists the concepts and topics required as a prerequisite to
- ASP.NET MVC
- ASP.NET MVC HTML Helpers
- **Topics**
- - [Adding Controls to an MVC Project](../../../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx): This topic explains how to get started with {environment:ProductName}™ components in an ASP.NET MVC application.
+ - [Adding Controls to an MVC Project](../../../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx): This topic explains how to get started with \{environment:ProductName\}™ components in an ASP.NET MVC application.
@@ -48,7 +51,7 @@ This topic contains the following sections:
### Adding *igDoughnutChart* summary
-The successful addition of `igDoughnutChart` to an ASP.NET MVC application, using {environment:ProductNameMVC} requires that you adjust its size by specifying values for its and options and adding at least one to it.
+The successful addition of `igDoughnutChart` to an ASP.NET MVC application, using \{environment:ProductNameMVC\} requires that you adjust its size by specifying values for its and options and adding at least one to it.
You must provide a pre-configured data source instance, or create one internally for the series. Apart from the option, in order to display the control, the and options require a value. The `valueMemberPath` parameter contains the value used in creating the slices of the series. In this example, the `ProductItemCollection` model is used to instantiate the `dataSource` option of the series. The `valueMemberPath` of the series is set to Index and uses its value to build its slices.
@@ -59,7 +62,7 @@ An ASP.NET MVC application configured with the required JavaScript files, CSS fi
## Adding igDoughnutChart to an ASP.NET MVC Application
-This topic walks through using {environment:ProductNameMVC} to instantiate an igDoughnutChart in an ASP.NET MVC application.
+This topic walks through using \{environment:ProductNameMVC\} to instantiate an igDoughnutChart in an ASP.NET MVC application.
### Preview
@@ -85,7 +88,7 @@ Following is a conceptual overview of the process:
### Steps
-This topic walks through using {environment:ProductNameMVC} to instantiate an `igDoughnutChart` in an ASP.NET MVC application.
+This topic walks through using \{environment:ProductNameMVC\} to instantiate an `igDoughnutChart` in an ASP.NET MVC application.
1. **Add a reference to *Infragistics.Web.Mvc.dll***
@@ -95,7 +98,7 @@ This topic walks through using {environment:ProductNameMVC} to instant
**1.** Import the *Infragistics.Web.Mvc* namespace
- In order to use {environment:ProductNameMVC}, you must first import the Infragistics.Web.Mvc namespace onto your view.
+ In order to use \{environment:ProductNameMVC\}, you must first import the Infragistics.Web.Mvc namespace onto your view.
**In ASPX:**
```csharp
@@ -184,7 +187,7 @@ This topic walks through using {environment:ProductNameMVC} to instant
4. **Instantiate the *igDoughnutChart***
- **Use {environment:ProductNameMVC} and set basic options in order to Instantiate the `igDoughnutChart`.** Use {environment:ProductNameMVC} within the body of your ASP.NET page to instantiate the `igDoughnutChart`. Several helper methods need to be set for a basic rendering when instantiating the control, there are including the following:
+ **Use \{environment:ProductNameMVC\} and set basic options in order to Instantiate the `igDoughnutChart`.** Use \{environment:ProductNameMVC\} within the body of your ASP.NET page to instantiate the `igDoughnutChart`. Several helper methods need to be set for a basic rendering when instantiating the control, there are including the following:
| | |
@@ -195,7 +198,7 @@ This topic walks through using {environment:ProductNameMVC} to instant
| Series() | Instantiates a series for the `igDoughnutChart`., Apart from its `dataSource`, a `name` must be assigned to the series and its `valueMemberPath` property must get a value which will be used to determine the size of the slices. |
- Finally, as with all of the {environment:ProductNameMVC} controls, you must call the Render method to render the HTML and JavaScript to the view.
+ Finally, as with all of the \{environment:ProductNameMVC\} controls, you must call the Render method to render the HTML and JavaScript to the view.
**In ASPX:**
@@ -255,13 +258,13 @@ The following topics provide additional information related to this topic.
- [Adding *igDoughnutChart* to an HTML Page](/igdoughnutchart-adding-to-an-html-page.mdx): This topic explains how to add the `igDoughnutChart` to an HTML page.
-- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the {environment:ProductNameMVC} for it.
+- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the \{environment:ProductNameMVC\} for it.
### Samples
The following sample provides additional information related to this topic.
-- [Bind to Collection]({environment:SamplesUrl}/doughnut-chart/bind-to-collection): This is an example of rendering the `igDoughnutChart` using {environment:ProductNameMVC}. The helper binds to a collection of objects on the server and serializes the collection to JSON objects and renders the required `igDoughnutChart` HTML and JavaScript.
+- [Bind to Collection](\{environment:SamplesUrl\}/doughnut-chart/bind-to-collection): This is an example of rendering the `igDoughnutChart` using \{environment:ProductNameMVC\}. The helper binds to a collection of objects on the server and serializes the collection to JSON objects and renders the required `igDoughnutChart` HTML and JavaScript.
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/api-links.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/api-links.mdx
index 14833c297c..fdd16013ae 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/api-links.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/api-links.mdx
@@ -2,6 +2,9 @@
title: "jQuery and MVC API Links (igDoughnutChart)"
slug: igdoughnutchart-api-links
---
+
+# jQuery and MVC API Links (igDoughnutChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# jQuery and MVC API Links (igDoughnutChart)
@@ -20,7 +23,7 @@ The following table lists the links to the API reference documentation for the `
The following topics provide additional information related to this topic.
-- [Adding igDoughnutChart](/adding/igdoughnutchart-adding.mdx): This topic walks through instantiating an `igDoughnutChart` in an ASP.NET MVC application using {environment:ProductNameMVC}.
+- [Adding igDoughnutChart](/adding/igdoughnutchart-adding.mdx): This topic walks through instantiating an `igDoughnutChart` in an ASP.NET MVC application using \{environment:ProductNameMVC\}.
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/configuring-selection-and-explosion.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/configuring-selection-and-explosion.mdx
index 6a0516fcc5..94e76ba47d 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/configuring-selection-and-explosion.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/configuring-selection-and-explosion.mdx
@@ -2,6 +2,9 @@
title: "Configuring Selection and Explosion (igDoughnutChart)"
slug: igdoughnutchart-configuring-selection-and-explosion
---
+
+# Configuring Selection and Explosion (igDoughnutChart)
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# Configuring Selection and Explosion (igDoughnutChart)
@@ -268,7 +271,7 @@ The following code example demonstrates how to toggle the explosion state of sli
The following samples provide additional information related to this topic.
-- [Bind to Collection]({environment:SamplesUrl}/doughnut-chart/bind-to-collection): This is an example of rendering the `igDoughnutChart` using {environment:ProductNameMVC}. The helper binds to a collection of objects on the server and serializes the collection to JSON objects and renders the required `igDoughnutChart` HTML and JavaScript.
+- [Bind to Collection](\{environment:SamplesUrl\}/doughnut-chart/bind-to-collection): This is an example of rendering the `igDoughnutChart` using \{environment:ProductNameMVC\}. The helper binds to a collection of objects on the server and serializes the collection to JSON objects and renders the required `igDoughnutChart` HTML and JavaScript.
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/igdoughnutchart.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/igdoughnutchart.mdx
index 16ed7b648f..17711031f1 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/igdoughnutchart.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/igdoughnutchart.mdx
@@ -23,7 +23,7 @@ The `igDoughnutChart` control allows for proportionally illustrating the occurre
- [Configuring Selection and Explosion (*igDoughnutChart*)](/igdoughnutchart-configuring-selection-and-explosion.mdx): This topic explains how to configure selection and explosion for the slices of the `igDoughnutChart`.
-- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the {environment:ProductNameMVC} for it.
+- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the \{environment:ProductNameMVC\} for it.
- [Known Issues and Limitations (*igDoughnutChart*)](/igdoughnutchart-known-issues-and-limitations.mdx): This topic provides information on the `igDoughnutChart` control’s known issues and limitations.
diff --git a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/overview.mdx b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/overview.mdx
index da50b7c539..b9e055cbfa 100644
--- a/docs/jquery/src/content/en/topics/controls/igdoughnutchart/overview.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igdoughnutchart/overview.mdx
@@ -2,6 +2,9 @@
title: "igDoughnutChart Overview"
slug: igdoughnutchart-overview
---
+
+# igDoughnutChart Overview
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# igDoughnutChart Overview
@@ -66,17 +69,17 @@ The following topics provide additional information related to this topic.
- [Configuring Selection and Explosion (*igDoughnutChart*)](/igdoughnutchart-configuring-selection-and-explosion.mdx): This topic explains how to configure the slice selection and explosion on `igDoughnutChart`.
-- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the {environment:ProductNameMVC} for it.
+- [jQuery and MVC API Links (*igDoughnutChart*)](/igdoughnutchart-api-links.mdx): This topic provides links to the API documentation about the `igDoughnutChart` control and the \{environment:ProductNameMVC\} for it.
### Samples
The following samples provide additional information related to this topic.
-- [Bind to Collection]({environment:SamplesUrl}/doughnut-chart/bind-to-collection): This sample demonstrates how to render `igDoughnutChart` using the {environment:ProductNameMVC} and bind it to a collection of objects on the server.
+- [Bind to Collection](\{environment:SamplesUrl\}/doughnut-chart/bind-to-collection): This sample demonstrates how to render `igDoughnutChart` using the \{environment:ProductNameMVC\} and bind it to a collection of objects on the server.
-- [Bind to JSON]({environment:SamplesUrl}/doughnut-chart/bind-json): This sample demonstrates how to bind doughnut chart to JSON data.
+- [Bind to JSON](\{environment:SamplesUrl\}/doughnut-chart/bind-json): This sample demonstrates how to bind doughnut chart to JSON data.
-- [Labels and Tooltips]({environment:SamplesUrl}/doughnut-chart/labels-tooltips): This sample demonstrates how to configure labels, tooltips and other options on `igDoughnutChart`.
+- [Labels and Tooltips](\{environment:SamplesUrl\}/doughnut-chart/labels-tooltips): This sample demonstrates how to configure labels, tooltips and other options on `igDoughnutChart`.
-- [Configure Legend]({environment:SamplesUrl}/doughnut-chart/configure-legend): This sample demonstrates how to configure `igDoughnutChart`'s legend.
+- [Configure Legend](\{environment:SamplesUrl\}/doughnut-chart/configure-legend): This sample demonstrates how to configure `igDoughnutChart`'s legend.
diff --git a/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-aspnet-mvc-validation.mdx b/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-aspnet-mvc-validation.mdx
index b45dcadf40..c656b68a3d 100644
--- a/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-aspnet-mvc-validation.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-aspnet-mvc-validation.mdx
@@ -5,24 +5,23 @@ slug: configuring-asp.net-mvc-validation
# Configuring ASP.NET MVC Validation
-
##Topic Overview
### Purpose
-Starting with a form consisting of {environment:ProductNameMVC} editor controls, this topic demonstrates how to create the form and validate the form with data annotations. It also shows how to configure an ASP.NET MVC ValidationMessage to further customize the layout of validation text.
+Starting with a form consisting of \{environment:ProductNameMVC\} editor controls, this topic demonstrates how to create the form and validate the form with data annotations. It also shows how to configure an ASP.NET MVC ValidationMessage to further customize the layout of validation text.
### Required background
####Concepts
- ASP.NET MVC Data Annotation Validators
-- Using {environment:ProductNameMVC} Editors and Combo
+- Using \{environment:ProductNameMVC\} Editors and Combo
####Topics
-- [Adding Controls to an MVC Project](../../../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx): To accomplish the basics of setting up an ASP.NET MVC application with {environment:ProductName} scripts, CSS, and assemblies.
+- [Adding Controls to an MVC Project](../../../01_General-and-Getting-Started/00_Adding IgniteUI Controls to an MVC Project.mdx): To accomplish the basics of setting up an ASP.NET MVC application with \{environment:ProductName\} scripts, CSS, and assemblies.
- [igTextEditor Overview](/igtexteditor/overview.mdx) : To familiarize you with the basics of using the igTextEditor in ASP.NET MVC
@@ -53,7 +52,7 @@ This topic contains the following sections:
### Introduction
-In this procedure, you create and configure a Person model for ASP.NET MVC Data Annotation Validation using {environment:ProductNameMVC} controls.
+In this procedure, you create and configure a Person model for ASP.NET MVC Data Annotation Validation using \{environment:ProductNameMVC\} controls.
### Preview
@@ -65,7 +64,7 @@ The following screenshot is a preview of the final result.
To complete the procedure, you need the an ASP.NET MVC Project with the following:
-- The required {environment:ProductName} JavaScript and CSS files
+- The required \{environment:ProductName\} JavaScript and CSS files
- The Infragistics.Web.Mvc.dll assembly referenced
### Overview
@@ -79,7 +78,7 @@ This topic takes you step-by-step toward creating a model with data annotations.
### Steps
-The following steps demonstrate how to configure data annotation validation for {environment:ProductName} controls.
+The following steps demonstrate how to configure data annotation validation for \{environment:ProductName\} controls.
**1.Create a Person class**
@@ -445,7 +444,7 @@ The following steps demonstrate how to configure data annotation validation for
The following topics provide additional information related to this topic.
-- [Configuring igEditors at Runtime](/configuring-igeditors-at-runtime.mdx) : To learn more about using editors at runtime including important information regarding how the {environment:ProductNameMVC} render the controls.
+- [Configuring igEditors at Runtime](/configuring-igeditors-at-runtime.mdx) : To learn more about using editors at runtime including important information regarding how the \{environment:ProductNameMVC\} render the controls.
### Samples
@@ -453,4 +452,4 @@ The following topics provide additional information related to this topic.
The following samples provide additional information related to this topic.
-- [Data Annotation Validation]({environment:SamplesUrl}/editors/data-annotation-validation): This sample shows data annotation validation when a submit button is pressed.
+- [Data Annotation Validation](\{environment:SamplesUrl\}/editors/data-annotation-validation): This sample shows data annotation validation when a submit button is pressed.
diff --git a/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-igeditors-at-runtime.mdx b/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-igeditors-at-runtime.mdx
index 59354a950b..8c8668d51f 100644
--- a/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-igeditors-at-runtime.mdx
+++ b/docs/jquery/src/content/en/topics/controls/igeditors/config/configuring-igeditors-at-runtime.mdx
@@ -5,7 +5,6 @@ slug: configuring-igeditors-at-runtime
# Configuring igEditors at Runtime
-
##Topic Overview
@@ -32,10 +31,10 @@ This topic contains the following sections:
#### General requirements
- jQuery-specific requirements
-- An HTML web page where {environment:ProductName} controls are instantiated.
+- An HTML web page where \{environment:ProductName\} controls are instantiated.
- MVC-specific requirements
- An MVC project in Microsoft Visual Studio®
-- A reference to the Infragsitics.Web.Mvc dll (contains the {environment:ProductNameMVC})
+- A reference to the Infragsitics.Web.Mvc dll (contains the \{environment:ProductNameMVC\})
#### Scripting requirements
@@ -43,7 +42,7 @@ This topic contains the following sections:
1. The jQuery core library script
2. The jQuery UI library
- 3. The required {environment:ProductName} script files for the editors on your page
+ 3. The required \{environment:ProductName\} script files for the editors on your page
##Binding to events and setting options
@@ -132,7 +131,7 @@ Therefore for example if want to attach to the “columnhiding” event of the
##### igTextEditor
-The following example instantiates an {environment:ProductNameMVC} `TextEditor` control using the HTML helper and then subscribes to the focus event once the control is initialized.
+The following example instantiates an \{environment:ProductNameMVC\} `TextEditor` control using the HTML helper and then subscribes to the focus event once the control is initialized.
@@ -161,7 +160,7 @@ $("#texteditor").bind(‘igeditorfocus’, function (evt, ui) {
##### igDateEditor
-The following example instantiates an {environment:ProductNameMVC} `DateEditor` using the HTML helper then subscribes to the focus event after initialization.
+The following example instantiates an \{environment:ProductNameMVC\} `DateEditor` using the HTML helper then subscribes to the focus event after initialization.
Begin by instantiating the `igTextEditor` control in the view.
@@ -197,7 +196,7 @@ In order to manipulate an option after initialization, you access the control cr
$(‘#inputFieldID’).igTextEditor (‘option’,
-
[{environment:ProductName} ASP.NET MVC Mobile Wrappers](#mvc-mobile-wrappers)
+
[\{environment:ProductName\} ASP.NET MVC Mobile Wrappers](#mvc-mobile-wrappers)
[The MVC Popup Mobile control requires jQuery Mobile version 1.2](#mvc-popup-mobile-control-requirements)
The Popup widget is introduced in the jQuery mobile 1.2.

@@ -694,7 +694,7 @@ In the `igHierarchicalGrid`, child layouts may have rendering issues (missing or
To avoid this, add the Row Selectors before grouping in the array.
-## {environment:ProductNameMVC}
+## \{environment:ProductNameMVC\}
### MVC helper generated code in conjunction with MVC Loader executes after any custom JavaScript code on a page solution
When MVC Loader and MVC helper for any control are used in an MVC view the JavaScript code they generate is executed after custom page set-up code put in `document.ready` or `window.load` events. (This is because the control is rendered in the body part of a page and script code is usually put in the head part.) If the custom code refers to the control rendered by the MVC helper code, it may fail since the control does not exist yet. This is a timing issue and depends on how quickly the loader loads necessary resources.
@@ -719,7 +719,7 @@ When `AutoGenerateLayouts()` is set to true in remote data binding scenarios suc
### The ASP.NET MVC Loader does not function properly in an MVC Razor layout view solution
-{environment:ProductNameMVC} do not produce the proper Loader code when the Loader is included in a layout page in an ASP.NET MVC Razor application. They use the regular jQuery `$(function() { }) (document.ready)` syntax. This happens only for ASP.NET MVC Razor applications and in MVC ASPX views with master pages the same problem is not experienced.
+\{environment:ProductNameMVC\} do not produce the proper Loader code when the Loader is included in a layout page in an ASP.NET MVC Razor application. They use the regular jQuery `$(function() { }) (document.ready)` syntax. This happens only for ASP.NET MVC Razor applications and in MVC ASPX views with master pages the same problem is not experienced.
The reason for this is that layout views are processed and executed after the particular view is rendered and the loader has no chance to initialize prior to the view rendering.
@@ -727,14 +727,14 @@ The solution is not to include the MVC Loader in an ASP.NET MVC Razor layout pag
## Infragistics Document Engine
-### Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround
+### Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround
-Using both the Infragistics ASP.NET and {environment:ProductName} documents assemblies together causes namespace conflict exceptions.
+Using both the Infragistics ASP.NET and \{environment:ProductName\} documents assemblies together causes namespace conflict exceptions.
-To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from {environment:ProductName} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
+To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from \{environment:ProductName\} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
-## {environment:ProductName} ASP.NET MVC Mobile Wrappers
+## \{environment:ProductName\} ASP.NET MVC Mobile Wrappers
### The ASP.NET MVC Popup Mobile control requires jQuery Mobile version 1.2
The popup widget is introduced in jQuery Mobile version 1.2. If you want to use the Popup MVC wrapper use a jQuery Mobile version higher or equal to 1.2.
diff --git a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/22-known-issues-and-limitations-2012-volume-2.mdx b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/22-known-issues-and-limitations-2012-volume-2.mdx
index 46b974be74..dfa6134ecd 100644
--- a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/22-known-issues-and-limitations-2012-volume-2.mdx
+++ b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/22-known-issues-and-limitations-2012-volume-2.mdx
@@ -8,7 +8,7 @@ slug: known-issues-and-limitations-2012-volume-2
## Topic Overview
### Purpose
-This topic lists known issues and limitations in the {environment:ProductName}™ library and provides a reference to individual controls’ known issues topics.
+This topic lists known issues and limitations in the \{environment:ProductName\}™ library and provides a reference to individual controls’ known issues topics.
### In this topic
@@ -25,7 +25,7 @@ This topic contains the following sections:
- [First and last items appear half cut in financial series charts](#first-last-items-half-cut)
- [Chart animation disabled when axis range changes](#chart-animation-disabled)
- [ASP.NET MVC helper generated code in conjunction with ASP.NET MVC Loader executes after any custom JavaScript code on a page](#mvc-heper-issue)
- - [Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround](#document-engines-workaround)
+ - [Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround](#document-engines-workaround)
- [igEditor styling](#igEditor-styling)
- [igEditor rendering failure](#igEditor-rendering-failure)
- [Cannot use igGridHiding with row templates](#igGridHiding-cannot-use-row-templates)
@@ -64,7 +64,7 @@ This topic contains the following sections:
## Known Issues and Limitations in 2012 Volume 2
### Overview
-The following table summarizes the known issues and limitations of the {environment:ProductName} 2012 Volume 2 release. Detailed explanations of known issues and the possible workarounds are provided in the known issues topics for each control.
+The following table summarizes the known issues and limitations of the \{environment:ProductName\} 2012 Volume 2 release. Detailed explanations of known issues and the possible workarounds are provided in the known issues topics for each control.
### Legend:
@@ -87,7 +87,7 @@ Feature | Description | Status
[First and last items appear half cut in financial series charts](#first-last-items-half-cut) | In a financial series, the first and the last data items do not appear entirely on the chart view but are plotted as if they are cut in half. | 
[Chart animations are disabled when the axis range changes](#chart-animation-disabled) | If you use the Motion Framework for charts and updated data causes the Y-axis range to change, then all chart animation is disabled and new data appears immediately without any motion effect. | 
[MVC helper generated code in conjunction with the MVC Loader executes after any custom JavaScript code on a page](#mvc-heper-issue) | When the MVC Loader and an MVC helper for any control is used in an ASP.NET MVC view, the JavaScript code they generate is executed after custom page set-up code from `document.ready()` or `window.load()` events. | 
-[Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround](#document-engines-workaround) | Using both the Infragistics ASP.NET and {environment:ProductName} documents assemblies together will cause namespace conflict exceptions. | 
+[Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround](#document-engines-workaround) | Using both the Infragistics ASP.NET and \{environment:ProductName\} documents assemblies together will cause namespace conflict exceptions. | 
[igEditor styling](#igEditor-styling) | Layout of HTML elements is modified and rounded corners are rendered around the whole editor, not only buttons. | 
igEditor spin buttons | Spin buttons are rendered horizontally. | 
[igEditor rendering failure](#igEditor-rendering-failure) | Rendering may fail if the base element is a TD. | 
@@ -199,11 +199,11 @@ $.ig.loader(function () {
In this example, the `customControlLogic()` function handles any custom code. This ensures that code affecting the control will execute after the control is instantiated.
-## Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround
+## Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround
-Using both the Infragistics ASP.NET and {environment:ProductName} documents assemblies together causes namespace conflict exceptions.
+Using both the Infragistics ASP.NET and \{environment:ProductName\} documents assemblies together causes namespace conflict exceptions.
-To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from {environment:ProductName} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
+To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from \{environment:ProductName\} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
## igEditor styling workaround
@@ -279,7 +279,7 @@ Before resizing the table, the height of the grid table container needs to be re
## The ASP.NET MVC Loader does not function properly in an MVC Razor layout view solution
-{environment:ProductNameMVC} do not produce the proper Loader code when the Loader is included in a layout page in an ASP.NET MVC Razor application. They use the regular jQuery `$(function() { }) (document.ready)` syntax. This happens only for ASP.NET MVC Razor applications and in MVC ASPX views with master pages the same problem is not experienced.
+\{environment:ProductNameMVC\} do not produce the proper Loader code when the Loader is included in a layout page in an ASP.NET MVC Razor application. They use the regular jQuery `$(function() { }) (document.ready)` syntax. This happens only for ASP.NET MVC Razor applications and in MVC ASPX views with master pages the same problem is not experienced.
The reason for this is that layout views are processed and executed after the particular view is rendered and the loader has no chance to initialize prior to the view rendering.
diff --git a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/23-known-issues-and-limitations-2012-volume-1.mdx b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/23-known-issues-and-limitations-2012-volume-1.mdx
index 11612715a4..24a0f0d7cd 100644
--- a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/23-known-issues-and-limitations-2012-volume-1.mdx
+++ b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/23-known-issues-and-limitations-2012-volume-1.mdx
@@ -8,7 +8,7 @@ slug: known-issues-and-limitations-2012-volume-1
## Topic Overview
### Purpose
-This topic lists known issues and limitations in the {environment:ProductName}™ library and provides reference to individual control’s known issues topics.
+This topic lists known issues and limitations in the \{environment:ProductName\}™ library and provides reference to individual control’s known issues topics.
### In this topic
@@ -26,7 +26,7 @@ This topic contains the following sections:
- [First and last items appear half cut in financial series charts](#half-cut-first-last-item)
- [Chart animation disabled when axis range changes](#chart-animation-disabled-axis-range-changed)
- [MVC helper generated code in conjunction with MVC Loader executes after any custom JavaScript code on a page](#mvc-helper-executes-after-custom-js-code)
- - [Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround](#document-engines-workaround)
+ - [Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround](#document-engines-workaround)
- [igEditor styling](#igEditor-styling)
- [igEditor rendering failure](#igEditor-rendering-failure)
- [Cannot use igGridHiding with row templates](#grid-hiding-cannot-use-row-templates)
@@ -46,7 +46,7 @@ This topic contains the following sections:
## Known Issues and Limitations in 2012 Volume 1
### Overview
-The following table summarizes the known issues and limitations of the {environment:ProductName} 2012 Volume 1 release. Detailed explanations of known issues and the possible workarounds are provided for in the known issues topics for each control.
+The following table summarizes the known issues and limitations of the \{environment:ProductName\} 2012 Volume 1 release. Detailed explanations of known issues and the possible workarounds are provided for in the known issues topics for each control.
### Legend:
@@ -70,7 +70,7 @@ Feature | Description | Status
[First and last items appear half cut in financial series charts ](#half-cut-first-last-item) | In financial series the first and the last data items do not appear entirely on the chart view but are plotted as if they are cut in half. | 
[Chart animation are disabled when axis range changes ](#chart-animation-disabled-axis-range-changed) | If you use the Motion Framework for charts and updated data causes Y-axis range to be changed then all chart animation is disabled and new data to appear immediately without any motion effect. | 
[MVC helper generated code in conjunction with MVC Loader executes after any custom JavaScript code on a page ](#mvc-helper-executes-after-custom-js-code) | When MVC Loader and MVC helper for any control are used in an MVC view the JavaScript code they generate is usually executed after custom page set-up code from `document.ready()` or `window.ready()` events. | 
-[Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround](#document-engines-workaround) | Using both the Infragistics ASP.NET and {environment:ProductName} documents assemblies together will cause namespace conflict exceptions. | 
+[Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround](#document-engines-workaround) | Using both the Infragistics ASP.NET and \{environment:ProductName\} documents assemblies together will cause namespace conflict exceptions. | 
[igEditor styling ](#igEditor-styling) | Layout of html elements was modified and rounded corners are rendered around whole editor, not only buttons. | 
`igEditor` spin buttons | Spin buttons are rendered horizontally. | 
[igEditor rendering failure ](#igEditor-rendering-failure) | Rendering may fail if the base element is TD. | 
@@ -166,12 +166,12 @@ $.ig.loader(function () {
Here the `customControlLogic()` function handles any custom code. This way you ensure that your code affecting the control will execute after the control is instantiated.
-## Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround
+## Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround
-Using both the Infragistics ASP.NET and {environment:ProductName} documents assemblies
+Using both the Infragistics ASP.NET and \{environment:ProductName\} documents assemblies
together will cause namespace conflict exceptions.
-To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from {environment:ProductName} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
+To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from \{environment:ProductName\} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
## igEditor styling workaround
diff --git a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/24-known-issues-and-limitations-2011-volume-2.mdx b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/24-known-issues-and-limitations-2011-volume-2.mdx
index 24b9f0650c..211acd42ca 100644
--- a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/24-known-issues-and-limitations-2011-volume-2.mdx
+++ b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/24-known-issues-and-limitations-2011-volume-2.mdx
@@ -8,13 +8,13 @@ slug: known-issues-and-limitations-2011-volume-2
## Topic Overview
### Purpose
-This topic lists the known issues and limitations in the 2011 Volume 2 release of the {environment:ProductName}™ library.
+This topic lists the known issues and limitations in the 2011 Volume 2 release of the \{environment:ProductName\}™ library.
## Known Issues and Limitations in 2011 Volume 2
### Overview
-The following table summarizes the known issues and limitations of the {environment:ProductName} 2011 Volume 2 release. Detailed explanations of known issues and the possible workarounds are provided for in the known issues topics for each control.
+The following table summarizes the known issues and limitations of the \{environment:ProductName\} 2011 Volume 2 release. Detailed explanations of known issues and the possible workarounds are provided for in the known issues topics for each control.
### Legend:
@@ -28,7 +28,7 @@ The following table summarizes the known issues and limitations of the {env
Feature | Description | Status
---|---|---
-[Using Document Engines from NetAdvantage for ASP.NET and {environment:ProductName} together workaround ](#using-document-engine) | Using both the Infragistics ASP.NET and {environment:ProductName} documents assemblies together will cause namespace conflict exceptions. | 
+[Using Document Engines from NetAdvantage for ASP.NET and \{environment:ProductName\} together workaround ](#using-document-engine) | Using both the Infragistics ASP.NET and \{environment:ProductName\} documents assemblies together will cause namespace conflict exceptions. | 
[igEditor styling ](#igEditor-styling) | Layout of html elements was modified and rounded corners are rendered around whole editor, not only buttons. | 
`igEditor` spin buttons | Spin buttons are rendered horizontally. | 
[igEditor rendering failure ](#rigEditor-rendering-failure) | Rendering may fail if the base element is TD. | 
@@ -42,12 +42,12 @@ Feature | Description | Status
[Virtualization does not work for igHierarchicalGrid ](#virtualization-doesnot-work-hierarchicalgrid) | The virtualization feature is not supported for `igHierarchicalGrid`. | 
-## Using Document Engines from Infragistics ASP.NET and {environment:ProductName} together workaround
+## Using Document Engines from Infragistics ASP.NET and \{environment:ProductName\} together workaround
-Using both the Infragistics ASP.NET and {environment:ProductName} documents assemblies
+Using both the Infragistics ASP.NET and \{environment:ProductName\} documents assemblies
together will cause namespace conflict exceptions.
-To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from {environment:ProductName} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
+To resolve this issue, reference either the documents assemblies from Infragistics ASP.NET or the documents assemblies from \{environment:ProductName\} in your application. The documents libraries within these assemblies are the same and can be used to replace one another.
## igEditor styling
diff --git a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/25-known-issues-and-limitations-2011-volume-1.mdx b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/25-known-issues-and-limitations-2011-volume-1.mdx
index 2838558e57..6e062e60d7 100644
--- a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/25-known-issues-and-limitations-2011-volume-1.mdx
+++ b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/25-known-issues-and-limitations-2011-volume-1.mdx
@@ -5,17 +5,16 @@ slug: known-issues-and-limitations-2011-volume-1
# Known Issues and Limitations in 2011 Volume 1
-
## Topic Overview
### Purpose
-This topic lists the known issues and limitations in the 2011 Volume 1 release of the {environment:ProductName}™ library.
+This topic lists the known issues and limitations in the 2011 Volume 1 release of the \{environment:ProductName\}™ library.
## Known Issues and Limitations in 2011 Volume 1
### Overview
-The following table summarizes the known issues and limitations in the 2011 Volume 1 release of the {environment:ProductName}. Detailed explanations of known issues and the possible workarounds are provided for in the known issues topics for each control.
+The following table summarizes the known issues and limitations in the 2011 Volume 1 release of the \{environment:ProductName\}. Detailed explanations of known issues and the possible workarounds are provided for in the known issues topics for each control.
### Legend:
diff --git a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/revision-history.mdx b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/revision-history.mdx
index b11c733e62..dc78315d0d 100644
--- a/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/revision-history.mdx
+++ b/docs/jquery/src/content/en/topics/known-issues/known-issues-revision-history/revision-history.mdx
@@ -7,63 +7,63 @@ slug: known-issues-revision-history
### Introduction
-This topic provides links to the Known Issues and Limitations documents for earlier versions of the {environment:ProductName}™ library.
+This topic provides links to the Known Issues and Limitations documents for earlier versions of the \{environment:ProductName\}™ library.
### Topics
Detailed information regarding the Known Issues and Limitations of each release is covered in the following topics:
-- [Known Issues and Limitations in 2023 Volume 2](/known-issues-and-limitations-2023-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2023 Volume 2 release.
+- [Known Issues and Limitations in 2023 Volume 2](/known-issues-and-limitations-2023-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2023 Volume 2 release.
-- [Known Issues and Limitations in 2023 Volume 1](/known-issues-and-limitations-2023-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2023 Volume 1 release.
+- [Known Issues and Limitations in 2023 Volume 1](/known-issues-and-limitations-2023-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2023 Volume 1 release.
-- [Known Issues and Limitations in 2022 Volume 2](/known-issues-and-limitations-2022-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2022 Volume 2 release.
+- [Known Issues and Limitations in 2022 Volume 2](/known-issues-and-limitations-2022-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2022 Volume 2 release.
-- [Known Issues and Limitations in 2022 Volume 1](/known-issues-and-limitations-2022-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2022 Volume 1 release.
+- [Known Issues and Limitations in 2022 Volume 1](/known-issues-and-limitations-2022-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2022 Volume 1 release.
-- [Known Issues and Limitations in 2021 Volume 2](/known-issues-and-limitations-2021-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2021 Volume 2 release.
+- [Known Issues and Limitations in 2021 Volume 2](/known-issues-and-limitations-2021-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2021 Volume 2 release.
-- [Known Issues and Limitations in 2021 Volume 1](/known-issues-and-limitations-2021-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2021 Volume 1 release.
+- [Known Issues and Limitations in 2021 Volume 1](/known-issues-and-limitations-2021-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2021 Volume 1 release.
-- [Known Issues and Limitations in 2020 Volume 2](/known-issues-and-limitations-2020-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2020 Volume 2 release.
+- [Known Issues and Limitations in 2020 Volume 2](/known-issues-and-limitations-2020-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2020 Volume 2 release.
-- [Known Issues and Limitations in 2020 Volume 1](/known-issues-and-limitations-2020-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2020 Volume 1 release.
+- [Known Issues and Limitations in 2020 Volume 1](/known-issues-and-limitations-2020-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2020 Volume 1 release.
-- [Known Issues and Limitations in 2019 Volume 2](/known-issues-and-limitations-2019-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2019 Volume 2 release.
+- [Known Issues and Limitations in 2019 Volume 2](/known-issues-and-limitations-2019-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2019 Volume 2 release.
-- [Known Issues and Limitations in 2019 Volume 1](/known-issues-and-limitations-2019-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2019 Volume 1 release.
+- [Known Issues and Limitations in 2019 Volume 1](/known-issues-and-limitations-2019-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2019 Volume 1 release.
-- [Known Issues and Limitations in 2018 Volume 2](/known-issues-and-limitations-2018-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2018 Volume 2 release.
+- [Known Issues and Limitations in 2018 Volume 2](/known-issues-and-limitations-2018-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2018 Volume 2 release.
-- [Known Issues and Limitations in 2018 Volume 1](/known-issues-and-limitations-2018-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2018 Volume 1 release.
+- [Known Issues and Limitations in 2018 Volume 1](/known-issues-and-limitations-2018-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2018 Volume 1 release.
-- [Known Issues and Limitations in 2017 Volume 2](/known-issues-and-limitations-2017-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2017 Volume 2 release.
+- [Known Issues and Limitations in 2017 Volume 2](/known-issues-and-limitations-2017-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2017 Volume 2 release.
-- [Known Issues and Limitations in 2017 Volume 1](/known-issues-and-limitations-2017-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2017 Volume 1 release.
+- [Known Issues and Limitations in 2017 Volume 1](/known-issues-and-limitations-2017-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2017 Volume 1 release.
-- [Known Issues and Limitations in 2016 Volume 2](/known-issues-and-limitations-2016-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2016 Volume 2 release.
+- [Known Issues and Limitations in 2016 Volume 2](/known-issues-and-limitations-2016-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2016 Volume 2 release.
-- [Known Issues and Limitations in 2016 Volume 1](/known-issues-and-limitations-2016-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2016 Volume 1 release.
+- [Known Issues and Limitations in 2016 Volume 1](/known-issues-and-limitations-2016-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2016 Volume 1 release.
-- [Known Issues and Limitations in 2015 Volume 2](/known-issues-and-limitations-2015-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2015 Volume 2 release.
+- [Known Issues and Limitations in 2015 Volume 2](/known-issues-and-limitations-2015-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2015 Volume 2 release.
-- [Known Issues and Limitations in 2015 Volume 1](/known-issues-and-limitations-2015-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2015 Volume 1 release.
+- [Known Issues and Limitations in 2015 Volume 1](/known-issues-and-limitations-2015-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2015 Volume 1 release.
-- [Known Issues and Limitations in 2014 Volume 2](/known-issues-and-limitations-2014-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2014 Volume 2 release.
+- [Known Issues and Limitations in 2014 Volume 2](/known-issues-and-limitations-2014-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2014 Volume 2 release.
-- [Known Issues and Limitations in 2014 Volume 1](/known-issues-and-limitations-2014-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2014 Volume 1 release.
+- [Known Issues and Limitations in 2014 Volume 1](/known-issues-and-limitations-2014-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2014 Volume 1 release.
-- [Known Issues and Limitations in 2013 Volume 2](/known-issues-and-limitations-2013-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2013 Volume 2 release.
+- [Known Issues and Limitations in 2013 Volume 2](/known-issues-and-limitations-2013-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2013 Volume 2 release.
-- [Known Issues and Limitations in 2013 Volume 1](/known-issues-and-limitations-2013-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2013 Volume 1 release.
+- [Known Issues and Limitations in 2013 Volume 1](/known-issues-and-limitations-2013-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2013 Volume 1 release.
-- [Known Issues and Limitations in 2012 Volume 2](/known-issues-and-limitations-2012-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2012 Volume 2 release.
+- [Known Issues and Limitations in 2012 Volume 2](/known-issues-and-limitations-2012-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2012 Volume 2 release.
-- [Known Issues and Limitations in 2012 Volume 1](/known-issues-and-limitations-2012-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2012 Volume 1 release.
+- [Known Issues and Limitations in 2012 Volume 1](/known-issues-and-limitations-2012-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2012 Volume 1 release.
-- [Known Issues and Limitations in 2011 Volume 2](/known-issues-and-limitations-2011-volume-2.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for the 2011 Volume 2 release.
+- [Known Issues and Limitations in 2011 Volume 2](/known-issues-and-limitations-2011-volume-2.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for the 2011 Volume 2 release.
-- [Known Issues and Limitations in 2011 Volume 1](/known-issues-and-limitations-2011-volume-1.mdx): This topic lists the known issues and limitations in the {environment:ProductName} library for releases before 2011 Volume 2.
+- [Known Issues and Limitations in 2011 Volume 1](/known-issues-and-limitations-2011-volume-1.mdx): This topic lists the known issues and limitations in the \{environment:ProductName\} library for releases before 2011 Volume 2.
diff --git a/docs/jquery/src/content/en/topics/known-issues/known-issues.mdx b/docs/jquery/src/content/en/topics/known-issues/known-issues.mdx
index 16f8da5f6f..6a9681e99d 100644
--- a/docs/jquery/src/content/en/topics/known-issues/known-issues.mdx
+++ b/docs/jquery/src/content/en/topics/known-issues/known-issues.mdx
@@ -5,19 +5,18 @@ slug: known-issues
# Known Issues
-
## Introduction
-The topics in this group provide information about the Known Issues, Limitations and Breaking Changes of the {environment:ProductName}™ library of controls.
+The topics in this group provide information about the Known Issues, Limitations and Breaking Changes of the \{environment:ProductName\}™ library of controls.
## Topics
Detailed information regarding known issues, limitations and breaking changes is covered in the following topics:
-- [Known Issues](/known-issues-and-limitations.mdx): This topic contains an up-to-date list of known issues and limitations in the {environment:ProductName}™ library.
+- [Known Issues](/known-issues-and-limitations.mdx): This topic contains an up-to-date list of known issues and limitations in the \{environment:ProductName\}™ library.
- [Breaking Changes](/whats-new/00-general-changelog.mdx): Breaking changes are listed within the changelog for each version in the General Changelog document.
-- [Known Issues Revision History](/known-issues-revision-history/known-issues-revision-history.mdx): This topic provides links to the Known Issues and Limitations documents for earlier versions of the {environment:ProductName}™ library.
+- [Known Issues Revision History](/known-issues-revision-history/known-issues-revision-history.mdx): This topic provides links to the Known Issues and Limitations documents for earlier versions of the \{environment:ProductName\}™ library.
-- [Breaking Changes Revision History](/breaking-changes-revision-history/breaking-changes-revision-history.mdx): This topic provides links to the Breaking Changes documents for earlier versions of the {environment:ProductName}™ library.
+- [Breaking Changes Revision History](/breaking-changes-revision-history/breaking-changes-revision-history.mdx): This topic provides links to the Breaking Changes documents for earlier versions of the \{environment:ProductName\}™ library.
diff --git a/docs/jquery/src/content/en/topics/typescript-definitions/typescript-definitions.mdx b/docs/jquery/src/content/en/topics/typescript-definitions/typescript-definitions.mdx
index b6bbaa0529..23ca966d62 100644
--- a/docs/jquery/src/content/en/topics/typescript-definitions/typescript-definitions.mdx
+++ b/docs/jquery/src/content/en/topics/typescript-definitions/typescript-definitions.mdx
@@ -4,13 +4,14 @@ slug: typescript-definitions
---
# TypeScript Definitions
+
## In This Group of Topics
### Introduction
-{environment:ProductName}® provides type definitions for TypeScript allowing you to take advantage of strong typing, compile time checking and intellisense features.
+\{environment:ProductName\}® provides type definitions for TypeScript allowing you to take advantage of strong typing, compile time checking and intellisense features.
### Topics
-- [Using {environment:ProductName} with TypeScript](Using-Ignite-UI-with-TypeScript.html) - This topic contains an overview for using the {environment:ProductName} type definitions for TypeScript.
+- [Using \{environment:ProductName\} with TypeScript](Using-Ignite-UI-with-TypeScript.html) - This topic contains an overview for using the \{environment:ProductName\} type definitions for TypeScript.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/typescript-definitions/typescript-samples.mdx b/docs/jquery/src/content/en/topics/typescript-definitions/typescript-samples.mdx
index 2de1978326..fbd773766f 100644
--- a/docs/jquery/src/content/en/topics/typescript-definitions/typescript-samples.mdx
+++ b/docs/jquery/src/content/en/topics/typescript-definitions/typescript-samples.mdx
@@ -6,7 +6,7 @@ slug: typescript-samples
# TypeScript Samples
## Topic Overview
-This topic covers samples with {environment:ProductName} controls and TypeScript.
+This topic covers samples with \{environment:ProductName\} controls and TypeScript.
### In this topic
@@ -55,8 +55,8 @@ This topic contains the following sections:
### Requirements
In order to run these samples, you need to have:
-- The required {environment:ProductName} JavaScript and CSS files
-- The required {environment:ProductName} TypeScript definitions
+- The required \{environment:ProductName\} JavaScript and CSS files
+- The required \{environment:ProductName\} TypeScript definitions
### Grid Sample
@@ -1442,4 +1442,4 @@ $(function () {
### Related Content
The following topic provides additional information related to this one:
-[Using {environment:ProductName} with TypeScript](Using-Ignite-UI-with-TypeScript.html) - This topic contains an overview for using the {environment:ProductName} type definitions for TypeScript.
+[Using \{environment:ProductName\} with TypeScript](Using-Ignite-UI-with-TypeScript.html) - This topic contains an overview for using the \{environment:ProductName\} type definitions for TypeScript.
diff --git a/docs/jquery/src/content/en/topics/typescript-definitions/using-ignite-ui-with-typescript.mdx b/docs/jquery/src/content/en/topics/typescript-definitions/using-ignite-ui-with-typescript.mdx
index b0912d0e9c..eccee4e179 100644
--- a/docs/jquery/src/content/en/topics/typescript-definitions/using-ignite-ui-with-typescript.mdx
+++ b/docs/jquery/src/content/en/topics/typescript-definitions/using-ignite-ui-with-typescript.mdx
@@ -1,13 +1,13 @@
---
-title: "Using {environment:ProductName} with TypeScript"
+title: "Using {environment:ProductName} with TypeScript"
slug: using-ignite-ui-with-typescipt
---
-# Using {environment:ProductName} with TypeScript
+# Using \{environment:ProductName\} with TypeScript
## Topic Overview
-This topic is an overview for using the {environment:ProductName} type definitions for TypeScript.
+This topic is an overview for using the \{environment:ProductName\} type definitions for TypeScript.
### Required background
@@ -20,7 +20,7 @@ The following table lists the materials required as a prerequisite to understand
**Topics**
-- [{environment:ProductName} Overview](/igniteui-for-jquery-overview.mdx)
+- [\{environment:ProductName\} Overview](/igniteui-for-jquery-overview.mdx)
### In this topic
@@ -29,34 +29,34 @@ This topic contains the following sections:
- [Introduction](#introduction)
- [Syntax](#syntax)
-- [Creating TypeScript App with {environment:ProductName}](#creating-app)
+- [Creating TypeScript App with \{environment:ProductName\}](#creating-app)
- [Related Content](#related-content)
## Introduction
-{environment:ProductName}® provides type definitions for TypeScript allowing you to take advantage of strong typing, compile time checking and intellisense features.
+\{environment:ProductName\}® provides type definitions for TypeScript allowing you to take advantage of strong typing, compile time checking and intellisense features.
The definitions for the controls can be installed via NPM with the following command `npm install @types/ignite-ui`. They extend the jQuery and jQuery UI definitions for TypeScript and thus it depends on them.
## Syntax
-Syntax for using {environment:ProductName} controls in TypeScript application is the same as you write vanilla JavaScript application. This means that you can refer to the [{environment:ProductName} API documentation](https://www.igniteui.com/help/api/2025.1) for code snippets reference.
+Syntax for using \{environment:ProductName\} controls in TypeScript application is the same as you write vanilla JavaScript application. This means that you can refer to the [\{environment:ProductName\} API documentation](https://www.igniteui.com/help/api/2025.1) for code snippets reference.
-## Creating TypeScript App with {environment:ProductName}
+## Creating TypeScript App with \{environment:ProductName\}
### Requirements
-When considering the required resources the same requirements and options apply as described in the ["Using JavaScript Resources in {environment:ProductName}"](/general-and-getting-started/deployment-guide-javascript-resources.mdx) documentation in addition to loading the {environment:ProductName} Angular directives module afterwards. This means that along with some styles the application would also need to include:
+When considering the required resources the same requirements and options apply as described in the ["Using JavaScript Resources in \{environment:ProductName\}"](/general-and-getting-started/deployment-guide-javascript-resources.mdx) documentation in addition to loading the \{environment:ProductName\} Angular directives module afterwards. This means that along with some styles the application would also need to include:
- [jQuery](http://www.jquery.com/) 1.9 and later
- [jQuery UI](http://jqueryui.com/) 1.10 and later
- [TypeScript](http://www.typescriptlang.org/) 1.4 and later
-- [{environment:ProductName}](http://www.igniteui.com/) 15.1 and later
+- [\{environment:ProductName\}](http://www.igniteui.com/) 15.1 and later
### Steps
1. Create a new HTML App with TypeScript in Visual Studio.
-2. Include the {environment:ProductName} theme and structural files:
+2. Include the \{environment:ProductName\} theme and structural files:
**In HTML:**
```html
@@ -74,7 +74,7 @@ When considering the required resources the same requirements and options apply
```
-4. Include {environment:ProductName} scripts. Preferably use a custom download, but you can also check ["Using JavaScript Resources in {environment:ProductName}"](/general-and-getting-started/deployment-guide-javascript-resources.mdx) topic for other methods.
+4. Include \{environment:ProductName\} scripts. Preferably use a custom download, but you can also check ["Using JavaScript Resources in \{environment:ProductName\}"](/general-and-getting-started/deployment-guide-javascript-resources.mdx) topic for other methods.
**In HTML:**
```html
@@ -92,7 +92,7 @@ When considering the required resources the same requirements and options apply
```
-6. Include the reference paths to the {environment:ProductName} and jQuery type definitions for TypeScript:
+6. Include the reference paths to the \{environment:ProductName\} and jQuery type definitions for TypeScript:
**In TypeScript:**
```typescript
@@ -137,6 +137,6 @@ When considering the required resources the same requirements and options apply
The following samples provide additional information related to this topic.
-- [igHierarchicalGrid TypeScript]({environment:SamplesUrl}/hierarchical-grid/typescript)
-- [igTreeGrid TypeScript]({environment:SamplesUrl}/tree-grid/typescript)
-- [igPivotGrid TypeScript]({environment:SamplesUrl}/pivot-grid/typescript)
+- [igHierarchicalGrid TypeScript](\{environment:SamplesUrl\}/hierarchical-grid/typescript)
+- [igTreeGrid TypeScript](\{environment:SamplesUrl\}/tree-grid/typescript)
+- [igPivotGrid TypeScript](\{environment:SamplesUrl\}/pivot-grid/typescript)
diff --git a/docs/jquery/src/content/en/topics/whats-new/00-general-changelog.mdx b/docs/jquery/src/content/en/topics/whats-new/00-general-changelog.mdx
index 78360fac19..7fddb6fee4 100644
--- a/docs/jquery/src/content/en/topics/whats-new/00-general-changelog.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/00-general-changelog.mdx
@@ -32,11 +32,11 @@ slug: general-changelog
### Added
-- Infragistics {environment:ProductNameASPNETCore} now supports ASP.NET Core for .NET 10 projects. For more information see the [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
+- Infragistics \{environment:ProductNameASPNETCore\} now supports ASP.NET Core for .NET 10 projects. For more information see the [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
### Breaking Changes
-- Infragistics {environment:ProductNameASPNETCore} no longer supports ASP.NET Core 3.1.
+- Infragistics \{environment:ProductNameASPNETCore\} no longer supports ASP.NET Core 3.1.
## 24.2.12
@@ -114,9 +114,9 @@ slug: general-changelog
### Added
-- Infragistics {environment:ProductNameASPNETCore} now supports ASP.NET Core for .NET 9 projects. For more information see the [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
+- Infragistics \{environment:ProductNameASPNETCore\} now supports ASP.NET Core for .NET 9 projects. For more information see the [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
-- Infragistics {environment:ProductName} now supports the recently released jQuery 3.7 and jQuery UI 1.14.
+- Infragistics \{environment:ProductName\} now supports the recently released jQuery 3.7 and jQuery UI 1.14.
- igGrid and igHierarchicalGrid
- new property `rowAttributeTemplate` allows for adding arbitrary attributes to rows [#2249](https://github.com/IgniteUI/ignite-ui/issues/2249)
diff --git a/docs/jquery/src/content/en/topics/whats-new/jquery-whats-new-landing-page.mdx b/docs/jquery/src/content/en/topics/whats-new/jquery-whats-new-landing-page.mdx
index 1071066bfa..c189d083e2 100644
--- a/docs/jquery/src/content/en/topics/whats-new/jquery-whats-new-landing-page.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/jquery-whats-new-landing-page.mdx
@@ -5,15 +5,14 @@ slug: jquery-whats-new-landing-page
# What's New
-
### Introduction
-The topics in this group provide information about the new controls and features introduced in the various versions of the {environment:ProductName}™ library of controls.
+The topics in this group provide information about the new controls and features introduced in the various versions of the \{environment:ProductName\}™ library of controls.
### Topics
Detailed information regarding what new controls and features are introduced is covered in the following topics:
-- [General Changelog](/general-changelog.mdx): This topic encapsulates all changes introduced in both major and minor versions of the {environment:ProductName} library since the 2024 Volume 1 release.
+- [General Changelog](/general-changelog.mdx): This topic encapsulates all changes introduced in both major and minor versions of the \{environment:ProductName\} library since the 2024 Volume 1 release.
- [Revision History](./02_Revision History/~jQuery_Whats_New_Revision_History.mdx): This is an archive of all What’s New topics for earlier versions.
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/00-whats-new-in-2023-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/00-whats-new-in-2023-volume2.mdx
index dfac062182..c539c565bf 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/00-whats-new-in-2023-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/00-whats-new-in-2023-volume2.mdx
@@ -5,11 +5,11 @@ slug: whats-new-in-2023-volume2
# What's New in 2023 Volume 2
-This topic presents the new features for the {environment:ProductFamilyName}™ 2023 Volume 2 release.
+This topic presents the new features for the \{environment:ProductFamilyName\}™ 2023 Volume 2 release.
-### {environment:ProductNameASPNETCore}
-Infragistics {environment:ProductNameASPNETCore} now supports ASP.NET Core for .NET 8 projects. For more information see the [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
+### \{environment:ProductNameASPNETCore\}
+Infragistics \{environment:ProductNameASPNETCore\} now supports ASP.NET Core for .NET 8 projects. For more information see the [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
-### {environment:ProductNameASPNETCore} Tag Helpers
-{environment:ProductNameASPNETCore} Tag Helpers now support ASP.NET Core for .NET 8 projects. For more information see the [Using {environment:ProductNameASPNETCore} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
+### \{environment:ProductNameASPNETCore\} Tag Helpers
+\{environment:ProductNameASPNETCore\} Tag Helpers now support ASP.NET Core for .NET 8 projects. For more information see the [Using \{environment:ProductNameASPNETCore\} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/01-whats-new-in-2022-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/01-whats-new-in-2022-volume2.mdx
index 8b3fc46a4f..825311723a 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/01-whats-new-in-2022-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/01-whats-new-in-2022-volume2.mdx
@@ -5,14 +5,14 @@ slug: whats-new-in-2022-volume2
# What's New in 2022 Volume 2
-This topic presents the new features for the {environment:ProductFamilyName}™ 2022 Volume 2 release.
+This topic presents the new features for the \{environment:ProductFamilyName\}™ 2022 Volume 2 release.
-### {environment:ProductNameASPNETCore}
-Infragistics {environment:ProductNameASPNETCore} now supports ASP.NET Core for .NET 7 projects. For more information see the [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
+### \{environment:ProductNameASPNETCore\}
+Infragistics \{environment:ProductNameASPNETCore\} now supports ASP.NET Core for .NET 7 projects. For more information see the [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
-### {environment:ProductNameASPNETCore} Tag Helpers
-{environment:ProductNameASPNETCore} Tag Helpers now support ASP.NET Core for .NET 7 projects. For more information see the [Using {environment:ProductNameASPNETCore} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
+### \{environment:ProductNameASPNETCore\} Tag Helpers
+\{environment:ProductNameASPNETCore\} Tag Helpers now support ASP.NET Core for .NET 7 projects. For more information see the [Using \{environment:ProductNameASPNETCore\} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
## Chart Improvements
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/02-whats-new-in-2022-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/02-whats-new-in-2022-volume1.mdx
index 95ba74b7ef..12acd3bc62 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/02-whats-new-in-2022-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/02-whats-new-in-2022-volume1.mdx
@@ -5,7 +5,7 @@ slug: whats-new-in-2022-volume1
# What's New in 2022 Volume 1
-This topic presents the new features for the {environment:ProductFamilyName}™ 2022 Volume 1 release.
+This topic presents the new features for the \{environment:ProductFamilyName\}™ 2022 Volume 1 release.
## Data Legend
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/03-whats-new-in-2021-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/03-whats-new-in-2021-volume2.mdx
index c0624b9a0c..505e51c24f 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/03-whats-new-in-2021-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/03-whats-new-in-2021-volume2.mdx
@@ -5,21 +5,21 @@ slug: whats-new-in-2021-volume2
# What's New in 2021 Volume 2
-This topic presents the new features for the {environment:ProductFamilyName}™ 2021 Volume 2 release.
+This topic presents the new features for the \{environment:ProductFamilyName\}™ 2021 Volume 2 release.
-### {environment:ProductNameASPNETCore}
-Infragistics {environment:ProductNameASPNETCore} now supports ASP.NET Core for .NET 6 projects. For more information see the [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
+### \{environment:ProductNameASPNETCore\}
+Infragistics \{environment:ProductNameASPNETCore\} now supports ASP.NET Core for .NET 6 projects. For more information see the [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
-### {environment:ProductNameASPNETCore} Tag Helpers
-{environment:ProductNameASPNETCore} Tag Helpers now support ASP.NET Core for .NET 6 projects. For more information see the [Using {environment:ProductNameASPNETCore} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
+### \{environment:ProductNameASPNETCore\} Tag Helpers
+\{environment:ProductNameASPNETCore\} Tag Helpers now support ASP.NET Core for .NET 6 projects. For more information see the [Using \{environment:ProductNameASPNETCore\} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
### Infragistics Documents
Infragistics Documents assemblies are now available for ASP.NET Core for .NET 6 projects.
-### {environment:ProductName}
-{environment:ProductName} now supports the recently released jQuery UI 1.13.0 .
+### \{environment:ProductName\}
+\{environment:ProductName\} now supports the recently released jQuery UI 1.13.0 .
## Chart Features
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/04-whats-new-in-2021-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/04-whats-new-in-2021-volume1.mdx
index 4384725f92..a496639a63 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/04-whats-new-in-2021-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/04-whats-new-in-2021-volume1.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2021 Volume 1"
slug: whats-new-in-2021-volume1
---
+
+# What's New in 2021 Volume 1
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# What's New in 2021 Volume 1
-This topic presents the new features for the {environment:ProductFamilyName}™ 2021 Volume 1 release.
+This topic presents the new features for the \{environment:ProductFamilyName\}™ 2021 Volume 1 release.
## Chart Features
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/05-whats-new-in-2020-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/05-whats-new-in-2020-volume2.mdx
index 664fdff523..4a6e5d6641 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/05-whats-new-in-2020-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/05-whats-new-in-2020-volume2.mdx
@@ -5,14 +5,14 @@ slug: whats-new-in-2020-volume2
# What's New in 2020 Volume 2
-This topic presents the new features for the {environment:ProductFamilyName}™ 2020 Volume 2 release.
+This topic presents the new features for the \{environment:ProductFamilyName\}™ 2020 Volume 2 release.
-### {environment:ProductNameASPNETCore}
-Infragistics {environment:ProductNameASPNETCore} now supports ASP.NET Core for .NET 5 projects. For more information see the [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
+### \{environment:ProductNameASPNETCore\}
+Infragistics \{environment:ProductNameASPNETCore\} now supports ASP.NET Core for .NET 5 projects. For more information see the [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
-### {environment:ProductNameASPNETCore} Tag Helpers
-{environment:ProductNameASPNETCore} Tag Helpers now support ASP.NET Core for .NET 5 projects. For more information see the [Using {environment:ProductNameASPNETCore} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
+### \{environment:ProductNameASPNETCore\} Tag Helpers
+\{environment:ProductNameASPNETCore\} Tag Helpers now support ASP.NET Core for .NET 5 projects. For more information see the [Using \{environment:ProductNameASPNETCore\} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
### Infragistics Documents
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/06-whats-new-in-2019-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/06-whats-new-in-2019-volume2.mdx
index 4ff9d6441f..1268940456 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/06-whats-new-in-2019-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/06-whats-new-in-2019-volume2.mdx
@@ -5,14 +5,14 @@ slug: whats-new-in-2019-volume2
# What's New in 2019 Volume 2
-This topic presents the new features for the {environment:ProductFamilyName}™ 2019 Volume 2 release.
+This topic presents the new features for the \{environment:ProductFamilyName\}™ 2019 Volume 2 release.
-### {environment:ProductNameASPNETCore}
-Infragistics {environment:ProductNameASPNETCore} now supports ASP.NET Core 3 projects. For more information see the [Using {environment:ProductNameASPNETCore}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
+### \{environment:ProductNameASPNETCore\}
+Infragistics \{environment:ProductNameASPNETCore\} now supports ASP.NET Core 3 projects. For more information see the [Using \{environment:ProductNameASPNETCore\}](Using-IgniteUI-Controls-in-ASP.NET-Core-project.html) topic.
-### {environment:ProductNameASPNETCore} Tag Helpers
-{environment:ProductNameASPNETCore} Tag Helpers now support ASP.NET Core 3 projects. For more information see the [Using {environment:ProductNameASPNETCore} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
+### \{environment:ProductNameASPNETCore\} Tag Helpers
+\{environment:ProductNameASPNETCore\} Tag Helpers now support ASP.NET Core 3 projects. For more information see the [Using \{environment:ProductNameASPNETCore\} Tag Helpers](using-ignite-ui-tag-helpers.html) topic.
### Infragistics Documents
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/07-whats-new-in-2018-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/07-whats-new-in-2018-volume2.mdx
index ad344668bf..9b0c4e1672 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/07-whats-new-in-2018-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/07-whats-new-in-2018-volume2.mdx
@@ -5,7 +5,7 @@ slug: whats-new-in-2018-volume2
# What's New in 2018 Volume 2
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2018 Volume 2 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2018 Volume 2 release.
### Overview
@@ -99,7 +99,7 @@ A new column type is added to the igGrid control - time column. In order to use
Now, it is possible to create custom editor provider for the filter cell. This means that you can extend the igEditorProvider class and set your own editor to filter the igGrid content. For more information, check the sample below.
### Sample
-[Excel-style Filtering]({environment:SamplesUrl}/grid/filtering-combo-editor-provider)
+[Excel-style Filtering](\{environment:SamplesUrl\}/grid/filtering-combo-editor-provider)
## igSpreadsheet
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/08-whats-new-in-2018-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/08-whats-new-in-2018-volume1.mdx
index c7f11b4142..3c2d35f120 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/08-whats-new-in-2018-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/08-whats-new-in-2018-volume1.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2018 Volume 1"
slug: whats-new-in-2018-volume1
---
+
+# What's New in 2018 Volume 1
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# What's New in 2018 Volume 1
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2018 Volume 1 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2018 Volume 1 release.
### Overview
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/09-whats-new-in-2017-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/09-whats-new-in-2017-volume2.mdx
index 5c7c7bd079..5d078fa97a 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/09-whats-new-in-2017-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/09-whats-new-in-2017-volume2.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2017 Volume 2"
slug: whats-new-in-2017-volume2
---
+
+# What's New in 2017 Volume 2
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# What's New in 2017 Volume 2
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2017 Volume 2 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2017 Volume 2 release.
### Overview
@@ -153,9 +156,9 @@ New options:
- [Editing API (igSpreadsheet)](//controls/igspreadsheet/igspreadsheet-overview/editing.mdx)
#### Related Samples
-- [Overview]({environment:SamplesUrl}/spreadsheet/overview)
-- [View Configuration]({environment:SamplesUrl}/spreadsheet/create-view-save)
-- [Import Data From Excel File]({environment:SamplesUrl}/spreadsheet/loading-data)
+- [Overview](\{environment:SamplesUrl\}/spreadsheet/overview)
+- [View Configuration](\{environment:SamplesUrl\}/spreadsheet/create-view-save)
+- [Import Data From Excel File](\{environment:SamplesUrl\}/spreadsheet/loading-data)
## Editors
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/10-whats-new-in-2017-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/10-whats-new-in-2017-volume1.mdx
index 56fdd22d57..080f7b57cf 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/10-whats-new-in-2017-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/10-whats-new-in-2017-volume1.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2017 Volume 1"
slug: whats-new-in-2017-volume1
---
+
+# What's New in 2017 Volume 1
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# What's New in 2017 Volume 1
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2017 Volume 1 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2017 Volume 1 release.
## What’s New Summary
@@ -131,9 +134,9 @@ In version 2017.1 we introduce the igSpreadsheet control. It is a jQuery widget
#### Related Samples
-- [Overview]({environment:SamplesUrl}/spreadsheet/overview)
-- [View Configuration]({environment:SamplesUrl}/spreadsheet/create-view-save)
-- [Import Data From Excel File]({environment:SamplesUrl}/spreadsheet/loading-data)
+- [Overview](\{environment:SamplesUrl\}/spreadsheet/overview)
+- [View Configuration](\{environment:SamplesUrl\}/spreadsheet/create-view-save)
+- [Import Data From Excel File](\{environment:SamplesUrl\}/spreadsheet/loading-data)
## igScheduler
### New Control
@@ -169,8 +172,8 @@ The `igScheduler`™ control provides a common scheduling solution for presentin
#### Related Samples
-- [igScheduler Agenda View]({environment:SamplesUrl}/scheduler/agenda-view)
-- [igScheduler Appointment Indicators]({environment:SamplesUrl}/scheduler/appointment-indicators)
+- [igScheduler Agenda View](\{environment:SamplesUrl\}/scheduler/agenda-view)
+- [igScheduler Appointment Indicators](\{environment:SamplesUrl\}/scheduler/appointment-indicators)
## igDataSource
@@ -183,7 +186,7 @@ The igDataSource component provides a way to search for a specific words or phra
#### Related Samples
-- [Simple Filtering]({environment:SamplesUrl}/grid/simple-filtering)
+- [Simple Filtering](\{environment:SamplesUrl\}/grid/simple-filtering)
## igGrid
@@ -211,7 +214,7 @@ The GroupBy Summaries feature allows an additional summary row to be displayed b
- [GroupBy Summaries Feature Overview (igGrid)](//controls/iggrid/features/columns/grouping/groupby-summaries.mdx)
#### Related Samples
-- [Grouping with summaries]({environment:SamplesUrl}/grid/grouping)
+- [Grouping with summaries](\{environment:SamplesUrl\}/grid/grouping)
## igCombo
@@ -247,7 +250,7 @@ When the dates in the editors are transferred from the client to the server аnd
#### Related Topics
- [Migrating date handling in 17.1](//controls/igeditors/igdateeditor/migrating-date-handling-in-17-1.mdx)
-- [{environment:ProductName} controls in different time zones](//general-and-getting-started/using-igniteui-controls-in-different-time-zones.mdx)
+- [\{environment:ProductName\} controls in different time zones](//general-and-getting-started/using-igniteui-controls-in-different-time-zones.mdx)
## igDatePicker
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/11-whats-new-in-2016-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/11-whats-new-in-2016-volume2.mdx
index 8ab42a26b4..1cc1e64c6e 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/11-whats-new-in-2016-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/11-whats-new-in-2016-volume2.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2016 Volume 2"
slug: whats-new-in-2016-volume2
---
+
+# What's New in 2016 Volume 2
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
#What's New in 2016 Volume 2
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2016 Volume 2 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2016 Volume 2 release.
##What’s New Summary
@@ -17,15 +20,15 @@ The following summarizes what’s new in 2016 Volume 2. Additional details follo
Feature | Description
---|---
-{environment:ProductName} OSS | A big part of the {environment:ProductName} toolset is now open source. Checkout the repository on [GitHub](https://github.com/IgniteUI/ignite-ui)|
-{environment:ProductName} directives for Angular 2 (RTM) | {environment:ProductName} widgets have component wrappers for Angular 2. For detailed information visit [{environment:ProductName} Angular 2 GitHub](https://github.com/IgniteUI/igniteui-angular-wrappers) page.|
-{environment:ProductName} Components for React (CTP) | {environment:ProductName} widgets have component wrappers for [React](https://facebook.github.io/react/). For detailed information visit [{environment:ProductName} Components for React](https://github.com/IgniteUI/igniteui-react) page.|
-ASP.NET Core 1.0 MVC Helpers | {environment:ProductName} MVC Helpers now support ASP.NET Core 1.0. Checkout the [Using {environment:ProductName} controls in ASP.NET Core 1.0](Using-IgniteUI-Controls-in-ASP.NET-Core-1.0-project.html) topic.|
-ASP.NET Core 1.0 MVC Tag Helpers | {environment:ProductName} now provides Tag Helpers for ASP.NET Core 1.0. Checkout the [Using {environment:ProductName} Tag Helpers](Using-Ignite-UI-Tag-Helpers.html) topic.|
+\{environment:ProductName\} OSS | A big part of the \{environment:ProductName\} toolset is now open source. Checkout the repository on [GitHub](https://github.com/IgniteUI/ignite-ui)|
+\{environment:ProductName\} directives for Angular 2 (RTM) | \{environment:ProductName\} widgets have component wrappers for Angular 2. For detailed information visit [\{environment:ProductName\} Angular 2 GitHub](https://github.com/IgniteUI/igniteui-angular-wrappers) page.|
+\{environment:ProductName\} Components for React (CTP) | \{environment:ProductName\} widgets have component wrappers for [React](https://facebook.github.io/react/). For detailed information visit [\{environment:ProductName\} Components for React](https://github.com/IgniteUI/igniteui-react) page.|
+ASP.NET Core 1.0 MVC Helpers | \{environment:ProductName\} MVC Helpers now support ASP.NET Core 1.0. Checkout the [Using \{environment:ProductName\} controls in ASP.NET Core 1.0](Using-IgniteUI-Controls-in-ASP.NET-Core-1.0-project.html) topic.|
+ASP.NET Core 1.0 MVC Tag Helpers | \{environment:ProductName\} now provides Tag Helpers for ASP.NET Core 1.0. Checkout the [Using \{environment:ProductName\} Tag Helpers](Using-Ignite-UI-Tag-Helpers.html) topic.|
[New Javascript file breakdown](#javascript-file-breakdown) | The goal is to reduce the amount of code required in order to load a specific feature. |
DPI Scaling | High DPI Scaling is enabled by default now which makes the components look much sharper and crisper than before. Components that have the DPI Scaling by default now are - igDataChart, igPieChart, igFunnelChart, igDoughnutChart, igRadialGauge, igLinearGauge, igBulletGraph, igSparkline, igRadialMenu. |
Standard moduling support | All of IgniteUI JavaScript files contain AMD module definitions. Therefore these files can be loaded using standard module loaders such as Require.JS, System.JS etc.|
-[{environment:ProductName} NuGet packages](#ignite-ui-nuget-packages) | New {environment:ProductName} NuGet packages are available, including a package for creating .NET Core applications. |
+[\{environment:ProductName\} NuGet packages](#ignite-ui-nuget-packages) | New \{environment:ProductName\} NuGet packages are available, including a package for creating .NET Core applications. |
### igCategoryChart
@@ -65,9 +68,9 @@ Sorting performance optimizations | Local sorting is now up to 10x faster. |
[Inline editing for Multi-Row Layout](#mrl-inline-editing)| The Multi-Row Layout feature now supports inline row and cell editing. |
Multi-Column Headers collapsible column groups | Collapsible Column Groups is a feature that provides an option to collapse/expand a Multi-Column Header to a smaller set of data. |
Column setter | Column collection now can be changed at runtime. |
-igGrid Modal Dialog extensibility| Grid features that include dialogs (Updating, Filtering, Sorting, Hiding, GroupBy, Column Moving) now add a new `dialogWidget` option allowing for custom dialog implementations - [view sample]({environment:SamplesUrl}/grid/custom-modal-dialog) and [topic](Extending_igGrid_Modal_Dialog.html). |
-Binding Real-Time Data sample| A new sample is added that demonstrates binding igGrid to real-time data - [view sample]({environment:SamplesUrl}/grid/binding-real-time-data). |
-Performance Options sample| A new sample is added that demonstrates the performance options provided by the igGrid - [view sample]({environment:SamplesUrl}/grid/grid-performance). |
+igGrid Modal Dialog extensibility| Grid features that include dialogs (Updating, Filtering, Sorting, Hiding, GroupBy, Column Moving) now add a new `dialogWidget` option allowing for custom dialog implementations - [view sample](\{environment:SamplesUrl\}/grid/custom-modal-dialog) and [topic](Extending_igGrid_Modal_Dialog.html). |
+Binding Real-Time Data sample| A new sample is added that demonstrates binding igGrid to real-time data - [view sample](\{environment:SamplesUrl\}/grid/binding-real-time-data). |
+Performance Options sample| A new sample is added that demonstrates the performance options provided by the igGrid - [view sample](\{environment:SamplesUrl\}/grid/grid-performance). |
### igPieChart
@@ -265,16 +268,16 @@ If you want to load the new igCategoryChart control you need everything you need
* infragistics.ui.categorychart.js
-### {environment:ProductName} NuGet packages
+### \{environment:ProductName\} NuGet packages
-Three new {environment:ProductName} NuGet packages are added in this 2016 volume 2 release. Those packages can boost your productivity allowing you to setup your application faster. They will automatically include the {environment:ProductName} files and references you need to your project.
+Three new \{environment:ProductName\} NuGet packages are added in this 2016 volume 2 release. Those packages can boost your productivity allowing you to setup your application faster. They will automatically include the \{environment:ProductName\} files and references you need to your project.
With the new ASP.NET most modules are now wrapped as NuGet packages. Having this in mind our new MVC wrappers built on top of ASP.NET Core are also available as a NuGet package.
The NuGet packages are installed with the product`s installer and during the installation a new local feed is created, meaning that you don`t need to setup your NuGet Package Manager. You will find the local NuGet feed Infragistics (Local) the next time you run your Visual Studio.
#### Related Topic:
-- [Using {environment:ProductName} NuGet packages](//general-and-getting-started/using-ignite-ui-nuget-packages.mdx)
+- [Using \{environment:ProductName\} NuGet packages](//general-and-getting-started/using-ignite-ui-nuget-packages.mdx)
## igDataChart
@@ -481,8 +484,8 @@ Local grouping performance is optimized and now can be up to 10x faster.
- [Column Grouping Overview (igGrid)](../../02_Controls/igGrid/03_Features/00_Columns/01_Grouping/00_igGrid_GroupBy_Overview.mdx#api-usage)
#### Related Samples
-- [Continuous Virtualization]({environment:SamplesUrl}/grid/virtualization-continuous)
-- [Grouping API]({environment:SamplesUrl}/grid/grouping-api)
+- [Continuous Virtualization](\{environment:SamplesUrl\}/grid/virtualization-continuous)
+- [Grouping API](\{environment:SamplesUrl\}/grid/grouping-api)
### Inline editing for Multi-Row Layout
@@ -494,7 +497,7 @@ Updating feature now works in row and cell edit mode when Multi-Row Layout is co
- [Grid Multi-Row Layout](../../02_Controls/igGrid/03_Features/16_igGrid_MultiRowLayout.mdx#features-integration)
#### Related Samples
-- [Multi-Row Layout Inline Editing]({environment:SamplesUrl}/grid/multi-row-layout-inline-editing)
+- [Multi-Row Layout Inline Editing](\{environment:SamplesUrl\}/grid/multi-row-layout-inline-editing)
## igPieChart
@@ -556,9 +559,9 @@ It allows you to create a consistent scrolling experience across all scrolling c
- [Configuring igScroll](Configuring-igScroll.html)
#### Related Samples
-- [Basic Usage]({environment:SamplesUrl}/scroll/basic-usage)
-- [Scrolling multiple containers at once]({environment:SamplesUrl}/scroll/scrolling-multiple-containers)
-- [Configuration Options]({environment:SamplesUrl}/scroll/configuration-options)
+- [Basic Usage](\{environment:SamplesUrl\}/scroll/basic-usage)
+- [Scrolling multiple containers at once](\{environment:SamplesUrl\}/scroll/scrolling-multiple-containers)
+- [Configuration Options](\{environment:SamplesUrl\}/scroll/configuration-options)
## igValidator
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/12-whats-new-in-2016-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/12-whats-new-in-2016-volume1.mdx
index a22031d0e2..5653cbb659 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/12-whats-new-in-2016-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/12-whats-new-in-2016-volume1.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2016 Volume 1"
slug: whats-new-in-2016-volume1
---
+
+# What's New in 2016 Volume 1
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
#What's New in 2016 Volume 1
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2016 Volume 1 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2016 Volume 1 release.
##What’s New Summary
@@ -17,16 +20,16 @@ The following summarizes what’s new in 2016 Volume 1. Additional details follo
Feature | Description
---|---
-New Bootstrap 4 theme | A new Bootstrap 4 compatible theme is now shipped with {environment:ProductName} - [view sample]({environment:SamplesUrl}/themes/bootstrap4-default).
-Angular 2 Components (CTP) | {environment:ProductName} widgets have component wrappers for Angular 2. For detailed information visit [{environment:ProductName} Angular 2 GitHub](https://github.com/IgniteUI/igniteui-angular-wrappers) page.|
+New Bootstrap 4 theme | A new Bootstrap 4 compatible theme is now shipped with \{environment:ProductName\} - [view sample](\{environment:SamplesUrl\}/themes/bootstrap4-default).
+Angular 2 Components (CTP) | \{environment:ProductName\} widgets have component wrappers for Angular 2. For detailed information visit [\{environment:ProductName\} Angular 2 GitHub](https://github.com/IgniteUI/igniteui-angular-wrappers) page.|
New scalable font icons | The default Infragistics theme now uses [jQuery UI font icons](https://github.com/mkkeck/jquery-ui-iconfont) instead of image icons. |
-Modernizr 3.x support | {environment:ProductName} uses Modernizr library to detect touch environments (see [Touch Support for {environment:ProductName} Controls](//general-and-getting-started/touch-support-for-igniteui-for-jquery-controls.mdx)). [Mordernizr 3.x](https://modernizr.com/) is now supported along with older Modernizr versions. |
+Modernizr 3.x support | \{environment:ProductName\} uses Modernizr library to detect touch environments (see [Touch Support for \{environment:ProductName\} Controls](//general-and-getting-started/touch-support-for-igniteui-for-jquery-controls.mdx)). [Mordernizr 3.x](https://modernizr.com/) is now supported along with older Modernizr versions. |
### igTileManager
Feature | Description
---|---
-Splitter Options| `splitterOptions` now replaces the `showSplitter` option. Besides showing and hiding, additional functionalities are added. You can configure the splitter to be collapsible as well as attach to its collapsed/expanded events. Since `showSplitter` option will no longer be available, you can refer to the following sample to see how the new option can be used - [view sample]({environment:SamplesUrl}/tile-manager/collapsible-splitter).
+Splitter Options| `splitterOptions` now replaces the `showSplitter` option. Besides showing and hiding, additional functionalities are added. You can configure the splitter to be collapsible as well as attach to its collapsed/expanded events. Since `showSplitter` option will no longer be available, you can refer to the following sample to see how the new option can be used - [view sample](\{environment:SamplesUrl\}/tile-manager/collapsible-splitter).
### igDataSource
@@ -38,11 +41,11 @@ New field option - `mapper`| For field with dataType="object" we now allow setti
Feature | Description
---|---
-New column option - mapper| For columns with dataType="object" we now allow setting a mapper function, which can be used for complex data extraction from complex objects, whose return value will be used for all data operations executed on the specific column.- [view sample]({environment:SamplesUrl}/grid/handling-complex-objects). You can find more detailed information in the following topic: [Columns and Layout](../../02_Controls/igGrid/03_Features/12_igGrid_Columns_and_Layout.mdx#defining-mapper)|
+New column option - mapper| For columns with dataType="object" we now allow setting a mapper function, which can be used for complex data extraction from complex objects, whose return value will be used for all data operations executed on the specific column.- [view sample](\{environment:SamplesUrl\}/grid/handling-complex-objects). You can find more detailed information in the following topic: [Columns and Layout](../../02_Controls/igGrid/03_Features/12_igGrid_Columns_and_Layout.mdx#defining-mapper)|
The ColumnFixing feature now works with grid width set in percentage| The ColumnFixing feature now works when the grid width is set in percentage. **Note**: The column widths should still be defined in pixels units (either explicitly or using the option).|
[Multi-Row Layout feature](#multi-row-layout)| The Multi-Row Layout feature enables you to create complex grid record layouts, that contain multiple rows with cells in them spanning multiple columns and rows. |
[Checkbox Appearance](#checkbox-appearance)| Checkbox column visual appearance have changed to indicate that the checkmarks are not interactable in display mode. |
-Paste from Excel sample| A new sample is added that demonstrates pasting Excel clipboard data into igGrid - [view sample]({environment:SamplesUrl}/grid/paste-from-excel). |
+Paste from Excel sample| A new sample is added that demonstrates pasting Excel clipboard data into igGrid - [view sample](\{environment:SamplesUrl\}/grid/paste-from-excel). |
### igTreeGrid
@@ -52,7 +55,7 @@ Feature | Description
### TypeScript Support
-Starting with 16.1 release {environment:ProductName} the minimum supported TypeScript version is 1.4.
+Starting with 16.1 release \{environment:ProductName\} the minimum supported TypeScript version is 1.4.
Feature | Description
---|---
@@ -73,7 +76,7 @@ Initializing the Multi-Row Layout is done entirely through the igGrid's column c
- [Grid Multi-Row Layout](//controls/iggrid/features/multirowlayout.mdx)
#### Related Samples
-- [Multi-Row Layout]({environment:SamplesUrl}/grid/multi-row-layout)
+- [Multi-Row Layout](\{environment:SamplesUrl\}/grid/multi-row-layout)
### Checkbox Appearance
Checkbox column visual appearance have changed and it's square box is not going to be rendered when the grid is in display mode. What would be provided is only a plain checkmark. This change is due to refinement of the experience for the end-users, who naturally perceived that this was an interactive element, which they can click to toggle.
@@ -84,7 +87,7 @@ Checkbox column visual appearance have changed and it's square box is not going
- [Rendering Checkboxes on a Column](../../02_Controls/igGrid/03_Features/12_igGrid_Columns_and_Layout.mdx#checkboxes)
#### Related Samples
-- [Checkbox Column]({environment:SamplesUrl}/grid/checkbox-column)
+- [Checkbox Column](\{environment:SamplesUrl\}/grid/checkbox-column)
## igTreeGrid
@@ -102,7 +105,7 @@ The add new row UI is rendered inline next to its parent.
- [Updating (igTreeGrid)](//controls/igtreegrid/features/updating.mdx)
#### Related Samples
-- [Updating]({environment:SamplesUrl}/tree-grid/updating)
+- [Updating](\{environment:SamplesUrl\}/tree-grid/updating)
## TypeScript Support
@@ -129,7 +132,7 @@ All possible methods with their parameters are now listed in the intellisense.

#### Methods intellisense on the widget's `data`
-In jQuery UI syntax the widget methods can be invoked from the widget's data: $(".selector").data('widgetName'). This is now possible with the {environment:ProductName} TypeScript directives.
+In jQuery UI syntax the widget methods can be invoked from the widget's data: $(".selector").data('widgetName'). This is now possible with the \{environment:ProductName\} TypeScript directives.

diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/13-whats-new-in-2015-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/13-whats-new-in-2015-volume2.mdx
index 47d28905df..bfe5ba84f2 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/13-whats-new-in-2015-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/13-whats-new-in-2015-volume2.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2015 Volume 2"
slug: whats-new-in-2015-volume2
---
+
+# What's New in 2015 Volume 2
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
#What's New in 2015 Volume 2
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2015 Volume 2 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2015 Volume 2 release.
##What’s New Summary
@@ -17,19 +20,19 @@ The following summarizes what’s new in 2015 Volume 2. Additional details follo
Feature | Description
---|---
-[New {environment:ProductName} Scaffolder for MVC](#igniteui-scaffolder) | New scaffolder for {environment:ProductName} widgets.
-Full support for ASP.NET MVC 6 for all {environment:ProductName} widgets | The Infragistics.Web.Mvc.dll now includes version build against ASP.NET MVC 6.
-{environment:ProductName} TypeScript 1.5 definitions | The {environment:ProductName} TypeScript definitions now support TypeScript 1.5. Intellisense is added for widget methods.
+[New \{environment:ProductName\} Scaffolder for MVC](#igniteui-scaffolder) | New scaffolder for \{environment:ProductName\} widgets.
+Full support for ASP.NET MVC 6 for all \{environment:ProductName\} widgets | The Infragistics.Web.Mvc.dll now includes version build against ASP.NET MVC 6.
+\{environment:ProductName\} TypeScript 1.5 definitions | The \{environment:ProductName\} TypeScript definitions now support TypeScript 1.5. Intellisense is added for widget methods.
### igCombo
Feature | Description
---|---
-Auto complete | Typing in the combo will now suggests the first matching result from the list. [View sample]({environment:SamplesUrl}/combo/filtering)
-[Grouping](#combo-grouping) | You can now group items in the combo list. [View sample]({environment:SamplesUrl}/combo/grouping)
-Header and Footer Templates | Header and footer can now be configured in the combo using templates. [View sample]({environment:SamplesUrl}/combo/templates)
+Auto complete | Typing in the combo will now suggests the first matching result from the list. [View sample](\{environment:SamplesUrl\}/combo/filtering)
+[Grouping](#combo-grouping) | You can now group items in the combo list. [View sample](\{environment:SamplesUrl\}/combo/grouping)
+Header and Footer Templates | Header and footer can now be configured in the combo using templates. [View sample](\{environment:SamplesUrl\}/combo/templates)
RTL Support | Added support for right-to-left languages.
[Dropdown Orientation](#combo-dd-orientation) | By default the dropdown list will automatically display on top or bottom depending on the available space. You can also explicilty configure its behavior with the `dropDownOrientation` option.
-Custom Values | The option `allowCustomValue` to set custom values in combo’s text input was dropped in 15.1, but we listened to your feedback and we are enabling this back in this release. [View sample]({environment:SamplesUrl}/combo/editing)
+Custom Values | The option `allowCustomValue` to set custom values in combo’s text input was dropped in 15.1, but we listened to your feedback and we are enabling this back in this release. [View sample](\{environment:SamplesUrl\}/combo/editing)
Performance Improvements | We ensure all interactions with the combo work smoothly with more than 10 000 records. Initial loading time, dropdown opening and closing animations, selection, typing with auto complete and auto select – it all works blazing fast.
### igDataChart
@@ -85,7 +88,7 @@ Feature | Description
### igValidator
Feature | Description
---|---
-[Refactored Validator](#validator) | The Validator is reworked to allow flexible validation on an array of {environment:ProductName} components, as well as standard input form elements
+[Refactored Validator](#validator) | The Validator is reworked to allow flexible validation on an array of \{environment:ProductName\} components, as well as standard input form elements
### igUpload
@@ -95,16 +98,16 @@ Sending additional data between the client and server during file uploading | Yo
##General
-### New {environment:ProductName} Scaffolder for MVC
+### New \{environment:ProductName\} Scaffolder for MVC
-We release a brand new Scaffolder for {environment:ProductName} widgets. With this we boost developer productivity greatly by providing code generation and templates to quickly target standard data scenarios like creating, reading, updating and deleting data. With a few clicks you can completely configure a Grid, generate a controller and save time on manual coding. Configuring other widgets as HierarchicalGrid, TreeGrid, Data Chart and others are already in the works.
-Along with the standard templates for create, edit, delete, details and list that ship with ASP.NET MVC, we provide customized {environment:ProductName} templates that use the new editor widgets.
+We release a brand new Scaffolder for \{environment:ProductName\} widgets. With this we boost developer productivity greatly by providing code generation and templates to quickly target standard data scenarios like creating, reading, updating and deleting data. With a few clicks you can completely configure a Grid, generate a controller and save time on manual coding. Configuring other widgets as HierarchicalGrid, TreeGrid, Data Chart and others are already in the works.
+Along with the standard templates for create, edit, delete, details and list that ship with ASP.NET MVC, we provide customized \{environment:ProductName\} templates that use the new editor widgets.

#### Related Topics
-- [{environment:ProductName} Scaffolder Visual Studio extension](//asp-net-mvc/mvcscaffolding/mvc-scaffolding.mdx)
+- [\{environment:ProductName\} Scaffolder Visual Studio extension](//asp-net-mvc/mvcscaffolding/mvc-scaffolding.mdx)
## igCombo
###
@@ -119,10 +122,10 @@ By default the dropdown orientation is set to 'auto' and this means that accordi
#### Related Samples
-- [Auto Complete]({environment:SamplesUrl}/combo/filtering)
-- [Grouping]({environment:SamplesUrl}/combo/grouping)
-- [Header and Footer Templates]({environment:SamplesUrl}/combo/templates)
-- [Custom Values]({environment:SamplesUrl}/combo/editing)
+- [Auto Complete](\{environment:SamplesUrl\}/combo/filtering)
+- [Grouping](\{environment:SamplesUrl\}/combo/grouping)
+- [Header and Footer Templates](\{environment:SamplesUrl\}/combo/templates)
+- [Custom Values](\{environment:SamplesUrl\}/combo/editing)
## igDataChart
@@ -175,12 +178,12 @@ For information on how to migrate to the new editors see the "Related Topics" se
#### Related Samples
-- [New Text Editor]({environment:SamplesUrl}/editors/text-editor)
-- [Credit]({environment:SamplesUrl}/editors/credit)
-- [Numeric Editor]({environment:SamplesUrl}/editors/numeric-editor)
-- [Mask Editor]({environment:SamplesUrl}/editors/mask-editor)
-- [Checkbox Editor]({environment:SamplesUrl}/editors/checkbox-editor)
-- [Date Editor]({environment:SamplesUrl}/editors/date-editor)
+- [New Text Editor](\{environment:SamplesUrl\}/editors/text-editor)
+- [Credit](\{environment:SamplesUrl\}/editors/credit)
+- [Numeric Editor](\{environment:SamplesUrl\}/editors/numeric-editor)
+- [Mask Editor](\{environment:SamplesUrl\}/editors/mask-editor)
+- [Checkbox Editor](\{environment:SamplesUrl\}/editors/checkbox-editor)
+- [Date Editor](\{environment:SamplesUrl\}/editors/date-editor)
## igGrid
@@ -196,8 +199,8 @@ Last, but not least, the new updating functionality of the grid component has be
- [Configuring the Row Edit Dialog (igGrid)](iggrid-updating-roweditdialog-configuring.html)
#### Related Samples
-- [Row Edit Dialog]({environment:SamplesUrl}/grid/row-edit-dialog)
-- [Editing: Custom Editor Provider]({environment:SamplesUrl}/grid/editing-custom-editor-provider)
+- [Row Edit Dialog](\{environment:SamplesUrl\}/grid/row-edit-dialog)
+- [Editing: Custom Editor Provider](\{environment:SamplesUrl\}/grid/editing-custom-editor-provider)
### Filtering Improvements
@@ -211,7 +214,7 @@ Two new options are introduced in the Filtering feature:
- - an array of consitions to be enabled per column basis.
#### Related Samples
-- [Filtering]({environment:SamplesUrl}/grid/custom-conditions-filtering)
+- [Filtering](\{environment:SamplesUrl\}/grid/custom-conditions-filtering)
### RowSelectors Improvements
When Paging feature is enabled in combination with Row Selectors an additional UI is introduced to allow users to select all rows across all pages.
@@ -245,7 +248,7 @@ Additionally when Paging feature is enabled in combination with Row Selectors an
- [Row Selectors (igTreeGrid)](//controls/igtreegrid/features/row-selectors.mdx)
#### Related Samples
-- [Row Selectors]({environment:SamplesUrl}/tree-grid/row-selectors)
+- [Row Selectors](\{environment:SamplesUrl\}/tree-grid/row-selectors)
### Remote Sorting, Paging, Filtering and Load on Demand in the TreeGrid MVC Wrapper
@@ -256,7 +259,7 @@ You just need to decorate the action that handles the remote features with the `
- [Remote Features (igTreeGrid)](//controls/igtreegrid/features/remote-features.mdx)
#### Related Samples
-- [Remote Features]({environment:SamplesUrl}/tree-grid/remote-features)
+- [Remote Features](\{environment:SamplesUrl\}/tree-grid/remote-features)
### Paging Context Row
@@ -272,7 +275,7 @@ The functionality is controlled by the Refactored Validator
-The refactored igValidator component allows flexible validation on an array of {environment:ProductName} components, as well as standard input form elements. The mechanism uses the igNotification component capabilities to both handle the validation process and display flexible and visually appealing notifications to the end user. See [Migrating to the new igValidator control](//controls/igvalidator/migration-topic.mdx) for information on how to migrate to the refactored igValidator.
+The refactored igValidator component allows flexible validation on an array of \{environment:ProductName\} components, as well as standard input form elements. The mechanism uses the igNotification component capabilities to both handle the validation process and display flexible and visually appealing notifications to the end user. See [Migrating to the new igValidator control](//controls/igvalidator/migration-topic.mdx) for information on how to migrate to the refactored igValidator.

@@ -305,4 +308,4 @@ The refactored igValidator component allows flexible validation on an array of &
- [Migrating to the new igValidator control](//controls/igvalidator/migration-topic.mdx)
#### Related Samples
-- [Basic Usage]({environment:SamplesUrl}/validator/basic-usage)
+- [Basic Usage](\{environment:SamplesUrl\}/validator/basic-usage)
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/14-whats-new-in-2015-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/14-whats-new-in-2015-volume1.mdx
index 5d2024478e..2349d400fa 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/14-whats-new-in-2015-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/14-whats-new-in-2015-volume1.mdx
@@ -2,11 +2,14 @@
title: "What's New in 2015 Volume 1"
slug: whats-new-in-2015-volume1
---
+
+# What's New in 2015 Volume 1
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
#What's New in 2015 Volume 1
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2015 Volume 1 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2015 Volume 1 release.
##What’s New Summary
@@ -17,13 +20,13 @@ The following summarizes what’s new in 2015 Volume 1. Additional details follo
Feature | Description
---|---
-[New {environment:ProductName} Help Viewer](#help-viewer) | We have a brand new, modernized help viewer for {environment:ProductName}.
+[New \{environment:ProductName\} Help Viewer](#help-viewer) | We have a brand new, modernized help viewer for \{environment:ProductName\}.
-### {environment:ProductName} Page Designer
+### \{environment:ProductName\} Page Designer
Feature | Description
---|---
-[Out-of-the-Box Theming Support](#page-designer-theming-support) | Added support for other {environment:ProductName} themes and common Bootstrap-based themes that you can easily select with the built-in theme picker.
+[Out-of-the-Box Theming Support](#page-designer-theming-support) | Added support for other \{environment:ProductName\} themes and common Bootstrap-based themes that you can easily select with the built-in theme picker.
[Improved Data Sources Experience](#page-designer-datasource-expirience) | Added explicit support for JSONP data source and local data source as well as a new data source editor.
[Intellisense support for Ace](#page-designer-intellisense-support) | Added support for showing intellisense when the designer is in code view and the user starts typing
[Remote data source – user friendly errors](#page-designer-remote-dataSource) | Web designer now has user interface for showing detailed information for the possible problem, while connecting to the remote data source
@@ -77,21 +80,21 @@ API Improvements| We also took this opportunity to revisit some less-than-optima
Feature | Description
---|---
-jQuery Mobile 1.4+ Support | {environment:ProductName} mobile controls are now compatible with the most recent version of jQuery Mobile, 1.4+.
+jQuery Mobile 1.4+ Support | \{environment:ProductName\} mobile controls are now compatible with the most recent version of jQuery Mobile, 1.4+.
##General
-### New {environment:ProductName} Help Viewer
+### New \{environment:ProductName\} Help Viewer
-We have a brand new, modernized help viewer for {environment:ProductName}. This makes it much easier to navigate through and share individual topics, and you can also easily switch between product versions (for version 14.1 and up) directly in a topic.
+We have a brand new, modernized help viewer for \{environment:ProductName\}. This makes it much easier to navigate through and share individual topics, and you can also easily switch between product versions (for version 14.1 and up) directly in a topic.
Beyond making the experience easier to use, the actual topics themselves are now available on GitHub in Markdown. This means that you can easily report issues on topics or perhaps even submit additions or changes to a topic via a GitHub pull request.
#### Related Content
-- [{environment:ProductName} Help Topics on GitHub](https://github.com/IgniteUI/help-topics)
+- [\{environment:ProductName\} Help Topics on GitHub](https://github.com/IgniteUI/help-topics)
-##{environment:ProductName} Page Designer
+##\{environment:ProductName\} Page Designer
### Out-of-the-Box Theming Support
Selecting a theme from the list changes the theme for all the components already dropped on the design surface.
@@ -124,13 +127,13 @@ In 14.2, we CTP’d the first version of the "Client-Side Excel Library" which i
#### Related Topics
- [Understanding the Infragistics JavaScript Excel Library](../../09_JavaScript Excel Library/00_Understanding/~Understanding_the_Infragistics_JavaScript_Excel_Library.mdx)
-- [Using the {environment:ProductName} JavaScript Excel Library](../../09_JavaScript Excel Library/01_Using/~Using_The_JavaScript_Excel_Library.mdx)
+- [Using the \{environment:ProductName\} JavaScript Excel Library](../../09_JavaScript Excel Library/01_Using/~Using_The_JavaScript_Excel_Library.mdx)
#### Related Samples
-- [Excel Table]({environment:NewSamplesUrl}/javascript-excel-library/excel-table)
-- [Excel Formatting]({environment:NewSamplesUrl}/javascript-excel-library/excel-formatting)
-- [Excel Formulas]({environment:NewSamplesUrl}/javascript-excel-library/excel-formulas)
+- [Excel Table](\{environment:NewSamplesUrl\}/javascript-excel-library/excel-table)
+- [Excel Formatting](\{environment:NewSamplesUrl\}/javascript-excel-library/excel-formatting)
+- [Excel Formulas](\{environment:NewSamplesUrl\}/javascript-excel-library/excel-formulas)
## igGrid
@@ -145,10 +148,10 @@ The igGridExcelExporter component allows you to export data from the igGrid into
#### Related Samples
-- [Export Basic Grid to Excel]({environment:NewSamplesUrl}/grid/export-basic-grid)
-- [Exporting Grid to Excel with Features]({environment:NewSamplesUrl}/grid/export-feature-rich-grid)
-- [Customizing Grid Excel Export]({environment:NewSamplesUrl}/grid/export-client-events)
-- [Exporting Grid to Excel with Progress Indicator]({environment:NewSamplesUrl}/grid/export-grid-loading-indicator)
+- [Export Basic Grid to Excel](\{environment:NewSamplesUrl\}/grid/export-basic-grid)
+- [Exporting Grid to Excel with Features](\{environment:NewSamplesUrl\}/grid/export-feature-rich-grid)
+- [Customizing Grid Excel Export](\{environment:NewSamplesUrl\}/grid/export-client-events)
+- [Exporting Grid to Excel with Progress Indicator](\{environment:NewSamplesUrl\}/grid/export-grid-loading-indicator)
### Responsive Feature Improvements
@@ -159,7 +162,7 @@ The igGridExcelExporter component allows you to export data from the igGrid into
#### Related Samples
-- [Responsive Single Column Template]({environment:NewSamplesUrl}/grid/responsive-single-column-template)
+- [Responsive Single Column Template](\{environment:NewSamplesUrl\}/grid/responsive-single-column-template)
### Column Styling
With the new and column settings you can apply CSS classes to both the header and the column data cells as shown in the screenshot below.
@@ -192,8 +195,8 @@ Supported features in the RTM are:
#### Related Samples
-- [JSON Binding]({environment:NewSamplesUrl}/tree-grid/json-binding)
-- [Balance Sheet]({environment:NewSamplesUrl}/tree-grid/balance-sheet)
+- [JSON Binding](\{environment:NewSamplesUrl\}/tree-grid/json-binding)
+- [Balance Sheet](\{environment:NewSamplesUrl\}/tree-grid/balance-sheet)
### Tree-Specific Filtering
@@ -208,7 +211,7 @@ The other available mode is `"showWithAncestorsAndDescendants"` which in additio
#### Related Samples
-- [File Explorer]({environment:NewSamplesUrl}/tree-grid/file-explorer)
+- [File Explorer](\{environment:NewSamplesUrl\}/tree-grid/file-explorer)
### Remote Load on Demand
@@ -222,7 +225,7 @@ The Load on Demand functionality enables the tree grid to request the data for t
#### Related Samples
-- [Load on Demand]({environment:NewSamplesUrl}/tree-grid/load-on-demand)
+- [Load on Demand](\{environment:NewSamplesUrl\}/tree-grid/load-on-demand)
##igCombo
@@ -239,11 +242,11 @@ Our original jQuery-based combo that we shipped almost four years ago was very f
#### Related Samples
-- [JSON Binding]({environment:NewSamplesUrl}/combo/json-binding)
-- [Selection and Checkboxes]({environment:NewSamplesUrl}/combo/selection-and-checkboxes)
-- [Filtering]({environment:NewSamplesUrl}/combo/filtering)
-- [Load-On-Demand]({environment:NewSamplesUrl}/combo/load-on-demand)
-- [Keyboard Navigation]({environment:NewSamplesUrl}/combo/keyboard-navigation)
+- [JSON Binding](\{environment:NewSamplesUrl\}/combo/json-binding)
+- [Selection and Checkboxes](\{environment:NewSamplesUrl\}/combo/selection-and-checkboxes)
+- [Filtering](\{environment:NewSamplesUrl\}/combo/filtering)
+- [Load-On-Demand](\{environment:NewSamplesUrl\}/combo/load-on-demand)
+- [Keyboard Navigation](\{environment:NewSamplesUrl\}/combo/keyboard-navigation)
### Rewritten Knockout Extension
@@ -251,4 +254,4 @@ The Knockout extension for the igCombo was adapted to meet the requirements of t
#### Related Samples
-- [KnockoutJS Binding]({environment:NewSamplesUrl}/combo/bind-combo-with-ko)
+- [KnockoutJS Binding](\{environment:NewSamplesUrl\}/combo/bind-combo-with-ko)
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/15-whats-new-in-2014-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/15-whats-new-in-2014-volume2.mdx
index d808d78353..2c04a33674 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/15-whats-new-in-2014-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/15-whats-new-in-2014-volume2.mdx
@@ -3,9 +3,11 @@ title: "What's New in 2014 Volume 2"
slug: whats-new-in-2014-volume2
---
+# What's New in 2014 Volume 2
+
#What's New in 2014 Volume 2
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2014 Volume 2 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2014 Volume 2 release.
##What’s New Summary
@@ -16,17 +18,17 @@ The following summarizes what’s new in 2014 Volume 2. Additional details follo
Feature | Description
---|---
-[AngularJS directives](#angular-directives) | Now {environment:ProductName} controls feature custom directives for AngularJS.
+[AngularJS directives](#angular-directives) | Now \{environment:ProductName\} controls feature custom directives for AngularJS.
-### {environment:ProductName} Page Designer
+### \{environment:ProductName\} Page Designer
Feature | Description
---|---
-[WYSIWYG for HTML5](#wysiwyg) | New drag-n-drop UI design surface for Modern Web using {environment:ProductName} controls.
+[WYSIWYG for HTML5](#wysiwyg) | New drag-n-drop UI design surface for Modern Web using \{environment:ProductName\} controls.
Responsive Web Design (RWD) | Visualize and manage breakpoints to make responsive design easier.
Clean Code Editor | See, edit, and copy clean code to incorporate into your projects.
-Easier Data Access | Easily configure {environment:ProductName} data source components to connect your controls to your data.
+Easier Data Access | Easily configure \{environment:ProductName\} data source components to connect your controls to your data.
Integrated API Help | See help for API members in both the component editor and in the code editor.
@@ -64,7 +66,7 @@ Feature | Description
Feature | Description
---|---
-[Bootstrap theming](#bootstrap-theming) | {environment:ProductName} controls now support Bootstrap theming.
+[Bootstrap theming](#bootstrap-theming) | \{environment:ProductName\} controls now support Bootstrap theming.
[New theme (RTM)](#new-theme) | The iOS 7-style theme is now RTM and renamed to just iOS theme—replaces prior iOS6-style theme. The theme also added support for the jQuery Mobile 1.4 + controls.
[Updated themes to support jQuery UI 1.11+](#update-themes) | New theme files are added in order to support jQuery UI 1.11+ own controls.
@@ -75,7 +77,7 @@ Feature | Description
We launched a preview of AngularJS directives last release on our GitHub repo; they are now officially in the product as well and are considered RTM.
-All of the {environment:ProductName} controls can be instantiated declaratively with custom tags or from the controller or via controller options. Further, the following controls support two-way data binding:
+All of the \{environment:ProductName\} controls can be instantiated declaratively with custom tags or from the controller or via controller options. Further, the following controls support two-way data binding:
- igGrid
- igCombo
@@ -87,28 +89,28 @@ All of the {environment:ProductName} controls can be instantiated decl
[AngularJS Directives](../../10_AngularJS Directives/~AngularJS_Directives.mdx)
-[{environment:ProductName} directives for AngularJS on GitHub](https://github.com/IgniteUI/igniteui-angularjs)
+[\{environment:ProductName\} directives for AngularJS on GitHub](https://github.com/IgniteUI/igniteui-angularjs)
#### Related Samples
-[{environment:ProductName} directives for AngularJS samples](http://igniteui.github.io/igniteui-angularjs/)
+[\{environment:ProductName\} directives for AngularJS samples](http://igniteui.github.io/igniteui-angularjs/)
-##{environment:ProductName} Page Designer
+##\{environment:ProductName\} Page Designer
### WYSIWYG for HTML5
-Leverage common HTML elements, Bootstrap components, and of course {environment:ProductName} components to lay out and jumpstart your modern LOB pages. It’s the best way to learn to use {environment:ProductName} and more quickly configure {environment:ProductName} controls to then copy into your projects.
+Leverage common HTML elements, Bootstrap components, and of course \{environment:ProductName\} components to lay out and jumpstart your modern LOB pages. It’s the best way to learn to use \{environment:ProductName\} and more quickly configure \{environment:ProductName\} controls to then copy into your projects.
-**Use it now at [{environment:DesignerUrl}]({environment:DesignerUrl}) !**
+**Use it now at [\{environment:DesignerUrl\}](\{environment:DesignerUrl\}) !**

### Responsive Web Design (RWD)
-Visualize and edit your responsive CSS breakpoints and jump into editing the CSS for breakpoints easily. You can also use Bootstrap row components or {environment:ProductName} layout components to easily defing a grid layout for your responsive page.
+Visualize and edit your responsive CSS breakpoints and jump into editing the CSS for breakpoints easily. You can also use Bootstrap row components or \{environment:ProductName\} layout components to easily defing a grid layout for your responsive page.

@@ -120,13 +122,13 @@ We built on top of the world-class ACE code editor to help you see, edit, and co
### Easier Data Access
-The {environment:ProductName} data source components make it easier to connect your controls to your data, and the Page Designer makes those easier to use with custom component editors and letting you easily set your data sources on components that use them. You can pick a data source from a list in the component editor or just drop a data source onto controls like the grid to get started.
+The \{environment:ProductName\} data source components make it easier to connect your controls to your data, and the Page Designer makes those easier to use with custom component editors and letting you easily set your data sources on components that use them. You can pick a data source from a list in the component editor or just drop a data source onto controls like the grid to get started.
### Integrated API Help
Throughout the designer, we incorporate API help so that you don’t have to go digging for it. We do it in the code editor as well as in the component editor:
-1. For {environment:ProductName} componets, you can click the ? link in the component editor to go directly to the API docs for that component.
+1. For \{environment:ProductName\} componets, you can click the ? link in the component editor to go directly to the API docs for that component.
2. When hovering over properties and events, we show you the related API docs right there.

@@ -141,12 +143,12 @@ Our new Excel Library is a 100% pure JavaScript client-side library that support
#### Related Topics
-- [{environment:ProductName} Client-Side Excel Library Overview](../../09_JavaScript Excel Library/00_Understanding/JavaScript_Excel_Library_Overview.mdx)
-- [Using the {environment:ProductName} Client-Side Excel Library](../../09_JavaScript Excel Library/01_Using/~Using_The_JavaScript_Excel_Library.mdx)
+- [\{environment:ProductName\} Client-Side Excel Library Overview](../../09_JavaScript Excel Library/00_Understanding/JavaScript_Excel_Library_Overview.mdx)
+- [Using the \{environment:ProductName\} Client-Side Excel Library](../../09_JavaScript Excel Library/01_Using/~Using_The_JavaScript_Excel_Library.mdx)
#### Related Samples
-- [JavaScript Excel Overview]({environment:NewSamplesUrl}/javascript-excel-library/overview)
+- [JavaScript Excel Overview](\{environment:NewSamplesUrl\}/javascript-excel-library/overview)
## igGrid
@@ -199,8 +201,8 @@ Supported features in the CTP are:
#### Related Samples
-- [File Explorer]({environment:NewSamplesUrl}/tree-grid/file-explorer)
-- [Balance Sheet]({environment:NewSamplesUrl}/tree-grid/balance-sheet)
+- [File Explorer](\{environment:NewSamplesUrl\}/tree-grid/file-explorer)
+- [Balance Sheet](\{environment:NewSamplesUrl\}/tree-grid/balance-sheet)
##igPivotGrid
@@ -213,13 +215,13 @@ The `igPivotGrid`™ control now allows you to visualize the row hierarchies in
#### Related Samples
-- [Layout Modes]({environment:NewSamplesUrl}/pivot-grid/layout-modes)
+- [Layout Modes](\{environment:NewSamplesUrl\}/pivot-grid/layout-modes)
##Theming
### Bootstrap theming
-This release adds a mechanism to apply any Bootstrap theme (which uses LESS variables defined by Bootstrap) look and feel to the {environment:ProductName} controls. The resulting themes are standalone and can be used with or without Bootstrap.
+This release adds a mechanism to apply any Bootstrap theme (which uses LESS variables defined by Bootstrap) look and feel to the \{environment:ProductName\} controls. The resulting themes are standalone and can be used with or without Bootstrap.
The product comes with four preset themes “Bootstrap” (equivalent to the default Bootstrap theme), “Superhero”, “Yeti”, “Flatly” which are compiled against the respective themes taken from [bootswatch.com](http://bootswatch.com/) site.
@@ -231,11 +233,11 @@ Note: The four preset themes as well as the LESS files used to generate them are
#### Related content
-- [Bootstrap Theme Generator]({environment:NewSamplesUrl}/bootstrap-theme-generator)
+- [Bootstrap Theme Generator](\{environment:NewSamplesUrl\}/bootstrap-theme-generator)
### New theme (RTM)
-The previously named iOS7 theme has been renamed to just iOS and replaces the prior iOS6-style theme. The iOS theme is now RTM and adds support for the {environment:ProductName} Mobile Controls.
+The previously named iOS7 theme has been renamed to just iOS and replaces the prior iOS6-style theme. The iOS theme is now RTM and adds support for the \{environment:ProductName\} Mobile Controls.

@@ -243,11 +245,11 @@ The previously named iOS7 theme has been renamed to just iOS and replaces the pr
#### Related samples
-- [iOS theme]({environment:NewSamplesUrl}/themes/ios)
+- [iOS theme](\{environment:NewSamplesUrl\}/themes/ios)
### Updated themes to support jQuery UI 1.11+
-We updated our themes to support the jQuery UI 1.11+ own controls. However, because there are some breaking changes in the CSS structure in jQuery UI, you may see some minor issues in the look and feel of native jQuery UI controls when using {environment:ProductName} themes.
+We updated our themes to support the jQuery UI 1.11+ own controls. However, because there are some breaking changes in the CSS structure in jQuery UI, you may see some minor issues in the look and feel of native jQuery UI controls when using \{environment:ProductName\} themes.
\ No newline at end of file
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/16-whats-new-in-2014-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/16-whats-new-in-2014-volume1.mdx
index 3439b9f58f..a64056f52c 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/16-whats-new-in-2014-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/16-whats-new-in-2014-volume1.mdx
@@ -2,13 +2,16 @@
title: "What's New in 2014 Volume 1"
slug: whats-new-in-2014-volume1
---
+
+# What's New in 2014 Volume 1
+
import ApiLink from 'docs-template/components/mdx/ApiLink.astro';
# What's New in 2014 Volume 1
## Topic Overview
-This topic presents the controls and the new and enhanced features for the {environment:ProductFamilyName}™ 2014 Volume 1 release.
+This topic presents the controls and the new and enhanced features for the \{environment:ProductFamilyName\}™ 2014 Volume 1 release.
## What’s New Summary
@@ -113,7 +116,7 @@ Each template includes documentation and more templates will appear in the Infra

-Note: In previous versions of {environment:ProductName}, the starter templates were installed with the product installer. They are now accessible through the Infragistics Template Gallery.
+Note: In previous versions of \{environment:ProductName\}, the starter templates were installed with the product installer. They are now accessible through the Infragistics Template Gallery.
### New theme (CTP)
@@ -124,7 +127,7 @@ iOS 7 design.
#### Related samples
-- [iOS 7 theme]({environment:SamplesUrl}/themes/ios)
+- [iOS 7 theme](\{environment:SamplesUrl\}/themes/ios)
## Charts Common Features
@@ -193,7 +196,7 @@ A new property – – has been
#### Related Samples
-- [Feature Persistence]({environment:SamplesUrl}/grid/feature-persistence)
+- [Feature Persistence](\{environment:SamplesUrl\}/grid/feature-persistence)
### Improved delete row on touch devices
@@ -211,7 +214,7 @@ In Row Edit mode, the Delete Row button is available along with the Cancel and D
#### Related Samples
-- [Basic Editing]({environment:SamplesUrl}/grid/basic-editing)
+- [Basic Editing](\{environment:SamplesUrl\}/grid/basic-editing)
## igHierarchicalGrid
@@ -242,7 +245,7 @@ by default.
#### Related Samples
-- [Feature Persistence]({environment:SamplesUrl}/grid/feature-persistence)
+- [Feature Persistence](\{environment:SamplesUrl\}/grid/feature-persistence)
### Improved delete row on touch devices
@@ -287,7 +290,7 @@ The `igOlapXmlaDataSource` has now built-in support for displaying KPIs defined
#### Related samples
-- [Binding to Xmla Data Source]({environment:SamplesUrl}/pivot-grid/binding-to-xmla-data-source)
+- [Binding to Xmla Data Source](\{environment:SamplesUrl\}/pivot-grid/binding-to-xmla-data-source)
### Remote ADOMD.NET data provider support
@@ -300,7 +303,7 @@ where ADOMD.NET is used for communication with the SSAS server.
#### Related samples
-- [Remote ADOMD.NET Provider]({environment:SamplesUrl}/pivot-grid/remote-adomd-provider)
+- [Remote ADOMD.NET Provider](\{environment:SamplesUrl\}/pivot-grid/remote-adomd-provider)
## igPopover
@@ -316,7 +319,7 @@ The `igPopover` control, now RTM, adds tooltip-like functionality to DOM element
#### Related samples
-- [Basic Usage]({environment:SamplesUrl}/popover/basic-popover)
+- [Basic Usage](\{environment:SamplesUrl\}/popover/basic-popover)
## igRadialMenu
@@ -332,7 +335,7 @@ The `igRadialMenu` control is a context menu presenting its items in a circular
#### Related samples
-- [Button Items]({environment:SamplesUrl}/radial-menu/button-items)
+- [Button Items](\{environment:SamplesUrl\}/radial-menu/button-items)
## igSplitButton
@@ -344,7 +347,7 @@ The `igSplitButton` control is a drop-down button with which the user can select
#### Related samples
-- [Split button basics]({environment:SamplesUrl}/split-button/change-shapes)
+- [Split button basics](\{environment:SamplesUrl\}/split-button/change-shapes)
## igToolbar
@@ -356,7 +359,7 @@ The `igToolbar` control allows you to create custom toolbars like those in the `
#### Related samples
-- [Standalone Toolbar]({environment:SamplesUrl}/html-editor/standalone-toolbar)
+- [Standalone Toolbar](\{environment:SamplesUrl\}/html-editor/standalone-toolbar)
## igUpload
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/17-whats-new-in-2013-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/17-whats-new-in-2013-volume2.mdx
index 33d8d5ff8b..2073452437 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/17-whats-new-in-2013-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/17-whats-new-in-2013-volume2.mdx
@@ -8,12 +8,12 @@ slug: whats-new-in-2013-volume2
## Topic Overview
### Purpose
-This topic provides an overview of the new features of {environment:ProductName}™ 2013 Volume 2 release.
+This topic provides an overview of the new features of \{environment:ProductName\}™ 2013 Volume 2 release.
## New Features
### New features summary chart
-The following table summarizes the new features for the {environment:ProductName} 2013 Volume 2 release. Additional details are available after the summary table.
+The following table summarizes the new features for the \{environment:ProductName\} 2013 Volume 2 release. Additional details are available after the summary table.
@@ -25,9 +25,9 @@ The following table summarizes the new features for the {environment:Produc
-
{environment:ProductName}
+
\{environment:ProductName\}
Custom downloads
-
A new tool for creating custom downloads is available. Select the controls you want to use and the tool creates a download package containing a customized, combined, and minified JavaScript file and theme files. Find out more on [the download page]({environment:SamplesUrl}/download).
+
A new tool for creating custom downloads is available. Select the controls you want to use and the tool creates a download package containing a customized, combined, and minified JavaScript file and theme files. Find out more on [the download page](\{environment:SamplesUrl\}/download).
@@ -200,7 +200,7 @@ The `igBulletGraph` control is a data visualization control for visualizing data
#### Related Sample
-- [Basic Configuration]({environment:SamplesUrl}/bullet-graph/basic-configuration)
+- [Basic Configuration](\{environment:SamplesUrl\}/bullet-graph/basic-configuration)
## igDataChart
@@ -216,7 +216,7 @@ You can now add a title and/or subtitle to the top section of the chart. When a
#### Related Sample
-- [Title and Subtitle]({environment:SamplesUrl}/data-chart/chart-title)
+- [Title and Subtitle](\{environment:SamplesUrl\}/data-chart/chart-title)
### Axis title and subtitle
@@ -230,7 +230,7 @@ You can now add a title and/or subtitle to the x- and y-axes of the control.
#### Related Sample
-- [Axis Title and Subtitle]({environment:SamplesUrl}/data-chart/axis-title)
+- [Axis Title and Subtitle](\{environment:SamplesUrl\}/data-chart/axis-title)
### Series highlighting
@@ -266,7 +266,7 @@ This feature allows the series to animate during the initialization of the `igDa
#### Related Samples
-- [Transition Animations]({environment:SamplesUrl}/data-chart/transition-animation)
+- [Transition Animations](\{environment:SamplesUrl\}/data-chart/transition-animation)
- [Transition Animations (Financial)](../../02_Controls/igDataChart/04_Configuring/08_igChart_Transitions_In_Animations.mdx#transition-example)
### Hover interactions
@@ -311,7 +311,7 @@ You can now use gradient colors in the chart.
#### Related Sample
-- [Color Gradients]({environment:SamplesUrl}/data-chart/chart-fill-gradients)
+- [Color Gradients](\{environment:SamplesUrl\}/data-chart/chart-fill-gradients)
### Default tooltips
@@ -377,7 +377,7 @@ Visualizing the occurrence of multiple variables (adding multiple series) is pos
#### Related Sample
-- [Doughnut Chart]({environment:SamplesUrl}/doughnut-chart/overview)
+- [Doughnut Chart](\{environment:SamplesUrl\}/doughnut-chart/overview)
## igGrid
@@ -393,7 +393,7 @@ Previously CTP, the Column Fixing feature has now been released to the market an
#### Related Sample
-- [Column Fixing]({environment:SamplesUrl}/grid/column-fixing)
+- [Column Fixing](\{environment:SamplesUrl\}/grid/column-fixing)
### jsRender integration
@@ -405,7 +405,7 @@ The `igGrid` control now supports the jsRender templating engine.
#### Related Sample
-- [**jsRender integration**]({environment:SamplesUrl}/grid/jsrender-integration)
+- [**jsRender integration**](\{environment:SamplesUrl\}/grid/jsrender-integration)
### RWD Mode Vertical Column Rendering
@@ -419,7 +419,7 @@ Vertical Column Rendering is a new feature that renders the grid in two columns
#### Related Sample
-- [**Responsive Vertical Rendering**]({environment:SamplesUrl}/grid/responsive-vertical-rendering)
+- [**Responsive Vertical Rendering**](\{environment:SamplesUrl\}/grid/responsive-vertical-rendering)
### New design of the Feature Chooser
@@ -434,7 +434,7 @@ for touch-enabled devices.
#### Related Sample
-- [Feature Chooser]({environment:SamplesUrl}/grid/feature-chooser)
+- [Feature Chooser](\{environment:SamplesUrl\}/grid/feature-chooser)
### Load-on-Demand (CTP)
@@ -447,7 +447,7 @@ With the `igGrid` Load-on-Demand feature, currently in CTP, the data is not load
#### Related Sample
-- [Load-on-Demand]({environment:SamplesEmbedUrl}/grid/append-rows-on-demand)
+- [Load-on-Demand](\{environment:SamplesEmbedUrl\}/grid/append-rows-on-demand)
## igLayoutManager
@@ -463,8 +463,8 @@ The `igLayoutManager` is a layout control for managing the overall HTML page lay
#### Related Samples
-- [Responsive Column Layout]({environment:SamplesUrl}/layout-manager/column-layout-markup)
-- [Responsive Flow Layout]({environment:SamplesUrl}/layout-manager/flow-layout)
+- [Responsive Column Layout](\{environment:SamplesUrl\}/layout-manager/column-layout-markup)
+- [Responsive Flow Layout](\{environment:SamplesUrl\}/layout-manager/flow-layout)
## igLinearGauge
@@ -482,7 +482,7 @@ against a scale and one or more comparative ranges.
#### Related Sample
-- [Basic Configuration]({environment:SamplesUrl}/linear-gauge/basic-configuration)
+- [Basic Configuration](\{environment:SamplesUrl\}/linear-gauge/basic-configuration)
## igMap
@@ -502,7 +502,7 @@ Because of the sheer number of data points, the series displays the scatter data
#### Related Sample
-- [High Density Scatter Series]({environment:SamplesUrl}/map/geo-high-density-scatter-series)
+- [High Density Scatter Series](\{environment:SamplesUrl\}/map/geo-high-density-scatter-series)
## igPieChart
@@ -514,7 +514,7 @@ You can now add two types of curves to the lines in the label callouts in the `i
#### Related Sample
-- [Layout Configuration]({environment:SamplesUrl}/pie-chart/layout-configuration)
+- [Layout Configuration](\{environment:SamplesUrl\}/pie-chart/layout-configuration)
## igPopover
@@ -533,7 +533,7 @@ The `igPopover` control, currently in CTP, adds tooltip-like functionality to th
#### Related Samples
-- [Basic Popover]({environment:SamplesUrl}/popover/basic-popover)
+- [Basic Popover](\{environment:SamplesUrl\}/popover/basic-popover)
## igQRCodeBarcode
@@ -549,7 +549,7 @@ The `igQRCodeBarcode` control generates QR (Quick Response) barcode images for u
#### Related Samples
-- [QR Barcode Basic Configuration]({environment:SamplesUrl}/barcode/basic-configuration)
+- [QR Barcode Basic Configuration](\{environment:SamplesUrl\}/barcode/basic-configuration)
## igRadialGauge
@@ -565,7 +565,7 @@ The `igQRCodeBarcode` control generates QR (Quick Response) barcode images for u
#### Related Samples
-- [igRadialGauge]({environment:SamplesUrl}/radial-gauge/overview)
+- [igRadialGauge](\{environment:SamplesUrl\}/radial-gauge/overview)
## igTileManager
@@ -584,10 +584,10 @@ The `igTileManager` is a layout control for rendering and managing data into til
#### Related Samples
-- [ASP.NET MVC Basic Usage]({environment:SamplesUrl}/tile-manager/aspnet-mvc-helper)
-- [Binding to JSON Data]({environment:SamplesUrl}/tile-manager/bind-json)
-- [Item Configurations]({environment:SamplesUrl}/tile-manager/item-configurations)
-- [Leading Tile Configuration]({environment:SamplesUrl}/tile-manager/leading-tile)
+- [ASP.NET MVC Basic Usage](\{environment:SamplesUrl\}/tile-manager/aspnet-mvc-helper)
+- [Binding to JSON Data](\{environment:SamplesUrl\}/tile-manager/bind-json)
+- [Item Configurations](\{environment:SamplesUrl\}/tile-manager/item-configurations)
+- [Leading Tile Configuration](\{environment:SamplesUrl\}/tile-manager/leading-tile)
## igZoombar
@@ -603,7 +603,7 @@ The `igZoombar` control provides zooming functionality to range-enabled controls
#### Related Samples
-- [Zoombar Financial Chart]({environment:SamplesUrl}/zoombar/financial-chart)
+- [Zoombar Financial Chart](\{environment:SamplesUrl\}/zoombar/financial-chart)
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/18-whats-new-in-2013-volume1.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/18-whats-new-in-2013-volume1.mdx
index 3682f5ba20..00347b822d 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/18-whats-new-in-2013-volume1.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/18-whats-new-in-2013-volume1.mdx
@@ -8,13 +8,13 @@ slug: whats-new-in-2013-volume1
## Topic Overview
### Purpose
-This topic provides an overview of the new features of {environment:ProductName}® 2013 Volume 1 release.
+This topic provides an overview of the new features of \{environment:ProductName\}® 2013 Volume 1 release.
## New Features
### New Features summary chart
-The following table summarizes the new features for the {environment:ProductName}® 2013 Volume 1 release. Additional details are available after the summary table.
+The following table summarizes the new features for the \{environment:ProductName\}® 2013 Volume 1 release. Additional details are available after the summary table.
@@ -40,7 +40,7 @@ The following table summarizes the new features for the {environment:Produc
igEditors™
[Knockout Support](#igeditors-knockout-support)
-
The support for the Knockout library in {environment:ProductName} editor controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure {environment:ProductName} editors.
+
The support for the Knockout library in \{environment:ProductName\} editor controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure \{environment:ProductName\} editors.
@@ -72,7 +72,7 @@ The following table summarizes the new features for the {environment:Produc
[Knockout Support is RTM](#knockout-support)
-
The support for the Knockout library in {environment:ProductName} `igGrid` controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure {environment:ProductName} grids.
+
The support for the Knockout library in \{environment:ProductName\} `igGrid` controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure \{environment:ProductName\} grids.
@@ -88,7 +88,7 @@ The following table summarizes the new features for the {environment:Produc
[Knockout Support is RTM](#hierarchicalgrid-knockout-support)
-
The support for the Knockout library in {environment:ProductName} `igHierarchicalGrid`™ controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure {environment:ProductName} grids.
+
The support for the Knockout library in \{environment:ProductName\} `igHierarchicalGrid`™ controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure \{environment:ProductName\} grids.
@@ -142,7 +142,7 @@ The following table summarizes the new features for the {environment:Produc
igTree™
[Knockout Support](#igtree-knockout-support)
-
The support for the Knockout library in {environment:ProductName} editor controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure {environment:ProductName} editors.
+
The support for the Knockout library in \{environment:ProductName\} editor controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure \{environment:ProductName\} editors.
@@ -162,15 +162,15 @@ The following table summarizes the new features for the {environment:Produc
-
{environment:ProductNameMVC}
+
\{environment:ProductNameMVC\}
[Support for Adding Events](#support-adding-events)
-
You can now add client events to the {environment:ProductNameMVC} controls’ by using the `AddClientEvent` helper method. Provide an event name and function name to the helper and it renders the required JavaScript on the client to handle the event.
+
You can now add client events to the \{environment:ProductNameMVC\} controls’ by using the `AddClientEvent` helper method. Provide an event name and function name to the helper and it renders the required JavaScript on the client to handle the event.
TypeScript Definition File
[New Feature (CTP)](#typescript-new-feature)
-
TypeScript is a language for adding a typed layer to JavaScript aiding in the development of JavaScript applications. {environment:ProductName} now includes a TypeScript definition file, `igniteui.d.ts`, providing type definitions for all controls.
+
TypeScript is a language for adding a typed layer to JavaScript aiding in the development of JavaScript applications. \{environment:ProductName\} now includes a TypeScript definition file, `igniteui.d.ts`, providing type definitions for all controls.
@@ -242,17 +242,17 @@ The `igDataChart` control now supports over 40 chart types. The following new ch
#### Related Samples
-- [Category Series]({environment:SamplesUrl}/data-chart/category-series)
-- [Polar Series]({environment:SamplesUrl}/data-chart/polar-series)
-- [Radial Series]({environment:SamplesUrl}/data-chart/radial-series)
-- [Scatter Series]({environment:SamplesUrl}/data-chart/scatter-series)
-- [Stacked Series]({environment:SamplesUrl}/data-chart/stacked-series)
+- [Category Series](\{environment:SamplesUrl\}/data-chart/category-series)
+- [Polar Series](\{environment:SamplesUrl\}/data-chart/polar-series)
+- [Radial Series](\{environment:SamplesUrl\}/data-chart/radial-series)
+- [Scatter Series](\{environment:SamplesUrl\}/data-chart/scatter-series)
+- [Stacked Series](\{environment:SamplesUrl\}/data-chart/stacked-series)
## igEditors
### Knockout Support
-The support for the Knockout library in {environment:ProductName} editor controls is
+The support for the Knockout library in \{environment:ProductName\} editor controls is
intended to provide easy means for developers to use the Knockout
library and its declarative syntax to instantiate and configure Ignite
UI editors.
@@ -317,7 +317,7 @@ To this end, the RWD Mode feature supports a set of pre-defined grid templates w
### Knockout Support is RTM
-The support for the Knockout library in {environment:ProductName} `igGrid` controls is
+The support for the Knockout library in \{environment:ProductName\} `igGrid` controls is
intended to provide easy means for developers to use the Knockout
library and its declarative syntax to instantiate and configure Ignite
UI grids.
@@ -336,7 +336,7 @@ The `igGrid`™ Column Fixing feature allows you to pin the columns on the left
#### Related Samples
-[**Column Fixing (igGrid)**]({environment:SamplesUrl}/grid/column-fixing)
+[**Column Fixing (igGrid)**](\{environment:SamplesUrl\}/grid/column-fixing)
## igHierarchicalGrid
@@ -369,11 +369,11 @@ left or the right of the grid so that they are always visible.
#### Related Samples
-[**Column Fixing (igGrid)**]({environment:SamplesUrl}/grid/column-fixing)
+[**Column Fixing (igGrid)**](\{environment:SamplesUrl\}/grid/column-fixing)
### Knockout Support is RTM
-The support for the Knockout library in {environment:ProductName} `igHierarchicalGrid` controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure {environment:ProductName} grids.
+The support for the Knockout library in \{environment:ProductName\} `igHierarchicalGrid` controls is intended to provide easy means for developers to use the Knockout library and its declarative syntax to instantiate and configure \{environment:ProductName\} grids.
The Knockout support is implemented as a Knockout extension which is
invoked initially when Knockout bindings are applied to a page and
@@ -383,7 +383,7 @@ your business case in the data-bind attribute.
#### Related Samples
-[**Hierarchical Grid Knockoutjs Integration**]({environment:SamplesUrl}/hierarchical-grid/bind-hgrid-with-ko)
+[**Hierarchical Grid Knockoutjs Integration**](\{environment:SamplesUrl\}/hierarchical-grid/bind-hgrid-with-ko)
## igListView
@@ -395,7 +395,7 @@ The `igListView` adds collapsible grouping to the default grouping functionality
#### Related Samples
-[Custom Groups]({environment:SamplesUrl}/mobile-list-view/custom-groups)
+[Custom Groups](\{environment:SamplesUrl\}/mobile-list-view/custom-groups)
## igOlapFlatDataSource
@@ -481,7 +481,7 @@ The `igSplitter` is a container control for managing layouts in HTML5 Web applic
## igTree
### Knockout Support
-The support for the Knockout library in {environment:ProductName} editor controls is
+The support for the Knockout library in \{environment:ProductName\} editor controls is
intended to provide easy means for developers to use the Knockout
library and its declarative syntax to instantiate and configure Ignite
UI editors.
@@ -532,10 +532,10 @@ The functionality is available only in the browsers which support multiple attri
[Configuring igUpload](../../02_Controls/igUpload/01_Working with igUpload/00_igUpload_Configuring_igUpload.mdx)
-## {environment:ProductNameMVC}
+## \{environment:ProductNameMVC\}
### Support for Adding Events
-You can now add events to {environment:ProductName} controls by adding them to the ASP.NET MVC helper. Use the `AddClientEvent` method to supply the event name and a handler function name. The helper will render to the appropriate instantiation JavaScript on the client to fire the event.
+You can now add events to \{environment:ProductName\} controls by adding them to the ASP.NET MVC helper. Use the `AddClientEvent` method to supply the event name and a handler function name. The helper will render to the appropriate instantiation JavaScript on the client to fire the event.
**In ASPX:**
@@ -556,16 +556,16 @@ Note: `igUpload`, `igGrid`/`igHierarchicalGrid` and their features will get this
### New Feature (CTP)
TypeScript is a language for adding a typed layer to JavaScript aiding
-in the development of JavaScript applications. {environment:ProductName} now includes a
+in the development of JavaScript applications. \{environment:ProductName\} now includes a
TypeScript definition file, `igniteui.d.ts`, providing type definitions
for all controls.
-You can find the definition file in the {environment:ProductName} installation directory under `{Installation Directory}typingsigniteui.t.ds.` Refer to the following articles for additional information.
+You can find the definition file in the \{environment:ProductName\} installation directory under `{Installation Directory}typingsigniteui.t.ds.` Refer to the following articles for additional information.
### Related Articles
- [Download TypeScript](http://www.typescriptlang.org/#Download)
-- [Introducing TypeScript Support for {environment:ProductName}](http://www.infragistics.com/community/blogs/angel_todorov/archive/2012/10/27/introducing-typescript-support-for-ignite-ui.aspx)
+- [Introducing TypeScript Support for \{environment:ProductName\}](http://www.infragistics.com/community/blogs/angel_todorov/archive/2012/10/27/introducing-typescript-support-for-ignite-ui.aspx)
- [TypeScript Tutorial](http://www.typescriptlang.org/Tutorial/)
- [TypeScript: Add Productivity and Manageability to your JavaScript Apps – Part 2](http://msdn.microsoft.com/en-us/magazine/jj983351.aspx)
@@ -579,8 +579,8 @@ Released as CTP in this version, the `igDoughnutChart` displays data similar to
#### Related Samples
-- [Bind to JSON]({environment:SamplesUrl}/doughnut-chart/bind-json)
-- [Bind to Collection]({environment:SamplesUrl}/doughnut-chart/bind-to-collection)
+- [Bind to JSON](\{environment:SamplesUrl\}/doughnut-chart/bind-json)
+- [Bind to Collection](\{environment:SamplesUrl\}/doughnut-chart/bind-to-collection)
## igLayoutManager
@@ -592,11 +592,11 @@ The `igLayoutManager` is a layout control for managing general layout in HTML We
#### Related Samples
-- [Border Layout from HTML Markup]({environment:SamplesUrl}/layout-manager/border-layout-markup)
-- [Responsive Column Layout]({environment:SamplesUrl}/layout-manager/column-layout-markup)
-- [Responsive Flow Layout]({environment:SamplesUrl}/layout-manager/flow-layout)
-- [Responsive Vertical Layout]({environment:SamplesUrl}/layout-manager/vertical-layout)
-- [Grid Layout with Column Spans and Row Spans]({environment:SamplesUrl}/layout-manager/grid-layout)
+- [Border Layout from HTML Markup](\{environment:SamplesUrl\}/layout-manager/border-layout-markup)
+- [Responsive Column Layout](\{environment:SamplesUrl\}/layout-manager/column-layout-markup)
+- [Responsive Flow Layout](\{environment:SamplesUrl\}/layout-manager/flow-layout)
+- [Responsive Vertical Layout](\{environment:SamplesUrl\}/layout-manager/vertical-layout)
+- [Grid Layout with Column Spans and Row Spans](\{environment:SamplesUrl\}/layout-manager/grid-layout)
## igTileManager
@@ -608,9 +608,9 @@ The `igTileManager` is a layout control for rendering and managing data into til
#### Related Samples
-- [Binding to JSON]({environment:SamplesUrl}/tile-manager/bind-json)
-- [ASP.NET MVC Basic Usage]({environment:SamplesUrl}/tile-manager/aspnet-mvc-helper)
-- [Item Configurations]({environment:SamplesUrl}/tile-manager/item-configurations)
+- [Binding to JSON](\{environment:SamplesUrl\}/tile-manager/bind-json)
+- [ASP.NET MVC Basic Usage](\{environment:SamplesUrl\}/tile-manager/aspnet-mvc-helper)
+- [Item Configurations](\{environment:SamplesUrl\}/tile-manager/item-configurations)
## igRadialGauge
@@ -622,8 +622,8 @@ The `igRadialGauge`, released as CTP, is a gauge control to show numerical value
#### Related Samples
-- [MVC Initialization]({environment:SamplesUrl}/radial-gauge/mvc-initialization)
-- [Gauge Animation]({environment:SamplesUrl}/radial-gauge/motion-framework)
+- [MVC Initialization](\{environment:SamplesUrl\}/radial-gauge/mvc-initialization)
+- [Gauge Animation](\{environment:SamplesUrl\}/radial-gauge/motion-framework)
##Related Content
@@ -634,7 +634,7 @@ The following topics provide additional information related to this topic.
- [Configuring Knockout Support (igCombo)](//controls/igcombo/configuring/knockoutjs-support.mdx): This topic explains how to configure the `igCombo`™ control to bind it to View-Model objects managed by the Knockout library.
-- [Configuring Knockout Support (igEditors)](../../02_Controls/igEditors/Config/02_Configuring Knockout Support (Editors).mdx): This topic explains how to configure {environment:ProductName}® editor controls to bind to View-Model objects using the Knockout library.
+- [Configuring Knockout Support (igEditors)](../../02_Controls/igEditors/Config/02_Configuring Knockout Support (Editors).mdx): This topic explains how to configure \{environment:ProductName\}® editor controls to bind to View-Model objects using the Knockout library.
- [igFunnelChart Overview](//controls/igfunnelchart/overview.mdx): This topic provides conceptual information about the `igFunnelChart`™ control including its main features, minimum requirements, and user functionality.
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/19-whats-new-in-2012-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/19-whats-new-in-2012-volume2.mdx
index 3c9d3f8089..ab9a96003d 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/19-whats-new-in-2012-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/19-whats-new-in-2012-volume2.mdx
@@ -8,7 +8,7 @@ slug: whats-new-in-2012-volume2
## New Features
### Features overview
-The following table summarizes the new features for the {environment:ProductName}™ 2012 Volume 2 release. Additional details are available after the summary table.
+The following table summarizes the new features for the \{environment:ProductName\}™ 2012 Volume 2 release. Additional details are available after the summary table.
- [igHtmlEditor control](#ightmleditor-control): The new `igHtmlEditor`™ is a jQuery WYSIWYG control and provides HTML editing capabilities in the web browser.
@@ -58,7 +58,7 @@ The following table summarizes the new features for the {environment:Produc
- [Mobile NavBar](#mobile-navbar): The NavBar ASP.NET MVC helper defines a menu of items that reference external pages or internal page blocks.
-- [Mobile Page, PageContent, PageFooter, PageHeader](#mobile-page): The {environment:ProductNameMVC} allow you to create jQuery Mobile pages using Razor or ASPX syntax.
+- [Mobile Page, PageContent, PageFooter, PageHeader](#mobile-page): The \{environment:ProductNameMVC\} allow you to create jQuery Mobile pages using Razor or ASPX syntax.
- [Mobile Popup](#mobile-popup): Popup is a widget that allows you to display HTML content in a popup window.
@@ -167,7 +167,7 @@ In the screenshot below you can see the column moving feature woring in immediat
### Related Samples:
-[Column moving (igGrid)]({environment:SamplesUrl}/grid/column-moving)
+[Column moving (igGrid)](\{environment:SamplesUrl\}/grid/column-moving)
## DataTable and DataSet binding for igGrid and igHierarchicalGrid
@@ -195,9 +195,9 @@ When `MergeUnboundColumns` =true and you haven’t set unbound values through `S
### Related Samples:
-[Unbound Columns(igGrid)]({environment:SamplesUrl}/grid/unbound-column)
+[Unbound Columns(igGrid)](\{environment:SamplesUrl\}/grid/unbound-column)
-[Unbound Columns(igHierarchicalGrid)]({environment:SamplesUrl}/hierarchical-grid/unbound-column)
+[Unbound Columns(igHierarchicalGrid)](\{environment:SamplesUrl\}/hierarchical-grid/unbound-column)
## Row Edit Template
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/20-jquery-whats-new-12-1-landing-page.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/20-jquery-whats-new-12-1-landing-page.mdx
index f23e7e7acd..57ab90110a 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/20-jquery-whats-new-12-1-landing-page.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/20-jquery-whats-new-12-1-landing-page.mdx
@@ -7,7 +7,7 @@ slug: jquery-whats-new-12-1-landing-page
## New Features
-The following table summarizes the new features of {environment:ProductName}™ 2012 Volume 1 release. Additional details are available after the summary table.
+The following table summarizes the new features of \{environment:ProductName\}™ 2012 Volume 1 release. Additional details are available after the summary table.
- [Hierarchical grid GroupBy](#hierarchical-grid-grouping): The grouping functionality available for flat grids is now fully supported for hierarchical grids.
@@ -29,25 +29,25 @@ The following table summarizes the new features of {environment:ProductName
- [Charts Motion Framework](#charts-motion-framework): The charting controls support the new Motion Framework which allows chart contents to be animated in different ways.
-- [Templating engine for jQuery controls](#templating-engine): The new `igTemplating`™ engine has been added to the {environment:ProductName} bundle. The `igTemplating` engine exposes powerful capabilities to create templates for dynamic text rendering inside jQuery controls.
+- [Templating engine for jQuery controls](#templating-engine): The new `igTemplating`™ engine has been added to the \{environment:ProductName\} bundle. The `igTemplating` engine exposes powerful capabilities to create templates for dynamic text rendering inside jQuery controls.
- [Mobile list view control](#mobile-list): The new `igListView`™ control provides list display and interaction functionality for jQuery Mobile platform.
- [Mobile rating control](#mobile-rating): The new `igRating`™ control for mobile devices has been implemented separately from the existing `igRating` control to address unique requirements of mobile and touch device environments.
-- [iOS theme for mobile controls](#mobile-ios-theme): The new iOS theme for iPhone applications has been added to the {environment:ProductName} library to provide better looks for mobile device applications.
+- [iOS theme for mobile controls](#mobile-ios-theme): The new iOS theme for iPhone applications has been added to the \{environment:ProductName\} library to provide better looks for mobile device applications.
-- [Touch support](#touch-support): All controls in the {environment:ProductName} library had been designed and tested to support touch interface for mobile devices.
+- [Touch support](#touch-support): All controls in the \{environment:ProductName\} library had been designed and tested to support touch interface for mobile devices.
- [Combo box load on demand](#combo-load-on-demand): Combo box load on demand is a new feature which improves `igCombo`™ performance by loading large sets of remote data on batches and not all at once.
- [Support for MVC validation](#mvc-validation): Support for MVC validation using data annotations has been incorporated into combo and editor controls.
-- [New jQuery themes & JavaScript resources structure](#themes-resources-structure): All JavaScript and CSS resources in the {environment:ProductName} library have been organized in a new folder structure and some of them have been renamed so that it is easier for developers using the library to figure out the purpose and location of each item. Note that this is a breaking change.
+- [New jQuery themes & JavaScript resources structure](#themes-resources-structure): All JavaScript and CSS resources in the \{environment:ProductName\} library have been organized in a new folder structure and some of them have been renamed so that it is easier for developers using the library to figure out the purpose and location of each item. Note that this is a breaking change.
- [CSS/JS resources loader](#resources-loader): The new `igLoader` control has been added to allow easier JavaScript and CSS resources loading into web pages and in relation to the new resources structure.
-- [Metro theme](#metro-theme): The new Metro theme has been added to allow better integration of {environment:ProductName} controls into the new Metro UI for upcoming versions of Microsoft® Windows®.
+- [Metro theme](#metro-theme): The new Metro theme has been added to allow better integration of \{environment:ProductName\} controls into the new Metro UI for upcoming versions of Microsoft® Windows®.
## Hierarchical grid GroupBy
@@ -103,7 +103,7 @@ The grid editing functionality has been improved to report only net transactions
## Grid Virtualization
-The virtualization technology used for better performance when displaying large data sets has been improved to support hierarchical grids and GroupBy mode for hierarchical grids. Now there are two virtualization modes: fixed and continuous. Fixed mode is the existing virtualization embedded in {environment:ProductName} controls. Continuous mode is a new development that supports hierarchical grid and the group by feature to handle situations with variable child row count.
+The virtualization technology used for better performance when displaying large data sets has been improved to support hierarchical grids and GroupBy mode for hierarchical grids. Now there are two virtualization modes: fixed and continuous. Fixed mode is the existing virtualization embedded in \{environment:ProductName\} controls. Continuous mode is a new development that supports hierarchical grid and the group by feature to handle situations with variable child row count.
### Related Topics:
@@ -144,7 +144,7 @@ On the screenshot below you can see a column chart with three data series.
## Charts Motion Framework
-The Motion Framework for charts allows developers using the {environment:ProductName} chart controls to animate the contents of a chart to increase visual appeal and imply trends or other meaning behind the data. The basic principle behind the framework is that whenever data behind the chart is updated the corresponding API method of the `igDataChart` control is called to initiate chart animation.
+The Motion Framework for charts allows developers using the \{environment:ProductName\} chart controls to animate the contents of a chart to increase visual appeal and imply trends or other meaning behind the data. The basic principle behind the framework is that whenever data behind the chart is updated the corresponding API method of the `igDataChart` control is called to initiate chart animation.
### Related Topics:
@@ -152,7 +152,7 @@ The Motion Framework for charts allows developers using the {environment:Pr
## Templating engine for jQuery controls
-The new `igTemplating` engine exposes to developers powerful capabilities to create templates for dynamic content rendering inside {environment:ProductName} controls. This engine is used throughout the {environment:ProductName} library instead of the jQuery templating plugin wherever the text in UI elements can be customized to display contents dynamically. On the screenshot below a template is applied on the first two columns of a data grid.
+The new `igTemplating` engine exposes to developers powerful capabilities to create templates for dynamic content rendering inside \{environment:ProductName\} controls. This engine is used throughout the \{environment:ProductName\} library instead of the jQuery templating plugin wherever the text in UI elements can be customized to display contents dynamically. On the screenshot below a template is applied on the first two columns of a data grid.

@@ -182,7 +182,7 @@ The new `igRating` control for mobile devices has been implemented to support mo
## iOS theme for mobile controls
-The new iOS theme for the mobile {environment:ProductName} controls has been implemented to target mobile devices. Its purpose is to provide more consistent look and better integration into iPhone and iPad mobile and touch capable applications.
+The new iOS theme for the mobile \{environment:ProductName\} controls has been implemented to target mobile devices. Its purpose is to provide more consistent look and better integration into iPhone and iPad mobile and touch capable applications.

@@ -194,7 +194,7 @@ All the Infragistics jQuery controls support touch interaction. New features and
### Related Topics:
-- [Touch Support for {environment:ProductName} Controls](//general-and-getting-started/touch-support-for-igniteui-for-jquery-controls.mdx)
+- [Touch Support for \{environment:ProductName\} Controls](//general-and-getting-started/touch-support-for-igniteui-for-jquery-controls.mdx)
## Combo box load on demand
@@ -208,7 +208,7 @@ If Load-on-Demand is enabled, the user should first be able to see a scrollbar i
## Support for MVC validation
-MVC style validation with data annotations is incorporated into combo and editor controls. That feature allows seamless integration of {environment:ProductName} validation capabilities with existing applications using data annotations.
+MVC style validation with data annotations is incorporated into combo and editor controls. That feature allows seamless integration of \{environment:ProductName\} validation capabilities with existing applications using data annotations.

@@ -218,7 +218,7 @@ MVC style validation with data annotations is incorporated into combo and editor
## New jQuery themes & JavaScript resources structure
-All JavaScript and CSS resources in the {environment:ProductName} library have been organized in a new folder structure and some of them have been renamed so that it is easier for developers using the library to figure out the purpose and location of each item. The new structure allows much faster script and resource loading by allowing applications to load only essentially required resources. Combined and minified version of the resources is still available.
+All JavaScript and CSS resources in the \{environment:ProductName\} library have been organized in a new folder structure and some of them have been renamed so that it is easier for developers using the library to figure out the purpose and location of each item. The new structure allows much faster script and resource loading by allowing applications to load only essentially required resources. Combined and minified version of the resources is still available.
Note:This is a breaking change.
@@ -226,28 +226,28 @@ Note:This is a breaking change.
### Related Topics:
-- [JavaScript Files in {environment:ProductName}](//general-and-getting-started/deployment-guide-javascript-files.mdx)
-- [Upgrading Projects to the Latest {environment:ProductName} Version](//general-and-getting-started/manually-updating-previous-versions.mdx)
+- [JavaScript Files in \{environment:ProductName\}](//general-and-getting-started/deployment-guide-javascript-files.mdx)
+- [Upgrading Projects to the Latest \{environment:ProductName\} Version](//general-and-getting-started/manually-updating-previous-versions.mdx)
## CSS/JS resources loader
-The new `igLoader` control has been added to allow easier JavaScript and CSS resources loading into web pages and in relation to the new resources structure. The control automates loading necessary resources and requires the application to specify the location of the {environment:ProductName} JavaScript and CSS files. For pure HTML/jQuery pages it is required to specify which controls and which features will be instantiated on the page, for example. “`igGrid`.*” for all features of the flat grid, or “`igDataChart.Category`” for plotting category charts only. The MVC counterpart of the loader does not require applications to specify needed resources as it automatically detects which scripts and CSS files must be loaded.
+The new `igLoader` control has been added to allow easier JavaScript and CSS resources loading into web pages and in relation to the new resources structure. The control automates loading necessary resources and requires the application to specify the location of the \{environment:ProductName\} JavaScript and CSS files. For pure HTML/jQuery pages it is required to specify which controls and which features will be instantiated on the page, for example. “`igGrid`.*” for all features of the flat grid, or “`igDataChart.Category`” for plotting category charts only. The MVC counterpart of the loader does not require applications to specify needed resources as it automatically detects which scripts and CSS files must be loaded.
The `igLoader` control is the easiest and recommended way to upgrade from previous versions and prevents the need to specify multiple JS and CSS files in the head part of web pages.
### Related Topics:
-- [Upgrading Projects to the Latest {environment:ProductName} Version](//general-and-getting-started/manually-updating-previous-versions.mdx)
+- [Upgrading Projects to the Latest \{environment:ProductName\} Version](//general-and-getting-started/manually-updating-previous-versions.mdx)
## Metro theme
-The new Metro theme is a result of research efforts to give native Metro UI look and feel to {environment:ProductName} controls for upcoming versions of Microsoft® Windows®. It aims not only styling and colors but also behavior and touch friendly user interface. On the picture below you can see a flat grid with the Metro theme applied.
+The new Metro theme is a result of research efforts to give native Metro UI look and feel to \{environment:ProductName\} controls for upcoming versions of Microsoft® Windows®. It aims not only styling and colors but also behavior and touch friendly user interface. On the picture below you can see a flat grid with the Metro theme applied.

### Related Topics:
-- [Styling and Theming in {environment:ProductName}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
+- [Styling and Theming in \{environment:ProductName\}](//general-and-getting-started/styling-and-theming/deployment-guide-styling-and-theming.mdx)
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/21-whats-new-in-2011-volume2.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/21-whats-new-in-2011-volume2.mdx
index 2b1374fbe3..ba3b70570f 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/21-whats-new-in-2011-volume2.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/21-whats-new-in-2011-volume2.mdx
@@ -6,7 +6,7 @@ slug: whats-new-in-2011-volume2
# What's New in 2011 Volume 2
## Topic Overview
-This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2011 Volume 2.
+This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2011 Volume 2.
### In this topic
This document contains the following sections:
@@ -37,7 +37,7 @@ The `igHierarchicalGrid` control is a new grid control used to render hierarchic
[Initializing the igHierarchicalGrid](//controls/ighierarchicalgrid/initializing.mdx)
### igTree™
-The {environment:ProductName} 2011 Volume 2 release now features a tree control. The `igTree` control comes equipped with a number of valuable features. The control supports load-on-demand to enable an optimized performance profile. Multiple selection scenarios are supported including bi-state and tri-state selection. The Selection feature is driven by a configurable set of selection options including checkboxes, keyboard input and individual selection. Node images are customizable and you have the option of configuring image through CSS, directly through bindings or by providing explicit URL paths to an image. The control may be created and managed through a pure JavaScript context or via the ASP.NET MVC helper.
+The \{environment:ProductName\} 2011 Volume 2 release now features a tree control. The `igTree` control comes equipped with a number of valuable features. The control supports load-on-demand to enable an optimized performance profile. Multiple selection scenarios are supported including bi-state and tri-state selection. The Selection feature is driven by a configurable set of selection options including checkboxes, keyboard input and individual selection. Node images are customizable and you have the option of configuring image through CSS, directly through bindings or by providing explicit URL paths to an image. The control may be created and managed through a pure JavaScript context or via the ASP.NET MVC helper.

@@ -45,7 +45,7 @@ The {environment:ProductName} 2011 Volume 2 release now features a tre
[Getting Started with igTree](//controls/igtree/getting-started.mdx)
### igCombo™
-The {environment:ProductName} 2011 Volume 2 release now features a combo control. The `igCombo` control comes equipped with a number of valuable features. User interface virtualization support includes the ability of the control to only create HTML elements for data items that are within the viewable area of the control. As additional data is required beyond what is visible, the control reuses existing HTML elements and keeps the scrollbar position in sync with the relative data position. The auto-complete feature allows users to begin typing in the combo box and matching selections begin to appear within the entry box to allow for easy selection. The auto-suggest feature allows users to begin typing in the entry box and the control will return a list of possible matches based on the entered text for selection. The selection features allow users to select single or multiple items via checkboxes, keyboard input or standard click-selection.
+The \{environment:ProductName\} 2011 Volume 2 release now features a combo control. The `igCombo` control comes equipped with a number of valuable features. User interface virtualization support includes the ability of the control to only create HTML elements for data items that are within the viewable area of the control. As additional data is required beyond what is visible, the control reuses existing HTML elements and keeps the scrollbar position in sync with the relative data position. The auto-complete feature allows users to begin typing in the combo box and matching selections begin to appear within the entry box to allow for easy selection. The auto-suggest feature allows users to begin typing in the entry box and the control will return a list of possible matches based on the entered text for selection. The selection features allow users to select single or multiple items via checkboxes, keyboard input or standard click-selection.

@@ -67,7 +67,7 @@ The `igGrid` Group By feature allows you to group a series of columns. The grid
[Enabling igGrid Outlook GroupBy](//controls/iggrid/features/columns/grouping/enabling-groupby.mdx)
### igGrid Column Hiding
-The {environment:ProductName} 2011 Volume 2 release now includes `igGrid` control column hiding. With this feature, you can hide columns from users before and after the grid is rendered. Further, columns can be hidden either programmatically or using UI elements in the column header. The image below depicts an `igGrid` control with a hidden column. The red arrow is pointing to the hidden column indicator:
+The \{environment:ProductName\} 2011 Volume 2 release now includes `igGrid` control column hiding. With this feature, you can hide columns from users before and after the grid is rendered. Further, columns can be hidden either programmatically or using UI elements in the column header. The image below depicts an `igGrid` control with a hidden column. The red arrow is pointing to the hidden column indicator:

@@ -75,7 +75,7 @@ The {environment:ProductName} 2011 Volume 2 release now includes `igGr
[Enabling Column Hiding](//controls/iggrid/features/columns/hiding/column-hiding-enabling-column-hiding.mdx)
### igGrid Column Resizing
-The {environment:ProductName} 2011 Volume 2 release now includes `igGrid` column resizing. The column resizing feature enables users to change the width of the columns in the grid. The effect of the resizing action can be applied to the grid either after the resize action has finished or simultaneously as it happens. The column resizing functionality has several features that are available for configuration in code including the levels at which resizing is allows– for the entire grid and for individual columns. The image below depicts a grid where the Color column is being resized by the user.
+The \{environment:ProductName\} 2011 Volume 2 release now includes `igGrid` column resizing. The column resizing feature enables users to change the width of the columns in the grid. The effect of the resizing action can be applied to the grid either after the resize action has finished or simultaneously as it happens. The column resizing functionality has several features that are available for configuration in code including the levels at which resizing is allows– for the entire grid and for individual columns. The image below depicts a grid where the Color column is being resized by the user.

@@ -83,7 +83,7 @@ The {environment:ProductName} 2011 Volume 2 release now includes `igGr
[igGrid Column Resizing](//controls/iggrid/features/columns/column-resizing.mdx)
### igGrid Row Selectors
-The {environment:ProductName} 2011 Volume 2 release now includes `igGrid` row selectors. The row selectors feature exposes options to enable checkboxes, row numbering and combine with the multiple selection feature of `igGrid` control (see the image below):
+The \{environment:ProductName\} 2011 Volume 2 release now includes `igGrid` row selectors. The row selectors feature exposes options to enable checkboxes, row numbering and combine with the multiple selection feature of `igGrid` control (see the image below):

@@ -91,7 +91,7 @@ The {environment:ProductName} 2011 Volume 2 release now includes `igGr
[Enabling Row Selectors](../../02_Controls/igGrid/03_Features/02_Row Selectors/00_igGrid_Enabling_Row_Selectors.mdx)
### igGrid Tooltips
-The {environment:ProductName} 2011 Volume 2 release now includes `igGrid` tooltips. This feature enables tooltips to appear over grid cells. The purpose of the tooltips is to make the whole cell content visible and enable users to select and copy the text that is inside the tooltip container.
+The \{environment:ProductName\} 2011 Volume 2 release now includes `igGrid` tooltips. This feature enables tooltips to appear over grid cells. The purpose of the tooltips is to make the whole cell content visible and enable users to select and copy the text that is inside the tooltip container.

@@ -99,7 +99,7 @@ The {environment:ProductName} 2011 Volume 2 release now includes `igGr
[Enabling igGrid Tooltips](//controls/iggrid/features/tooltips/enabling-tooltips.mdx)
### igGrid Column Summaries
-The {environment:ProductName} 2011 Volume 2 release now includes `igGrid` column summaries. The column summaries feature exposes the option to calculate summaries based on column data. The grid includes a number of default summary functions, as well as giving you the ability to define custom functions to calculate the summaries. Further, options exist which allow you to choose whether summaries are calculated remotely or local. The following image depicts a grid with summaries enabled.
+The \{environment:ProductName\} 2011 Volume 2 release now includes `igGrid` column summaries. The column summaries feature exposes the option to calculate summaries based on column data. The grid includes a number of default summary functions, as well as giving you the ability to define custom functions to calculate the summaries. Further, options exist which allow you to choose whether summaries are calculated remotely or local. The following image depicts a grid with summaries enabled.

@@ -107,7 +107,7 @@ The {environment:ProductName} 2011 Volume 2 release now includes `igGr
[Enabling Column Summaries](../../02_Controls/igGrid/03_Features/00_Columns/05_Summaries/00_igGrid_Enabling _Column_Summaries.mdx)
### igGrid Model Metadata enhancement
-The {environment:ProductName} 2011 Volume 2 release now includes the ability of the `igGrid` MVC helper to recognize the `DisplayName` attribute. Use of the `DisplayName` attribute allows the MVC helper to automatically use this attribute as `headerText` for a specified column. Keep in mind that if `headerText` is set explicitly in the grid, the value from the `DisplayName` is overwritten. The following example shows simple model and `igGrid` which automatically binds the `headerText` to the `DisplayName` attribute value.
+The \{environment:ProductName\} 2011 Volume 2 release now includes the ability of the `igGrid` MVC helper to recognize the `DisplayName` attribute. Use of the `DisplayName` attribute allows the MVC helper to automatically use this attribute as `headerText` for a specified column. Keep in mind that if `headerText` is set explicitly in the grid, the value from the `DisplayName` is overwritten. The following example shows simple model and `igGrid` which automatically binds the `headerText` to the `DisplayName` attribute value.
diff --git a/docs/jquery/src/content/en/topics/whats-new/revision-history/jquery-whats-new-revision-history.mdx b/docs/jquery/src/content/en/topics/whats-new/revision-history/jquery-whats-new-revision-history.mdx
index 9aa1435b2c..fd277bea46 100644
--- a/docs/jquery/src/content/en/topics/whats-new/revision-history/jquery-whats-new-revision-history.mdx
+++ b/docs/jquery/src/content/en/topics/whats-new/revision-history/jquery-whats-new-revision-history.mdx
@@ -7,55 +7,55 @@ slug: jquery-whats-new-revision-history
### Introduction
-The topics referred below provide information about what new controls and features are introduced in earlier versions of the {environment:ProductName}™ library of controls.
+The topics referred below provide information about what new controls and features are introduced in earlier versions of the \{environment:ProductName\}™ library of controls.
### Topics
Detailed information regarding what new controls and features are introduced is covered in the following topics:
-- [What's New in 2023 Volume 2](/whats-new-in-2023-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2023 Volume 2.
+- [What's New in 2023 Volume 2](/whats-new-in-2023-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2023 Volume 2.
-- [What's New in 2022 Volume 2](/whats-new-in-2022-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2022 Volume 2.
+- [What's New in 2022 Volume 2](/whats-new-in-2022-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2022 Volume 2.
-- [What's New in 2022 Volume 1](/whats-new-in-2022-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2022 Volume 1.
+- [What's New in 2022 Volume 1](/whats-new-in-2022-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2022 Volume 1.
-- [What's New in 2021 Volume 2](/whats-new-in-2021-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2021 Volume 2.
+- [What's New in 2021 Volume 2](/whats-new-in-2021-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2021 Volume 2.
-- [What's New in 2021 Volume 1](/whats-new-in-2021-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2021 Volume 1.
+- [What's New in 2021 Volume 1](/whats-new-in-2021-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2021 Volume 1.
-- [What's New in 2020 Volume 2](/whats-new-in-2020-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2020 Volume 2.
+- [What's New in 2020 Volume 2](/whats-new-in-2020-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2020 Volume 2.
-- [What's New in 2019 Volume 2](/whats-new-in-2019-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2019 Volume 2.
+- [What's New in 2019 Volume 2](/whats-new-in-2019-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2019 Volume 2.
-- [What's New in 2018 Volume 2](/whats-new-in-2018-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2018 Volume 2.
+- [What's New in 2018 Volume 2](/whats-new-in-2018-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2018 Volume 2.
-- [What's New in 2018 Volume 1](/whats-new-in-2018-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2018 Volume 1.
+- [What's New in 2018 Volume 1](/whats-new-in-2018-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2018 Volume 1.
-- [What's New in 2017 Volume 2](/whats-new-in-2017-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2017 Volume 2.
+- [What's New in 2017 Volume 2](/whats-new-in-2017-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2017 Volume 2.
-- [What's New in 2017 Volume 1](/whats-new-in-2017-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2017 Volume 1.
+- [What's New in 2017 Volume 1](/whats-new-in-2017-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2017 Volume 1.
-- [What's New in 2016 Volume 2](/whats-new-in-2016-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2016 Volume 2.
+- [What's New in 2016 Volume 2](/whats-new-in-2016-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2016 Volume 2.
-- [What's New in 2016 Volume 1](/whats-new-in-2016-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2016 Volume 1.
+- [What's New in 2016 Volume 1](/whats-new-in-2016-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2016 Volume 1.
-- [What's New in 2015 Volume 2](/whats-new-in-2015-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2015 Volume 2.
+- [What's New in 2015 Volume 2](/whats-new-in-2015-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2015 Volume 2.
-- [What's New in 2015 Volume 1](/whats-new-in-2015-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2015 Volume 1.
+- [What's New in 2015 Volume 1](/whats-new-in-2015-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2015 Volume 1.
-- [What's New in 2014 Volume 2](/whats-new-in-2014-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2014 Volume 2.
+- [What's New in 2014 Volume 2](/whats-new-in-2014-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2014 Volume 2.
-- [What's New in 2014 Volume 1](/whats-new-in-2014-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2014 Volume 1.
+- [What's New in 2014 Volume 1](/whats-new-in-2014-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2014 Volume 1.
-- [What’s New in 2013 Volume 2](/whats-new-in-2013-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2013 Volume 2.
+- [What’s New in 2013 Volume 2](/whats-new-in-2013-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2013 Volume 2.
-- [What’s New in 2013 Volume 1](/whats-new-in-2013-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2013 Volume 1.
+- [What’s New in 2013 Volume 1](/whats-new-in-2013-volume1.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2013 Volume 1.
-- [What’s New in 2012 Volume 2](/whats-new-in-2012-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2012 Volume 2.
+- [What’s New in 2012 Volume 2](/whats-new-in-2012-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2012 Volume 2.
-- [What’s New in 2012 Volume 1](/jquery-whats-new-12-1-landing-page.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2012 Volume 1.
+- [What’s New in 2012 Volume 1](/jquery-whats-new-12-1-landing-page.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2012 Volume 1.
-- [What's New in 2011 Volume 2](/whats-new-in-2011-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the {environment:ProductName}™ 2011 Volume 2.
+- [What's New in 2011 Volume 2](/whats-new-in-2011-volume2.mdx): This topic provides an overview of the new functionalities and components introduced with the \{environment:ProductName\}™ 2011 Volume 2.
diff --git a/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-directives.mdx b/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-directives.mdx
index 762fa4d8b4..ce4be09e99 100644
--- a/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-directives.mdx
+++ b/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-directives.mdx
@@ -4,14 +4,15 @@ slug: angularjs-directives
---
# AngularJS ディレクティブ
+
## このグループのトピックについて
### 概要
-AngularJS アプリケーションで {environment:ProductName}® コントロールを使用する場合に、AngularJS 用の {environment:ProductName}® ディレクティブによりデータ バインディングとビューの宣言型プログラミングを利用できます。最新のソースとサンプルは、[{environment:ProductName} の GitHub リポジトリ](https://github.com/IgniteUI/igniteui-angularjs)から入手できます。
+AngularJS アプリケーションで \{environment:ProductName\}® コントロールを使用する場合に、AngularJS 用の \{environment:ProductName\}® ディレクティブによりデータ バインディングとビューの宣言型プログラミングを利用できます。最新のソースとサンプルは、[\{environment:ProductName\} の GitHub リポジトリ](https://github.com/IgniteUI/igniteui-angularjs)から入手できます。
### トピック
-- [AngularJS での {environment:ProductName} の使用](/using-ignite-ui-with-angularjs) - このトピックでは、AngularJS の {environment:ProductName} ディレクティブの使用方法の概要を説明します。
-- [AngularJS を使用した条件付きテンプレート化および高度なテンプレート化](/conditional-and-advanced-templating-with-angularjs) - このトピックでは、条件付きテンプレートの使用方法と、AngularJS の {environment:ProductName} ディレクティブを使用して作成されたコントロールをカイタマイズするための高度なテンプレート化の方法について説明します。
-- [AngularJS サンプル](/angularjs-samples) - このトピックは、AngularJS の {environment:ProductName} ディレクティブを使用するサンプルを含みます。
\ No newline at end of file
+- [AngularJS での \{environment:ProductName\} の使用](/using-ignite-ui-with-angularjs) - このトピックでは、AngularJS の \{environment:ProductName\} ディレクティブの使用方法の概要を説明します。
+- [AngularJS を使用した条件付きテンプレート化および高度なテンプレート化](/conditional-and-advanced-templating-with-angularjs) - このトピックでは、条件付きテンプレートの使用方法と、AngularJS の \{environment:ProductName\} ディレクティブを使用して作成されたコントロールをカイタマイズするための高度なテンプレート化の方法について説明します。
+- [AngularJS サンプル](/angularjs-samples) - このトピックは、AngularJS の \{environment:ProductName\} ディレクティブを使用するサンプルを含みます。
\ No newline at end of file
diff --git a/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-samples.mdx b/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-samples.mdx
index 4df3b411b9..c402eab3ac 100644
--- a/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-samples.mdx
+++ b/docs/jquery/src/content/ja/topics/angularjs-directives/angularjs-samples.mdx
@@ -6,7 +6,7 @@ slug: angularjs-samples
# AngularJS サンプル
## トピックの概要
-このトピックは、AngularJS の {environment:ProductFamilyName} ディレクティブのサンプルについて説明します。
+このトピックは、AngularJS の \{environment:ProductFamilyName\} ディレクティブのサンプルについて説明します。
### このトピックの内容
@@ -40,8 +40,8 @@ slug: angularjs-samples
### 要件
このサンプルを実行するために以下が必要です。
-- 必要となる {environment:ProductName} の JavaScript と CSS ファイル
-- {environment:ProductFamilyName} AngularJS ディレクティブ
+- 必要となる \{environment:ProductName\} の JavaScript と CSS ファイル
+- \{environment:ProductFamilyName\} AngularJS ディレクティブ
### グリッド サンプル
このサンプルは、`igGrid` を AngularJS で使用する方法を示します。
@@ -50,7 +50,7 @@ slug: angularjs-samples
以下は最終結果のプレビューです。
")`
+> **注:** \{environment:ProductNameMVC\} を使用して HTML DIV プレースホルダー コードを定義したい場合は、ダイアログ ヘルパーで示される次のメソッドを使用することができます。DIV HTML プレースホルダーの定義と同じ効果を実現したい場合は、次のメソッドを使用してください。 `Dialog.ContentHTML("
]*)>(?!<\/a>)/gm, '$1');
- body = body.replace(/^(#{1,6}[ \t]+)<\/a>/gm, '$1');
-
- // Fix self-closing pairs →
- body = body.replace(/]*)\/>([ \t]*)<\/a>/g, '$2');
-
- // Dedent code fence markers (MDX does not support indented code fences)
- body = body.replace(/^[ \t]+(```)/gm, '$1');
-
- // Fix (non-self-closed) using fence-only split (avoids backtick-in-URL issue)
- {
- const fenceParts = body.split(/(```[\s\S]*?```)/g);
- body = fenceParts.map((part: string, i: number) => i % 2 === 1 ? part : part.replace(/ /gi, ' ')).join('');
- }
-
- // Fix unclosed backtick code spans that had } escaped by a previous run
- body = body.replace(/`}\);(?!`)/g, '`});`');
-
- // Fix unquoted attribute: id=value"" → id="value"
- body = body.replace(/\b(id|class|name|href)=([^"'\s>{/][^\s>"]*)"">/g, '$1="$2">');
-
- // Escape pseudo-tags (slash in tag name)
- body = body.replace(/<([a-zA-Z][a-zA-Z0-9._-]*\/[a-zA-Z][a-zA-Z0-9._-]*)>/g,
- (_: string, tag: string) => `<${tag}>`);
-
- // Escape HTML block-level tags inside markdown link text
- body = body.replace(/\[([^\]\n]*?)<(div|section|article|aside|ul|ol|li|p|nav|main|header|footer)\b([^>]*?)>([^\]\n]*?)\]/g,
- (_: string, before: string, tag: string, attrs: string, after: string) => `[${before}<${tag}${attrs}>${after}]`);
-
- // Escape block-level HTML tags used as inline descriptive text (surrounded by spaces)
- body = body.replace(/([ \t])<(div|section|article|aside|p|nav|main|header|footer)\b([^>]*?)>([ \t])/g,
- (_: string, before: string, tag: string, attrs: string, after: string) => `${before}<${tag}${attrs}>${after}`);
-
- // Remove stray immediately after
- body = body.replace(/<\/a><\/span>/g, '');
-
- // Remove stray /
/
from markdown pipe table rows
- body = body.replace(/^([^<\n]*\|[^\n]*?)<\/(?:td|th|tr)>([ \t]*)$/gm, '$1$2');
-
- // Remove stray at end of blockquote lines without matching
- body = body.replace(/^(>[ \t]+(?:(?!
([ \t]*)$/gm, '$1$2');
-
- // Remove stray
that appear at the very start of a pipe table cell (after |).
- body = body.replace(/(\|[ \t]*)<\/li>/g, '$1');
-
- // Remove stray > right after at end of line
- body = body.replace(/(<\/(?:td|th)>)([ \t]*)>[ \t]*$/gm, '$1$2');
-
- // Remove orphaned tags inside markdown table cells: closing tags that
- // appear before any opening
in the same cell. These are artifacts from
- // table conversion where list items span cell boundaries.
- // Only applies to markdown table rows (lines containing | separators).
- body = body.split('\n').map(line => {
- // Only process markdown table rows (contain | but are not separator rows)
- if (!line.includes('|') || /^\s*\|?\s*[-:]+\s*(\|\s*[-:]+\s*)*\|?\s*$/.test(line)) return line;
-
- // Process each cell: remove
before the first
in each cell.
- return line.split('|').map(cell => {
- const firstLi = cell.indexOf('
in this cell — remove all
- return cell.replace(/<\/li>/g, '');
- }
- // Remove only before the first
\n${indent}${closeTag}>`
- );
-
- // Repair cells broken by prior runs (nested tables cut at first inner ).
- body = repairBrokenOuterCells(body);
-
- // Fix multiline
/
and unmatched * in all table cells.
- // Must run before prose splitting so the full open+close tag pair is visible.
- body = fixTableCells(body);
-
- // Remove blank lines that break MDX's inline HTML block parsing.
- // MDX ends an inline HTML block at a blank line, causing errors.
- // 3a: blank line immediately after table/row opening tag
- body = body.replace(/(<(?:table|thead|tbody|tfoot|tr)\b[^>]*>)\r?\n[ \t]*\r?\n/g, '$1\n');
- // 3b: blank lines between or
and the next
/
//
- body = body.replace(/(<\/(?:td|th)>[ \t]*)\r?\n(?:[ \t]*\r?\n)+([ \t]*<(?:\/tr|td|th|tr)\b)/g, '$1\n$2');
-
- // MDX/JSX chokes when
follows or on the same line because
- // it conflicts with the paragraph flow context inside the cell. Put
- // on its own line to prevent "Expected the closing tag …" errors.
- body = body.replace(/<\/(td|th)>(\s*)<\/tr>/g, '$1>\n');
-
- // Escape HTML tags inside markdown table cells that cause MDX/JSX parse errors.
- // Safe inline tags (br, code, em, strong, b, i, a, span, sub, sup) are kept.
- // Block/complex tags (div, ul, ol, li, p, table, etc.) are escaped to <...>.
- body = escapeHtmlInMarkdownTableCells(body);
-
- // Fix prose sections: pseudo-HTML escaping, void element self-closing,
- // curly brace escaping. Skip code spans/fences.
- const parts = body.split(/(```[\s\S]*?```|`[^`\n]+`)/g);
- body = parts.map((part, i) => (i % 2 === 1 ? part : fixProseChunk(part))).join('');
-
- // Escape orphaned table-element tags that appear outside
blocks.
- // After fixTableCells and table-to-markdown conversion, some closing tags
- // (e.g. , , ,
) may be left without matching
- // opening tags, causing MDX JSX parse errors.
- body = escapeOrphanedTableTags(body);
-
- // Return null only if absolutely nothing changed.
- if (body === source) return null;
- return body;
-}
-
-// ---------------------------------------------------------------------------
-// Directory walker
-// ---------------------------------------------------------------------------
-
-export interface NormalizeMdxDirResult {
- processed: number;
- skipped: number;
- errors: number;
-}
-
-/**
- * Normalize all `.mdx` and `.md` files under `dir`, in place.
- *
- * @param dir Absolute path to the topics directory to process.
- * @param verbose When true, logs each file action to stdout.
- */
-export function normalizeMdxDir(
- dir: string,
- { verbose = false }: { verbose?: boolean } = {},
-): NormalizeMdxDirResult {
- if (!fs.existsSync(dir)) {
- console.warn(`[normalize-mdx] Directory not found, skipping: ${dir}`);
- return { processed: 0, skipped: 0, errors: 0 };
- }
-
- let processed = 0;
- let skipped = 0;
- let errors = 0;
-
- function walk(current: string): void {
- for (const entry of fs.readdirSync(current, { withFileTypes: true })) {
- const full = path.join(current, entry.name);
- if (entry.isDirectory()) { walk(full); continue; }
- if (!entry.name.endsWith('.mdx') && !entry.name.endsWith('.md')) continue;
-
- try {
- const raw = fs.readFileSync(full, 'utf8');
- // Strip UTF-8 BOM (\uFEFF) if present.
- const source = raw.charCodeAt(0) === 0xFEFF ? raw.slice(1) : raw;
-
- const updated = normalizeMdxContent(source);
- if (updated === null) {
- skipped++;
- if (verbose) console.log(` [SKIP] ${path.relative(dir, full)}`);
- } else {
- fs.writeFileSync(full, updated, 'utf8');
- processed++;
- if (verbose) console.log(` [OK] ${path.relative(dir, full)}`);
- }
- } catch (err) {
- errors++;
- console.error(
- ` [ERR] ${path.relative(dir, full)}: ${(err as Error).message}`,
- );
- }
- }
- }
-
- walk(dir);
-
- return { processed, skipped, errors };
-}
diff --git a/src/plugins/remark-docfx.ts b/src/plugins/remark-docfx.ts
index c391de14a8..090e359a93 100644
--- a/src/plugins/remark-docfx.ts
+++ b/src/plugins/remark-docfx.ts
@@ -63,7 +63,7 @@ function loadEnv(): Record {
return _ENV as Record;
}
-const ENV_PATTERN = /(?:\{|{)environment:(\w+)(?:\}|})/g;
+const ENV_PATTERN = /(?:\\\{|\{|{)environment:(\w+)(?:\\\}|\}|})/g;
// ---------------------------------------------------------------------------
// Slug resolution map — lazily built once per DOCS_SOURCE_PATH.
@@ -386,6 +386,35 @@ export function remarkDocfx() {
const docsDir = process.env.DOCS_SOURCE_PATH
? path.resolve(process.env.DOCS_SOURCE_PATH)
: (filePath ? path.dirname(filePath) : '');
+
+ // 0. Pre-pass: stitch back env tokens that remark-directive (enabled by
+ // Starlight) has split into text("…{environment") + textDirective(name)
+ // + text("}…"). Without this our env-token regex never sees the token.
+ // eslint-disable-next-line @typescript-eslint/no-explicit-any
+ visit(tree, (parent: any) => {
+ if (!parent || !Array.isArray(parent.children)) return;
+ const children = parent.children;
+ for (let i = 0; i < children.length - 2; i++) {
+ const a = children[i];
+ const b = children[i + 1];
+ const c = children[i + 2];
+ if (
+ a && a.type === 'text' && typeof a.value === 'string' &&
+ b && b.type === 'textDirective' && typeof b.name === 'string' &&
+ c && c.type === 'text' && typeof c.value === 'string'
+ ) {
+ const aMatch = /(.*)(\\?\{|{)environment$/s.exec(a.value);
+ const cMatch = /^(\\?\}|})(.*)/s.exec(c.value);
+ if (aMatch && cMatch) {
+ const merged = `${aMatch[1]}{environment:${b.name}}${cMatch[2]}`;
+ children.splice(i, 3, { type: 'text', value: merged });
+ // re-check this index since we replaced 3 with 1
+ i--;
+ }
+ }
+ }
+ });
+
// 1. Walk the AST and replace environment variables in text/links/html
// eslint-disable-next-line @typescript-eslint/no-explicit-any
visit(tree, (node: any) => {
@@ -430,6 +459,31 @@ export function remarkDocfx() {
node.value = transformDividers(node.value as string);
node.value = (node.value as string).replace(/src="(\.\.\/)+images\//g, 'src="/images/');
}
+
+ // MDX JSX elements (e.g.