Support date range in footer copyright element

[chalin]

• Contributes to:
  • Footer layout refactoring and improvements for 0.9.0 #1818
  • Cleanup: don't hard-code styles into layouts #783
• Fixes Allow configuring the range of copyright years at the footer #436
• From the CHANGELOG:

  • Footer copyright:
    • The Hugo config option params.copyright can be a map with the following
      optional fields: authors, from_year, to_year. When unset, to_year
      defaults to the year that the site built. The default authors is "Site Authors"
      and is rendered as markdown.
    • If params.copyright is unset, then the site copyright option will be
      used and rendered as markdown, "as is" — with no year is added.

• Sets the User Guide Hugo config options as an example, illustrating the use case shown in The footer should allow a more flexible copyright statement #2 of "Copyright 2018 The <product_name> Authors | Documentation Distributed under CC BY 4.0"

  params:
    copyright:
      authors: >-
        Docsy Authors |
        [CC BY 4.0](https://creativecommons.org/licenses/by/4.0) | 
      from_year: 2018
    # ...
    ui:
      footer_about_disable: true

User Guide screenshots

Wide screen:

Narrow screen:

[chalin]

@emckean - what would be the right starting year for the copyright in the User Guide?

[yann-soubeyrand]

Hi @chalin,
What’s the rationale behind this change (previously it was {{ with .Site.Copyright }}{{ . | safeHTML }}{{ end }})? I’m worried that it makes it difficult to include HTML badges like the ones generated from https://chooser-beta.creativecommons.org/.

[yann-soubeyrand]

Hi @chalin, friendly ping as I don’t know if you received a notification for my question above?

[chalin]

Thanks for the ping @yann-soubeyrand -- I'll get back to you this week before the next Docsy release :).

[yann-soubeyrand]

Thanks!

In the meantime, I found how to achieve what I needed by putting this in my config:

copyright: |
  ++++
  Copyright Camptocamp SA
  <p xmlns:cc="http://creativecommons.org/ns#" xmlns:dct="http://purl.org/dc/terms/"><span property="dct:title">Content</span> is licensed under <a href="http://creativecommons.org/licenses/by-sa/4.0/?ref=chooser-v1" target="_blank" rel="license noopener noreferrer" style="display:inline-block;">CC BY-SA 4.0<img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/cc.svg?ref=chooser-v1"><img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/by.svg?ref=chooser-v1"><img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/sa.svg?ref=chooser-v1"></a></p>
  ++++

I’m using AsciiDoc and ++++ is used for pass-through blocks. I haven’t searched if it’s possible to do something similar in Markdown (maybe by allowing unsafe content in Goldmark?).

[chalin]

Hi @chalin, What’s the rationale behind this change (previously it was {{ with .Site.Copyright }}{{ . | safeHTML }}{{ end }})? I’m worried that it makes it difficult to include HTML badges like the ones generated from https://chooser-beta.creativecommons.org/.

@yann-soubeyrand: My rational was to make processing consistent across alternatives, but it doesn't really need to be consistent -- I can claim backwards compatibility for .Site.Copyright. That is, I'm willing to revert back to the old behavior for .Site.Copyright. How does that sound to you?