* Remove references to font family not used in the theme
* Update theme.json
Remove references to Source Sans font, not included in the theme (I believe this was a leftover from development process).
* "Cottage is blogging theme with a cottagecore aesthetic."
Issues caused by CBT described here must be addressed.
* A round of updates
* Fixed the empty alt attributes.
* Fixed the WordPress link in the footer.
* Fixed the quote on the homepage.
* Remove hidden .DS_store files
---------
Co-authored-by: alaczek <ola@bodera.com>
This PR changes the current theme preview workflow to use an external
function that executes the same process, but has two advantages:
1. It runs using `pull_request_target`, meaning that PRs created from
forks will get previews too.
2. The action can be shared with other repos with a similar structure to
get Playground previews as well, such as the [WordPress Community Themes](https://github.com/WordPress/community-themes) repo.
The Handy theme has been renamed to Fixmate in #7992. Given that Handy
was added just yesterday, isn't active on any site and has never been
network activated, it won't have been used on any site. I'm therefore
removing it entirely rather than leaving an unused theme lying around
the repo.
The footer copyright statement has been removed from the following themes:
* Vitrum
* Fontaine (x2)
* Pendant
* Bitacora
* Jaida
The standard for a while has been to use "Designed with WordPress" (or something similar) in the footer, rather than a copyright statement. Additionally the copyright line is often incorrect - where it hardcodes the year, this is obviously not accurate and where it credits the name of the blog, or states "All Rights Reserved", this may not be accurate either. We should leave it to users to set their own copyright statements appropriately, and most of these themes leave an empty paragraph available to make it easy to do that.
The copyright symbol in these themes was just positioned infront of
'Designed with...' which didn't make sense. Removing completely - users
would've needed to customise the pattern for the copyright to have made
sense anyway.
`gh pr create` can't non-interactively push a branch and create a PR.
Just use a plain old `git push` before running `gh pr create --head`
which will work non-interactively if the branch is already pushed.
The dotted separator wasn't displaying because the height of the
separator was too small. This change overrides the height for the dotted
separator only.
The dotted separator wasn't displaying because the height of the
separator was too small. This change overrides the height for the dotted
separator only.
This changes all usage of `arc` to GitHub's `gh` utility.
---------
Co-authored-by: Miguel <miguel.san.segundo@automattic.com>
Co-authored-by: Dean Sas <dean.sas@automattic.com>
