Skip to content
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

Add Block: Copyright #18895

Open
melchoyce opened this issue Dec 3, 2019 · 17 comments
Open

Add Block: Copyright #18895

melchoyce opened this issue Dec 3, 2019 · 17 comments
Labels
[Feature] Themes Questions or issues with incorporating or styling blocks in a theme. Needs Dev Ready for, and needs developer efforts New Block Suggestion for a new block [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Type] Enhancement A suggestion for improvement.

Comments

@melchoyce
Copy link
Contributor

This block would be useful for themes to use once we have Full-site editing, and would automatically output the site title, ©, and the year. Additionally, it would be good if themes could somehow hook into it to add an author credit. Like:

©2019 [My Example Site]. Theme by [Theme Author].

@melchoyce melchoyce added the New Block Suggestion for a new block label Dec 3, 2019
@BinaryMoon
Copy link

I like to add an automatic link to the privacy policy in my theme footers too.

@shaunandrews shaunandrews added the Needs Design Needs design efforts. label Dec 4, 2019
@richtabor
Copy link
Member

I like to add an automatic link to the privacy policy in my theme footers too.

100% this, based on the privacy policy WP page.

@mapk
Copy link
Contributor

mapk commented Dec 27, 2019

Initially, I thought this could be based largely on the Paragraph block. The block settings would include an option for the theme's author as a toggle which appends that text to whatever text the user wrote in the block.

Block

Copyright

Block Settings

Block Settings


But after some thinking about this, what if made this a "License block"? And people can change between "Copyright" or "Creative Commons" or "GPL", whatever license we wanted to include. Do you think this makes sense?

Basically, when switching to a new license, the license icon swaps out to show one of the other lisence icons like CC for Creative Commons.

Block

License-block

Block Settings

License-block-settings

@mapk mapk added Needs Design Feedback Needs general design feedback. and removed Needs Design Needs design efforts. labels Dec 27, 2019
@ZebulanStanphill
Copy link
Member

@mapk In that second mockup, I think "License type" should not be in the inspector. I consider it to be a primary option of the block, and therefore it should be either in the toolbar or an inline control shown within the block's edit canvas.

It should also be noted that you would probably use the standard copyright symbol regardless of what license you are using.

@karmatosed
Copy link
Member

I like the idea about the licence, I wonder though if it should be an option at the point of placeholder or something to switch. I can see a step for example of 'choose license' and it would create. I kind of agree it doesn't fit as well in the sidebar, but I more think it's a first step over having in toolbar. I do love a block that doesn't need sidebar options, they are simple and easier for people.

@mapk
Copy link
Contributor

mapk commented Jan 6, 2020

Really great feedback! Thank you. I wonder if we should start with a set of licenses we'd like to expose in this block?

  • Copyright
  • Creative Commons
    -- Attribution
    -- Attribution Share Alike
    -- Attribution No Derivatives
    -- Attribution Non-Commercial
    -- Attribution Non-Commercial Share Alike
    -- Attribution Non-Commercial No Derivatives
  • Public Domain
  • GNU Free Documentation License (GFDL)

I'm not sure how well GPL aligns with just web content. Same question for other licenses like MIT and Apache. Should we include those options?

Are there others I haven't included?

