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

Consider Using Coding With The Force’s Apex Common Wiki as the documentation for this library #386

Open
Coding-With-The-Force opened this issue Nov 16, 2021 · 6 comments
Labels
discussion on hold Signifies that the PR is "on hold" pending outcome of internal team discussions. question

Comments

@Coding-With-The-Force
Copy link

Hey there, I realize I'm kind of promoting my own material here, but everywhere I've been people have hated using this library despite how incredible it is because there is virtually no documentation on how to use it. So I made a ton of extremely thorough documentation on it.

I spent 200+ hours creating a wiki outlining how to use this library and what separation of concerns is and created ~17 hours worth of training tutorial videos for it.

I would like to request to increase user adoption for this library that you consider leveraging my wiki to help educate people on how to use this incredible free resource.

You can find the repo here: https://github.com/Coding-With-The-Force/Salesforce-Separation-Of-Concerns-And-The-Apex-Common-Library

And a direct link to the wiki here: https://github.com/Coding-With-The-Force/Salesforce-Separation-Of-Concerns-And-The-Apex-Common-Library/wiki

Thanks a bunch,
Matt Gerry

@Coding-With-The-Force
Copy link
Author

I also just want to state that since I've created this, I've personally tested it and used it to train 17 developers of varying skill levels how to use this library and they all now understand it and are able to easily leverage it. Before I created it I don't know that I could've ever convinced most devs to use this library. It's made it much easier for me to get my projects on board with leveraging it.

@ImJohnMDaniel
Copy link
Contributor

G'day @Coding-With-The-Force. Thanks for the question. Let the team review the materials and we will get back to you with any questions or comments. Cheers!

@ImJohnMDaniel ImJohnMDaniel added discussion on hold Signifies that the PR is "on hold" pending outcome of internal team discussions. question labels Nov 30, 2021
@Coding-With-The-Force
Copy link
Author

Hey there @ImJohnMDaniel, just checking in on this since it's been a few months now. No worries if you guys aren't interested I was just trying to help with it being more widely adopted because I'm a big fan of what's been built and maybe make it easier for those interested in helping with the library to make additions or resolve issues.

@rr-salesforce
Copy link

Bump for effort on the wiki

@matthewpomar-at-reddit
Copy link

matthewpomar-at-reddit commented Feb 23, 2023

Matt Gerry's documentation and videos are the most complete and comprehensive our team has found and has certainly made it so that our team can quickly adopt this library. Not sure I could have gotten my team onboard with this if his content didn't exist. At the very least, I think it would be worth linking to his Wiki and videos from this project's Documentation section.

Thanks for putting all that great content together @Coding-With-The-Force !

@bdJohnson72
Copy link

I also use Matt's documentation to help my team adopt the library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion on hold Signifies that the PR is "on hold" pending outcome of internal team discussions. question
Projects
None yet
Development

No branches or pull requests

5 participants