Siteground's automatic updater will update CP to latest version of WP after migration. Support needs to disable automatic updater.
https://forums.classicpress.net/t/can-site-revert-back-to-wp-after-migration/4305/8

https://wordpress.org/support/article/using-permalinks/

Moved from Notion list.

With ClassicPress/ClassicPress#624 pending merge, we need to create a fallback for the users to get information of why/how they should update PHP.

Preferrably via https://docs.classicpress.net/user-guides/update-php/

See: https://wordpress.org/support/update-php/ and https://make.wordpress.org/hosting/handbook/server-environment/#php

Adding status: on hold until the merge.

https://wordpress.org/support/article/settings-general-screen/

Note: ClassicPress has additional features on this page, such as login image.

Moved from Notion list.

https://wordpress.org/support/article/settings-reading-screen/

Moved from Notion list.

https://developer.wordpress.org/themes/basics/template-files/

Moved from Notion list.

https://wordpress.org/support/article/excerpt/

Moved from Notion list.

https://wordpress.org/support/article/settings-writing-screen/

Moved from Notion list.

Before I outline the proposed permalink structure, I will note that any URL changes will include redirects. So no old URLs will go to the 404 error page.

Right now we have permalinks such as:

https://docs.classicpress.net/user-guides/using-classicpress/posts-screen/
https://docs.classicpress.net/user-guides/debugging-in-classicpress/
https://docs.classicpress.net/developer-guides/installing-with-composer/
https://docs.classicpress.net/plugin-guidelines/plugin-directory-submission-guidelines/

Code reference permalinks are fine, won't be touched:
https://docs.classicpress.net/reference/functions/__autoload/

Proposed structure:

In addition to a long, complex structure, the CPTs are treated as pages. So the parent dropdown is getting longer and longer.

Proposed change 1: Switch CPTs to post type, no need for parents.

Now, once they don't have parents to be part of the URL we would simply that part.

Proposed change 2: Simplify user guides and developer guides permalinks:
https://docs.classicpress.net/user/posts-screen/
https://docs.classicpress.net/developer/installing-with-composer/

Lastly, right now we have plugin guidelines CPT. But we will be adding themes and snippets soon, which would require their own CPTs.

Proposal change 3: Change plugin guidelines CPT to "guidelines" and keep them with page capabilities, so we can use the parent page for each type of guideline:
https://docs.classicpress.net/guidelines/plugins/directory-submission-guidelines/
https://docs.classicpress.net/guidelines/themes/directory-submission-guidelines/
https://docs.classicpress.net/guidelines/snippets/directory-submission-guidelines/

One additional note. Currently, parent/child relationship is used to automatically display a list of child pages on the parent page. We can either do this manually once changes are made or use the object relationship plugin to create necessary associations for a shortcode to display associated posts.

Feedback and suggestions are welcome.

https://wordpress.org/support/article/settings-permalinks-screen/

Moved from Notion list.

Article about writing secure code.

Moved from Notion list.

Based on the proposal #31, the following changes will be implemented:

Permalink structures:

• User manual content: /learn/content-title
• Plugin manual content: /dev/plugins/content-title
• Theme manual content: /dev/themes/content-title
• Code reference content: /reference/content-title (kept as is for now)

To structure the content into "manuals," we will use pages and categories as needed.

https://wordpress.org/support/article/comments-in-wordpress/

Moved from Notion list.

https://wordpress.org/support/article/roles-and-capabilities/

Moved from Notion list.

https://developer.wordpress.org/themes/basics/the-loop/

Moved from Notion list.

https://wordpress.org/support/article/users-your-profile-screen/

Moved from Notion list.

https://wordpress.org/support/article/pages/

Moved from Notion list.

https://codex.wordpress.org/Plugin_API/Action_Reference

Large, complex project.

Moved from Notion list.

https://wordpress.org/support/article/must-use-plugins/

Moved from Notion list.

Link https://docs.classicpress.net/testing-classicpress/#reporting-bugs is broken via https://github.com/ClassicPress/ClassicPress/blob/develop/src/wp-admin/includes/class-wp-automatic-updater.php#L840

Where do the bugs get reported? A PR is needed for core file

Need to add manual installation instructions for WordPress Importer on the Importers page for PR 1173.

Page:
https://docs.classicpress.net/user-guides/using-classicpress/tools-import-screen/

Needs a link for
ClassicPress/ClassicPress#1051 (comment)

Need a decision on whether to converge the info on https://developer.wordpress.org/apis/wp-config-php/ with https://docs.classicpress.net/user-guides/editing-wp-config-php/ I don't see the need to seperate them since the information is related.

We can reduce the linkages and make editorial work on one page. it makes reading it easy as well.

https://developer.wordpress.org/apis/wp-config-php/ is linked in https://wordpress.org/support/article/editing-wp-config-php/ and https://docs.classicpress.net/user-guides/editing-wp-config-php/ for now.

Originally posted by @bahiirwa in #3 (comment)

https://wordpress.org/support/article/embeds/

Moved from Notion list.

https://developer.wordpress.org/apis/handbook/dashboard-widgets/

Moved from Notion list.

https://wordpress.org/support/article/administration-screens/

Moved from Notion list.

https://developer.wordpress.org/themes/basics/template-hierarchy/

Moved from Notion list.

https://wordpress.org/support/article/settings-media-screen/

Moved from Notion list.

https://developer.wordpress.org/themes/

Moved from Notion list.

https://wordpress.org/support/article/settings-discussion-screen/

Moved from Notion list.

https://wordpress.org/support/article/keyboard-shortcuts/

Moved from Notion list.

https://wordpress.org/support/article/tools-screen/

Moved from Notion list.

https://wordpress.org/support/article/comment-spam/

Moved from Notion list.

https://wordpress.org/support/article/importing-content/

Linked to in #28

https://wordpress.org/support/article/media-add-new-screen/

Moved from Notion list.

https://wordpress.org/support/article/tools-import-screen/

Linked to from #15

https://docs.classicpress.net/plugin-guidelines/plugin-header-requirements/ says (yeah, I have had written that myself in past) that:

Requires at least: The lowest WordPress version that the plugin will work on.
Note: this field only works if the plugin is stored on the WordPress Repository.
Note 2: if set, the version should be no higher than 4.9.15

That is suboptimal, because a plugin can very well require WP above 4.9.15 and also support CP.
The way to do that, is to require WP > 4.9.15 in the header, and if CP is active load whatever other code.
This can be done using something like function_exists( 'classicpress_version' ) && version_compare(classicpress_version(), '1.0.0', '>=');

However, due to the header requirements, one wouldn't be able to do that.

Has the CP Community meanwhile created other types of Header tags (remember that the Requires at least actually ONLY works if the plugin is stored on WP Repo), and/or removed this requirement?

Thanks!