-
Notifications
You must be signed in to change notification settings - Fork 27
Rework First steps methodology #77
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
base: master
Are you sure you want to change the base?
Conversation
…int and easier to digest
… guides for near-future use. WIP
…e; prepare ground for importing users;
…-first-steps to sync it with latest master changes
…lish phrasing here and there
…change heading structure for clarity; describe mapping naming policices
Because we decided they need to be versioned and thus kept in midpoint/reference. The deleted stubs were worthless in their current state and, thus, could be safely deleted as such.
We don't have a suitable tutorials yet as I had to put the work on GUI guides section on hold to create it in the versioned docs section.
Also adjust (grammar/language) in the Multiple source article.
| . If the account in the secondary system is synchronized to midPoint first, create a user with minimal information in the _draft_ lifecycle state. | ||
| ** Set _unmatched_ situation reaction to _add focus_ to create a new midPoint users if they do not exist yet. | ||
| ** Set _unlinked_ situation reaction to _link_ to ensure the accounts for existing midPoint users will be linked. | ||
| ** Set the mappings as _weak_ and the lifecycle state to _draft_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@licehammer : I am not sure I understand the reason for setting the mapping lifecycle state to draft . I feel I am missing something because according to what I know, a configuration item in draft is not used at all. I may have rewritten the sentence wrong but the original sentence of yours has the same meaning, I think.
(BTW, I hereby deeply apologize for moving and making changes to the file in the same commit in which the move was not picked up as a rename but as a delete & create.)
This PR presents the completely reworked First steps methodology. My goal was to make the guide work as a standalone series of articles (modules) that are independent on the video presentations in the original MID-301 First steps training (unlike the original 6-article First steps methodology we currently have in the Documentation). One of the reasons is that I believe it may be for many users more comfortable and beneficial to follow a textual guide rather than watching videos because following text guides supports the learning process better, I think. I used the original training as a foundation for the content in the First steps guide I have written.
I would hereby like to kindly ask for a review of my work here. I would be grateful for validation (or rejection for that matter) of the learning flow, the value for learners, and for pieces of advice on what can possibly be improved in that regard, as I find the flow and learning value the most important aspects of such a guide. However, I will be happy to hear any remarks, of course.
I am assigning this to you, @dejavix , since the original course is your work, but please feel free to delegate as you see fit; I am aware it is a lot of content and the time invenstment is substantial. Obviously, I count on the fact the review may take some time, that is completely fine.
I am tagging for visibility @licehammer and @jirihuf .