classicpress / classicpress-network Goto Github PK

Old code repository for *.classicpress.net - Do not use!

classicpress-network's Introduction

ClassicPress: The CMS for Creators. Stable. Lightweight. Instantly Familiar.

ClassicPress is a community-led open source content management system for creators. It is a fork of WordPress 6.2 that preserves the TinyMCE classic editor as the default option. It is half the size of WordPress, contains less bloat improving performance, and has no block editor (Gutenberg/Full Site Editing).

For more information, see:

Contributions

This project exists thanks to all the people who contribute and who have contributed in the past, whether as part of the long history of thousands of contributions to WordPress from many different people, or as contributions to ClassicPress itself.

Would you like to help? Here is how you can start ›

Financial Contributors

Support the ClassicPress project by making a donation › All donations are tax-deductible in the United States.

Individuals

Organizations

classicpress-network's People

Contributors

Stargazers

Watchers

Forkers

senlin scottybo controlledchaos

classicpress-network's Issues

GitHub download links need updating

Links from https://www-new.classicpress.net/get-classicpress/, probably also appear in other places on the site.

The link to download the migration plugin is currently:

https://api.github.com/repos/ClassicPress/ClassicPress-Migration-Plugin/zipball/1.0.1

but it should be this instead:

https://github.com/ClassicPress/ClassicPress-Migration-Plugin/releases/download/1.0.1/switch-to-classicpress.zip

See https://github.com/ClassicPress/ClassicPress-Migration-Plugin/releases for details. The existing code that gets a list of GitHub releases is probably not flexible enough to handle this situation yet.

The link to download the latest ClassicPress release is currently:

https://api.github.com/repos/ClassicPress/ClassicPress/zipball/1.0.1+dev

but it should be this instead:

https://github.com/ClassicPress/ClassicPress-release/archive/1.0.1.zip

(note different URL format, and also ClassicPress-release instead of ClassicPress repository).

Unable to upload large images

Please could we increase the max upload size to 20mb

Add classicpress-latest.zip download

Split off from https://github.com/ClassicPress/ClassicPress/issues/453

https://www.classicpress.net/classicpress-latest.zip or https://www.classicpress.net/latest.zip to start
future options for latest beta, latest nightly, etc?

Download page

Rough mockup

Existing WordPress Site?              [Switch to ClassicPress vX]

text here

New ClassicPress Site?                [Download ClassicPress vX]

text here

Need more help?

text here explaining quickly how to get a server and install ClassicPress on it

where the Existing WordPress Site? and New ClassicPress Site? are section headings, and the [Switch] and [Download] are big, clear buttons that link to the zip files

Set up redirects for blog posts

The current site uses the date in blog post permalinks, the new site does not.

Redirects from Ray, though it should be possible to do this with a single redirect:

