{"id":46611643,"url":"https://github.com/salesforcecli/plugin-community","last_synced_at":"2026-05-23T08:05:07.624Z","repository":{"id":36963594,"uuid":"400299079","full_name":"salesforcecli/plugin-community","owner":"salesforcecli","description":null,"archived":false,"fork":false,"pushed_at":"2026-04-04T11:50:37.000Z","size":5948,"stargazers_count":3,"open_issues_count":2,"forks_count":1,"subscribers_count":5,"default_branch":"main","last_synced_at":"2026-04-04T13:35:16.491Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/salesforcecli.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2021-08-26T20:35:11.000Z","updated_at":"2026-04-04T11:50:42.000Z","dependencies_parsed_at":"2025-11-30T17:04:05.428Z","dependency_job_id":null,"html_url":"https://github.com/salesforcecli/plugin-community","commit_stats":{"total_commits":329,"total_committers":17,"mean_commits":"19.352941176470587","dds":0.3890577507598785,"last_synced_commit":"13fe0104bd2f198ff71d9dd930535bc068349529"},"previous_names":[],"tags_count":201,"template":false,"template_full_name":"salesforcecli/plugin-template","purl":"pkg:github/salesforcecli/plugin-community","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-community","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-community/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-community/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-community/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/salesforcecli","download_url":"https://codeload.github.com/salesforcecli/plugin-community/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-community/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":31957158,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-18T00:39:45.007Z","status":"online","status_checked_at":"2026-04-18T02:00:07.018Z","response_time":103,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-03-07T18:31:33.860Z","updated_at":"2026-05-23T08:05:07.618Z","avatar_url":"https://github.com/salesforcecli.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# plugin-community;\n\n[![NPM](https://img.shields.io/npm/v/@salesforce/plugin-community.svg?label=@salesforce/plugin-community)](https://www.npmjs.com/package/@salesforce/plugin-community) [![Downloads/week](https://img.shields.io/npm/dw/@salesforce/plugin-community.svg)](https://npmjs.org/package/@salesforce/plugin-community) [![License](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://opensource.org/license/apache-2-0)\n\n## Learn about the plugin-community\n\nUse the community commands to create and publish an Experience Cloud site, and view a list of available templates in you org.\n\nThis plugin is bundled with the [Salesforce CLI](https://developer.salesforce.com/tools/sfdxcli). For more information on the CLI, read the [getting started guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm).\n\nWe always recommend using the latest version of these commands bundled with the CLI, however, you can install a specific version or tag if needed.\n\n## Install\n\n```bash\nsfdx plugins:install community@x.y.z\n```\n\n## Issues\n\nPlease report any issues at https://github.com/forcedotcom/cli/issues\n\n## Contributing\n\n1. Please read our [Code of Conduct](CODE_OF_CONDUCT.md)\n2. Create a new issue before starting your project so that we can keep track of\n   what you are trying to add/fix. That way, we can also offer suggestions or\n   let you know if there is already an effort in progress.\n3. Fork this repository.\n4. [Build the plugin locally](#build)\n5. Create a _topic_ branch in your fork. Note, this step is recommended but technically not required if contributing using a fork.\n6. Edit the code in your fork.\n7. Write appropriate tests for your changes. Try to achieve at least 95% code coverage on any new code. No pull request will be accepted without unit tests.\n8. Sign CLA (see [CLA](#cla) below).\n9. Send us a pull request when you are done. We'll review your code, suggest any needed changes, and merge it in.\n\n### CLA\n\nExternal contributors will be required to sign a Contributor's License\nAgreement. You can do so by going to https://cla.salesforce.com/sign-cla.\n\n### Build\n\nTo build the plugin locally, make sure to have yarn installed and run the following commands:\n\n```bash\n# Clone the repository\ngit clone git@github.com:salesforcecli/plugin-community\n\n# Install the dependencies and compile\nyarn install\nyarn build\n```\n\nTo use your plugin, run using the local `./bin/dev` or `./bin/dev.cmd` file.\n\n```bash\n# Run using local run file.\n./bin/dev community\n```\n\nThere should be no differences when running via the Salesforce CLI or using the local run file. However, it can be useful to link the plugin to do some additional testing or run your commands from anywhere on your machine.\n\n```bash\n# Link your plugin to the sfdx cli\nsfdx plugins:link .\n# To verify\nsfdx plugins\n```\n\n## Commands\n\n\u003c!-- commands --\u003e\n\n- [`sf community create`](#sf-community-create)\n- [`sf community list template`](#sf-community-list-template)\n- [`sf community publish`](#sf-community-publish)\n\n## `sf community create`\n\nCreate an Experience Cloud site using a template.\n\n```\nUSAGE\n  $ sf community create -n \u003cvalue\u003e -t \u003cvalue\u003e -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-p \u003cvalue\u003e] [-d \u003cvalue\u003e]\n    [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -d, --description=\u003cvalue\u003e      Description of the site.\n  -n, --name=\u003cvalue\u003e             (required) Name of the site to create.\n  -o, --target-org=\u003cvalue\u003e       (required) Username or alias of the target org. Not required if the `target-org`\n                                 configuration variable is already set.\n  -p, --url-path-prefix=\u003cvalue\u003e  URL to append to the domain created when Digital Experiences was enabled for this org.\n  -t, --template-name=\u003cvalue\u003e    (required) Template to use to create a site.\n      --api-version=\u003cvalue\u003e      Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Create an Experience Cloud site using a template.\n\n  Run the \"community list template\" command to see the templates available in your org. See 'Which Experience Cloud\n  Template Should I Use?' in Salesforce Help for more information about the different template types available.\n  (https://help.salesforce.com/s/articleView?id=sf.siteforce_commtemp_intro.htm\u0026type=5)\n\n  When you create a site with the Build Your Own (LWR) template, you must also specify the AuthenticationType value\n  using the format templateParams.AuthenticationType=value, where value is AUTHENTICATED or\n  AUTHENTICATED_WITH_PUBLIC_ACCESS_ENABLED. Name and values are case-sensitive. See 'DigitalExperienceBundle' in the\n  Metadata API Developer Guide for more information.\n  (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_digitalexperiencebundle.htm)\n\n  The site creation process is an async job that generates a jobId. To check the site creation status, query the\n  BackgroundOperation object and enter the jobId as the Id. See ‘BackgroundOperation’ in the Object Reference for the\n  Salesforce Platform for more information. (https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/obj\n  ect_reference/sforce_api_objects_backgroundoperation.htm)\n\n  If the job doesn’t complete within 10 minutes, it times out. You receive an error message and must restart the site\n  creation process. Completed jobs expire after 24 hours and are removed from the database.\n\n  When you run this command, it creates the site in preview status, which means that the site isn't yet live. After you\n  finish building your site, you can make it live.\n\n  If you have an Experience Builder site, publish the site using the \"community publish\" command to make it live.\n\n  If you have a Salesforce Tabs + Visualforce site, to activate the site and make it live, update the status field of\n  the Network type in Metadata API.\n  (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_network.htm) Alternatively, in\n  Experience Workspaces, go to Administration | Settings, and click Activate.\n\n  For Experience Builder sites, activating the site sends a welcome email to site members.\n\nALIASES\n  $ sf force community create\n\nEXAMPLES\n  Create an Experience Cloud site using template 'Customer Service' and URL path prefix 'customers':\n\n    $ sf community create --name 'My Customer Site' --template-name 'Customer Service' --url-path-prefix customers \\\n      --description 'My customer site'\n\n  Create a site using 'Partner Central' template:\n\n    $ sf community create --name partnercentral --template-name 'Partner Central' --url-path-prefix partners\n\n  Create a site using the 'Build Your Own (LWR)' template with authentication type of UNAUTHENTICATED:\n\n    $ sf community create --name lwrsite --template-name 'Build Your Own (LWR)' --url-path-prefix lwrsite \\\n      templateParams.AuthenticationType=UNAUTHENTICATED\n\nFLAG DESCRIPTIONS\n  -d, --description=\u003cvalue\u003e  Description of the site.\n\n    The description displays in Digital Experiences - All Sites in Setup and helps with site identification.\n\n  -p, --url-path-prefix=\u003cvalue\u003e  URL to append to the domain created when Digital Experiences was enabled for this org.\n\n    For example, if your domain name is https://MyDomainName.my.site.com and you create a customer site, enter\n    'customers' to create the unique URL https://MyDomainName.my.site.com/customers.\n\n  -t, --template-name=\u003cvalue\u003e  Template to use to create a site.\n\n    An example of a template is Customer Service. Run the \"community template list\" command to see which templates are\n    available in your org.\n```\n\n_See code: [src/commands/community/create.ts](https://github.com/salesforcecli/plugin-community/blob/3.3.63/src/commands/community/create.ts)_\n\n## `sf community list template`\n\nRetrieve the list of templates available in your org.\n\n```\nUSAGE\n  $ sf community list template -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Retrieve the list of templates available in your org.\n\n  See 'Which Experience Cloud Template Should I Use?'\n  (https://help.salesforce.com/s/articleView?id=sf.siteforce_commtemp_intro.htm\u0026type=5) in Salesforce Help for more\n  information about the different template types available for Experience Cloud.\n\nALIASES\n  $ sf force community template list\n\nEXAMPLES\n  Retrieve the template list from an org with alias my-scratch-org:\n\n    $ sf community list template --target-org my-scratch-org\n```\n\n_See code: [src/commands/community/list/template.ts](https://github.com/salesforcecli/plugin-community/blob/3.3.63/src/commands/community/list/template.ts)_\n\n## `sf community publish`\n\nPublish an Experience Builder site to make it live.\n\n```\nUSAGE\n  $ sf community publish -n \u003cvalue\u003e -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e]\n\nFLAGS\n  -n, --name=\u003cvalue\u003e         (required) Name of the Experience Builder site to publish.\n  -o, --target-org=\u003cvalue\u003e   (required) Username or alias of the target org. Not required if the `target-org`\n                             configuration variable is already set.\n      --api-version=\u003cvalue\u003e  Override the api version used for api requests made by this command\n\nGLOBAL FLAGS\n  --flags-dir=\u003cvalue\u003e  Import flag values from a directory.\n  --json               Format output as json.\n\nDESCRIPTION\n  Publish an Experience Builder site to make it live.\n\n  Each time you publish a site, you update the live site with the most recent updates. When you publish an Experience\n  Builder site for the first time, you make the site's URL live and enable login access for site members.\n\n  In addition to publishing, you must activate a site to send a welcome email to all site members. Activation is also\n  required to set up SEO for Experience Builder sites. To activate a site, update the status field of the Network type\n  in Metadata API. (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_network.htm)\n  Alternatively, in Experience Workspaces, go to Administration | Settings, and click Activate.\n\n  An email notification informs you when your changes are live on the published site. The site publish process is an\n  async job that generates a jobId. To check the site publish status manually, query the BackgroundOperation object and\n  enter the jobId as the Id. See ‘BackgroundOperation’ in the Object Reference for the Salesforce Platform for more\n  information. (https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_obje\n  cts_backgroundoperation.htm)\n\n  If the job doesn’t complete within 15 minutes, it times out. You receive an error message and must restart the site\n  publish process. Completed jobs expire after 24 hours and are removed from the database.\n\nALIASES\n  $ sf force community publish\n\nEXAMPLES\n  Publish the Experience Builder site with name \"My Customer Site':\n\n    $ sf community publish --name 'My Customer Site'\n```\n\n_See code: [src/commands/community/publish.ts](https://github.com/salesforcecli/plugin-community/blob/3.3.63/src/commands/community/publish.ts)_\n\n\u003c!-- commandsstop --\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsalesforcecli%2Fplugin-community","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsalesforcecli%2Fplugin-community","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsalesforcecli%2Fplugin-community/lists"}