Next up, you’re probably going to want to customize the theme without overriding a lot of files (not cool if you choose to go with another theme), the following customizations are available:
Here is a copy of the current theme.yml
file, along with comments. This file should be copied and overridden by your project. If you switch between themes are are testing themes out, hopefully I’ve made this easy.
The original social feature was hard coded, where adding a new social link required adding to theme.yml
and updating the social.html
file. I’ve removed that requirement and provided the new social.yml
that can accept any number of social links that you have available. Here is an example of Github and Instagram:
The site logo defaults to the file /assets/img/logo.png
. There are a number of ways to override this in your own site:
/assets/img/logo.png
in your own repository.logo
entry in theme.yml
The fav icon can be updated in much the same ways:
/assets/img/favicon.png
in your own repository.favicon
entry in theme.yml
When on a smaller device (mobile or tablet) the menu will be accessible through the floating action button. The button can be customized by /_includes/fab.html
file. To just change the image displayed, set the site.data.theme.fab
setting in /data/theme.yml
.
The image will default to the /assets/img/logo.png
if not provided.
If you’re using this on GitHub Pages with a custom domain name, you’ll want to change this to be the domain you’re going to use. All that should be in here is a domain name on the first line and nothing else(like: example.com
).
Just as with the original Lagom the Rouge highlight is using the Solarized theme. This can be overwritten by providing a new _sass/syntax.scss
or manually applying styles to the .highlight
selector.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
package com.example;
import com.example.UserMapper;
public class UserServiceImpl {
@Inject
private UserMapper userMapper;
@CacheGet
public User getUserByEmail(String email) {
return userMapper.getByEmail(email);
}
}