Conversation
I added a [Remote Development Containers](https://code.visualstudio.com/docs/devcontainers/tutorial) in Visual Studio Code (VSCode). Lots of people like to develop in Containers to have a clean system. With this PR, it is possible to work with al-folio without any installation (except for VS Code, its Remote Dev Container extension, and Docker). Once you've opened the `al-folio` repository, a prompt will appear requesting to reopen the project within a container. <img width="541" alt="grafik" src="https://github.com/alshedivat/al-folio/assets/1998723/2963446f-8e42-4df1-9e8c-22691d78b7e4"> Upon doing so, Jekyll will automatically start within the container and prompt you to open the website's preview sidebar directly in VSCode or using your Browser. Additionally, it installs extensions for `liquid` and Prettier (`npx prettier`). Files are formatted using `al-folios`-prettier settings (`.prettierrc`) to streamline pull request submission. Additionally, the performance seems to be much better compared to the `docker-compose`setup, see #2333. --------- Co-authored-by: George <31376482+george-gca@users.noreply.github.com>
…age (#2298) adding "location" element when location object is added to work experience. Location icon and the entered value will appear on the CV page under the work experience section. This feature already exists for education section, but not for work. The change is made to make the experiece more consistent. 
Adjusting issue #2343 by adding null check.
Fixing the docker command based on `docker compose [-f <arg>...] [options] [COMMAND] [ARGS...]` format on the [website](https://docs.docker.com/compose/reference/#command-options-overview-and-help). Because the old command would give error: `unknown shorthand flag: 'f' in -f`
…… (#2349) …page same as pull request alshedivat/al-folio#2298 and commit alshedivat/al-folio@363f277 for **Volunteer** section
This PR enables to have `abbr` and `preview` for a single publication (closing #1162). The following example shows all three possibilities: 1) Preview + Abbr 2) Preview only 3) Abbr only. <img width="786" alt="grafik" src="https://github.com/alshedivat/al-folio/assets/1998723/0633f443-b430-4fa6-a0eb-750170a638bd">
The current state of project looks a bit unharmonized. # Vertical layout before: <img width="834" alt="Bildschirmfoto 2024-04-20 um 18 09 16" src="https://github.com/alshedivat/al-folio/assets/1998723/55ba0968-bfd9-443f-b58a-eb6723deccfc"> # Vertical layout after: <img width="834" alt="Bildschirmfoto 2024-04-20 um 18 10 28" src="https://github.com/alshedivat/al-folio/assets/1998723/9b06b9b8-9228-4dfd-ab10-ca16ce028b1d"> # Horizontal layout before: <img width="834" alt="Bildschirmfoto 2024-04-20 um 18 08 54" src="https://github.com/alshedivat/al-folio/assets/1998723/97aaf5b4-1d3e-4a1c-8175-3a97391739b3"> # Horizontal layout after: <img width="834" alt="Bildschirmfoto 2024-04-20 um 18 07 46" src="https://github.com/alshedivat/al-folio/assets/1998723/a357fa62-8551-4e92-91d3-3d5d01dbc605"> *** These improvements are not perfect, but to be honest, I have no deep experiences with bootstrap. Actually, I just read the [docs](https://getbootstrap.com/docs/4.4/components/card/) and tried my best. But I think it looks way better than before. I'm pretty happy with the vertical layout, but the horizontal could be improved. I tried various things to get a better alignment of the image, without any success. In theroy, there is e.g. `card-img-top`, but I could not make it work. I changed the project descriptions to make some of these edge-cases visible. Feedback and improvements (especially code) are more than welcome Closes #2246
Signed-off-by: George Araujo <george.gcac@gmail.com>
Added condition to avoid security issue according to GitHub's dependabot  --------- Signed-off-by: George Araujo <george.gcac@gmail.com>
This PR is related to #2309. I added an optional `last_updated` field. This new field represents the timestamp for when the post was last updated. Consequently, the existing `date` metadata should now be interpreted as the creation date of the post. The formatting for displaying these dates has been standardized as follows: ```text Created: July 11, 2023 | Last Updated: April 14, 2024 ``` For a practical implementation example, please refer to [this post](https://torydeng.github.io/blog/2023/deploying-server/) on my website, where I have applied these changes. --- Any feedback is wellcome.
[Reference](alshedivat/al-folio#2352 (comment)) I'm not sure if the removal of `max-width: 90vw;` for all images causes any side issues. I could at least not find any. But having this properties will produce unaligned preview sizes. Help/testing is more than welcome. # Before <img width="364" alt="Bildschirmfoto 2024-04-21 um 14 17 51" src="https://github.com/alshedivat/al-folio/assets/1998723/5ad1a4d7-dfe6-43f8-98ec-eae19dd991c2"> # After <img width="364" alt="Bildschirmfoto 2024-04-21 um 14 21 53" src="https://github.com/alshedivat/al-folio/assets/1998723/fb942403-a01f-42ec-95c6-697378ed0d92"> ... <img width="364" alt="Bildschirmfoto 2024-04-21 um 14 22 03" src="https://github.com/alshedivat/al-folio/assets/1998723/1ddf43d8-98a8-421d-9f64-3352190c4bb8">
Basically adds suggestions of how to cite a post, as suggested in #2374.  --------- Signed-off-by: George Araujo <george.gcac@gmail.com>
This PR fixes a very niche bug. If there is a co-author that is not *me* (=`<em>` tagged) and does not have a `coauthor_url` (=`<a>` tagged), there will be a leading whitespace before the separating comma. If the author list is split into multiple lines (due to long author lists or a small view), the whitespace can lead to a line beginning with a comma. As I said, very niche, but interestingly, the other cases already did the same whitespace handling. Just the case not-me/no-url was mising. Currently, we do not have this case on vanilla al-folio, but you can see it for example on [my website](https://christianmainka.de/publications/) if the view is small (e.g., 430px). Related to #1502.
Google [Typograms](https://github.com/google/typograms/) is a lightweight image format (text/typogram) useful for defining simple diagrams in technical documentation.   --------- Signed-off-by: George Araujo <george.gcac@gmail.com>
Added support for [jekyll-tabs](https://github.com/Ovski4/jekyll-tabs), implemented #1977. Light:  Dark:  --------- Signed-off-by: George Araujo <george.gcac@gmail.com>
I've added my al-folio themed website link to the README's Academic websites section.
This PR should fix the issues reported in alshedivat/al-folio#2384 , alshedivat/al-folio#2392 and alshedivat/al-folio#2395. It seems that the ruby docker image is not affected by these problems.
Signed-off-by: George Araujo <george.gcac@gmail.com>
Signed-off-by: George Araujo <george.gcac@gmail.com>
Implementation of Google tag ID to correctly getting tracked requires further modification in addition to the one line script in the `_includes/scripts.liquid` file as ``` <script async src="https://www.googletagmanager.com/gtag/js?id={{ site.google_analytics }}"></script> <script> window.dataLayer = window.dataLayer || []; function gtag() { dataLayer.push(arguments); } gtag('js', new Date()); gtag('config', '{{ site.google_analytics }}'); </script> ``` I have made the changes and tested it out on my personal webpage to ensure the tracking in analytics dashboard.
…3002) As described in alshedivat/al-folio#300, standard Markdown code highlighting doesn't work in the Distill template because it is clobbered by the Distill "Prism" syntax highlighting. This PR will allow d-code tags (distill-specific code tags) to function with the Distill syntax highlighter, but will default `highlight` and Markdown code blocks to use the Jekyll/Rouge highlighter. This PR also removes overrides.js, which is currently broken because jquery isn't loaded.
…ional Chinese (#3015) The author of github-readme-stats uses the non-standard code "cn" for simplified Chinese, see [here](https://github.com/anuraghazra/github-readme-stats?tab=readme-ov-file#available-locales). While for traditional Chinese the author only provides "zh-tw". The github-readme-stats functions on repo page will break if the user sets the site language to ALL variants of Chinese except for zh-tw. This hack is to make all sub-variants of simplified Chinese fall back to "cn" and all sub-variants of traditional Chinese fall back to "zh-tw". This patch fixes the problem and has been tested locally & with GitHub pages.
Fix alshedivat/al-folio#3012 (make abbr color inside bibliography a variable)
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.18.1 to 1.18.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sparklemotion/nokogiri/releases">nokogiri's releases</a>.</em></p> <blockquote> <h2>v1.18.3 / 2025-02-18</h2> <h3>Security</h3> <ul> <li>[CRuby] Vendored libxml2 is updated to <a href="https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.13.6">v2.13.6</a> to address CVE-2025-24928 and CVE-2024-56171. See <a href="https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vvfq-8hwr-qm4m">GHSA-vvfq-8hwr-qm4m</a> for more information.</li> </ul> <!-- raw HTML omitted --> <pre><code>cab20305133078a8f6b60cf96311b48319175038cc7772e5ec586ff624cb7838 nokogiri-1.18.3-aarch64-linux-gnu.gem acb256bb3213a180b1ed84a49c06d5d4c6c1da26f33bc9681f1fece4dab09a79 nokogiri-1.18.3-aarch64-linux-musl.gem ce088965cd424b8e752d82087dcf017069d55791f157098ed1f671d966857610 nokogiri-1.18.3-arm64-darwin.gem 37b73a55e0d1e8a058a24abb16868903e81cb4773049739c532b864f87236b1b nokogiri-1.18.3-arm-linux-gnu.gem 09407970cd13736cf87e975fae69c13e1178bab0313d07b35580ee4dd3650793 nokogiri-1.18.3-arm-linux-musl.gem 6b9fc3b14fd0cedd21f6cad8cf565123ba7401e56b5d0aec180c23cdca28fd5a nokogiri-1.18.3.gem 236078c5f80ffc3d49c223fa98933d970543455403f9d672ca0aa5a6178a84fe nokogiri-1.18.3-java.gem 216be1cb454c4657fc64747e5ae32b2ab4015843183766f238e4f4a62fb1f6be nokogiri-1.18.3-x64-mingw-ucrt.gem d729406bb5a7b1bbe7ed3c0922336dd2c46085ed444d6de2a0a4c33950a4edea nokogiri-1.18.3-x86_64-darwin.gem 3c7ad5cee39855ed9c746065f39b584b9fd2aaff61df02d0f85ba8d671bbe497 nokogiri-1.18.3-x86_64-linux-gnu.gem 8aaecc22c0e5f12dac613e15f9a04059c3ec859d6f98f493cc831bd88fe8e731 nokogiri-1.18.3-x86_64-linux-musl.gem </code></pre> <!-- raw HTML omitted --> <h2>v1.18.2 / 2024-01-19</h2> <h3>Fixed</h3> <ul> <li>When performing a CSS selector query, an XML document's root namespace declarations should not be applied to wildcard selectors (<code>"*"</code>). Fixes a bug introduced in v1.17.0. (<a href="https://redirect.github.com/sparklemotion/nokogiri/issues/3411">#3411</a>) <a href="https://github.com/flavorjones"><code>@flavorjones</code></a></li> </ul> <!-- raw HTML omitted --> <pre><code>74e0f9a7487a30a2957f46c5113d58f836436b033c9906e0bc6fee9d8cdafabf nokogiri-1.18.2-aarch64-linux-gnu.gem 99bcea596a80eaee99f2bae2596275641ea688262c1da32b4e90db6159e86477 nokogiri-1.18.2-aarch64-linux-musl.gem 8288ec7a296e2510ca9bd053c0c5989f11260f8c07bc3e9afbafa536f7077281 nokogiri-1.18.2-arm64-darwin.gem 6fb0246b69f2c589a69254e82bc2a40aa238c4f977fd7903e283341a92935729 nokogiri-1.18.2-arm-linux-gnu.gem dcdd4d10ed2743f0d8c887825700c3a8506aea1aa415917ac50ccc01597c51a3 nokogiri-1.18.2-arm-linux-musl.gem 93791cfb33186fe077eb9e1b8a6855b5621e328f81f565334572fa398366f8bf nokogiri-1.18.2.gem eefdf9f0d6086173d3488cf7a736732ee13fb6674ef15643478c20502a67bf37 nokogiri-1.18.2-java.gem 894514572fa7503ce9210e51a7f8a9a35f34f154d6406cec1ac148c3ce1536a3 nokogiri-1.18.2-x64-mingw-ucrt.gem 7fca165e5ee87e9b6b3f1377180376afc0c8652ed2a3d761f472f0e3d3a1c651 nokogiri-1.18.2-x86_64-darwin.gem 9330ced4a976604865c2a76ce158e2bc608fa83999552e85a32ec06f85f427db nokogiri-1.18.2-x86_64-linux-gnu.gem 1cd7786ed15c76958d6a8f9a864df6208fecd624c340eb4ed211fbea60328f02 nokogiri-1.18.2-x86_64-linux-musl.gem </code></pre> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sparklemotion/nokogiri/blob/v1.18.3/CHANGELOG.md">nokogiri's changelog</a>.</em></p> <blockquote> <h2>v1.18.3 / 2025-02-18</h2> <h3>Security</h3> <ul> <li>[CRuby] Vendored libxml2 is updated <a href="https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.13.6">v2.13.6</a> to address CVE-2025-24928 and CVE-2024-56171. Nokogiri's maintainers believe these vulnerabilities do not affect users of Nokogiri, but we advise upgrading at your earliest convenience anyway.</li> </ul> <h2>v1.18.2 / 2024-01-19</h2> <h3>Fixed</h3> <ul> <li>When performing a CSS selector query, an XML document's root namespace declarations should not be applied to wildcard selectors (<code>"*"</code>). Fixes a bug introduced in v1.17.0. (<a href="https://redirect.github.com/sparklemotion/nokogiri/issues/3411">#3411</a>) <a href="https://github.com/flavorjones"><code>@flavorjones</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sparklemotion/nokogiri/commit/fd3ca2e22df67fd25fd5c25c466f6896b6547cb8"><code>fd3ca2e</code></a> version bump to v1.18.3</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/a8c526adf17716cf115e78995c815fc65f5937a2"><code>a8c526a</code></a> dep: update libxml2 to v2.13.6 (<a href="https://redirect.github.com/sparklemotion/nokogiri/issues/3437">#3437</a>)</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/0847cf86885ea5d25ccc9d3ff1c4c097f2891a60"><code>0847cf8</code></a> ci: tired of waiting for gnome mirrors</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/11945c82df6fca8827c2914e585e8e3a7027dcb5"><code>11945c8</code></a> dep: update libxml2 to v2.13.6</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/aa54fa59544ceb224d3fe6e3a53d05d5c937b15b"><code>aa54fa5</code></a> version bump to v1.18.2</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/0fb5541c95596fa67ea1ef60df9ad740fbcda672"><code>0fb5541</code></a> backport: fix(css-selector): default XML namespace should not be applied to w...</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/8ef2e918e7121a0773d3f777e9abe415180368a4"><code>8ef2e91</code></a> ci: bump windows test images from "head" to "3.4"</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/c10fd7a02e5f13e7889587141e8522b2d864a7c6"><code>c10fd7a</code></a> dev: so tired of psych not building on various things</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/83787496149d2ff2203892951a44e835181c1558"><code>8378749</code></a> fix(css-selector): default XML namespace is not applied to wildcard</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/b112e18a4851eca1d40dcc7e755653dc32ea885d"><code>b112e18</code></a> prefactor: restructure css-to-xpath tests</li> <li>See full diff in <a href="https://github.com/sparklemotion/nokogiri/compare/v1.18.1...v1.18.3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/alshedivat/al-folio/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Fixed a small typo in `post.liquid`.
Resolve #3037 This PR just re-enable the old exclusions of jekyll-minifier to ensure that the files aren't altered.
Since I was annoyed at not being able to use [jekyll-archives](https://github.com/jekyll/jekyll-archives) to create an archive for the books, I decided to implement myself the [jekyll-archives-v2](https://github.com/george-gca/jekyll-archives-v2) that doesn't have this limitation. Closes #923. --------- Signed-off-by: George Araújo <george.gcac@gmail.com>
Refactor footer content into a reusable variable for cleaner code
Fixes #2668 Signed-off-by: George Araújo <george.gcac@gmail.com>
Fixes #3055 Signed-off-by: George Araújo <george.gcac@gmail.com>
Signed-off-by: George Araújo <george.gcac@gmail.com>
Bumps [json](https://github.com/ruby/json) from 2.10.1 to 2.10.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ruby/json/releases">json's releases</a>.</em></p> <blockquote> <h2>v2.10.2</h2> <h2>What's Changed</h2> <ul> <li>Fix a potential crash in the C extension parser.</li> <li>Raise a ParserError on all incomplete unicode escape sequence. This was the behavior until <code>2.10.0</code> unadvertently changed it.</li> <li>Ensure document snippets that are included in parser errors don't include truncated multibyte characters.</li> <li>Ensure parser error snippets are valid UTF-8.</li> <li>Fix <code>JSON::GeneratorError#detailed_message</code> on Ruby < 3.2</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/ruby/json/compare/v2.10.1...v2.10.2">https://github.com/ruby/json/compare/v2.10.1...v2.10.2</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ruby/json/blob/master/CHANGES.md">json's changelog</a>.</em></p> <blockquote> <h3>2025-03-12 (2.10.2)</h3> <ul> <li>Fix a potential crash in the C extension parser.</li> <li>Raise a ParserError on all incomplete unicode escape sequence. This was the behavior until <code>2.10.0</code> unadvertently changed it.</li> <li>Ensure document snippets that are included in parser errors don't include truncated multibyte characters.</li> <li>Ensure parser error snippets are valid UTF-8.</li> <li>Fix <code>JSON::GeneratorError#detailed_message</code> on Ruby < 3.2</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ruby/json/commit/350c1fd154eaf7840f696c623362478a9148166c"><code>350c1fd</code></a> Release 2.10.2</li> <li><a href="https://github.com/ruby/json/commit/c56db31f800d5d508389793e69682f99749dbadf"><code>c56db31</code></a> Merge commit from fork</li> <li><a href="https://github.com/ruby/json/commit/cf242d89a0523bacd5238a59c77b33411b8c3208"><code>cf242d8</code></a> Fix potential out of bound read in <code>json_string_unescape</code>.</li> <li><a href="https://github.com/ruby/json/commit/57911f1ecf065c36cf36e6bc46fd037c675ceb55"><code>57911f1</code></a> Merge pull request <a href="https://redirect.github.com/ruby/json/issues/762">#762</a> from byroot/invalid-escape</li> <li><a href="https://github.com/ruby/json/commit/7d0637b9e6e0269c88418b142cb9a1ef2799587d"><code>7d0637b</code></a> Raise a ParserError on all incomplete unicode escape sequence.</li> <li><a href="https://github.com/ruby/json/commit/c079793b7655b749a4d85f5c8e6bd2649fd31c0c"><code>c079793</code></a> Avoid fast-path IO writes when IO has ext enc</li> <li><a href="https://github.com/ruby/json/commit/ac30b69c06a2e4d21cca4875a7265c24f6ede5ed"><code>ac30b69</code></a> Merge pull request <a href="https://redirect.github.com/ruby/json/issues/757">#757</a> from rahim/fix-generator-error-no-method-error</li> <li><a href="https://github.com/ruby/json/commit/2e015ff839ed2044ead0fd27b63a912766270a1b"><code>2e015ff</code></a> Fix JSON::GeneratorError#detailed_message with Ruby < 3.2</li> <li><a href="https://github.com/ruby/json/commit/f3e113654fb61cb670ab70f2470dc26183c369e1"><code>f3e1136</code></a> Merge pull request <a href="https://redirect.github.com/ruby/json/issues/756">#756</a> from byroot/utf8-snippets</li> <li><a href="https://github.com/ruby/json/commit/e144793b7226c2df75c414749d6f87ab7fcf4dce"><code>e144793</code></a> Ensure parser error snippets are valid UTF-8</li> <li>Additional commits viewable in <a href="https://github.com/ruby/json/compare/v2.10.1...v2.10.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/alshedivat/al-folio/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
`excludes` should be `exclude`. `excludes` with `s` does not work with `_config.yml`, which itself uses `exclude` and `include`.
Again, I saw this version problem with current version of our docker image. Supposedly, there is some json package problem which I dealt with. But here is the overall solution to this problem for whoever is having it. --------- Co-authored-by: George <31376482+george-gca@users.noreply.github.com>
Love the theme and just used it for my own personal website! Thought I'd link from here as suggested in the README to show my support! :)
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Collaborator
Author
|
@NinaWie I'd like to merge this first, then re-do #8 because that's easier than resolving the merge conflicts. Could you try building this locally? Instructions are here: github.com/iiccsss. |
NinaWie
approved these changes
Mar 23, 2025
Collaborator
|
I could build it locally, and all pages look fine! I didn't go through the commits and changes, but should be fine to merge. Thanks for the effort in updating the whole template! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We are way behind the parent repository, and our version is still using a docker image that has known issues on M-series Apple silicon chips (see issue 2911 in parent repo.) I couldn't build the website locally, but the parent repo worked fine.
Hence, I've pulled the parent repo and resolved merge conflicts, hopefully keeping everything intact. A few minor things changed, e.g. links to social are no longer in
_config.ymlbut in_data/socials.yml.While I'm at it, this closes #9 by setting the width to 900 instead of 800.