Hosting bookdown in github

[itsmecevi]

Anybody knows how to publish my bookdown into github?

Thx
/cevi

[technocrat]

Read all about it in Publishing Bookdown to github by @yihui

[itsmecevi]

Thank you. The link is a little bit confusing for me (a lot of technical terms). Do you have some of video or another simple tutorial @technocrat

[technocrat]

Check

Using Bookdown for tidy documentation

http://seankross.com/2016/11/17/How-to-Start-a-Bookdown-Book.html

A Minimal Book Example

How to self-publish a book: Customizing Bookdown

Open tools for writing open interactive textbooks (and more)

and the collection of related videos at

https://www.google.com/search?q=bookdown+github&source=lnms&tbm=vid&sa=X&ved=0ahUKEwjq5ve-yrffAhUqxlQKHfTKCLwQ_AUIDigB&biw=1290&bih=814

However, there's really no substitute for DIY and sweating the small stuff from a minimal working example, such as the one given in the primary resource and working your way through increasing bells and whistles.

When, back in the second Reagan administration, I was a law student, my classmates spent a ton of money and time looking for the answers in a variety of so-called hornbooks and other study guides when they should have been paying attention to the questions. I was lucky. My contracts prof told us that everything we needed to know was in the table of contents of the casebook, and the rest was merely detail. Needless to say, I didn't believe him at first, and I kept looking for the answers until I was called to jury duty.

I looked around. There was the judge, the bailiff, the court clerk, the stenographer, the plaintiff's attorney and the defendant's attorney. I did the math. As a juror, it would be my job to give an answer guilt/not guilty or liable/not liable. I got paid $10/day plus parking. At that time, the lawyers were probably getting around $250/hour for knowing the right questions to asked. That's what tripped me to the realization that the questions are far more important than the answers. The same question will always have different answers.

[itsmecevi]

Thank you-@technocrat. I will try it.

[cderv]

If your question's been answered (even by you!), would you mind choosing a solution? It helps other people see which questions still need help, or find solutions if they have similar problems. Here’s how to do it:

FAQ: How do I mark a solution?

If your question has been answered, don't forget to mark the solution! How do I mark a solution? Find the reply you want to mark as the solution and look for the row of small gray icons at the bottom of that reply. Click the one that looks like a box with a checkmark in it: [image] Hovering over the mark solution button shows the label, "Select if this reply solves the problem". If you don't see the mark solution button, try clicking the three dots button ( ••• ) to expand the full set of options. When a solution is chosen, the icon turns green and the hover label changes to: "Unselect if this reply no longer solves the problem". Success! [solution_reply_author] …

[apreshill]

If you mean you would like to use GitHub pages to publish or deploy your bookdown project and:

a) you would like to place the rendered book (i.e., the folder _book is not in your .gitignore file) on GitHub
b) further, you are OK with placing your rendered book in a folder on your "master" GitHub branch
c) even further, you are OK with using a project domain name like http(s)://<username>.github.io/<projectname>

Then you can take advantage of a neat trick with GitHub pages which allows you publish to GH pages from the master branch /docs folder. To do that:

1. Configure source for GH pages through GitHub website as master branch /docs folder
2. Go to your _bookdown.yml file and add output_dir: "docs" on a line by itself
3. Serve/preview your book locally
4. Push to GitHub, you should see it there.