Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

SinglePaged - Simple Jekyll template

License

NotificationsYou must be signed in to change notification settings

z-pattern-matching/z-pattern-matching.github.io

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

79 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Here're some examples:

Why?

Got somekiller app, someneat project, a cool portfolio? Make an easy single-page site to show it all off. SinglePaged uses jekyll niceties to make apolished, modular, and beautiful single page site.

  • Each vertical section is a markdown file in_posts/ directory.
    • They're sorted by 'date'. (we don't use date anywhere, it only sorts)
  • Each vertical section sets it's owncolor,header icon (or image),title, and easy-to-write markdown body.
  • Onlytwo things to edit:
    1. Edit_config.yml to set the site title, description, etc
    2. Add _posts/*.md to make each vertical section. Copy some examples and add the sections from your README.md for a fast start!
  • Easy adding ofSEO terms,favicon & such, andgoogle analytics token.

Sound good? Let's go!

There are three way to get started: (links jump to that section)

  1. Make auser homepage (or organization)
  2. Make astandalone project page
  3. Make asite under anexisting project

Setup as user homepage

  • Go clickfork on thegithub project page
  • Rename your new repository to**username**.github.io. (click settings in the right column)
  • Clone your repository,cd into the project
  • Rungit checkout publish && git branch -m master && git push -u origin master && git branch -D gh-pages to get thepublish branch as master for a clean, empty starting point.
  • On your github project page go tosettings again and change yourdefault branch tomaster
  • Rungit push origin --delete gh-pages to delete your remote's development branch

Now hop over toUsage to get it running with your own stuff!

When you publish changes usegit push -u origin master


Setup as standalone project page

  • Go clickfork on thegithub project page
  • Rename your new repository towhatever you want. (click settings in the right column)
    • It will go live at yourusername.github.io/WhateverYouWant
  • Clone your repository, cd into the project
  • Rungit checkout publish && git branch -D gh-pages && git branch -m gh-pages && git push -uf origin gh-pages to swap thepublish andgh-pages branch.

Now hop over toUsage to get it running with your own stuff!

When you publish changes usegit push -u origin gh-pages


Setup inside existing project

This is the most complicated use-case .. but it's the coolest.Say you've got your kickass projectgithub.com/t413/kicker and want to havesome web presence to post about onhacker news.This will create an orphan branch calledgh-pages in your repositorywhere you can publish changes, posts, images, and such. It won't alter your code at all.

  • cd into your project on the command line
  • usegit remote add -t publish singlepage git@github.com:t413/SinglePaged.git to get access to this repository.
  • usegit fetch singlepage publish:gh-pages to fetch the remote branch
  • usegit branch --set-upstream-to gh-pages singlepage/publish && git checkout gh-pages;This creates and checks out an orphan branch called gh-pages that tracks the original and lets you make changes.
  • When you rungit push origin gh-pages it'll be live atyourusername.github.io/repositoryName

Now hop over toUsage to get it running with your own stuff!

When you publish changes usegit push -u origin gh-pages

Usage

Alright, you've got a clean copy and are ready to push some schmancy pages for the world to ogle at.

  • Edit_config.yml to change your title, keywords, and description.
  • Create a new file in_posts/ called2014-01-01-intro.mdEdit it, and add:
  ---  title: "home"  bg: white     #defined in _config.yml, can use html color like '#010101'  color: black  #text color  style: center  ---  # Example headline!  and so on..
  • Create a second post called2014-01-02-art.md with an divider image this time:
  ---  title: "Art"  bg: turquoise  #defined in _config.yml, can use html color like '#0fbfcf'  color: white   #text color  fa-icon: paint-brush  ---  #### A new section- oh the humanity!

Note: That partfa-icon: paint-brush will use a font-awesome icon ofpaint-brush. You can use any icon from thisfont-awesome icon directory.

  • install Jekyll withsudo gem install github-pages
  • runjekyll serve -w
  • Push changes and see them live!

Changing your colors

  • In each post file you can definebg: mycolor andcolor: myothercolor to change the background and text colors for that section.
  • mycolor can be a quoted html color like'#0fbfcf' or a key to a special color defined in_config.yml under 'colors'.
    • Note: Changes to _config.yml require a manual restart to your local server with^C andjekyll serve -w.

Nifty, right!

Updating

So you've got a copy running and there's some new update? Let's update!

  1. Checkout your github-pages branch
  • git checkout gh-pages for a standalone or existing page
  • git checkout master for ausername.github.io page
  1. rungit remote | grep -q "singlepage" || git remote add -t publish singlepage https://github.com/t413/SinglePaged.git to be sure you have access to this repository (you can run this command at any time).
  2. git fetch singlepage to fetch-in-place new changes.
  3. Update to the new base (using merge)
    1. git merge singlepage/publish
  4. You can alternatively update using rebase. Thisrewrites history (bad), but it is cleaner.
    1. git rebase singlepage/publish

About

SinglePaged - Simple Jekyll template

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • CSS77.3%
  • JavaScript11.6%
  • HTML10.8%
  • Ruby0.3%

[8]ページ先頭

©2009-2025 Movatter.jp