Skip to content

Allow customized copyright contents#254

Merged
sli1989 merged 2 commits intotheme-next:masterfrom
shenchsh:master
May 14, 2018
Merged

Allow customized copyright contents#254
sli1989 merged 2 commits intotheme-next:masterfrom
shenchsh:master

Conversation

@shenchsh
Copy link
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our guidelines.
  • Tests for the changes have been added (for bug fixes / features).
    • Muse | Mist have been tested.
    • Pisces | Gemini have been tested.
  • Docs have been added / updated (for bug fixes / features).

PR Type

What kind of change does this PR introduce?

  • Bugfix.
  • Feature.
  • Code style update (formatting, local variables).
  • Refactoring (no functional changes, no api changes).
  • Build related changes.
  • CI related changes.
  • Documentation content changes.
  • Other... Please describe:

What is the current behavior?

This theme does not support customized copyright contents.

What is the new behavior?

Use can defined there copyright contents in post

  • Screens with this changes: N/A
  • Link to demo site with this changes: N/A

How to use?

In post, user can use copyright in front-matter block to define their own copyright contents

Does this PR introduce a breaking change?

  • Yes.
  • No.

@sli1989
Copy link
Collaborator

sli1989 commented May 14, 2018

Can u provide the screenshots of this features in all schemes?

@sli1989 sli1989 added this to the v6.3.0 milestone May 14, 2018
@sli1989 sli1989 merged commit 10503cc into theme-next:master May 14, 2018
@ivan-nginx
Copy link
Member

No need this. Custom language feature (#253) already suppport custom translates for all keys. Docs will be later.

ivan-nginx added a commit that referenced this pull request Jun 12, 2018
tongluyang pushed a commit to tongluyang/hexo-theme-next that referenced this pull request Nov 19, 2019
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants