alembic-jekyll-theme 0.1.2 → 0.1.3

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +13 -14
  3. data/_layouts/default.html +1 -1
  4. metadata +16 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: b154dc633509f1e8c077176b04fc8beb596f9146
4
- data.tar.gz: f8acaa96aefa7761be837206f1c6578b0b9227cb
3
+ metadata.gz: d234ab67db429193c79fe92b135899c1426f5cbf
4
+ data.tar.gz: 63d0dcc07965358d4c4622bc719993d23a692175
5
5
  SHA512:
6
- metadata.gz: 9b6335df9c27c2054ce143d6e4463cf4f83ac7960e402ee03f7cc39bf4c6d8b2044003e4a3513314be4733d2faf4a938c17482d6a1e6eed4ba2784d5f0c99f97
7
- data.tar.gz: c99f097fb128822fb61effe554d3bca5eeabbd8ea2a95126df3cd0ee7bec6da7c60d417502c5c0536d8dbacd7a43ba3818f0f54572ebb7e0132d5d8fc6fa60ff
6
+ metadata.gz: 5916bc1e97327a62c2ce84d7e75784f1babec2506b787c67d7caae08d8cdabb2e84ec6a994b591997685995488bcb094281374708e029ec5cb6f6a2569e139f0
7
+ data.tar.gz: 9ed28812e5dc7eaf76a1d47e97256180a0067e528c00b4aa659ca0b9cc5b7c0387b586694176698c391abe2891ec301dbf272056da6fd57d0943db1440ef3734
data/README.md CHANGED
@@ -39,29 +39,28 @@ Alembic is a starting point for [Jekyll](https://jekyllrb.com/) projects. Rather
39
39
 
40
40
  ## Installation
41
41
 
42
- ### As a boilerplate kit
42
+ ### As a Boilerplate / Fork
43
43
 
44
- 1. Fork the repo
44
+ 1. [Fork the repo](https://github.com/daviddarnes/alembic#fork-destination-box)
45
45
  2. Clone down the repo with `$ git clone git@github.com:username/reponame.git`
46
- 3. Delete the `demo/` folder, `alembic-jekyll-theme.gemspec` and `screenshot.png` files
47
- 4. Open the `/_config.yml` file and change details to your own project details
48
- 5. Change the `CNAME` record to your projects' record
49
- 6. Install GitHub Pages locally with `$ gem install github-pages`
50
- 7. Run Jekyll from inside the the root of the repo using `$ jekyll serve --watch`
46
+ 3. Delete the `demo/` folder and `screenshot.png` files
47
+ 4. Change the `CNAME` record to your projects' record
48
+ 5. Install bundler with `$ gem install bundler`
49
+ 6. Install gems with `$ bundle install`
50
+ 7. Run Jekyll with `$ bundle exec jekyll serve --watch`
51
51
  8. Begin hacking for your project
52
52
 
53
53
  ### As a Jekyll 3.3 theme gem
54
54
 
55
- 1. Install the gem with `$ gem install alembic-jekyll-theme`
56
- 2. Download the starter `/demo` content, [quick download link](https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/daviddarnes/alembic/tree/master/demo)
57
- 3. Customise demo content to your project content
58
- 4. Open the `/_config.yml` file and change details to your own project details
59
- 5. Run Jekyll from inside the the root of the repo using `$ jekyll serve --watch`
60
- 6. Begin hacking for your project
55
+ 1. Download the starter `/demo` content, [quick download link](https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/daviddarnes/alembic/tree/master/demo)
56
+ 2. Install bundler with `$ gem install bundler`
57
+ 3. Install gems with `$ bundle install`
58
+ 4. Run Jekyll with `$ bundle exec jekyll serve --watch`
59
+ 5. Begin hacking for your project
61
60
 
62
61
  ### Boilerplate & Theme differences
63
62
 
64
- The boilerplate kit is better for more drastic hacking and changes, a project that's quite different to any other and needs a lot of custom work done. Additionally, you'll only be able to use this method if you want to host it on GitHub Pages, as themes can't be submitted so [this one hasn't been approved](https://pages.github.com/themes/)... yet.
63
+ The boilerplate kit is better for more drastic hacking and changes, a project that's quite different to any other and needs a lot of custom work done. Additionally you'll only be able to use this method if you want to host it on GitHub Pages, as [themes can't be submitted](https://pages.github.com/themes/)... yet.
65
64
 
66
65
  Using the theme will allow you to receive updates made and will be more programmatic. To make your own changes you'll need to overwrite the files with your own. For example: If I want to change the colours of my site I'll need to copy the [`_colors.scss`](https://github.com/daviddarnes/alembic/blob/master/_sass/_colors.scss) file and create my own in `_sass/colors.scss` with my own changes. This is the same for all files within the theme, which means your own project will be more lean than if you were to use the boilerplate.
67
66
 
@@ -17,7 +17,7 @@
17
17
  {% seo %}
18
18
  {% endif %}
19
19
 
20
- <link rel="stylesheet" href="/assets/styles.css">
20
+ <link rel="stylesheet" href="{{ "/assets/styles.css" | relative_url }}">
21
21
 
22
22
  {% include site-favicons.html %}
23
23
  </head>
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: alembic-jekyll-theme
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.2
4
+ version: 0.1.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - David Darnes
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-10-10 00:00:00.000000000 Z
11
+ date: 2016-10-13 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: jekyll
@@ -122,6 +122,20 @@ dependencies:
122
122
  - - "~>"
123
123
  - !ruby/object:Gem::Version
124
124
  version: '0.7'
125
+ - !ruby/object:Gem::Dependency
126
+ name: bundler
127
+ requirement: !ruby/object:Gem::Requirement
128
+ requirements:
129
+ - - "~>"
130
+ - !ruby/object:Gem::Version
131
+ version: '1.12'
132
+ type: :development
133
+ prerelease: false
134
+ version_requirements: !ruby/object:Gem::Requirement
135
+ requirements:
136
+ - - "~>"
137
+ - !ruby/object:Gem::Version
138
+ version: '1.12'
125
139
  description: Alembic is a starting point for Jekyll projects. Rather than starting
126
140
  from scratch, this boilerplate is designed to get the ball rolling immediately.
127
141
  email: