jekyll-theme-fica 0.2.0 → 0.3.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (62) hide show
  1. checksums.yaml +4 -4
  2. data/.github/ISSUE_TEMPLATE/bug_report.md +38 -0
  3. data/.github/ISSUE_TEMPLATE/feature_request.md +20 -0
  4. data/.github/workflows/ci.yaml +5 -2
  5. data/.github/workflows/ci.yaml.orig +34 -0
  6. data/404.html +12 -10
  7. data/License.md +2 -8
  8. data/README.md +53 -49
  9. data/_includes/Footer.html +88 -85
  10. data/_includes/Head.html +24 -12
  11. data/_includes/Header.html +21 -34
  12. data/_includes/assets/BTT.html +8 -0
  13. data/_includes/{Google-Analytics.html → assets/Google-Analytics.html} +12 -12
  14. data/_includes/assets/anchor-headings.html +164 -0
  15. data/_includes/assets/comments.html +16 -0
  16. data/_includes/assets/toc.html +174 -0
  17. data/_layouts/default.html +16 -14
  18. data/_layouts/home.html +25 -67
  19. data/_layouts/page.html +5 -3
  20. data/_layouts/post.html +48 -52
  21. data/_layouts/post_list.html +103 -0
  22. data/_posts/2022-03-31-To-Know-if-the-nav-works.md +9 -8
  23. data/_posts/{2022-04-1-Demo.md → 2022-04-1-Elements-of-Fica-Theme.md} +111 -113
  24. data/_posts/2022-04-5-Getting-Started.md +149 -149
  25. data/_posts/2022-04-6-Creating-a-new-post.md +144 -136
  26. data/_posts/2023-04-24-Fica-Customization.md +43 -0
  27. data/_sass/base.scss +437 -0
  28. data/_sass/{themes/dark theme/highlight.scss → colors/dark-theme/highlight.scss} +362 -362
  29. data/_sass/{themes/dark theme/theme-dark.scss → colors/dark-theme/theme-dark.scss} +132 -142
  30. data/_sass/{themes/light theme/highlight.scss → colors/light-theme/highlight.scss} +198 -198
  31. data/_sass/{themes/light theme/theme-light.scss → colors/light-theme/theme-light.scss} +126 -136
  32. data/_sass/jekyll-theme-fica.scss +1 -8
  33. data/_sass/layouts/Google-fonts.scss +103 -138
  34. data/_sass/layouts/component.scss +272 -0
  35. data/_sass/layouts/layout.scss +657 -718
  36. data/_sass/layouts/typography.scss +492 -0
  37. data/_sass/layouts/variable.scss +215 -0
  38. data/assets/css/Style.scss +4 -13
  39. data/assets/favicons/android-chrome-192x192.png +0 -0
  40. data/assets/favicons/android-chrome-512x512.png +0 -0
  41. data/assets/favicons/apple-touch-icon.png +0 -0
  42. data/assets/favicons/browserconfig.xml +9 -0
  43. data/assets/favicons/favicon-16x16.png +0 -0
  44. data/assets/favicons/favicon-32x32.png +0 -0
  45. data/assets/favicons/favicon.ico +0 -0
  46. data/assets/favicons/mstile-150x150.png +0 -0
  47. data/assets/favicons/safari-pinned-tab.svg +32 -0
  48. data/assets/favicons/site.webmanifest +19 -0
  49. data/assets/img/homepage-pic.png +0 -0
  50. data/bin/run +195 -150
  51. data/js/Main.js +74 -0
  52. data/js/back-to-top.js +39 -48
  53. data/logo.png +0 -0
  54. data/post/index.html +3 -3
  55. metadata +35 -32
  56. data/_includes/BTT.html +0 -7
  57. data/_layouts/post_home.html +0 -113
  58. data/_sass/custom/styles.scss +0 -1
  59. data/_sass/custom/variables.scss +0 -1
  60. data/_sass/layouts/base.scss +0 -579
  61. data/_sass/layouts/variables.scss +0 -230
  62. data/docs/contributing.md +0 -69
