classicpress / site-www

Files for the site at www.classicpress.net

www.classicpress.net

This repository contains the files for https://www.classicpress.net/.

Local development

Download the site files and contact a site administrator (probably James) for a recent database dump.

Load the database dump into a MySQL database on your computer. The site is configured using a .env file, so you can copy .env.example to .env and fill in your database values there.

You will need to install composer and run composer install in order to download the library that makes the .env file work properly.

Then update the site URL, for example using WP-CLI:

wp search-replace https://www.classicpress.net http://www.classicpress.local

Finally add a local administrative user, for example:

wp user create admin [email protected] --role=administrator --user_pass=changeme

Pull requests

We accept pull requests for this website via GitHub. Many of the guidelines at https://github.com/ClassicPress/ClassicPress/blob/develop/.github/CONTRIBUTING.md also apply here, for example:

• Please be sure to test your PR on a local development installation as described above, or at least using the browser development tools.
• Please include screenshots of the site before and after your changes as well as an explanation of what has been changed and why.
• Some parts of the above guidelines are specific to ClassicPress core and do not apply here, like the instructions for backporting changes from WP and running the automated tests.

Please always use a separate branch for each change, to avoid issues with your master branch not being reset or updated correctly in between different pull requests. If you're not sure how to do this, you can use the GitHub web interface to edit files, open a new branch, and propose your changes as a pull request.

CSS/JS changes

If you make any CSS or JS changes, you need to update version number in the functions.php to clear cache:

function cp_susty_get_asset_version() {
    return '20210919';
}

Use the date when the changes were made as the version number in the format YYYYMMDD. If there are multiple changes in one day, you can add a decimal to increment the version number (ex: 20210919.1, 20200919.2).

site-www's Issues

Home page CTAs aren't calling to action

The donation and download buttons at the top aren't calling to action for a few reasons:

1. Little contrast. Nothing calls attention to them.
2. Tiny fonts. CTAs should have larger, bolder text than the rest of the buttons/links.
3. Tiny buttons. The menu items are larger than the CTAs.

Current

Recommend at the very least changing the background color of the download link, although the buttons should be made larger and moved to a more appropriate area for a CTA.

This rule purples the final anchor in the list, though that may be assuming too much.

#secondary-nav .smenu ul li.switchbutton.download:last-child a {
    background: #89288f;
}

Update FAQ entry for migration and rollback

FAQ: Can I convert a WordPress site to ClassicPress – and what if I don’t like it?

Says, "We are working on a way to automate the rollback." Is this not already done?

Add a "Switch to ClassicPress" graphic to the brand assets page.

Per Slack convo, add the following image(s) to the official brand assets page.

Review css class structures

See #30 discussion regarding the homepanel1 and homepanel2.

Sitemap

Could we add a sitemap to the new site, it would be great to submit it to Google Search Console.

This link is no longer active - Slack

The link https://www.classicpress.net/join-slack/ from upper left corner of main page does not work.

I have an account for WooCommerce and cannot use it to sign in on classicpress workspace.

Can anyone advice me what to do?

Code display plugin on ClassicPress.net not working

Is the plugin broken? I can't see the button in the editor and the code that's normally displayed like:

Is now displayed like:

FAQ page improvements

• Allow linking directly to an individual FAQ entry (this should expand that answer)
• Allow expanding all FAQs at once
• Look for places where we linked to FAQ entries on the old site (using #fragments) and make these links work again

Privacy/Cookie Policy

Not critical, but we should update the privacy/cookie policy and ideally it should live somewhere on our site (not link out Iubenda).

We also have a different privacy policy on the forums.

Better link previews in Slack

I am not sure exactly how this works but here you can see that forums.classicpress.net (Discourse) has nicer link expansions in Slack than our sites do:

Improvements to Brand Guidelines page

This has the potential to be a pretty large issue so it may be a good idea to break it up into smaller issues once we start on it. See also https://forums.classicpress.net/c/team-discussions/design-forum for other relevant discussion.

Quoting from Slack today:

Has anyone else noticed that the new website doesn't quite follow the brand guidelines? Some of the headers use #4b2063 instead of Deep Purple Violet (#361946) and others use Mid Violet (#89288f). Am I being too pedantic? Personally, I think #4b2063 is better than #361946 anyway as I think the latter is a tad too dark. Just my tuppence worth.
On a related note, is it worth adding the CMYK and RGB codes in addition to the hex?

...

https://github.com/ClassicPress/ClassicPress-Themes/wiki/Design-Specs
we shouldn't be using this repo for anything anymore, but the #4b2063 comes from there
one of the colors in the "Purple Gradient"

We could use some clearer guidelines for when to use each color or visual element.

Quick note/aside about fonts:

The Wiki page on Github also shows the font as DejaVu Sans whereas we're using Source Sans Pro.
I can answer the font question, in that case https://www.classicpress.net/brand-guidelines/ and the site are correct with Source Sans

A few things to do, there are undoubtedly more:

• get some clarification on when to use each purple color [and probably other design elements as well], this is a question for @BlueSkyPhoenix, but to my eye at least the current site is doing it right
• general improvements to the documentation at https://www.classicpress.net/brand-guidelines/
• make https://github.com/ClassicPress/ClassicPress-Themes/wiki/Design-Specs and https://docs.classicpress.net/press-and-branding/ go away, any content, visual guides etc in these pages that is not already at https://www.classicpress.net/brand-guidelines/ should be folded into that page [see also https://github.com/ClassicPress/ClassicPress-Themes/issues/25]

https://docs.classicpress.net/press-and-branding/ contains a shortcode that currently lives in this repository to display a list of images: https://github.com/ClassicPress/ClassicPress-Network/blob/master/wp-content/mu-plugins/file-list.php

This shortcode should be ported over to the new site and possibly re-styled since it will no longer be the main element on the page.

Another idea for this asset/file list would be to sort the logos into categories, explain when to use each one, and also present downloadable files in a couple of different formats (.png for example).

This issue is intended to be a brain dump of some fairly minor improvements that should not require a full re-working of the brand guidelines. If you are interested in working on some of this then drop a comment here and let's chat.