Add a WordPress credit block pattern and load it in the footer

[jffng]

This PR is an attempt to solve #30. It depends on WordPress/gutenberg#33217

It adds a WordPress credit block pattern — which contains some text that can be translated — and includes it in the footer, instead of using the block markup directly.

To test

• Check out the above Gutenberg PR
• Verify the credit in the footer appears as expected in the site editor and front-end
• Verify you can add the pattern in the editor
• Verify you can edit it in the site editor

Kapture.2021-10-07.at.14.42.47.mp4

[kjellr]

Interesting idea! I'm seeing this issue across both of my test sites though:

Edit: Whoops, I missed that this requires WordPress/gutenberg#33217

[kjellr]

Ok now that I've got it working, this is clever! I have one chief concern though: we shouldn't show these translation patterns in the inserter:

I believe the two strings we have in the theme currently are for the footer, and for the 404 page. And it'll look really confusing for folks to see "This page can not be found" text in the pattern inserter. They'll 100% think there's a bug.

So if WordPress/gutenberg#33217 lands, I think we'll also need some way to hide this sort of pattern. Given that, I worry a little bit about the "workarounds on top of workarounds" aspect of this approach. 😅

[LittleBigThing]

Just wondering how this solution would work with multilingual websites? Probably it depends on the plugin that is used, but I assume most popular plugins do (can?) not support this.

[jffng]

Just wondering how this solution would work with multilingual websites?

Since patterns are php files, the strings in those files can be marked for translation just like any other string supplied by a theme or plugin. The site may provide a .po/.pot file for each language, or use a plugin that provides a mechanism to translate + save translated strings.

[jffng]

Closing in favor of #182.