Restructure the layout of the tutorial into a GitBook

[sohilpandya]

After having the standup on 1st December, Ines/Nelson recommended that we update the layout of the tutorial.

It needs to be:

• easy to follow for both beginners/non-beginners
• clear structure, something along the lines of this https://github.com/evancz/guide.elm-lang.org

[nelsonic]

@sohilpandya the reason for recommending a GitBook https://www.gitbook.com/ is because it creates a linear learning process which I find useful when learning something from scratch. 😉

[sohilpandya]

I am planning to tackle this in the afternoon today, I was going to setup a GitBook with the following structure, to begin with:

- Introduction to Learn Apple Watch Development
- Setup
- Basics of Swift
  - variables
  - control flow
  - functions
  - etc.
- Tutorials
  - iPhone
    - Calculator
    - FoodTracker
  - Apple Watch
    - Simple Counter
  - iPhone + Apple Watch
    - Interaction App (interaction on AW to represent changes on iPhone)

How does that look @nelsonic?

[nelsonic]

@sohilpandya looks like a good structure. (can always be incrementally improved through user-feedback later...) 👍

[sohilpandya]

Thanks @nelsonic for merging the PR! 👍

I thought that PR would solve the issue of the GitBook not showing up correctly, but it doesn't seem to have done the trick. 😢

I'll have to look into why the summary.md page is not being recognised as the entry.

[nelsonic]

@sohilpandya good plan (next action) 👍
If you're stuck with GitBook, you can always #HelpWanted and ask friends who do git-booking every day... 😉

[sohilpandya]

@nelsonic Thanks for that action plan, unfortunately, I won't have time until later this week to have a look at what is causing this particular issue, so I have added the help wanted label. Will try to sort this issue out before the Christmas break! 🎄

[nelsonic]

@sohilpandya sounds good. the repo is already in pretty good shape so people can start using the tutorial to get "up-and-running" with swift...

Note: we need to get a lot more systematic about our use of help wanted in all our projects in 2017! I'm excited! see: dwyl/labels#44 😉 CC: @markwilliamfirth

[sohilpandya]

@nelsonic do we have a dwyl organisation for gitbook or is it ok for me to create one?

[nelsonic]

@sohilpandya yes, we do.
login with: dwyl or [email protected]
(I've messaged you the password)

[sohilpandya]

@nelsonic I'm having trouble logging into GitBook 😢

Used both the above logins emails along with the password that you had sent me.

[nelsonic]

@sohilpandya are you @sciencemuseum today? remind me and we can pair on logging in and setup. 👍

[sohilpandya]

@nelsonic I am @sciencemuseum today, catch you shortly!

[sohilpandya]

@nelsonic thanks for helping out with the sign-up process I can confirm that the email address for login is [email protected], there are still a couple of things that need to happen for us to link this repo to the DWYL gitbook.

• verify ownership via email
• link the GitHub organisation to this account
• update user profile image

[sohilpandya]

I've sent a message to GitBook with regards to us not being able to link the GitHub account.

Currently getting this error message:

They may get back to us on the hello email, so it'd be great if you kept an eye on it! 😄

[nelsonic]

@sohilpandya you do have a @dwyl email address right?
Have you tried emailing them?

[sohilpandya]

@nelsonic I did send a message with regards to the error above, but have just sent another one asking for steps to connect this org to the gitbook account.

[ghost]

this ok to do @nelsonic ?

[ghost]

or should we install globally? Not sure if write access to code means it pushes to master?

[iteles]

@markwilliamfirth Write access is fine (and required for what gitbook does). We should also set up with just the repos we want for now so I agree with the way you're proposing Mark!

We can also set up master as a protected branch so that it can't be force pushed or deleted.

Admin access is the one that we're trying to avoid at all costs as that grants access to delete the repo itself.

[ghost]

Cool - done!

@sohilpandya

[nelsonic]

@markwilliamfirth that looks like it should work. thanks! 👍

[sohilpandya]

Thanks @markwilliamfirth for sorting that out.

We finally have our first book on GitBooks! https://dwyl.gitbooks.io/learn-apple-watch-development/content/ 🎉