Update new al folio 2024-04-28 #12
Merged
Conversation
This file contains 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
Implementing #1440. Still not sure if the year should be shown there or not. Also, I limited to be displayed at least 2 at most 3 elements on the row of featured blog posts, since when having only 1 featured post the card would occupy the whole row (and it looks weird). What do you think @alshedivat? Also, idk how to force the cards to have the same height. I think it would look nicer, but my lack of web dev skills made a difference here. Some current screenshots:   --------- Signed-off-by: George Araujo <[email protected]> Co-authored-by: Maruan <[email protected]>
Added the following examples: * A personal homepage * A workshop website
I added multi-architecture support for docker images. - #1469 ToDo: - [ ] Update deploy tag file accrodingly
Addresses #1524 Signed-off-by: George Araujo <[email protected]>
Implemented #417. --------- Signed-off-by: George Araújo <[email protected]> Co-authored-by: Amir Pourmand <[email protected]>
Signed-off-by: George Araujo <[email protected]>
Added anmspro.github.io in academics
I have redesigned the CV to have some options that I have in my pdf CV. I'm not too inspired to include more example data, if anyone wants to add data, go ahead. With my data the CV looks like this: [https://jmrplens.github.io/cv/](https://jmrplens.github.io/cv/ ). My data: [VIEW FILE](https://github.com/jmrplens/jmrplens.github.io/blob/ce8b5b67dbc5a37dafe9083681b92a6746640b13/_data/cv.yml) Some screenshots: <img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-09-51)" src="https://user-images.githubusercontent.com/28966312/233200752-e49afa44-1c07-42eb-b38c-337f81b60406.png"><img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-10-22)" src="https://user-images.githubusercontent.com/28966312/233200844-0201d061-df3e-4e80-8107-3b6f7c72faa3.png"> <img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-10-37)" src="https://user-images.githubusercontent.com/28966312/233200898-77040d1a-bf9a-47f1-a46d-3008f7331020.png"><img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-10-54)" src="https://user-images.githubusercontent.com/28966312/233200949-055fe27e-ce06-4929-91e8-cab2983b4850.png"> Mobile: <img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-21-36)" src="https://user-images.githubusercontent.com/28966312/233203168-8b5cc777-e3f8-4387-96d4-a5d405d7032b.png"><img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-21-48)" src="https://user-images.githubusercontent.com/28966312/233203238-5ccc424e-b0e3-41a1-bd2b-2c64e01cfc85.png"> <img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-22-00)" src="https://user-images.githubusercontent.com/28966312/233203297-7174be99-08a1-427a-a414-5bded2d6c2d8.png"><img width="45%" alt="Screenshot of Google Chrome (19-4-23, 23-22-14)" src="https://user-images.githubusercontent.com/28966312/233203312-f5067ce7-134f-4a39-bb5b-aaa3d247b3e7.png"> --------- Co-authored-by: George <[email protected]>
Just as discussed in #1513 , this pull request adds support for [jsonresume](https://jsonresume.org/). Create the resume once, either as a file in the repository or at [github gist](https://gist.github.com/) called `resume.json`. Put the file in the `_config.yaml` file and that's it! Other platforms like [resumake](https://latexresu.me/) use the same schema. I also incorperated the changes introduced by #1339 to the best of my abilites. The style could be further improved. **Please merge this pull request after #1339 is merged, due to dependencies from it** If someone has a bettet approach on how to solve the problem that each section needs its own template, please let me know. But for now it works fine and is still backwards compatible with the `cv.yaml` file. Co-authored-by: George <[email protected]>
Fixes #1552 --------- Signed-off-by: George Araujo <[email protected]>
Implemented #1193 --------- Signed-off-by: George Araujo <[email protected]>
The layout template of cv.html has repeated parts. When site.data.resume is not defined, the cv page will be rendered incorrectly.
Signed-off-by: George Araujo <[email protected]>
Panelbear is now Cronitor RUM, the old script does not work.
Changed metadata info for when page is a blog post. Signed-off-by: George Araujo <[email protected]>
Solving #1569 I added Zotero socials because I needed them; opened a issue/pull request in case I'm not the only one. Second pull request (previous: #1570 ) because unwanted commits retroactively crept in somehow. It was easier to force reset (which closed the pull request automatically apparently).
Signed-off-by: George Araujo <[email protected]>
#1569 Fixed mismatch between zotero-id in _config.yml and the zotero-id called upon in the socials html file introduced by #1572 (sorry about that; slipped in when I had to reset my zotero-branch)
I should merge this whenever normal deploy is well-tested for Mac computers.
Solves #1586 by adding the option for giscus comments sites using the pages layout and minimally modifies Project 2 to show giscus comments as an example
figure.html was incorrectly setting height=max-height instead of max-height=max-height
Addressing #1395 but with a different solution from #1478, using semantic versioning based on implementation found [here](https://distresssignal.org/busting-css-cache-with-jekyll-md5-hash). Implemented a way of calculating the hash for both a single file or directory. This way we can calculate the hash for when there is a change in the `_sass` dir, for example, or in the contents of a single file. Examples of generated outputs of the plugin: ``` /al-folio/assets/css/main.css?d41d8cd98f00b204e9800998ecf8427e /al-folio/assets/js/theme.js?96d6b3e1c3604aca8b6134c7afdd5db6 /al-folio/assets/js/dark_mode.js?9b17307bb950ffa2e34be0227f53558f /al-folio/assets/js/no_defer.js?d633890033921b33e0ceb13d22340a9c /al-folio/assets/js/common.js?acdb9690d7641b2f8d40529018c71a01 /al-folio/assets/js/copy_code.js?c9d9dd48933de3831b3ee5ec9c209cac /al-folio/assets/img/prof_pic.jpg?974957d202f671e4fa6700c04e68deae ``` Signed-off-by: George Araujo <[email protected]>
Signed-off-by: George Araujo <[email protected]>
Dear `al-folio` maintainers, I would greatly appreciate it if you could add my homepage as a star in the academic examples. Thank you for your wonderful work on this.
Docker is well-tested for a long time. I think it is better to make it the recommended method for all OS types. This way, it is a lot easier to install docker (than to install jekyll and ruby and what not) and also we wouldn't have to deal with issues like these: - alshedivat/al-folio#1520 - alshedivat/al-folio#1491
I added further social integration for: 1. ACM: https://dl.acm.org/profile/ 2. IEEE: https://ieeexplore.ieee.org/author/ Given their importance in computer science, I would like to have them in al-folio.
This PR adds an "award" button to publications. It takes the `award` value from the bibtex entry and displays(incl. Markdown rendering) the text in a box similarly to abstract and bibtex. User can set the entry `award_name` to configure the value. See example config with `award_name: Nobel Prize`. The color of the award box can be configured in `_base.scss`. Note, there is a similar PR #2175, it I saw to issues with: 1. There was no progress 2. The award button just prints the text directly in the button, similarly to `award_name`. Long award names could clutter the webpage. 3. IMHO, it brokes the current al-folio design, since butons do have a fixed size/text. However, variable prize names are also possible with this PR. *** Pictures: Default. Text are hidden: <img width="708" alt="grafik" src="https://github.com/alshedivat/al-folio/assets/1998723/1221c82c-c384-4297-807e-39385e2ce4fd"> Additional info is shown when the button is clicked. Markdown supported. <img width="684" alt="grafik" src="https://github.com/alshedivat/al-folio/assets/1998723/2354aeee-12b0-4d32-b194-5d2ea80d8363"> Only one text box shown at the same time, like it is with "ABS" and "BIB": <img width="691" alt="grafik" src="https://github.com/alshedivat/al-folio/assets/1998723/d3937bb9-d9c2-47ac-b819-b92aec3d916a"> *** Feedback welcome. You can also check [my website](https://christianmainka.de/publications/awarded), which was the base for this PR.
Created a plugin to tackle #1181. Currently have an issue with tikzjax since it imports some wasm file from its javascript. The rest should work as expected. --------- Signed-off-by: George Araujo <[email protected]>
Fixes #2303. See #2333 for discussion.
I added further filds to `bib.liquid`. A common field is `location`, which is now printed. I added fields for `acceptance` and `acceptance_rate`. These fields might be usefull for external people to better determine a vanue's quality. `acceptance` is used for the accepted vs submitted papers. `acceptance_rate` is a percent-value. <img width="785" alt="Bildschirmfoto 2024-04-07 um 18 11 49" src="https://github.com/alshedivat/al-folio/assets/1998723/d5eaeb08-7f67-4fb7-b9b9-fd5f4a3c331c"> The existence of two distinct variables stems from the fact that the 'acceptance_rate' is represented using the venue color. On my website, I employ venue colors correlated with computer science conference rankings, which naturally leads to associating the acceptance rate with the same color scheme for coherence and better understanding. <img width="785" alt="Bildschirmfoto 2024-04-07 um 18 14 54" src="https://github.com/alshedivat/al-folio/assets/1998723/33ef0419-00ee-4fea-93d9-18c0269188de"> You can find more examples on my [website](https://christianmainka.de/publications/peerreviewed). Also, I added a CVE Score, which is mainly usefull for IT-Security researchers, see this [example](https://christianmainka.de/cve/). *** Let me know what you think about this proposal.
Signed-off-by: George Araújo <[email protected]>
As discussed in #1181, I suggest to make embedding videos an optional feature. This behavior aligns well with recently merged PR #2312. Open questions: 1. I added a youtube link to `papers.bib`. Is this link okay? 2. I set `enable_video_embedding: false` as the default. I argue that privacy settings should be the default. Also, the current implementation of `video.liquid` only works for some very specific video URLs. For example, to embed youtube, specialized links must be used to avoid `X-Frame-Option` issues. This behavior can lead to a broken embedding, which would not look very nice. Feedback welcome.
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 <[email protected]>
…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 <[email protected]>
Added condition to avoid security issue according to GitHub's dependabot  --------- Signed-off-by: George Araujo <[email protected]>
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">
# Conflicts: # .github/workflows/deploy-docker-tag.yml # .github/workflows/deploy-image.yml # .github/workflows/deploy.yml # .gitignore # _bibliography/papers.bib # _config.yml # _drafts/2020-09-28-github-metadata.md # _drafts/2020-09-28-twitter.md # _pages/about.md # _pages/publications.md # docker-compose.yml
![https://user-images.githubusercontent.com/28966312/233200752-e49afa44-1c07-42eb-b38c-337f81b60406.png"><img](https://user-images.githubusercontent.com/28966312/233200752-e49afa44-1c07-42eb-b38c-337f81b60406.png"><img){kind=link}
![https://user-images.githubusercontent.com/28966312/233200898-77040d1a-bf9a-47f1-a46d-3008f7331020.png"><img](https://user-images.githubusercontent.com/28966312/233200898-77040d1a-bf9a-47f1-a46d-3008f7331020.png"><img){kind=link}
![https://user-images.githubusercontent.com/28966312/233203168-8b5cc777-e3f8-4387-96d4-a5d405d7032b.png"><img](https://user-images.githubusercontent.com/28966312/233203168-8b5cc777-e3f8-4387-96d4-a5d405d7032b.png"><img){kind=link}
![https://user-images.githubusercontent.com/28966312/233203297-7174be99-08a1-427a-a414-5bded2d6c2d8.png"><img](https://user-images.githubusercontent.com/28966312/233203297-7174be99-08a1-427a-a414-5bded2d6c2d8.png"><img){kind=link}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.