betterplace-content 0.7.14 → 0.7.16
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +24 -4
- data/_sass/about-us/transparency.sass +1 -1
- metadata +3 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: f79374c5a57a1c20de8e19f186aa59c1e6eff65cac9600ca882abf29dd0f0adf
|
|
4
|
+
data.tar.gz: 35928ba925d3b6eae0b3b7bede2ab173976bb8495281b466cd7775e9bc1f0106
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6552aefde57f8b3dca1df11b56a51690dbc3ba2acbec8ec6d080d08a96cec6baee328ba49e1808b279599b649c4e169458331fe3b872b4fd0072f0063afb2e49
|
|
7
|
+
data.tar.gz: dcd27ed464121a8c42b349a186f8b95ddfd751ee8106f7991bb18f6eec1e564e0b091556ed8efcc83e613266399a6c6357531ea5d9da43c039b13f8008ed9f3d
|
data/README.md
CHANGED
|
@@ -22,12 +22,32 @@ And then execute:
|
|
|
22
22
|
|
|
23
23
|
## Development
|
|
24
24
|
|
|
25
|
-
To set up your environment to develop this theme, run
|
|
25
|
+
To set up your environment to develop this theme, run the bootstrap script. Note that
|
|
26
|
+
this will check out **all** betterplace content repositories and install their bundles
|
|
26
27
|
|
|
27
|
-
Your theme is setup just like a normal Jekyll site! To test your theme, run `bundle exec jekyll serve`
|
|
28
|
+
Your theme is setup just like a normal Jekyll site! To test your theme, run `bundle exec jekyll serve`
|
|
29
|
+
and open your browser at `http://localhost:4000`.
|
|
30
|
+
This starts a Jekyll server using your theme. Add pages, documents, data, etc. like normal to test
|
|
31
|
+
your theme's contents. As you make modifications to your theme and to your content,
|
|
32
|
+
your site will regenerate and you should see the changes in the browser after a refresh, just like normal.
|
|
28
33
|
|
|
29
34
|
When your theme is released, only the files in `_layouts`, `_includes`, and `_sass` tracked with Git will be released.
|
|
30
35
|
|
|
31
|
-
##
|
|
36
|
+
## Release a new version
|
|
37
|
+
|
|
38
|
+
There are a number of script to deal with the messy setup of our content pages. Since the theme is used
|
|
39
|
+
in **all** betterplace content pages, there are a number of scripts in `scripts` to make things
|
|
40
|
+
a little easier. Read the comments in those scripts to find out what they do.
|
|
41
|
+
|
|
42
|
+
You can run `script/release-theme` to **attempt an automated update of everything**. This will
|
|
43
|
+
|
|
44
|
+
* Bump the version number of the theme
|
|
45
|
+
* Release the theme to rubygems.org
|
|
46
|
+
* Wait for it to appear
|
|
47
|
+
* Attempt to update all "content" repositories to use the new theme
|
|
48
|
+
|
|
49
|
+
The last step can easily fail. If it does, you can safely re-run
|
|
50
|
+
`script/update-dependencies` as often as you like. Do not re-run the
|
|
51
|
+
release script after the gem was released, or you'll create a new version on
|
|
52
|
+
github every time.
|
|
32
53
|
|
|
33
|
-
See `*.sh`-Files, specifically `content-bundle-update.sh`
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: betterplace-content
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.7.
|
|
4
|
+
version: 0.7.16
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- betterplace.org Developers
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2020-01-29 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: jekyll
|
|
@@ -220,7 +220,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
220
220
|
- !ruby/object:Gem::Version
|
|
221
221
|
version: '0'
|
|
222
222
|
requirements: []
|
|
223
|
-
rubygems_version: 3.0.
|
|
223
|
+
rubygems_version: 3.0.6
|
|
224
224
|
signing_key:
|
|
225
225
|
specification_version: 4
|
|
226
226
|
summary: betterplace.org's Jekyll Content Theme
|