W-21369029 remove snippets

modules/ROOT/nav.adoc

@@ -80,7 +80,6 @@
 * xref:int-developing-integrations.adoc[]
 ** xref:int-create-integrations.adoc[]
 ** xref:int-configure-components.adoc[]
-*** xref:int-work-with-code-snippets.adoc[]
 *** xref:int-configure-components-add.adoc[]
 *** xref:int-configure-dw-expressions.adoc[]
 *** xref:int-configure-components-check-connection.adoc[]

modules/ROOT/pages/_partials/acb-component-info.adoc

@@ -52,7 +52,7 @@ For reference documentation on specific connector and component configurations,
 
 //
 // tag::note-component-add-config[]
-When adding components, you can start from xref:int-work-with-code-snippets.adoc[code snippets], the canvas, or the configuration XML for your app.
+When adding components, you can start from the canvas or the configuration XML for your app.
 You can configure components from their configuration panels in the canvas or from the XML.
 // end::note-component-add-config[]
 //
@@ -234,21 +234,11 @@ The configuration XML file now includes the XML for the HTTP Listener within the
 
 </flow>
 ----
-. Add another component, this time using the XML configuration menu.
+. Add another component, this time using the configuration XML.
 +
-For example, add the `<http:listener-config/>` component from a snippet.
+In the configuration XML, place your cursor before the opening `<flow>` tag. Ensure that the cursor is not inside the `<flow/>` element. Add the following code:
 +
-For more information about snippets, see xref:anypoint-code-builder::int-work-with-code-snippets.adoc[].
-+
-.. In the configuration XML, place your cursor before the opening `<flow>` tag, and type `http`.
-+
-Ensure that the cursor is not inside the `<flow/>` element.
-+
-.. Type `http`, and select the `http:listener-config` snippet:
-+
-image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config snippet highlighted in the configuration XML menu"]
-+
-The snippet adds the following code:
+// image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config highlighted in the configuration XML menu"]
 +
 [source,xml]
 ----

modules/ROOT/pages/af-project-files.adoc

