-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor several components in _config.yml
#965
Merged
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
stevenjoezhang
changed the title
Remove some options that can be controlled by custom css in
Refactor several components in Jul 11, 2019
_config.yml
_config.yml
11 tasks
11 tasks
|
About the second question, it has already been reset. You can check the master branch. |
oh, thanks. but how to custom these two css for xiaobai. 😢 |
Add this to .site-author-image {
opacity: 0.7;
} |
Answers like that must be documented in site for around excess questions. |
@ivan-nginx FAQ? |
See also theme-next/theme-next.org#36 |
Yep. |
tongluyang
pushed a commit
to tongluyang/hexo-theme-next
that referenced
this pull request
Nov 19, 2019
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.
Breaking change
Deleted:
avatar.opacity
codeblock.border_radius
Renamed:
highlight_theme
->codeblock.highlight_theme
custom_logo.image
->custom_logo
pace_theme
->pace.theme
In
_config.yml
,avatar.opacity
andcodeblock.border_radius
only changes the style of one particular class of elements.As a result of #868, creating custom css is unprecedented in simplicity. These options should be removed and users can use custom css instead.
Besides,
codeblock.border_radius
should followcodeblock.copy_button.style
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue resolved: #299
What is the new behavior?
How to use?
In NexT
_config.yml
:Does this PR introduce a breaking change?