* Fixes#357 by upgrading to fontawesome-free 6.3.0
* Replaced the existing font-awesome files with new ones
* Updated references in _variables.scss ro reference theme location
* Tweaked social.html to remove redundant css class
* Updating netlify.toml to more modern values
---------
Co-authored-by: Victoria Drake <24644237+victoriadrake@users.noreply.github.com>
* Add files via upload
import from scss files from ../vendor
* added academicons import
import from _academicons-import.sass
* added license for academicons
* added academicons fonts/scss in vendor
* added academicons in static/fonts
* changed social.html to differentiate between fontawesome and academicons
* deleted academicons manually loading
in the first steps I had implemented academicons manually before I added it in the assets/sass
* Delete .DS_Store
* Delete .DS_Store
* Delete .DS_Store
---------
Co-authored-by: bpkleer <benk@sowi.jlug.de>
* Add showMenu option
The showMenu option allows users to remove the navigation menu if
necessary.
* Update README.md
This commit will update the README.md file to include information about
the showMenu option.
* Use image only when project has an image
So if there is no images, then projects can form a bit tigher and more
centered position in a square.
* Use same principle for all projects listing template
As per the review comment the listing of the projects would also be dependent on the existance of the image and creation of the space for it
* Add project_timeline to the project template
Project timeline is sometimes very important aspect of your project as
it shows that you have been working on it for some time. This adds the
feature to the template, but only uses it when it is defined.
* Add description of a new feature to README
* Apply suggestions from code review
Co-authored-by: Victoria Drake <24644237+victoriadrake@users.noreply.github.com>
This way it's much easier to tune the comment handling in general (like
disable it for some sections) or integrate a different commenting system
than disqus.
This PR adds functionality for users to specify which `icon_pack` to use (`fas` or `fab`; see: https://fontawesome.com/how-to-use/on-the-web/setup/upgrading-from-version-4) in the `config.toml` file, so that users can use the solid icons as well as the brand icons.
```
[[params.social]]
url = "https://twitter.com/"
icon = "twitter" # icon name without the 'fa-'
icon_pack = "fab"
[[params.social]]
url = "https://facebook.com/"
icon = "facebook-f" # icon name without the 'fa-'
icon_pack = "fab"
[[params.social]]
url = "https://linkedin.com/"
icon = "linkedin-in" # icon name without the 'fa-'
icon_pack = "fab"
[[params.social]]
url = "mailto:youremail@email.com" # For a direct email link, use "mailto:test@example.org".
icon = "paper-plane" # icon name without the 'fa-'
icon_pack = "fas"
```
* Center the navbar again on the home page
* Favor the project page for listing projects
The project listing has its own page we can link to instead of going
back to the (potentially fading in) home page each time.
