Options to better control footer.#1886
Merged
ivan-nginx merged 4 commits intoiissnan:masterfrom Sep 28, 2017
Merged
Conversation
Signed-off-by: jokiestrunk <[email protected]>
Contributor
Author
Signed-off-by: jokiestrunk <[email protected]>
1. Fix by comments some blocks. 2. Target blank in external links. 3. Separate `powered`, `theme` and `custom` options & refactor some formatting.
1. Separate `powered`, `theme` and `custom` options. 2. Refactor some options and comments & add template to `custom_text`.
Collaborator
|
Tested. Improved. Merged. |
This was referenced Sep 28, 2017
hk-mp5a3
pushed a commit
to hk-mp5a3/hexo-theme-next
that referenced
this pull request
Oct 11, 2025
Options to better control footer.
This file contains hidden or 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
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.
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 Number(s): N/A
What is the new behavior?
Description about this pull, in several words...
How to use?
In NexT
_config.yml:Old footer configuration:
New footer configuration:
Does this PR introduce a breaking change?