Redirect 301 /blog/2019/07/02/meet-the-community-simone-fioravanti/ https://www.classicpress.net/blog/meet-the-community-simone-fioravanti/
Redirect 301 /blog/2019/06/27/classicpress-development-update/ https://www.classicpress.net/blog/classicpress-development-update/
Redirect 301 /blog/2019/06/27/creating-a-child-theme/ https://www.classicpress.net/blog/creating-a-child-theme/
Redirect 301 /blog/2019/06/19/meet-the-community-pete-thomas/ https://www.classicpress.net/blog/meet-the-community-pete-thomas/
Redirect 301 /blog/2019/06/05/meet-the-community-zulfikar-gani/ https://www.classicpress.net/blog/meet-the-community-zulfikar-gani/
Redirect 301 /blog/2019/05/29/meet-the-community-michelle-coe/ https://www.classicpress.net/blog/meet-the-community-michelle-coe/
Redirect 301 /blog/2019/05/20/meet-the-community-tommy-thanasi/ https://www.classicpress.net/blog/meet-the-community-tommy-thanasi/
Redirect 301 /blog/2019/05/15/meet-the-community-earle-davies/ https://www.classicpress.net/blog/meet-the-community-earle-davies/
Redirect 301 /blog/2019/05/08/meet-the-community-dick-metcalf/ https://www.classicpress.net/blog/meet-the-community-dick-metcalf/
Redirect 301 /blog/2019/05/01/meet-the-community-daniele-scasciafratte/ https://www.classicpress.net/blog/meet-the-community-daniele-scasciafratte/
Redirect 301 /blog/2019/04/24/meet-the-community-laurence-bahiirwa/ https://www.classicpress.net/blog/meet-the-community-laurence-bahiirwa/
Redirect 301 /blog/2019/04/17/meet-the-community-nerissa-mccanmore/ https://www.classicpress.net/blog/meet-the-community-nerissa-mccanmore/
Redirect 301 /blog/2019/04/10/meet-the-community-lesley-jones/ https://www.classicpress.net/blog/meet-the-community-lesley-jones/
Redirect 301 /blog/2019/04/08/directors-added-to-classicpress-limited/ https://www.classicpress.net/blog/directors-added-to-classicpress-limited/
Redirect 301 /blog/2019/04/04/what-is-missing-in-the-classicpress-project-that-you-could-contribute-to/ https://www.classicpress.net/blog/what-is-missing-in-the-classicpress-project-that-you-could-contribute-to/
Redirect 301 /blog/2019/04/01/meet-the-community-wade-striebel/ https://www.classicpress.net/blog/meet-the-community-wade-striebel/
Redirect 301 /blog/2019/03/27/meet-the-community-ian-grieve/ https://www.classicpress.net/blog/meet-the-community-ian-grieve/
Redirect 301 /blog/2019/03/22/meet-the-community-patrick-van-noort/ https://www.classicpress.net/blog/meet-the-community-patrick-van-noort/
Redirect 301 /blog/2019/03/19/meet-the-community-andy-towler/ https://www.classicpress.net/blog/meet-the-community-andy-towler/
Redirect 301 /blog/2019/03/12/upgrade-your-site-to-classicpress-1-0-1/ https://www.classicpress.net/blog/upgrade-your-site-to-classicpress-1-0-1/
Redirect 301 /blog/2019/03/11/meet-the-community-alan-coggins/ https://www.classicpress.net/blog/meet-the-community-alan-coggins/
Redirect 301 /blog/2019/03/06/meet-the-community-james-nylen/ https://www.classicpress.net/blog/meet-the-community-james-nylen/
Redirect 301 /blog/2019/03/05/introducing-classicpress-1-0-0-aurora/ https://www.classicpress.net/blog/introducing-classicpress-1-0-0-aurora/
Redirect 301 /blog/2019/03/04/meet-the-community-elisabetta-carrara/ https://www.classicpress.net/blog/meet-the-community-elisabetta-carrara/
Redirect 301 /blog/2019/02/27/classicpress-1-0-0-rc2-is-live/ https://www.classicpress.net/blog/classicpress-1-0-0-rc2-is-live/
Redirect 301 /blog/2019/02/25/what-does-community-led-mean-anyway/ https://www.classicpress.net/blog/what-does-community-led-mean-anyway/
Redirect 301 /blog/2019/02/24/classicpress-1-0-0-release-update/ https://www.classicpress.net/blog/classicpress-1-0-0-release-update/
Redirect 301 /blog/2019/02/22/meet-the-community-john-alarcon/ https://www.classicpress.net/blog/meet-the-community-john-alarcon/
Redirect 301 /blog/2019/02/20/classicpress-1-0-0-rc1-is-live/ https://www.classicpress.net/blog/classicpress-1-0-0-rc1-is-live/
Redirect 301 /blog/2019/02/18/where-is-classicpress-headed/ https://www.classicpress.net/blog/where-is-classicpress-headed/
Redirect 301 /blog/2019/02/11/why-choose-classicpress-for-your-business-professional-website-cms/ https://www.classicpress.net/blog/why-choose-classicpress-for-your-business-professional-website-cms/
Redirect 301 /blog/2019/02/07/classicpress-core-development-update/ https://www.classicpress.net/blog/classicpress-core-development-update/
Redirect 301 /blog/2019/02/03/classicpress-a-six-month-review/ https://www.classicpress.net/blog/classicpress-a-six-month-review/
Redirect 301 /blog/2019/01/29/classicpress-localization/ https://www.classicpress.net/blog/classicpress-localization/
Redirect 301 /blog/2018/12/18/upgrade-your-site-to-1-0-0-beta2-now/ https://www.classicpress.net/blog/upgrade-your-site-to-1-0-0-beta2-now/
Redirect 301 /blog/2018/12/06/can-i-use-the-classicpress-beta-on-live-website/ https://www.classicpress.net/blog/can-i-use-the-classicpress-beta-on-live-website/
Redirect 301 /blog/2018/11/27/how-to-support-classicpress-on-giving-tuesday/ https://www.classicpress.net/blog/how-to-support-classicpress-on-giving-tuesday/
Redirect 301 /blog/2018/11/21/classicpress-beta-release/ https://www.classicpress.net/blog/classicpress-beta-release/
Redirect 301 /blog/2018/11/05/michelle-coe-joins-the-classicpress-founding-committee/ https://www.classicpress.net/blog/michelle-coe-joins-the-classicpress-founding-committee/
Redirect 301 /blog/2018/11/03/accessibility-and-universal-design-core-features-of-classicpress/ https://www.classicpress.net/blog/accessibility-and-universal-design-core-features-of-classicpress/
Redirect 301 /blog/2018/10/29/classicpress-for-business-professional-organization-websites/ https://www.classicpress.net/blog/classicpress-for-business-professional-organization-websites/
Redirect 301 /blog/2018/10/25/a-new-dawn-announcing-sunrise-the-first-alpha-release-of-classicpress/ https://www.classicpress.net/blog/a-new-dawn-announcing-sunrise-the-first-alpha-release-of-classicpress/
Redirect 301 /blog/2018/10/18/theme-and-plugin-compatibility-with-classicpress/ https://www.classicpress.net/blog/theme-and-plugin-compatibility-with-classicpress/
Redirect 301 /blog/2018/10/17/project-management-planning-initial-meeting/ https://www.classicpress.net/blog/project-management-planning-initial-meeting/
Redirect 301 /blog/2018/10/09/committee-meeting-the-one-with-the-orange/ https://www.classicpress.net/blog/committee-meeting-the-one-with-the-orange/
Redirect 301 /blog/2018/09/26/committee-meeting/ https://www.classicpress.net/blog/committee-meeting/
Redirect 301 /blog/2018/09/11/tutorial-resolving-merge-conflicts-on-the-classicpress-github/ https://www.classicpress.net/blog/tutorial-resolving-merge-conflicts-on-the-classicpress-github/
Redirect 301 /blog/2018/09/08/committee-meeting-a-focus-on-v1-roadblocks/ https://www.classicpress.net/blog/committee-meeting-a-focus-on-v1-roadblocks/
Redirect 301 /blog/2018/08/28/wordpress-gutenberg-the-500-million-cost-to-business/ https://www.classicpress.net/blog/wordpress-gutenberg-the-500-million-cost-to-business/
Redirect 301 /blog/2018/08/20/classicpress-a-fork-of-wordpress-without-gutenberg/ https://www.classicpress.net/blog/classicpress-a-fork-of-wordpress-without-gutenberg/

