Skip to content

Commit a101b9e

Browse files
committed
DOC-3329: Copy edits, links and minor changes.
1 parent 42ce924 commit a101b9e

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

modules/ROOT/pages/creating-an-icon-pack.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,18 @@
88

99
This guide provides comprehensive coverage of creating, building, and deploying custom icon packs, including solutions to common issues. It details two approaches:
1010

11-
* The inline approach, for adding a small number of custom icons
12-
* The icon file approach, using the Icon Pack Template project to easily generate the required output file from a folder of SVGs.
11+
* The manual approach, for adding a small number of custom icons
12+
* Using the xref:using-the-icon-pack-template.adoc[Icon Pack Template tool] to easily generate the required output file from a folder of SVGs.
1313

1414
== How Icons Work in {productname}
1515

16-
A {productname} icon pack is a JavaScript construct containing strings of link:https://developer.mozilla.org/en-US/docs/Web/SVG[SVG's]. Icon packs are often kept in separate files, but can be inlined if needed. An icon pack can be used to add one or more custom icons or to replace some or all of the default {productname} icons.
16+
A {productname} icon pack is a JavaScript construct containing strings of link:https://developer.mozilla.org/en-US/docs/Web/SVG[SVGs]. Icon packs are often kept in separate files, but can be inlined if needed. An icon pack can be used to add one or more custom icons or to replace some or all of the default {productname} icons.
1717

1818
An icon pack only **requires** the custom icons to be included; the default {productname} icons are used as a fallback for icons missing from the custom icon pack.
1919

2020
== Registering an icon pack
2121

22-
Icon packs are registered with {productname} using the IconManager. Whether creating the icon pack manually or using the Icon Pack Template tool, the JavaScript required to setup an icon pack looks like:
22+
Icon packs are registered with {productname} using the IconManager. Whether creating the icon pack manually or using the xref:using-the-icon-pack-template.adoc[Icon Pack Template tool], the JavaScript required to setup an icon pack looks like:
2323

2424
[source,javascript]
2525
----
@@ -35,7 +35,7 @@ tinymce.IconManager.add('custom-pack-name', {
3535

3636
== Creating an icon pack manually
3737

38-
When adding only a few icons, it may be easier to manually configure the new icon pack than to use the Icon Pack Template tool. To do this:
38+
When adding only a few icons, it may be easier to manually configure the new icon pack than to use the xref:using-the-icon-pack-template.adoc[Icon Pack Template tool]. To do this:
3939

4040
. Gather the SVG files for the new icons. Extract their content string, e.g. `+<svg width="24" height="24">...</svg>+`
4141
. Call `+tinymce.IconManager.add()+`
@@ -49,7 +49,7 @@ The new icons can then be used by name within {productname}.
4949
*Icon Override:* If custom icons have the same name as a default {productname} icon, they will override the default icon.
5050
====
5151

52-
This JavaScript can be included as a separate icon file or inlined beside the application's `+tinymce.init()+` call. Configure {productname} to load the icon pack and possibly where from.
52+
This JavaScript can be included as a separate icon file or inlined beside the application's `+tinymce.init()+` call. Configure {productname} to load the icon pack and, if necessary, where from using the xref:editor-icons.adoc#icons[`+icons+`] and xref:editor-icons.adoc#icons_url[`+icons_url+`] options.
5353

5454
[NOTE]
5555
====

0 commit comments

Comments
 (0)