@@ -1145,7 +1145,7 @@ The `ref` element is used in different elements in the agent network YAML, and i
 
 The `ref` element represents another asset that exists in Exchange. The type of asset referenced depends on the context (such as agent, MCP server, LLM provider). The semantic is always that of referencing an asset that exists in Exchange, or will exist when the agent network is published (meaning, it's defined in the file). If referenced, it's in the `dependencies` section of `exchange.json`.
 
-This snippet represents a link to an HR agent. The `name` attribute doesn't point to the agent's human friendly or logical name (which can change); instead, it references the `assetId` that `hr-agent` has in Exchange.
+This example represents a link to an HR agent. The `name` attribute doesn't point to the agent's human friendly or logical name (which can change); instead, it references the `assetId` that `hr-agent` has in Exchange.
 
 [source,yaml]
 ----

modules/ROOT/pages/index.adoc

@@ -83,13 +83,6 @@ A flow reference enables you to trigger execution of a flow or subflow from anot
 [[business-groups]]
 * Business groups organize APIs, Mule applications, and other resources within an Anypoint Platform organization. Organization administrators create and control access to business groups. For details about business groups, organizations, and related management features, see xref:access-management::business-groups.adoc[].
 
-[[snippets]]
-== Code Snippets
-
-Snippets are code patterns that you can insert from the IDE into the configuration XML files of your Mule applications. Using code snippets for reusable code patterns helps you work more efficiently and reduces the potential for configuration errors. 
-
-The IDE provides built-in snippets, and you can create your own user snippets. To use and create code snippets, see xref:int-work-with-code-snippets.adoc[].
-
 == Anypoint Platform Product Integrations
 
 //relationships to our other products

modules/ROOT/pages/int-ai-gen-flow-examples.adoc

@@ -71,7 +71,7 @@ After reviewing and inserting the generated flow into your project:
 ----
 +
 This example flow is configured to poll for new cases every 5000 milliseconds.
-. Use built-in snippets to add configurations for your Salesforce instance and email inbox.
+. Add the required configurations for your Salesforce instance and email inbox in your configuration XML.
 
 The following is an example of the completed flow:
 
@@ -165,7 +165,7 @@ The `type` attribute is set to `Account` to specify the object type to update.
 
 === Complete the Flow 
 
-To run this flow, use built-in snippets to add configurations for your Salesforce instance. For more information about built-in snippets, see xref:int-work-with-code-snippets.adoc[].
+To run this flow, add the required configurations for your Salesforce instance in your configuration XML.
 
 The following is an example of the completed flow:
 
@@ -265,7 +265,7 @@ output application/java
 After reviewing and inserting the generated flow into your project:
 
 . Update the name of the database table and fields to match what is configured in your MySQL database. 
-. To run this flow, use built-in snippets to add configurations for your Salesforce instance.
+. To run this flow, add the required configurations for your Salesforce instance in your configuration XML.
 
 The following is an example of a completed flow:
 
@@ -372,7 +372,7 @@ After reviewing and inserting the generated flow into your project:
 . Update the `watermarkColumn` in the Database *Listener* to whichever database column is used to indicate new records. 
 +
 The values that are taken from this column are used to filter the contents of the next poll, so that only rows with a greater watermark value are processed.
-. To run this flow, use built-in snippets to add configurations for your database and email inbox.
+. To run this flow, add the required configurations for your database and email inbox in your configuration XML.
 
 The following is an example of the completed flow:
 
@@ -430,7 +430,6 @@ The following is an example of the completed flow:
 
 == See Also
 
-* xref:int-work-with-code-snippets.adoc[]
 * xref:vibes-create-integrations.adoc[]
 * xref:acb-reference.adoc[]
 * xref:acb-component-scheduler.adoc[]

modules/ROOT/pages/int-configure-components.adoc

@@ -1,5 +1,6 @@
 = Configuring Components
 :page-deployment-options: cloud-ide, desktop-ide
+:page-aliases: int-work-with-code-snippets.adoc, work-with-code-snippets.adoc, create-xml-snippets.adoc
 :open-config-xml: In the Explorer, open the configuration XML file for your project:
 
 include::reuse::partial$beta-banner.adoc[tag="anypoint-code-builder"] 
@@ -8,7 +9,6 @@ Configure connectors and processors within your implementation and integration p
 
 Common tasks include the following: 
 
-* xref:int-work-with-code-snippets.adoc[Work with Code Snippets]
 * <<add-components>>
 * xref:int-configure-dw-expressions.adoc[Configure Expressions]
 * <<check-connection>>
@@ -17,7 +17,7 @@ Common tasks include the following:
 
 == Before You Begin
 
-* Determine which connectors, processors, and snippets you intend to use.
+* Determine which connectors and processors you intend to use.
 +
 // Note on ways to start component configs: 
 include::partial$acb-component-info.adoc[tags="note-component-add-config"]

modules/ROOT/pages/int-create-integrations.adoc

@@ -132,5 +132,4 @@ The file's canvas provides the same options for building your project file that
 
 * xref:start-workspaces.adoc[]
 * xref:acb-reference.adoc[]
-* xref:int-work-with-code-snippets.adoc[]
 * xref:debugging-mule-apps.adoc[]

modules/ROOT/pages/int-create-secure-configs.adoc

@@ -391,11 +391,9 @@ The POM file includes dependencies for the components in the configuration XML.
 
 To use an encrypted value in a Mule application: 
 
-. Before the `<flow/>` element in the configuration XML, add the Secure Configuration Properties _snippet_ (`<secure-properties:config/>`) by pressing Cmd+Space (Mac) or Ctrl+Space (Windows), typing the initial letters of the element name, such as `secu`, and then selecting the snippet:
+. Before the `<flow/>` element in the configuration XML, add the following Secure Configuration Properties configuration (`<secure-properties:config/>`):
 +
-image::acb-snippet-secure-config-prop.png["Selecting Secure Configuration Properties Snippet"]
-+
-The XML for an unmodified snippet looks like this before a `<flow/>` element:
+// image::acb-snippet-secure-config-prop.png["Selecting Secure Configuration Properties"]
 +
 [source,xml]
 ----
@@ -409,12 +407,10 @@ The XML for an unmodified snippet looks like this before a `<flow/>` element:
 ...
 ----
 +
-The snippet preconfigures parts of the element that the basic XML configuration does not, so be sure to select the _snippet_ and _not_ the basic XML for this element, which has the same name but a different icon. Like all snippets, this snippet is identified by a two-dimensional box icon, while the basic XML for this element has a three-dimensional box icon. 
-+
-When you _first_ add the `<secure-properties:config/>` snippet to the configuration XML, you can tab to the `algorithm` attribute to select another algorithm, or you can change the value manually:
+. Optionally change the `algorithm` attribute to select another algorithm:
 +
 image::int-secure-config-algorithms.png["List of supported algorithms in Secure Configuration Properties module."]
-. Configure the snippet with values for the `file`, `key`, and `algorithm` attributes, for example:
+. Configure the element with values for the `file`, `key`, and `algorithm` attributes, for example:
 +
 [source,xml]
 ----
@@ -431,7 +427,7 @@ If you want to use the variable `$\{env}` in your filename configuration, see <<
 * `name`: A name of your choice for the encryption key (defaults to `${encryption.key}`) 
 +
 This name serves as the key for the encryption value (password) used to encrypt your secure properties with the Secure Properties Tool.
-* `algorithm`: Algorithm you used to encrypt your secure properties (defaults to Blowfish in the snippet). Other <<algorithms, algorithms>> are available.
+* `algorithm`: Algorithm you used to encrypt your secure properties (defaults to Blowfish in the previous example). Other <<algorithms, algorithms>> are available.
 . In the connector or component XML, add the key of an encrypted property as the value of an XML attribute, for example:
 +
 [source,xml]
@@ -510,7 +506,7 @@ Before you begin:
 
 To hide sensitive values from the Runtime Manager UI when you deploy to CloudHub or CloudHub 2.0: 
 
-. In the `mule-artifact.json` file for your application, provide the _name_ of the encryption key (`encryption.key` by default) that you provided in the global `<secure-properties:config/>` snippet within your configuration XML, for example:
+. In the `mule-artifact.json` file for your application, provide the _name_ of the encryption key (`encryption.key` by default) that you provided in the global `<secure-properties:config/>` element within your configuration XML, for example:
 +
 ----
 {

modules/ROOT/pages/int-developing-integrations.adoc

@@ -22,7 +22,6 @@ Some common use cases are:
 After you xref:int-create-integrations.adoc[create your integration project],
 you can optionally:
 
-* xref:int-work-with-code-snippets.adoc[Work with code snippets].
 * xref:int-create-secure-configs.adoc[Define and secure properties for your Mule application].
 * xref:int-trigger-flows.adoc[Trigger flows in your development environment].
 * xref:int-use-dw-to-transform-data.adoc[Use the DataWeave language].