ClassicPress branding changes

[viktorix]

Change everything to use ClassicPress branding.

• [ ] Color changes (where?)
• [ ] #43
• [ ] #37
• [x] #36
• [ ] #29
• [ ] #30
• [x] #31
• [x] #34
• [ ] #35
• [ ] #46

This is not a complete list. There may be more.

[mattyrob]

It may fit well as part of this Issue to consider Documentation blocks.

At the top of many files there are sections like: @package WordPress

We should consider changing those to: @package ClassicPress

I would propose we can leave upstream @since and @deprecated version numbers as they are to ease future backporting. To differentiate our code introductions we should prefix the version, so @since CP-1.1.0 for example.

Swapping other instances of WordPress in document blocks can also probably be left, I see no problem leaving those alone, it's no secret that ClassicPress is a fork of WordPress.

[viktorix]

We should replace WordPress with ClassicPress based on the context. In some places it's more accurate to have ClassicPress. But, this can be done as we go and should not stop anything. For example, wp-activate.php line 11:

• https://github.com/ClassicPress/wp-cms-experimental/blob/main/src/wp-activate.php#L11
• /** Sets up the WordPress Environment. */

---

For @package WordPress, I just submitted a PR #4 with that specific change using sed. 879 files.