alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-11-13 07:57:02 +01:00
Code Releases Activity
974203f6eb
hugo-theme-bootstrap4-blog/package.json

29 lines
1.2 KiB
JSON
Raw Normal View History

First commit with initial theme Some file are empty (created by `hugo new theme`), but I've left them for reference later.
2016-08-28 15:21:39 +02:00
{
Change theme name to "hugo-theme-bootstrap4-blog" This reflects the target usage better, and pays homage to the fact that it was based on the Bootstrap v4 Alpha blogging example: http://v4-alpha.getbootstrap.com/examples/blog/
2016-09-19 09:26:58 +02:00
"name": "hugo-theme-bootstrap4-blog",
package.json: Bump version to 1.2.1 It looks like I forgot to do this for a few releases.
2019-04-14 15:30:30 +02:00
"version": "1.2.1",
First commit with initial theme Some file are empty (created by `hugo new theme`), but I've left them for reference later.
2016-08-28 15:21:39 +02:00
"description": "A Bootstrap v4 theme for the Hugo static site generator.",
package.json: Only god knows why npm reformatted this
2016-09-13 17:07:35 +02:00
"repository": {
"type": "git",
Change theme name to "hugo-theme-bootstrap4-blog" This reflects the target usage better, and pays homage to the fact that it was based on the Bootstrap v4 Alpha blogging example: http://v4-alpha.getbootstrap.com/examples/blog/
2016-09-19 09:26:58 +02:00
"url": "https://github.com/alanorth/hugo-theme-bootstrap4-blog.git"
package.json: Add git repository
2016-08-28 19:54:53 +02:00
},
First commit with initial theme Some file are empty (created by `hugo new theme`), but I've left them for reference later.
2016-08-28 15:21:39 +02:00
"scripts": {
package.json: Update clean-css and build scripts Bootstrap had previously been staying with clean-css < 4.0 because it introduced some backwards incompatible changes[0], but now I see that they have started using the new version. I have also updated the npm build scripts to take into account the name change to "clean-css-cli" as well as the latest minification options that are being used by Bootstrap themselves[1]. [0] https://github.com/jakubpawlowicz/clean-css#important-40-breaking-changes [1] https://github.com/twbs/bootstrap/blob/v4-dev/package.json
2017-02-15 11:38:03 +01:00
"build:css": "node-sass --output-style expanded --precision 6 source/scss/style.scss static/css/style.css.tmp && cleancss --level 1 static/css/style.css.tmp -o static/css/style.css",
package.json: Add run script to copy font-awesome fonts
2016-09-15 15:30:46 +02:00
"build:fonts": "cp node_modules/font-awesome/fonts/* static/fonts",
package.json: Add run script for cookieconsent
2016-11-13 12:42:22 +01:00
"build:cookieconsent": "cp node_modules/cookieconsent/build/cookieconsent.min.css static/css && cp node_modules/cookieconsent/build/cookieconsent.min.js static/js",
Add tooling to generate SRI hashes for assets Subresource integrity allows user agents to verify that a fetched resource has been delivered without unexpected manipulation[0]. I put theme assets in a json configuration file and save the hashes to a TOML file that Hugo loads via its theme data mechanism[1]. [0] https://www.w3.org/TR/SRI/ [1] https://gohugo.io/extras/datafiles/
2017-01-11 09:32:43 +01:00
"build:generatesri": "node build/sri.js > data/sri.toml",
"build": "npm run build:css && npm run build:fonts && npm run build:cookieconsent && npm run build:generatesri && npm run clean",
package.json: Add clean task to remove temp style Ignoring the temporary, intermediate style in .gitignore works for this project, but the site still ends up with a copy of it in its public folder. It's better to just clean up the temp file after successful generation of the minified style.
2016-09-26 09:06:47 +02:00
"clean": "rm static/css/style.css.tmp"
First commit with initial theme Some file are empty (created by `hugo new theme`), but I've left them for reference later.
2016-08-28 15:21:39 +02:00
},
"keywords": "hugo",
"author": "Alan Orth",
Change license from GPL-3.0 to CC-BY-3.0 It seems as if I was never actually allowed to license this as GPL from the start because the example HTML layouts I based this theme on are part of the Bootstrap documentation, which are CC-BY-3.0. See: https://v4-alpha.getbootstrap.com/examples/
2018-09-12 12:32:36 +02:00
"license": "CC-BY-3.0",
First commit with initial theme Some file are empty (created by `hugo new theme`), but I've left them for reference later.
2016-08-28 15:21:39 +02:00
"devDependencies": {
Update to Bootstrap v4.3.1 See: https://blog.getbootstrap.com/2019/02/11/bootstrap-4-3-0/
2019-02-13 17:38:44 +01:00
"bootstrap": "~4.3.1",
Update dependencies in package.json To keep in sync with upstream bootstrap dependencies.
2019-04-17 12:58:07 +02:00
"clean-css-cli": "^4.3.0",
package.json: Pin cookieconsent to version 3.0.4 for now It looks like they made many updates in version 3.1.0 and I haven't tested it yet.
2018-08-29 11:38:24 +02:00
"cookieconsent": "3.0.4",
package.json: Bump Font Awesome to latest version See the version 4.7.0 pull request with a change log of sorts: https://github.com/FortAwesome/Font-Awesome/pull/10012
2016-11-06 21:54:47 +01:00
"font-awesome": "^4.7.0",
Use rtlcss to make styles appropriate for RTL languages
2019-04-18 21:17:28 +02:00
"node-sass": "^4.11.0",
"rtlcss": "^2.4.0"
First commit with initial theme Some file are empty (created by `hugo new theme`), but I've left them for reference later.
2016-08-28 15:21:39 +02:00
}
}
Copy Permalink