@@ -1,230 +0,0 @@
1
- @charset "utf-8";
2
- //
3
- // Fonts
4
- //
5
- $text-font-family: "Roboto",
6
- sans-serif !default;
7
- $code-font-family: "Noto Sans",
8
- sans-serif !default;
9
-
10
- $text-font-weight: 390 !default;
11
-
12
- //
13
- // Table
14
- //
15
- $table-text-align: left !default;
16
-
17
- //
18
- // Headers
19
- //
20
- //
21
- $h2-h6_fnt-wght: 450;
22
- $h1_fnt-wght: 700;
23
- $h1_fnt-sze: 2.4rem;
24
-
25
- $font-size: 1rem !default;
26
- $small-font-size: $font-size * 0.875 !default;
27
-
28
- $line-height: 1.5 !default;
29
- $spacing-unit: 30px !default;
30
-
31
- //
32
- // Site banner
33
- //
34
- $site-banner-title-fnt-sze: 50px;
35
- $site-banner-description-fnt-sze: 18px;
36
- $site-banner-picture-sze_wdth: 60%; //make sure that the width and height are the same
37
-
38
- //
39
- // Transitions
40
- //
41
- $transition-btn: all 0.2s ease-in-out;
42
- $transition-links: color 0.3s ease-in-out;
43
- $tansitions-page-bar: all 0.3s ease-in-out;
44
-
45
- //
46
- // Animations
47
- //
48
- $animation-site-pic: 2s; //animations for banner-pic
49
- $animation-main: 1s; //animations for banner description and the body of the site.
50
- $animation-left: 250ms;
51
-
52
- //
53
- // Content width
54
- //
55
- $content-width: 800px !default;
56
-
57
- $mobile-width: 710px !default;
58
- $pc-width: 800px !default;
59
-
60
- // //
61
- // ---------- site queries ---------- //
62
- // //
63
-
64
- @mixin media-query($device) {
65
- @media screen and (max-width: $device) {
66
- @content;
67
- }
68
- }
69
-
70
- @mixin animation-fade-in($speed) {
71
- opacity: 0;
72
- animation: fade-in 1s linear forwards;
73
- animation-delay: #{$speed}s;
74
- -webkit-animation-delay: #{$speed}s;
75
- }
76
-
77
-
78
-
79
- @mixin relative-font-size($ratio) {
80
- font-size: #{$ratio}rem;
81
- }
82
-
83
- // //
84
- // ---------- Media queries ---------- //
85
- // //
86
-
87
- @mixin large {
88
- @media screen and (min-width: #{$large-breakpoint}) {
89
- @content;
90
- }
91
- }
92
-
93
- @mixin medium {
94
- @media screen and (min-width: #{$medium-breakpoint}) and (max-width: #{$large-breakpoint}) {
95
- @content;
96
- }
97
- }
98
-
99
- @mixin small {
100
- @media screen and (max-width: #{$medium-breakpoint}) {
101
- @content;
102
- }
103
- }
104
-
105
- // //
106
- //---------- scss mixin --------- //
107
- // //
108
-
109
- @mixin text-muted {
110
- color: $footer-head-link-color;
111
- }
112
-
113
- @mixin text-unmuted {
114
- color: $text-color;
115
- }
116
-
117
- @mixin footer-wrapper {
118
- margin-bottom: $spacing-unit / 2;
119
- width: calc(28% - (#{$spacing-unit} / 2));
120
- padding: 0 ($spacing-unit / 2);
121
-
122
- &:first-child {
123
- padding-right: $spacing-unit / 2;
124
- padding-left: 0;
125
- }
126
-
127
- &:last-child {
128
- padding-right: 0;
129
- padding-left: $spacing-unit / 2;
130
- }
131
- }
132
-
133
- @mixin prompt($gf-icon, $gf-color, $bg-color, $fnt-fam) {
134
- border-radius: 5px;
135
- padding: 0.80rem 1.2rem;
136
- font-style: normal;
137
- color: $text-color;
138
- font-weight: 400;
139
- display: flex;
140
- border-left: 6px solid $gf-color;
141
- background-color: $bg-color;
142
- font-size: 0.975rem;
143
-
144
- &::before {
145
- content: $gf-icon;
146
- font-family: $fnt-fam;
147
- color: $gf-color;
148
- font-size: 34px;
149
- line-height: 1;
150
- padding-right: 10px;
151
- padding-bottom: 13px;
152
- }
153
- }
154
-
155
- @mixin horizontal-scroll {
156
- &::-webkit-scrollbar {
157
- width: 7px;
158
- height: 9px;
159
- }
160
-
161
- &::-webkit-scrollbar-track {
162
- background-color: $code-background-color;
163
- }
164
-
165
- &::-webkit-scrollbar-thumb {
166
- background: $scroll_bar_bg_color;
167
- border-radius: 4px;
168
- }
169
-
170
- }
171
-
172
-
173
- // //
174
- //---------- Animations --------- //
175
- // //
176
-
177
-
178
- @keyframes left-animation {
179
- from {
180
- opacity: 0;
181
- transform: translate3d(100%, 0, 0);
182
- }
183
-
184
- to {
185
- opacity: 1;
186
- transform: translate3d(0, 0, 0);
187
- }
188
- }
189
-
190
- @keyframes BTT-Entrance {
191
- from {
192
- opacity: 0;
193
- transform: translate3d(0, 100%, 0);
194
- }
195
-
196
- to {
197
- opacity: 1;
198
- transform: translate3d(0, 0, 0);
199
- }
200
- }
201
-
202
- @keyframes BTT-Exit {
203
- from {
204
- opacity: 1;
205
- }
206
-
207
- to {
208
- opacity: 0;
209
- transform: translate3d(0, 100%, 0);
210
- }
211
- }
212
-
213
- @keyframes slide {
214
- 100% {
215
- transform: translateX(0);
216
- }
217
- }
218
-
219
- @keyframes slide-up {
220
- 100% {
221
- opacity: 1;
222
- transform: translateY(0);
223
- }
224
- }
225
-
226
- @keyframes fade-in {
227
- 100% {
228
- opacity: 1;
229
- }
230
- }
data/docs/contributing.md DELETED
@@ -1,69 +0,0 @@
1
- # Contributing to the Fica Theme
2
-
3
- Hi there! We're thrilled that you'd like to contribute to the Fica Theme. Your help is essential for keeping it great.
4
-
5
- the Fica Theme is an open source project supported by the efforts of an entire community and built one contribution at a time by users like you. We'd love for you to get involved. Whatever your level of skill or however much time you can give, your contribution is greatly appreciated. There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests, helping other users by commenting on issues, or writing code which can be incorporated into the Fica Theme itself.
6
-
7
- Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
8
-
9
- ## How to report a bug
10
-
11
- Think you found a bug? Please check [the list of open issues](https://github.com/Involts/jekyll-theme-fica/issues) to see if your bug has already been reported. If it hasn't please [submit a new issue](https://github.com/Involts/jekyll-theme-fica/issues/new).
12
-
13
- Here are a few tips for writing *great* bug reports:
14
-
15
- * Describe the specific problem (e.g., "widget doesn't turn clockwise" versus "getting an error")
16
- * Include the steps to reproduce the bug, what you expected to happen, and what happened instead
17
- * Check that you are using the latest version of the project and its dependencies
18
- * Include what version of the project your using, as well as any relevant dependencies
19
- * Only include one bug per issue. If you have discovered two bugs, please file two issues
20
- * Even if you don't know how to fix the bug, including a failing test may help others track it down
21
-
22
- **If you find a security vulnerability, do not open an issue. Please email security@github.com instead.**
23
-
24
- ## How to suggest a feature or enhancement
25
-
26
- If you find yourself wishing for a feature that doesn't exist in the Fica Theme, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that the Fica Theme has today have been added because our users saw the need.
27
-
28
- Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and goals of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible, including describing the problem you're trying to solve.
29
-
30
- [Open an issue](https://github.com/Involts/jekyll-theme-fica/issues/new) which describes the feature you would like to see, why you want it, how it should work, etc.
31
-
32
-
33
-
34
- ## Your first contribution
35
-
36
- We'd love for you to contribute to the project. Unsure where to begin contributing to the Fica Theme? You can start by looking through these "good first issue" and "help wanted" issues:
37
-
38
- * [Good first issues](https://github.com/Involts/jekyll-theme-fica/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) - issues which should only require a few lines of code and a test or two
39
- * [Help wanted issues](https://github.com/Involts/jekyll-theme-fica/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) - issues which may be a bit more involved, but are specifically seeking community contributions
40
-
41
- ## How to propose changes
42
-
43
- Here's a few general guidelines for proposing changes:
44
-
45
- * If you are making visual changes, include a screenshot of what the affected element looks like, both before and after.
46
- * Follow the [Jekyll style guide](https://ben.balter.com/jekyll-style-guide).
47
- * If you are changing any user-facing functionality, please be sure to update the documentation
48
- * Each pull request should implement **one** feature or bug fix. If you want to add or fix more than one thing, submit more than one pull request
49
- * Do not commit changes to files that are irrelevant to your feature or bug fix
50
- * Don't bump the version number in your pull request (it will be bumped prior to release)
51
- * Write [a good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
52
-
53
- At a high level, [the process for proposing changes](https://docs.github.com/get-started/quickstart/github-flow) is:
54
-
55
- 1. [Fork](https://github.com/Involts/jekyll-theme-fica/fork) and clone the project
56
- 2. Configure and install the dependencies: `bin/run insdep`
57
- 3. Make sure the tests pass on your machine: `bin/run chktheme`
58
- 4. Create a new branch: `git checkout -b my-branch-name`
59
- 5. Make your change, add tests, and make sure the tests still pass
60
- 6. Push to your fork and [submit a pull request](https://github.com/Involts/jekyll-theme-fica/compare)
61
- 7. Pat your self on the back and wait for your pull request to be reviewed and merged
62
-
63
- ## Bootstrapping your local development environment
64
-
65
- `bin/run insdep`
66
-
67
- ## Running tests
68
-
69
- `bin/run server`