Check for PHP notices

I saw several of these during local development, we need to make sure notice logging is enabled on the server (but disabled on the frontend) and then look through the logs for anything else that was missed.

Add custom error pages

In https://github.com/ClassicPress/ClassicPress/issues/20#issuecomment-425661592, @stefanos82 writes:

https://www.classicpress.net/wp-content/uploads/ and https://www.classicpress.net/wp-includes/ return plain NGINX 403 Forbidden message.

The website needs custom error messages to reduce valuable information about the stack tech used behind the scenes.

cc: @dsnid3r @striebwj @scottybo

FA external-link-alt not showing

Just shows as a square:

Here is the css:

Contact Form not working

The contact form on the new website returns and error:

message: "There was an error trying to send your message. Please try again later."
status: "mail_failed"

Update author descriptions/profiles

Multiple authors have "lorem ipsum" style text in their profile. For example, from https://www-new.classicpress.net/blog/meet-the-community-tommy-thanasi/:

Improve Discourse comment styling

Waiting for #38, but once that's done, the comments will look something like this:

There are some styles on the current site that can be copied over / adapted to make this work better.

Update screenshot on homepage

We should use a higher-resolution image here, and also an image from the latest version of ClassicPress.

Blockquote with only margin doesn't distinguish other paragraphs in a blog post.

Only defining the blockquote style as a margin doesn't distinguish other paragraphs in a blog post.

Take for example the below image, can you spot the important section:

Compared to something like this:

Adding this to the border, did the trick

 border-left: 4px solid #057f99;
 padding-left: 1em;

What do you think?

Fix menu dropdown effect

With JavaScript disabled, or before the page has loaded the menu JavaScript, the menus look like this:

Not good - the menu dropdown effect should use CSS instead.

Use of !important will make future maintenance more difficult

As of now:

$ grep '!important' wp-content/themes/classicpress-susty-child/style.css | wc -l
36

None of these should be necessary:

$ grep '!important' wp-content/themes/susty-master/style.css | wc -l
3

All 3 instances in the parent theme are related to the screen-reader-text class which is a bit of a special case and shouldn't need to be overridden anywhere.

Network URLs missing social meta tags.

I went to share the CP migration page on Twitter and the Tweet didn't expand with a graphic or description. It looks like the Twitter tags aren't present, so it displays as a text link that doesn't stand out or compel an interaction. Adding these tags network-wide will allow people to share any page and have the post show up with an icon and description.

Link on Get Involved page needs to be updated

On the Get Involved page, there's a button to "View our dev todo list". This button leads to a closed milestone. It should probably be updated.

Home Page Issues

CTAs to switch/download ClassicPress start the download... but, what does the user do next? A small link under each CTA leading to instruction would help. There is a CTA leading to docs below; it's not close enough to serve the purpose.
Improved Security block on homepage, missing comma. It should read, "We are, too."

