Sync master #2
Merged
Sync master #2
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
…vat#334) * adds submenu in navigation bar. (fixes issue alshedivat#159) * Updated scss files to change hover animations on dropdown submenus, on both dark mode and light mode
This reverts commit 0e4df83.
* Revert "Fix latex rendering issue in the bibliography entries (alshedivat#358)" This reverts commit e328dc6. * Update mathjax version to 3.2.0 * Add bibtex_filters explicitly to _config.yml
* add jekyll target blank * Remove manual target blank from everywhere * Update README.md * Set ruby version to 3.0.2 in the deploy script Co-authored-by: Maruan Al-Shedivat <[email protected]>
* Add mermaid support via jekyll-diagrams * Add mermaid install to deploy workflow
* Add rss icon * Add a blank line to make sure rss icon is always at the last
‘action’ is deprecated, change to ‘ruby’ https://github.com/ruby/setup-ruby
* Place js files after body tag * Add Analytics to the end of script * Minor nits and fixes Co-authored-by: Maruan Al-Shedivat <[email protected]>
…hedivat#346) * Add webpage to academic pages list * adding panelbear analytics * added categories for projects and horizontal mode display for projects * rewrote the code to ensure it works properly with current project definitions * Style adjustments * added blockquote format, jekyll-archives, tag, year archive pages, and reading time. * added archive meta to blog posts list and individual posts. * added sitemap * stylistic modifications to jekyll-archive addition * Minor fixes Co-authored-by: Maruan Al-Shedivat <[email protected]>
* Optimize dark theme * Fix-up * Minor fixes Co-authored-by: Maruan Al-Shedivat <[email protected]>
…edivat#1167) This PR changes README.md to encourage people to use `Use this template` rather than `fork`. ### Differences between `Use this template` and fork > - A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit. > - Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph. > - A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly. [Ref](https://docs.github.com/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template) ### Cons Possible con would be that it is harder to pull the new changes from this repo to the users' repos. It does not seem like impossible to do so but it will require additonal actions on the users end. - https://github.com/orgs/community/discussions/23528 - https://stackoverflow.com/questions/56577184/github-pull-changes-from-a-template-repository --------- Co-authored-by: Maruan <[email protected]>
I imagine more people have wikipedia accounts than wikidata entries about them 😉
Added missing "/" in the OSF link.
By using this Github action it is possible to keep the derived repository up-to-date with its template. I am currently using this to keep my website up to date with the template repository. An example of the PR this action creates can be seen [here](george-gca/george-gca.github.io#13). Signed-off-by: George Araújo <[email protected]>
Creates a new section with user trophies.
This PR updates `deploy.yml` to use the GitHub Action [Deploy to GitHub Pages](https://github.com/marketplace/actions/deploy-to-github-pages).
Avoids a warning that appears in the console when opening the site on Google Chrome
…at#1266) Added `related_posts: false` to the announcements front matter to avoid errors like alshedivat#1203. Also included explanation in README FAQ section.
Implemented support for copy code button in code blocks (alshedivat#1262), also updated blog post about code to reflect it.
majority of the recent improvements to al-folio have been truly driven by a growing community of fans and contributors. this template has gradually transformed from a low-key weekend project into a "public good" of some sort used by thousands of people, university labs and classes, and academic conference and workshops. as such, having personal sponsorship info from the repository is no longer relevant. as the community grows a bit further, we may have to think about establishing some kind of governance around decisions of how al-folio is supposed to evolve, which features to prioritize, and how to reward contributors for their hard work. for now, these decisions will be made by the project maintainers (active contributors are welcome to join the team). and I'm all ears for proposals and suggestions!
Moved information about using this template to the beginning of the installation part, added a few more documentation links in it, fixed some typos. --------- Signed-off-by: George Araújo <[email protected]>
Adresses alshedivat#340 --------- Signed-off-by: George Araújo <[email protected]>
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.
This PR syncs master with the latest changes present in ai-folio