... | ... | @@ -19,5 +19,16 @@ In my experience there are 2 approaches you can take: |
|
|
1. the extension approach where you give them the basics of extension development and only mention that there is also buildkit, unit tests and core bugs but ONLY mention it. This is the approach I prefer as it allows me enough time to ensure the basics of extension, API, hooks, pages and forms are covered and understood by all. The ambitious ones will then certainly find out how to fix core bugs with the documentation or at a next sprint. I firmly believe in unit testing but I also believe it then makes for a heavy load for 2 days.
|
|
|
|
|
|
There is no list of topics that you have to cover in your training. Obviously it makes sense to talk about extensions, civix, API and hooks. Below is a list of topics I cover:
|
|
|
* presentation round (who are you, what is your CiviCRM experience, what do you want to take home from the training)
|
|
|
* civicrm developer community & information resources (Developer Guide, StackExchange, Mattermost, Gitlab)
|
|
|
* extensions
|
|
|
* pages
|
|
|
* API
|
|
|
* hooks
|
|
|
* forms
|
|
|
* some real life examples
|
|
|
* if I have time left: upgrader, custom searches, reports, entities
|
|
|
|
|
|
# Running the training |
|
|
\ No newline at end of file |
|
|
# Running the training
|
|
|
|
|
|
You usually need time for setup. |
|
|
\ No newline at end of file |