├── .github └── CODEOWNERS ├── README.md ├── admins.md ├── assets ├── default-slack-avatar.png └── slack-expanded-link.png ├── getting-started.md ├── sandbox.md ├── terms-of-use.md └── tools.md /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | * @sfcc-unofficial/SFCC-Unofficial-Admins 2 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Joining 2 | You can [access the community](https://sfcc-unofficial.slack.com/) here. If you haven't already been invited, then please request an invitation from someone who you know is already in the community, or from the form listed below. 3 | 4 | ## Invitations 5 | If you don't know anyone in the community, please [request an invitation](https://docs.google.com/forms/d/e/1FAIpQLSdy875PlJuib35naCkr3-Frn2qtaSuuRgYezRSb2uBYkhXt7g/viewform). (Your email address will only be used for the sole purpose of inviting you to the community.) 6 | 7 | ## Community Documentation 8 | Documentation by and for the SF B2C Commerce Unofficial Slack Community 9 | 10 | ### 📜 Terms of Use 11 | By joining the community you must agree to our [Terms of Use](./terms-of-use.md). 12 | 13 | ### 🚀 Getting Started 14 | Please review our [Getting Started](./getting-started.md) doc for some helpful tips to be aware of when using the SFCC Unofficial Slack. 15 | 16 | ### 👥 Who are the Admins? 17 | Please review our [list of administrators](./admins.md) to get to know the volunteers helping to keep the community thriving. 18 | 19 | ### 🔧 Community Tools 20 | [List of tools/projects](./tools.md) developed by community members. Feel free to contribute or suggest new tools. 21 | -------------------------------------------------------------------------------- /admins.md: -------------------------------------------------------------------------------- 1 | # Admins of SFCC Unofficial Slack Community 2 | 3 | All admins of this community are fulfilling that duty in a volunteer capacity. Please keep that in mind when they reach out to you or you reach out to them. 4 | 5 | ## Admins List 6 | 7 | | :camera: Photo| :label: Name | :book: Description | :id: Trailblazer ID | :octocat: GH ID | 8 | | :--: | :--- | :---------- | :------------- | :--------: | 9 | |![Photo of Steve Holsinger](https://ca.slack-edge.com/TAU70QQBY-UAV0HQQJK-9d8b4e70c62e-72)|[Steve Holsinger](https://sfcc-unofficial.slack.com/team/UAV0HQQJK)|Co-founder of the 2014/15 original version of the SFCC B2C Slack which eventually was accidentally closed to the public in May of 2018. In addition to volunteering in this community, Steve is also a senior technical leader of a Salesforce Practice. Steve has 11+ years of experience in SFCC B2C/Demandware development & architecture.| [sholsinger](https://trailblazer.me/id/sholsinger) | [sholsinger](https://github.com/sholsinger) | 10 | |![Avatar of Matt Rose](https://www.gravatar.com/avatar/fe2e106fbcbeea6f0b949e3594f18840)|[Matt Rose](https://sfcc-unofficial.slack.com/team/UAT3HAL92)| Matt has 10+ years of experience in SFCC B2C/Demandware across various technical roles related to design, development and architecture. Matt created the current SFCC Unofficial Slack Community after the previously mentioned original community was closed. Matt is currently working as an independent contractor after working at Salesforce and various partner agencies. | [mattrose](https://trailblazer.me/id/mattrose) | [matthewrose](https://github.com/matthewrose) | 11 | |![Photo of Oleg Sapishchuk](https://ca.slack-edge.com/TAU70QQBY-UASPSP28H-776050e8d86e-72)|[Oleg Sapishchuk](https://sfcc-unofficial.slack.com/team/UASPSP28H)| Oleg's overall goal is to become a thought leader that leads and teaches by example. Oleg wants continuously to build products that will bring positive impacts to people. Working as a Technical Architect at Salesforce, Oleg promotes community recognition and support from Salesforce. In addition to mentioned above, Oleg is Co-founder of the Unofficial Salesforce Commerce Cloud Podcast, an initiative that is running under the "Unofficial" Community umbrella.| [osapishchuk](https://trailblazer.me/id/osapishchuk) | [Gektorian](https://github.com/Gektorian) | 12 | |![Photo of Daniel Anechitoaie](https://ca.slack-edge.com/TAU70QQBY-UAV9A93GF-a999f8ff1837-512)|[Daniel Anechitoaie](https://sfcc-unofficial.slack.com/team/UAV9A93GF)| With 11+ years of experience with SFCC (former Demandware) stack, starting with dev position and leading up to principal solution architect, Daniel is still really pasionate about the next thing and likes to be the "early bird" when new things are planned or available in alpha/beta phases. He's also passionate about CI/CD and the author and mantainer of the [OSF Builder Suite for SFCC for Jenkins](https://plugins.jenkins.io/ui/search/?query=OSF%20Builder%20Suite%20For%20Salesforce%20Commerce%20Cloud) which are a set of Jenkins plugins targeted towards CI/CD for SFCC platform. Currently experimenting/working on some products using GPT3/Codex. | [daniel-anechitoaie](https://trailblazer.me/id/daniel-anechitoaie) | [danechitoaie](https://github.com/danechitoaie) | 13 | |![Photo of Kyle Montgomery](https://ca.slack-edge.com/T04T4TH8W-U5L4G7NCA-28205ce68242-72)|[Kyle Montgomery](https://sfcc-unofficial.slack.com/team/UAW7KE9HV)|VP Salesforce Commerce at Astound Commerce, a Salesforce Summit partner. Kyle is a remote-work enthusiast also passionate in DevOps, Agile, code, and no-code. Kyle has 10+ years Salesforce B2C/Demandware experience. Goes with he/him pronouns. | [kyleamontgomery](https://trailblazer.me/id/kyleamontgomery) | [k-montgomery](https://github.com/k-montgomery) | 14 | |![Photo of Gökay Gürcan](https://ca.slack-edge.com/TAU70QQBY-UAYMETYLX-b784d49304f1-72)|[Gökay Gürcan](https://sfcc-unofficial.slack.com/team/UAYMETYLX)|Late addition to the admins group after lurking around for a few years and trying to make a meaningful contribution to the community. Has about almost a decade of SFCC B2C Commerce Cloud/Demandware experience and many projects under his belt. Currently working as Development Manager of multiple software development teams. Goes with he/him pronouns.| [gokaygurcan](https://trailblazer.me/id/gokaygurcan) | [gokaygurcan](https://github.com/gokaygurcan)| 15 | |![Photo of Thomas Theunen](https://ca.slack-edge.com/TAU70QQBY-UFR4SL94H-78b02c36955b-512)|[Thomas Theunen](https://sfcc-unofficial.slack.com/team/UFR4SL94H)|He joined the admin group in 2022 after being in the community for a few years. He has more than a decade of experience in Commerce and is mainly focussing on Customer 360 for the past few years. Goes with he/him pronouns. | [thomas-theunen](https://trailblazer.me/id/thomas-theunen) |[taurgis](https://github.com/taurgis)| 16 | -------------------------------------------------------------------------------- /assets/default-slack-avatar.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sfcc-unofficial/docs/31fdca9e3bf70caac3509ab2cc7c20b5f84e0045/assets/default-slack-avatar.png -------------------------------------------------------------------------------- /assets/slack-expanded-link.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/sfcc-unofficial/docs/31fdca9e3bf70caac3509ab2cc7c20b5f84e0045/assets/slack-expanded-link.png -------------------------------------------------------------------------------- /getting-started.md: -------------------------------------------------------------------------------- 1 | # Getting Started 2 | 3 | Welcome to the [Unofficial Salesforce B2C Commerce Slack community](https://sfcc-unofficial.slack.com/). We created this community to give everyone access to each other to share ideas and help one another in a near real-time. It also gives members a place to discuss Salesforce B2C Commerce in a free and open environment. 4 | 5 | ## Setting Up Your Profile 6 | 7 | ### Name Fields 8 | 9 | Please use your actual name in the `Full Name` field. Please also use your real name or a shortened form of your real name in the `Display name (optional)` field. You do not need to submit a `Display name (optional)` value if you are happy with everyone seeing your `Full Name`. 10 | 11 | This community is expected to be a professional environment. The community does not benefit from anyone masquerading as another. It is requested that you not use fictional character names in either field. Violating this request may be grounds for deactivation of your account. 12 | 13 | ### What I do 14 | 15 | Please provide a brief summary of what you do and who you do it for. Openness in our community is helpful in developing a strong network. Knowing where someone works or their job role increases their credibility within the community. You do not _need_ to provide your employer's name, but it does help increase credibility. 16 | 17 | Please see the below examples: 18 | 19 | * Junior Developer at Northern Trail Outfitters 20 | * Technical Architect at Salesforce 21 | * Business Analyst at System Integrator X 22 | 23 | ### Profile photo 24 | 25 | Please upload a unique Profile photo or avatar as they are sometimes called. This will allow members of the community to easily recognize your posts and give you a unique persona within the community. If you don't provide one, your default Profile photo will be a Slack-generated image. However, there are only so many variations of this image and it becomes very monotonous to see the same patterns all over the place. 26 | 27 | Example of the Slack default Profile photo: 28 | 29 | ![Sample Slack Profile Photo](assets/default-slack-avatar.png) 30 | 31 | ## Dos and Don'ts 32 | 33 | ### Do ask questions 34 | 35 | There is a [`#newbies`](https://sfcc-unofficial.slack.com/messages/CDG4R5CT1) channel that is a good place for asking questions that don't appear to be relevant for any other channel. Questions that aren't related to newcomers can be asked in [`#general`](https://sfcc-unofficial.slack.com/messages/CAT794PC3). _See also:_ [Do Respect Channel Topics](#do-respect-channel-topics). 36 | 37 | ### Do respect others 38 | 39 | As a community based around a professional topic and setting, respect is a critical value for the success of the community overall. Remember the _Golden Rule_, "Treat others as you would wish to be treated." 40 | 41 | ### Do respect channel topics 42 | 43 | Many channels exist within the community. Some have specific topics such as `#ocapi`, `#einstein`, and `#sfcc-certification`. Others, such as `#general` and `#random` don't have a specific topic. Please try to locate the right place to post your message. 44 | 45 | ### Do ask for new public channel creation on [#admin-requests](https://sfcc-unofficial.slack.com/archives/C011P1G8R7W) 46 | 47 | If a channel that you feel should exist doesn't exist, make a request [#admin-requests](https://sfcc-unofficial.slack.com/archives/C011P1G8R7W). Additional channels should only be created when there's a robust need that doesn't fit into any of our current channels. Unnecessary multiplication of channels can lead to confusion and important messages may get missed. 48 | 49 | ### Do not ask for private channel creation 50 | 51 | We do not support the creation of private channels as we believe that knowledge and information should be open and accessible to those who seek it. We reserve the right to have few private channels that are used by the admins to discuss matters related to the running and management of the Slack workspace. 52 | 53 | ### Don't use this Slack for your company's business 54 | 55 | If your workplace doesn't use Slack and you want to use it anyway, don't use this slack for that purpose. Slacks are free to start, go ahead and [create your own](https://slack.com/get-started#create). 56 | 57 | ### Don't use `@everyone` & `@channel` 58 | 59 | Supporting others in the community is a volunteer position. As such, you as a member should have no expectation that others will be as attentive as your coworkers or friends. `@everyone` and `@channel` force notifications to all members of a channel regardless of they are active (being online and having Slack open) or not at that moment. They can become rather noisy to the hundreds of members in channels. Therefore, out of respect for the other members, please remember to avoid using those keywords in your messages. `@here` on the other hand, only notifies the **active** members and might be handy in some situations. Please do not overuse these keywords. 60 | 61 | ### Don't post content that may be vulgar, offensive, or illegal 62 | 63 | As a professional environment, it is not appropriate to share offensive or vulgar content within our Slack community. Additionally, do not share any information that may be illegal in nature. Please consider the global nature of the community when determining the legality of content. 64 | 65 | ### Don't duplicate content 66 | 67 | Let's imagine that you posted a message to `#ocapi` a couple days ago and you're not getting any responses. Your first instinct may be to re-post that same message to `#general` so that it will get more attention. Please don't do that. You can easily copy a link to the message within `#ocapi` and ask in `#general` for someone to look at it in the original channel instead. For example: 68 | 69 | ![Slack expanded link example](assets/slack-expanded-link.png) 70 | 71 | Slack will helpfully display an excerpt of your original message for folks to see when you share a link to it. 72 | 73 | ### Don't spam channels 74 | 75 | While the preferred method to ask your question again is to share a link, don't do so in a single channel as an attempt to bury or de-prioritize other messages that came after yours. A general rule of thumb is to not repost your message until at least 4-5 messages have come after it **and** at least 48 hrs of time has elapsed. This is to give our community the chance to respond across all timezones and schedules. 76 | 77 | Please remember that many of our members volunteer their time to answer questions and it can only happen when they are not focused on other obligations. 78 | 79 | ### Don't create duplicate accounts 80 | 81 | This Slack community doesn't restrict your ability to change your email address. Don't worry if you registered with an old employer's email account. You can just change the email address associated with it to your new employer. Simply go to [Account Settings](https://sfcc-unofficial.slack.com/account/settings) and change your email address. 82 | 83 | #### Recovering Accounts 84 | 85 | If you no longer have access to your Slack account, you can ask for an [admin](./admins.md) to change your account's email address. Try to get in touch by whatever means necessary. We've received requests by way of a friend or colleague who still has access to Slack. 86 | 87 | Please note that in some cases, we might not be able to do this, if we are not able to prove your identity or get from you enough details to confirm the old account was really yours. Trust is the value we care about a lot, like official Salesforce. 88 | 89 | #### Example 90 | 91 | ![change_email_example](https://user-images.githubusercontent.com/3693219/140220090-6a271be0-6f3f-4201-80b9-efa1cc2d3baf.png) 92 | 93 | ### Do use snippets when pasting large amounts of code 94 | 95 | Pasted code can easily fill the entire chat window and be difficult to read. For this reason it is highly preferred that our users to take advantage of Slacks's [snippets](https://slack.com/help/articles/204145658-Create-or-paste-code-snippets-in-Slack) feature when sharing code. 96 | 97 | Not only does this feature make the code easier to read via language-specific syntax highlight, it becomes collapsible and easier to copy and paste for others who may want to test your code locally. 98 | -------------------------------------------------------------------------------- /sandbox.md: -------------------------------------------------------------------------------- 1 | # Getting an SFCC Sandbox 2 | 3 | ### For Customers and Partners 4 | 5 | There are three main ways to get sandboxes for Salesforce B2C Commerce: 6 | * For customers and prospects: Please reach out to your Commerce Cloud Account Executive 7 | * For System Integrator (SI) partners: reach out to your Partner Manager, or see details [here](https://partners.salesforce.com/pdx/s/learn/article/b2c-commerce-MCDSZA63SNTNCRRBPDZX3PU7OGWI?language=en_US) about becoming a Salesforce Partner where you can get your own sandboxes 8 | * For ISVs and ISV prospects: You can complete [this form](https://1.appexchange.com/LINK-contact-us) if you are looking to be an ISV Partner where you can get a trial sandbox 9 | 10 | ### For Other Uses 11 | 12 | For any other reason for a sandbox, reach out to [@Andrew Lawrence](https://sfcc-unofficial.slack.com/team/UMN1ZJME3) in the SFCC Unofficial Slack. There are no promises for other use cases -- it will depend on what you are looking to use it for, who you are working for, length of time you need it, etc. 13 | -------------------------------------------------------------------------------- /terms-of-use.md: -------------------------------------------------------------------------------- 1 | # Terms of Use 2 | 3 | By joining the Unofficial SFCC Slack, hereby the "community", you agree to be bound by the following terms: 4 | 5 | ## Good Faith 6 | 7 | You agree that you will use the community in good faith with honesty and fairness. The Administrators also agree to operate in good faith with honesty and fairness. 8 | 9 | ## Unofficial Capacity 10 | 11 | You agree that you understand that any information or opinions shared within the community, even by Salesforce employees shall not be considered official guidance or statements by Salesforce. 12 | 13 | ## Recruiting and Job Opportunities 14 | 15 | You agree that no professional recruiting shall be performed within the community. Professional recruiting shall be considered as behaviors typically performed by a recruiting profession including, but not limited to: 16 | 17 | * Soliciting applicants for a job that you have been professionally engaged to locate applicants 18 | * Soliciting applicants directly via Direct Messaging 19 | * Soliciting clients to hire you to locate applicants 20 | 21 | You agree that you may: 22 | 23 | * Post job opportunities for your direct organization within the `#careers` channel. 24 | 25 | ## Non-Commercial Use 26 | 27 | You agree to use the community only for: sharing information, asking and answering questions, and other discussion with members of the community. You agree that you will not use the community for any business operations or business communications for yourself or your employer. 28 | 29 | Using the Slack community to communicate with your clients or prospective clients about a project or pitch is forbidden. Please start your own company or project-specific Slack community and manage that yourself. 30 | 31 | Posting any message that can be interepreted as an ad about you or your company's products or services is prohibited unless it directly relates to a question being asked. For example: if someone wants a tool for managing product images, and your company makes one, you're welcome to briefly mention the existence of your company's product as a solution, as shown below. 32 | 33 | > **Jane Slack User**: Does anyone have any recommendations for a good image or asset management solution? 34 | > 35 | > **Joe Employee**: My employer, Example Technologies, makes a product called "Asset Management Deluxe" that may be a good option for you. 36 | 37 | ## Privacy 38 | 39 | You agree that any information shared within the slack is no longer considered private and as a semi-private community there is no expectation of privacy. Anything you share within the community is potentially accessible to others and may be saved by those persons for their personal use. 40 | 41 | ## Indemnity 42 | 43 | You agree that the operators of this community including its Administrators and the "Owner" of the Slack account cannot be held liable for any damages resulting from the use of the community or the information contained within. 44 | -------------------------------------------------------------------------------- /tools.md: -------------------------------------------------------------------------------- 1 | # Community Tools 2 | This is a list of tools/projects developed by community members. Feel free to contribute or suggest new tools. 3 | If you have any question, suggestion or just want to chat about any of these tools, [join our #community-tools Slack channel](https://sfcc-unofficial.slack.com/archives/C05T19F4J4A). 4 | 5 | ## Table of Contents 6 | - [Community Tools](#community-tools) 7 | - [Table of Contents](#table-of-contents) 8 | - [CI](#ci) 9 | - [Productivity](#productivity) 10 | 11 | ## CI 12 | **[`^ back to top ^`](#community-tools)** 13 | - [OSF Builder Suite For Salesforce Commerce Cloud :: Deploy](https://plugins.jenkins.io/osf-builder-suite-for-sfcc-deploy/) - Easy-to-use and highly configurable Jenkins plugin that is used to deploy your builds to your Salesforce Commerce Cloud continuous integration sandbox, development or staging instance. 14 | - [OSF Builder Suite For Salesforce Commerce Cloud :: Data Import](https://plugins.jenkins.io/osf-builder-suite-for-sfcc-data-import/) - Easy-to-use and highly configurable Jenkins plugin that is used to automate data imports to your Salesforce Commerce Cloud continuous integration sandbox, development or staging instance. 15 | - [OSF Builder Suite For Salesforce Commerce Cloud :: Run Job](https://plugins.jenkins.io/osf-builder-suite-for-sfcc-run-job/) - Easy-to-use and highly configurable Jenkins plugin that is used to run your Salesforce Commerce Cloud jobs on your continuous integration sandbox, development or staging instance. 16 | 17 | ## Productivity 18 | **[`^ back to top ^`](#community-tools)** 19 | - [DWWithEase Chrome Plugin](https://dwithease.com) - Helpful plugin to ease user interactions in the Salesforce Commerce Cloud B2C Business Manager application. ([#dwwithease channel](https://sfcc-unofficial.slack.com/archives/CJK7QH8NR)) 20 | --------------------------------------------------------------------------------