anchor.diff:  
   image::https://user-images.githubusercontent.com/2006548/80399009-ce9d5980-88b8-11ea-9bea-9bd34cc71216.png[]
   
  -The password is not the one you use for GitLab or GitHub, it is a password you will have to define, to encrypt you personal token in your localStorage. So you will not have to remember your personal token to login, only this password.
  +The password is not the one you set on GitLab or GitHub, it is a password you will have to define and it will be use to encrypt you personal token in your localStorage. 
  +So you will not have to remember your personal token to login, only this password.
   
   The last (maybe not 🤔) step is the configuration of your repository.
   
  
positive.code: Here again, two possibilities, if you use GitLab or GitHub, all the fields are in read-only because they are calculated. 
  If not, you will have to fill the form by your own.
  
  I think the onboarding is now really better than just a config.json file, maybe you agree, maybe not, feel free to give me your feedback.
  
  That's all for today, in a future article,i'll explain how i calculate all the stuff about GitHub and GitLab and how i validate datas.
  
  
  
  
negative.code: 
  This kind of stuff is ok for a developer maybe, but certainly not enough for great user experience.
  
  My goal with my tools is to provide a UX between Jekyll and Wordpress or Ghost for {url_ohmypages}[ohmypages!] and between RevealJS with HTML and PowerPoint for {url_ohmydeck}[ohmydeck!], so it was clear for me that I had something to do with the *onboarding*.
  
  So, here is what I did
  
  I started with a *Welcome*, I'm not sure about the content yet but... we'll see 😄
  
  