@enriquesanchez enriquesanchez added the [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later label Apr 21, 2020
@enriquesanchez
Copy link
Contributor

In addition to the ability to add a license, it'll be super useful if the block auto updated the year as time passes.

@mapk mapk added Needs Dev Ready for, and needs developer efforts and removed Needs Design Feedback Needs general design feedback. labels Apr 30, 2020
@scruffian scruffian added the [Feature] Themes Questions or issues with incorporating or styling blocks in a theme. label Nov 19, 2020
@peroyomas
Copy link

Not sure if a new block is needed for this, but something that can help a lot is a core shortcode that displays the current year. Many themes has a similar solution to keep the copyright updated, so it may be good to feature it in core, too.

@pagelab
Copy link
Contributor

pagelab commented Dec 7, 2022

@peroyomas There's already a proposal for creating a sort of shortcodes v2 – or dynamic tokens – for use cases like this one.

@paaljoachim
Copy link
Contributor

Hey

I happen to create a duplicate: #47522
It shows some newer examples from current plugins.

@paaljoachim
Copy link
Contributor

paaljoachim commented Feb 9, 2023

I will bring over a few comments to this issue from the newer issue that I made. #47522
I closed it as a duplicate.

Michelle has made a Copyright year block located here: https://github.com/marktimemedia/copyright-year-block
I believe it is fairly close to the current design used in Gutenberg.
Screenshot 2023-02-09 at 10 56 01

Block settings contains Typography and Dimensions panels. It does not currently contain the split between Styles and Settings seen in example the Post Title block

One can click directly into the "My Site Name. All Rights Reserved." and change the text.

It would be great to do something very similar for a Copyright block added to Gutenberg.


Looking at other Copyright plugins.

@mkaz Marcus has made this Copyright and Date block.
https://wordpress.org/plugins/copyright-block/

No changes can be made as I see. There are no sidebar settings. Insert the block and the text "Copyright © 2023" will be seen.

Screenshot 2023-02-09 at 11 07 45

@pbearne Paul has made this Copyright block.
https://github.com/pbiron/shc-copyright/releases/tag/0.9.0

One can click directly into the "© 2023 Copyright Statement." and change Copyright Statement text.
It has a Launch Year setting and an Advanced panel.

Screenshot 2023-02-09 at 11 13 01

EDIT:
I found another Copyright plugin on Github. Editable Copyright Block by Richard.
https://github.com/sidewaysdesign/editable-copyright-block

It looks like this:
Screenshot 2023-02-09 at 11 35 13

One can edit the Prefix (Copyright symbol) and the Suffix (Name of Organization).


Looking at the earlier above comments...

@melchoyce mentions outputting the site title, ©, and the year. Additionally the author credit.
@BinaryMoon mentions a link to the privacy page.
@mapk mentions license type.
To me this could be a version 2 of a Copyright block.

A version 1 would really work on adding something very similar to Michelle's plugin mentioned and seen just above in my comment. Are we on a good to go with getting a developer to create version 1?

@aristath
Copy link
Member

aristath commented Feb 9, 2023

I still don't understand why we need this block.
Is it something that users want to import in multiple pages? Then why can't they create a reusable block with a paragraph and their content? The copyright characters etc all exist and can be properly added in any paragraph.
Is it something that users want in all their pages? If so, then why not add a simple paragraph with that content, in their templates?
Why is a separate "copyright" block necessary if all it contains is plain text? If something is missing from a paragraph which prevents this scenario, then I'd rather we enhance the paragraph block to add the missing features instead of creating a new block for this edge case

@pbiron
Copy link

pbiron commented Feb 9, 2023

We don't need it, but it's certainly a "nice to have". At least 2 of the sample blocks that were mentioned in @paaljoachim 's (now closed) ticket are dynamic blocks (including mine): where the year(s) displayed are dynamic, so that a site admin doesn't have to edit the footer template on Jan 1 every year.

In classic themes, I've always included a shortcode to accomplish that dynamic behavior...so it'd be nice to have a core block for block-based themes. If others decide it's not needed in core, that's fine...I'll just continue to use the block I created ;-)

@aristath
Copy link
Member

aristath commented Feb 9, 2023

I agree that we need some strings that are dynamic... But I'd prefer to have a mechanism to inject dynamic strings in content - in lieu of custom blocks. I have some ideas on that topic, as soon as we're finished with the WP 6.2 release I plan to make a POC and a suggestion for Gutenberg to include them 👍

@peroyomas
Copy link

As I said before, I think that an option of insert an inline text token that always displays the CURRENT YEAR is the minimum to have.

@jordesign jordesign added the [Type] Enhancement A suggestion for improvement. label Aug 16, 2023
@unscripted
Copy link
Member

Has there been any movement on this? Since it's the new year this is top of mind as we just manually updated several site's copyright year.

I know there are several plugins that introduce a year block, but I'd love either a core block or dynamic string method.

@creativecoder
Copy link
Contributor

The recently published "Bits" proposal is a potential alternative to dynamically display the current year: https://make.wordpress.org/core/2024/06/08/proposal-bits-as-dynamic-tokens/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Themes Questions or issues with incorporating or styling blocks in a theme. Needs Dev Ready for, and needs developer efforts New Block Suggestion for a new block [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests