Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestions for improvements in Salesforce page #8391

Closed
anupama-pathirage opened this issue Dec 4, 2023 · 6 comments
Closed

Suggestions for improvements in Salesforce page #8391

anupama-pathirage opened this issue Dec 4, 2023 · 6 comments
Assignees
Labels
Type/Improvement Improvements required on the website.

Comments

@anupama-pathirage
Copy link
Contributor

anupama-pathirage commented Dec 4, 2023

1. Connect Salesforce with e-commerce platforms blade. Can we link to Ballerina library also, so the readers can quickly check on various connector availability.

2. Reword Make sales staff aware of customer issues blade title.

 Making the sales staff aware is one example of usage/interconnections right?  Can we make the title more generic and then use this scenario as the sample? 

e.g. Integrate your internal operations seamlessly, Seamlessly connect your back office systems etc

3. Instead of linking to GitHub directly from each blade, can we add those samples to Pre-buit Integrations and then link that one. That will give a good overview via picture too.

4. Can we simplify the code samples? For example the sample in Utilize AI to extract sales information has lots of stuff with gmail connector which is not that important for the message we need to communicate. Can we either think of different scenario with less work from the given connector or simplify this code?

5. Copy edit the page. There are few punctuation errors etc.

@anupama-pathirage anupama-pathirage added the Type/Improvement Improvements required on the website. label Dec 4, 2023
@chathurace
Copy link
Contributor

  1. +1

  2. IMO, it's better to use more concrete titles than a generic title that readers may not be able to quickly relate to a real scenario.

  3. For this, we need to put all samples under a separate folder. Even though we do that, still I think it's better to give a link for the sample being discussed in each blade.

  4. We need samples that make sense as well. So IMO, code length is reasonable.

@anupama-pathirage
Copy link
Contributor Author

  1. +1
  2. IMO, it's better to use more concrete titles than a generic title that readers may not be able to quickly relate to a real scenario.
  3. For this, we need to put all samples under a separate folder. Even though we do that, still I think it's better to give a link for the sample being discussed in each blade.

@chathurace I didn't get we need to put all samples under a separate folder. What I meant is not to remove the link. Instead of pointing to github directly can we point to individual sample we add to pre-built integrations?

i.e. Having the link in the box below as https://pre-prod.ballerina.io/learn/pre-built-integrations/mysql-to-salesforce-integration/ instead of https://github.com/chathurace/integration-samples/blob/main/salesforce_api/mysql-record-to-sfdc-new-product/main.bal

image
  1. We need samples that make sense as well. So IMO, code length is reasonable.

@sahanHe
Copy link
Contributor

sahanHe commented Dec 8, 2023

5. Copy edit the page. There are few punctuation errors etc.

Updated the github links. I went through the descriptions again and passed them through gramarly and updated the description accordingly

About the 1st comment, where should we put the hyperlink? should i place it parallel to Download Ballerina Button?

@anupama-pathirage
Copy link
Contributor Author

Few more comments. @chathurace / @sahanHe

  1. https://pre-prod.ballerina.io/usecases/salesforce/#custom-edi - Utilizing AI blade is not showing any code related to openAI chat client as it is hidden inside function call. Can we refactor the code a bit to move some of the email logic to separate functions and show the openAI usage in the code of the blade as it is the main highlight here.
image
  1. Check the Blade URLs.
    e.g. https://pre-prod.ballerina.io/usecases/salesforce/#custom-edi is the URL for Utilize AI to extract sales information which is incorrect as custom-edi is not the highlight here, but AI.

  2. Incorrect to say libraries. See Replace standard library with Ballerina library text #7782 (comment)

image

@sahanHe
Copy link
Contributor

sahanHe commented Dec 19, 2023

branch sahan-salesforce-usecases is updated with changes. @sm1990 can you push to the pre-prod?

@anupama-pathirage
Copy link
Contributor Author

Closing as this done and page is live. https://ballerina.io/usecases/salesforce/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type/Improvement Improvements required on the website.
Projects
None yet
Development

No branches or pull requests

3 participants