03--More_about_Jekyll.md - Carlos Donze

[thedonz]

• Practice terminal commands:
  • Try Github
  • CodeSchool: Git Real
  • Everyday Git
  • Treehouse: Console Foundations
  • Extra Credit: Treehouse: Technology Foundations (How the internet works, 101).
• Make a list of the terminal commands that we have covered...
  • Follow the instructions in TheIronYard--Orlando/FEE--2014--FALL#63
  • Collaborate!
• Trick out your Github pages with a Jekyll theme...
  • Make sure you have merged all your feature branches with Pull Requests first!
  • Create a new branch for this work based on master
    • Check out the master branch again and use git pull to get your work from Github.
    • Create a new branch named feature/jekyll-theme.
    • Check out the new feature/jekyll-theme branch.
  • Convert index.html into a simple Jekyll template...
    • Create an index.md file in the project root.
    • Take everything from the middle of index.html, rewrite in Markdown, put into index.md
    • Add two lines to the front of index.md with three dashes (---) each, called YAML Frontmatter.
    • Create a folder in project root called _layouts.
    • Move the index.html file into _layouts/default.html.
    • Try to rebuild your site with jekyll build; what happens? Comment on this...
    • Put {{content}} into the middle of _layouts/default.html (where you took index.md out).
    • Build your site with jekyll build; what happens? Comment on this...
  • Push to Github; open a PR; link your PR to your issue.
  • Edit your index.md file to link your posts using Markdown (and server-relative URLs).
  • Commit and push these changes to Github; what happens to your PR? Comment on this...
• Write a post about today in your Github Pages blog...
  • Add a new file to your _posts directory in C9, write stuff!
  • Rebuild your site with Jekyll and check out the awesome via C9!
  • Push your post to Github and check it out on your website!
  • Add a link to your blog post into your issue!
  • Add a link to your blog post to your index.md file!
  • Push to Github!

[thedonz]

• Fork this repository into your own account; use the terminal-commands branch for this assignment.
  *In the file Notes/terminal-commands.md:
  • Add some terminal commands that we know (and some options that we've used) inside of "code blocks" (see Github Flavored Markdown)
  • Add a description of the command and the flags that we know how to use after the code block.
• Open a Pull Request from your terminal-commands branch to the terminal-commands branch in this repository.
• Add a link to this Pull Request in your Pull Request using the Github shortcut: TheIronYard--Orlando/FEE--2014--FALL#63

Please add questions about this assignment to this PR, so that everyone can see your question and help answer it.

[thedonz]

when trying to build the jekyll site, I get the following error
Configuration file: none Source: /home/ubuntu/workspace Destination: /home/ubuntu/workspace/_site Generating... jekyll 2.4.0 | Error: undefined methoddefault_proc=' for #String:0x00000001d529c8`

[thedonz]

Tried proceeding to the next step and still got this error:

"Configuration file: none Source: /home/ubuntu/workspace Destination: /home/ubuntu/workspace/_site Generating... jekyll 2.4.0 | Error: undefined methoddefault_proc=' for #String:0x000000018a1320"`

[thedonz]

Had a few errors along the way

[al-the-x]

So when you run into errors during my intentionally vague assignments, you should probably stop and look around. I'll try really hard not to lead you down a path that leads to a land mine... But if I do, you can be reasonably sure that others in the class will step on it, too.