Latest post title showing on 404 page

The 404 page is showing the title of the latest post. My guess is there's a custom query in the 404 template that missed a call to wp_reset_postdata().

Investigate HTML validation results

Some things to fix here: https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww-new.classicpress.net%2F

Follow-up from ClassicPress/ClassicPress-Themes#23

Problems with FAQ page

Reported in Slack

On the website, under FAQs "Is there a list of plugins and themes compatible with CP?" The link on "See Will WP plugins/themes work with CP?" doesn't work - it goes anywhere.Also 'copyright 2018' needs updating.

Join Slack Link

I think we should be using the https://classicpress.net/join-slack/ link.

I would also like to see the same thing set up for Discord so we don't need to find that link everytime someone asks.

Link blog posts to Discourse forum topics

Need to export the correct postmeta values from the current site and import them into the new site, then make sure comments show up.

Accessibility issue with Democracy page

@KTS915 says:

Just an update on accessibility on the ClassicPress website. @senlin and I have fixed most of the accessibility issues, but there is a big one left that we can't fix while we use Elementor. The problem is on this page: https://www.classicpress.net/democracy/ and the problem lies with the accordion after the heading "Our democratic structure, rights & responsibilities".

There are actually two problems with this. (I initially thought it was just one, but actually things are much worse than I thought.) The first is that Elementor assigns a tabindex to each section within the accordion, and that tabindex corresponds with the section's id. This means anyone using a screenreader gets taken straight to those sections before anything else on the page, and only gets to things like the menu afterwards. That is so disorientating as to probably make the page unusable.

But it's actually worse than that. Because there is no way for a screenreader user actually to access the content within each section! They can only read the title. This has been reported previously, but no fix has been forthcoming. See elementor/elementor#3576

Maybe this should be a private repo

I saw that this repo contains ElementorPRO in it, which is not GPL, maybe this repository should be a private one to make sure that there will be no legal problems.

Several missing redirects

Looks like a roadmap redirect was missed when building the new site. Recommend scanning the database and replacing with the new URL, as well as setting up a redirect to preserve any previously created external links.

Old URL: https://www.classicpress.net/classicpress-roadmap/

New URL: https://www.classicpress.net/roadmap/

Reported via the forums.
https://forums.classicpress.net/t/introducing-the-new-classicpress-website/1536/11

Make sure all blog posts were imported from the old site

Before launch we need to make sure that https://www.classicpress.net/blog/ and https://www-new.classicpress.net/blog/ match (and that the Discourse comments are imported for any new posts also, see #38). Currently there is 1 more post on the old site.

Roadmap Issues

The word "our" is not needed in this link:
The word "Our" here is miscapitalized, but, it's awkward; I'd remove the word altogether.
The phrase "backwards compatible" is incorrect. Correct is "backward compatible".
The phrase "plugin / theme authors" should be fully spelled out as "plugin and theme authors"
The term "security-first" doesn't need a hyphen.
The phrase "We’ve introduced a well-thought-out versioning scheme based on a modern industry standard" is awkward. It flows better with less words as:
"We’ve introduced a modern industry-standard versioning scheme". Also, this entry lacks a period while the other items in the list do not:
External link indicators seem outlined but missing; see previous screenshot.
Less bloat section: missing comma.
Headings should follow title-caps format:
Missing hyphens? "little-to-no
Incorrect wording "included into" should read "included in"
Inconsistent capitalization; (this and other pages) some say "Version 1" and "Version 2" while others say "version 1" and "version 2" Scan the database and replace one way or the other for consistency.
Misspelling "modernise"
A single sentence is not a paragraph.
Incorrect wording "in service to our mission to create" should be "in service of our mission to create"
Awkward wording: "turned on by default" should be "enabled by default"
"Through no fault of their own" is not really true; I'd remove it. Also the word "poor" could be replaced with "lower".
Punctuation should lie within parentheses, not outside. Not just this page.

Add blog section to homepage

I think this is a valuable feature of the current site, others agree/disagree?

Support per-locale GlotPress admins

Quoting @Mte90 from Slack:

the big problem is that glotpress doesn't support admin for locales but admin for all the locales and project
instead wp.org has that because they implemented it and replicate it require a lot of studying of the code because there is no documentation

or we create a new group with the various capabilities but again the problem to assign a specific locale to an user without developing is very difficult

Header/Footer Issues

Header menu. The word "ClassicPress" is repeated so many times that it clutters the menu. SEO should never trump UI. I'd remove it from all but the About link.
Footer links. The underlines look bad. Also, there are two links to the contact page "Contact" and "Press Inquiries" One or the other is redundant.