@salesforce/plugin-templates 56.5.2 → 56.7.0

package/README.md

@@ -118,26 +118,28 @@ Congrats, you are debugging!
 
 <!-- commands -->
 
-- [`sf analytics generate template`](#sf-analytics-generate-template)
-- [`sf lightning generate app`](#sf-lightning-generate-app)
-- [`sf lightning generate component`](#sf-lightning-generate-component)
-- [`sf lightning generate event`](#sf-lightning-generate-event)
-- [`sf lightning generate interface`](#sf-lightning-generate-interface)
-- [`sf lightning generate test`](#sf-lightning-generate-test)
-- [`sf project generate`](#sf-project-generate)
-- [`sf static-resource generate`](#sf-static-resource-generate)
+- [`sf template generate analytics template`](#sf-template-generate-analytics-template)
 - [`sf template generate apex class`](#sf-template-generate-apex-class)
 - [`sf template generate apex trigger`](#sf-template-generate-apex-trigger)
-- [`sf visualforce generate component`](#sf-visualforce-generate-component)
-- [`sf visualforce generate page`](#sf-visualforce-generate-page)
-
-## `sf analytics generate template`
+- [`sf template generate digital-experience site`](#sf-template-generate-digital-experience-site)
+- [`sf template generate lightning app`](#sf-template-generate-lightning-app)
+- [`sf template generate lightning component`](#sf-template-generate-lightning-component)
+- [`sf template generate lightning event`](#sf-template-generate-lightning-event)
+- [`sf template generate lightning interface`](#sf-template-generate-lightning-interface)
+- [`sf template generate lightning test`](#sf-template-generate-lightning-test)
+- [`sf template generate project`](#sf-template-generate-project)
+- [`sf template generate static-resource`](#sf-template-generate-static-resource)
+- [`sf template generate visualforce component`](#sf-template-generate-visualforce-component)
+- [`sf template generate visualforce page`](#sf-template-generate-visualforce-page)
+
+## `sf template generate analytics template`
 
 Generate a simple Analytics template.
 
 ```
 USAGE
-  $ sf analytics generate template -n <value> [--json] [--flags-dir <value>] [-d <value>] [--api-version <value>]
+  $ sf template generate analytics template -n <value> [--json] [--flags-dir <value>] [-d <value>] [--api-version
+  <value>]
 
 FLAGS
   -d, --output-dir=<value>   [default: .] Directory for saving the created files.
@@ -157,29 +159,210 @@ DESCRIPTION
 
 ALIASES
   $ sf force analytics template create
+  $ sf analytics generate template
 
 EXAMPLES
   Generate the metadata files for a simple Analytics template file called myTemplate in the
   force-app/main/default/waveTemplates directory:
 
-    $ sf analytics generate template --name myTemplate --output-dir force-app/main/default/waveTemplates
+    $ sf template generate analytics template --name myTemplate --output-dir force-app/main/default/waveTemplates
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+```
+
+_See code: [src/commands/template/generate/analytics/template.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/analytics/template.ts)_
+
+## `sf template generate apex class`
+
+Generate an Apex class.
+
+```
+USAGE
+  $ sf template generate apex class -n <value> [--json] [--flags-dir <value>] [-t
+    ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Apex class.
+  -t, --template=<option>    [default: DefaultApexClass] Template to use for file creation.
+                             <options: ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate an Apex class.
+
+  Generates the Apex *.cls file and associated metadata file. These files must be contained in a parent directory called
+  "classes" in your package directory. Either run this command from an existing directory of this name, or use the
+  --output-dir flag to generate one or point to an existing one.
+
+ALIASES
+  $ sf force apex class create
+  $ sf apex generate class
+
+EXAMPLES
+  Generate two metadata files associated with the MyClass Apex class (MyClass.cls and MyClass.cls-meta.xml) in the
+  current directory:
+
+    $ sf template generate apex class --name MyClass
+
+  Similar to previous example, but generates the files in the "force-app/main/default/classes" directory:
+
+    $ sf template generate apex class --name MyClass --output-dir force-app/main/default/classes
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Apex class.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService
+
+    Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [src/commands/template/generate/apex/class.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/apex/class.ts)_
+
+## `sf template generate apex trigger`
+
+Generate an Apex trigger.
+
+```
+USAGE
+  $ sf template generate apex trigger -n <value> [--json] [--flags-dir <value>] [-t ApexTrigger] [-d <value>] [--api-version
+    <value>] [-s <value>] [-e before insert|before update|before delete|after insert|after update|after delete|after
+    undelete...]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -e, --event=<option>...    [default: before insert] Events that fire the trigger.
+                             <options: before insert|before update|before delete|after insert|after update|after
+                             delete|after undelete>
+  -n, --name=<value>         (required) Name of the generated Apex trigger
+  -s, --sobject=<value>      [default: SOBJECT] Salesforce object to generate a trigger on.
+  -t, --template=<option>    [default: ApexTrigger] Template to use for file creation.
+                             <options: ApexTrigger>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate an Apex trigger.
+
+  Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent
+  directory called "triggers" in your package directory. Either run this command from an existing directory of this
+  name, or use the --output-dir flag to generate one or point to an existing one.
+
+  If you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with
+  the Salesforce object you want to generate a trigger for. If you don't specify --event, "before insert" is used.
+
+ALIASES
+  $ sf force apex trigger create
+  $ sf apex generate trigger
+
+EXAMPLES
+  Generate two files associated with the MyTrigger Apex trigger (MyTrigger.trigger and MyTrigger.trigger-meta.xml) in
+  the current directory:
+
+    $ sf template generate apex trigger --name MyTrigger
+
+  Similar to the previous example, but generate the files in the "force-app/main/default/triggers" directory:
+
+    $ sf template generate apex trigger --name MyTrigger --output-dir force-app/main/default/triggers
+
+  Generate files for a trigger that fires on the Account object before and after an insert:
+
+    $ sf template generate apex trigger --name MyTrigger --sobject Account --event "before insert,after insert"
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
 
     The location can be an absolute path or relative to the current working directory. The default is the current
     directory.
+
+  -n, --name=<value>  Name of the generated Apex trigger
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=ApexTrigger  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [src/commands/template/generate/apex/trigger.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/apex/trigger.ts)_
+
+## `sf template generate digital-experience site`
+
+Generate an Experience Cloud site.
+
+```
+USAGE
+  $ sf template generate digital-experience site -n <value> -t BuildYourOwnLWR [--json] [--flags-dir <value>] [-o <value>] [-p <value>] [-e
+    <value>] [-d <value>]
+
+FLAGS
+  -d, --output-dir=<value>       Directory to generate the site files in.
+  -e, --admin-email=<value>      Email address for the site administrator. Defaults to the username of the currently
+                                 authenticated user.
+  -n, --name=<value>             (required) Name of the Experience Cloud site to generate.
+  -o, --target-org=<value>       Username or alias of the target org.
+  -p, --url-path-prefix=<value>  URL path prefix for the site; must contain only alphanumeric characters.
+  -t, --template=<option>        (required) Template to use when generating the site.
+                                 <options: BuildYourOwnLWR>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate an Experience Cloud site.
+
+  Creates an Experience Cloud site with the specified template, name, and URL path prefix. The site includes all
+  necessary metadata files, including DigitalExperienceConfig, DigitalExperienceBundle, Network, and CustomSite.
+
+EXAMPLES
+  Generate an Experience Cloud site using the BuildYourOwnLWR template. The site is called "mysite" and has the URL
+  path prefix "mysite":
+
+    $ sf template generate digital-experience site --template BuildYourOwnLWR --name mysite --url-path-prefix mysite
+
+  Generate an Experience Cloud site like the last example, but generate the files into the specified output directory:
+
+    $ sf template generate digital-experience site --template BuildYourOwnLWR --name mysite --url-path-prefix mysite \
+      --output-dir force-app/main/default
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory to generate the site files in.
+
+    The location can be an absolute path or relative to the current working directory. If not specified, the command
+    reads your sfdx-project.json file and uses the default package directory. When running outside a Salesforce DX
+    project, defaults to the current directory.
 ```
 
-_See code: [src/commands/analytics/generate/template.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/analytics/generate/template.ts)_
+_See code: [src/commands/template/generate/digital-experience/site.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/digital-experience/site.ts)_
 
-## `sf lightning generate app`
+## `sf template generate lightning app`
 
 Generate a Lightning App.
 
 ```
 USAGE
-  $ sf lightning generate app -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningApp] [-d <value>] [--api-version
+  $ sf template generate lightning app -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningApp] [-d <value>] [--api-version
     <value>]
 
 FLAGS
@@ -201,15 +384,16 @@ DESCRIPTION
 
 ALIASES
   $ sf force lightning app create
+  $ sf lightning generate app
 
 EXAMPLES
   Generate the metadata files for a Lightning app bundle called "myapp" in the current directory:
 
-    $ sf lightning generate app --name myapp
+    $ sf template generate lightning app --name myapp
 
   Similar to the previous example, but generate the files in the "force-app/main/default/aura" directory:
 
-    $ sf lightning generate app --name myapp --output-dir force-app/main/default/aura
+    $ sf template generate lightning app --name myapp --output-dir force-app/main/default/aura
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -226,15 +410,15 @@ FLAG DESCRIPTIONS
     Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/lightning/generate/app.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/lightning/generate/app.ts)_
+_See code: [src/commands/template/generate/lightning/app.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/app.ts)_
 
-## `sf lightning generate component`
+## `sf template generate lightning component`
 
 Generate a bundle for an Aura component or a Lightning web component.
 
 ```
 USAGE
-  $ sf lightning generate component -n <value> [--json] [--flags-dir <value>] [-t
+  $ sf template generate lightning component -n <value> [--json] [--flags-dir <value>] [-t
     default|analyticsDashboard|analyticsDashboardWithStep] [-d <value>] [--api-version <value>] [--type aura|lwc]
 
 FLAGS
@@ -262,23 +446,24 @@ DESCRIPTION
 
 ALIASES
   $ sf force lightning component create
+  $ sf lightning generate component
 
 EXAMPLES
   Generate the metadata files for an Aura component bundle in the current directory:
 
-    $ sf lightning generate component --name mycomponent
+    $ sf template generate lightning component --name mycomponent
 
   Generate a Lightning web component bundle in the current directory:
 
-    $ sf lightning generate component --name mycomponent --type lwc
+    $ sf template generate lightning component --name mycomponent --type lwc
 
   Generate an Aura component bundle in the "force-app/main/default/aura" directory:
 
-    $ sf lightning generate component --name mycomponent --output-dir force-app/main/default/aura
+    $ sf template generate lightning component --name mycomponent --output-dir force-app/main/default/aura
 
   Generate a Lightning web component bundle in the "force-app/main/default/lwc" directory:
 
-    $ sf lightning generate component --name mycomponent --type lwc --output-dir force-app/main/default/lwc
+    $ sf template generate lightning component --name mycomponent --type lwc --output-dir force-app/main/default/lwc
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -295,15 +480,15 @@ FLAG DESCRIPTIONS
     Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/lightning/generate/component.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/lightning/generate/component.ts)_
+_See code: [src/commands/template/generate/lightning/component.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/component.ts)_
 
-## `sf lightning generate event`
+## `sf template generate lightning event`
 
 Generate a Lightning Event.
 
 ```
 USAGE
-  $ sf lightning generate event -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningEvt] [-d <value>] [--api-version
+  $ sf template generate lightning event -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningEvt] [-d <value>] [--api-version
     <value>]
 
 FLAGS
@@ -325,15 +510,16 @@ DESCRIPTION
 
 ALIASES
   $ sf force lightning event create
+  $ sf lightning generate event
 
 EXAMPLES
   Generate the metadata files for a Lightning event bundle called "myevent" in the current directory:
 
-    $ sf lightning generate event --name myevent
+    $ sf template generate lightning event --name myevent
 
   Similar to previous example, but generate the files in the "force-app/main/default/aura" directory:
 
-    $ sf lightning generate event --name myevent --output-dir force-app/main/default/aura
+    $ sf template generate lightning event --name myevent --output-dir force-app/main/default/aura
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -350,15 +536,15 @@ FLAG DESCRIPTIONS
     Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/lightning/generate/event.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/lightning/generate/event.ts)_
+_See code: [src/commands/template/generate/lightning/event.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/event.ts)_
 
-## `sf lightning generate interface`
+## `sf template generate lightning interface`
 
 Generate a Lightning Interface.
 
 ```
 USAGE
-  $ sf lightning generate interface -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningIntf] [-d <value>]
+  $ sf template generate lightning interface -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningIntf] [-d <value>]
     [--api-version <value>]
 
 FLAGS
@@ -380,15 +566,16 @@ DESCRIPTION
 
 ALIASES
   $ sf force lightning interface create
+  $ sf lightning generate interface
 
 EXAMPLES
   Generate the metadata files for a Lightning interface bundle called "myinterface" in the current directory:
 
-    $ sf lightning generate interface --name myinterface
+    $ sf template generate lightning interface --name myinterface
 
   Similar to the previous example but generate the files in the "force-app/main/default/aura" directory:
 
-    $ sf lightning generate interface --name myinterface --output-dir force-app/main/default/aura
+    $ sf template generate lightning interface --name myinterface --output-dir force-app/main/default/aura
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -405,15 +592,15 @@ FLAG DESCRIPTIONS
     Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/lightning/generate/interface.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/lightning/generate/interface.ts)_
+_See code: [src/commands/template/generate/lightning/interface.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/interface.ts)_
 
-## `sf lightning generate test`
+## `sf template generate lightning test`
 
 Generate a Lightning test.
 
 ```
 USAGE
-  $ sf lightning generate test -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningTest] [-d <value>]
+  $ sf template generate lightning test -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningTest] [-d <value>]
     [--api-version <value>]
 
 FLAGS
@@ -435,15 +622,16 @@ DESCRIPTION
 
 ALIASES
   $ sf force lightning test create
+  $ sf lightning generate test
 
 EXAMPLES
   Generate the metadata files for the Lightning test called MyLightningTest in the current directory:
 
-    $ sf lightning generate test --name MyLightningTest
+    $ sf template generate lightning test --name MyLightningTest
 
   Similar to the previous example but generate the files in the "force-app/main/default/lightningTests" directory:
 
-    $ sf lightning generate test --name MyLightningTest --output-dir force-app/main/default/lightningTests
+    $ sf template generate lightning test --name MyLightningTest --output-dir force-app/main/default/lightningTests
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -460,15 +648,15 @@ FLAG DESCRIPTIONS
     Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/lightning/generate/test.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/lightning/generate/test.ts)_
+_See code: [src/commands/template/generate/lightning/test.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/test.ts)_
 
-## `sf project generate`
+## `sf template generate project`
 
 Generate a Salesforce DX project.
 
 ```
 USAGE
-  $ sf project generate -n <value> [--json] [--flags-dir <value>] [-t standard|empty|analytics] [-d <value>] [-s
+  $ sf template generate project -n <value> [--json] [--flags-dir <value>] [-t standard|empty|analytics] [-d <value>] [-s
     <value>] [-p <value>] [-x] [--api-version <value>]
 
 FLAGS
@@ -498,23 +686,24 @@ DESCRIPTION
 
 ALIASES
   $ sf force project create
+  $ sf project generate
 
 EXAMPLES
   Generate a project called "mywork":
 
-    $ sf project generate --name mywork
+    $ sf template generate project --name mywork
 
   Similar to previous example, but generate the files in a directory called "myapp":
 
-    $ sf project generate --name mywork --default-package-dir myapp
+    $ sf template generate project --name mywork --default-package-dir myapp
 
   Similar to prevoius example, but also generate a default package.xml manifest file:
 
-    $ sf project generate --name mywork --default-package-dir myapp --manifest
+    $ sf template generate project --name mywork --default-package-dir myapp --manifest
 
   Generate a project with the minimum files and directories:
 
-    $ sf project generate --name mywork --template empty
+    $ sf template generate project --name mywork --template empty
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -565,16 +754,16 @@ FLAG DESCRIPTIONS
     Override the api version used for api requests made by this command
 ```
 
-_See code: [src/commands/project/generate.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/project/generate.ts)_
+_See code: [src/commands/template/generate/project/index.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/project/index.ts)_
 
-## `sf static-resource generate`
+## `sf template generate static-resource`
 
 Generate a static resource.
 
 ```
 USAGE
-  $ sf static-resource generate -n <value> [--json] [--flags-dir <value>] [--type <value>] [-d <value>] [--api-version
-  <value>]
+  $ sf template generate static-resource -n <value> [--json] [--flags-dir <value>] [--type <value>] [-d <value>]
+  [--api-version <value>]
 
 FLAGS
   -d, --output-dir=<value>   [default: .] Directory for saving the created files.
@@ -596,19 +785,20 @@ DESCRIPTION
 
 ALIASES
   $ sf force staticresource create
+  $ sf static-resource generate
 
 EXAMPLES
   Generate the metadata file for a static resource called MyResource in the current directory:
 
-    $ sf static-resource generate --name MyResource
+    $ sf template generate static-resource --name MyResource
 
   Similar to previous example, but specifies a MIME type of application/json:
 
-    $ sf static-resource generate --name MyResource --type application/json
+    $ sf template generate static-resource --name MyResource --type application/json
 
   Generate the resource file in the "force-app/main/default/staticresources" directory:
 
-    $ sf static-resource generate --name MyResource --output-dir force-app/main/default/staticresources
+    $ sf template generate static-resource --name MyResource --output-dir force-app/main/default/staticresources
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -627,145 +817,15 @@ FLAG DESCRIPTIONS
     etc.
 ```
 
-_See code: [src/commands/static-resource/generate.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/static-resource/generate.ts)_
-
-## `sf template generate apex class`
-
-Generate an Apex class.
-
-```
-USAGE
-  $ sf template generate apex class -n <value> [--json] [--flags-dir <value>] [-t
-    ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService] [-d <value>] [--api-version <value>]
-
-FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated Apex class.
-  -t, --template=<option>    [default: DefaultApexClass] Template to use for file creation.
-                             <options: ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService>
-      --api-version=<value>  Override the api version used for api requests made by this command
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Generate an Apex class.
-
-  Generates the Apex *.cls file and associated metadata file. These files must be contained in a parent directory called
-  "classes" in your package directory. Either run this command from an existing directory of this name, or use the
-  --output-dir flag to generate one or point to an existing one.
-
-ALIASES
-  $ sf force apex class create
-  $ sf apex generate class
-
-EXAMPLES
-  Generate two metadata files associated with the MyClass Apex class (MyClass.cls and MyClass.cls-meta.xml) in the
-  current directory:
-
-    $ sf template generate apex class --name MyClass
-
-  Similar to previous example, but generates the files in the "force-app/main/default/classes" directory:
-
-    $ sf template generate apex class --name MyClass --output-dir force-app/main/default/classes
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated Apex class.
-
-    The name can be up to 40 characters and must start with a letter.
-
-  -t, --template=ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService
-
-    Template to use for file creation.
-
-    Supplied parameter values or default values are filled into a copy of the template.
-```
-
-_See code: [src/commands/template/generate/apex/class.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/template/generate/apex/class.ts)_
-
-## `sf template generate apex trigger`
-
-Generate an Apex trigger.
-
-```
-USAGE
-  $ sf template generate apex trigger -n <value> [--json] [--flags-dir <value>] [-t ApexTrigger] [-d <value>] [--api-version
-    <value>] [-s <value>] [-e before insert|before update|before delete|after insert|after update|after delete|after
-    undelete...]
-
-FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -e, --event=<option>...    [default: before insert] Events that fire the trigger.
-                             <options: before insert|before update|before delete|after insert|after update|after
-                             delete|after undelete>
-  -n, --name=<value>         (required) Name of the generated Apex trigger
-  -s, --sobject=<value>      [default: SOBJECT] Salesforce object to generate a trigger on.
-  -t, --template=<option>    [default: ApexTrigger] Template to use for file creation.
-                             <options: ApexTrigger>
-      --api-version=<value>  Override the api version used for api requests made by this command
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Generate an Apex trigger.
+_See code: [src/commands/template/generate/static-resource/index.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/static-resource/index.ts)_
 
-  Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent
-  directory called "triggers" in your package directory. Either run this command from an existing directory of this
-  name, or use the --output-dir flag to generate one or point to an existing one.
-
-  If you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with
-  the Salesforce object you want to generate a trigger for. If you don't specify --event, "before insert" is used.
-
-ALIASES
-  $ sf force apex trigger create
-  $ sf apex generate trigger
-
-EXAMPLES
-  Generate two files associated with the MyTrigger Apex trigger (MyTrigger.trigger and MyTrigger.trigger-meta.xml) in
-  the current directory:
-
-    $ sf template generate apex trigger --name MyTrigger
-
-  Similar to the previous example, but generate the files in the "force-app/main/default/triggers" directory:
-
-    $ sf template generate apex trigger --name MyTrigger --output-dir force-app/main/default/triggers
-
-  Generate files for a trigger that fires on the Account object before and after an insert:
-
-    $ sf template generate apex trigger --name MyTrigger --sobject Account --event "before insert,after insert"
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated Apex trigger
-
-    The name can be up to 40 characters and must start with a letter.
-
-  -t, --template=ApexTrigger  Template to use for file creation.
-
-    Supplied parameter values or default values are filled into a copy of the template.
-```
-
-_See code: [src/commands/template/generate/apex/trigger.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/template/generate/apex/trigger.ts)_
-
-## `sf visualforce generate component`
+## `sf template generate visualforce component`
 
 Generate a Visualforce Component.
 
 ```
 USAGE
-  $ sf visualforce generate component -n <value> -l <value> [--json] [--flags-dir <value>] [-t DefaultVFComponent] [-d <value>]
+  $ sf template generate visualforce component -n <value> -l <value> [--json] [--flags-dir <value>] [-t DefaultVFComponent] [-d <value>]
     [--api-version <value>]
 
 FLAGS
@@ -788,15 +848,16 @@ DESCRIPTION
 
 ALIASES
   $ sf force visualforce component create
+  $ sf visualforce generate component
 
 EXAMPLES
   Generate the metadata files for a Visualforce component in the current directory:
 
-    $ sf visualforce generate component --name mycomponent --label mylabel
+    $ sf template generate visualforce component --name mycomponent --label mylabel
 
   Similar to previous example, but generate the files in the directory "force-app/main/default/components":
 
-    $ sf visualforce generate component --name mycomponent --label mylabel --output-dir components
+    $ sf template generate visualforce component --name mycomponent --label mylabel --output-dir components
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -813,16 +874,16 @@ FLAG DESCRIPTIONS
     Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/visualforce/generate/component.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/visualforce/generate/component.ts)_
+_See code: [src/commands/template/generate/visualforce/component.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/visualforce/component.ts)_
 
-## `sf visualforce generate page`
+## `sf template generate visualforce page`
 
 Generate a Visualforce Page.
 
 ```
 USAGE
-  $ sf visualforce generate page -n <value> -l <value> [--json] [--flags-dir <value>] [-d <value>] [--api-version
-  <value>]
+  $ sf template generate visualforce page -n <value> -l <value> [--json] [--flags-dir <value>] [-d <value>]
+  [--api-version <value>]
 
 FLAGS
   -d, --output-dir=<value>   [default: .] Directory for saving the created files.
@@ -842,15 +903,16 @@ DESCRIPTION
 
 ALIASES
   $ sf force visualforce page create
+  $ sf visualforce generate page
 
 EXAMPLES
   Generate the metadata files for a Visualforce page in the current directory:
 
-    $ sf visualforce generate page --name mypage --label mylabel
+    $ sf template generate visualforce page --name mypage --label mylabel
 
   Similar to previous example, but generate the files in the directory "force-app/main/default/pages":
 
-    $ sf visualforce generate page --name mypage --label mylabel --output-dir pages
+    $ sf template generate visualforce page --name mypage --label mylabel --output-dir pages
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -863,6 +925,6 @@ FLAG DESCRIPTIONS
     The name can be up to 40 characters and must start with a letter.
 ```
 
-_See code: [src/commands/visualforce/generate/page.ts](https://github.com/salesforcecli/plugin-templates/blob/56.5.2/src/commands/visualforce/generate/page.ts)_
+_See code: [src/commands/template/generate/visualforce/page.ts](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/visualforce/page.ts)_
 
 <!-- commandsstop -->