classicpress / classicpress-docs Goto Github PK

@nylen - would you mind deleting everything in this repository?

We have the ClassicPress/site-docs for the actual code of the website and this repo here is redundant in terms of content, not in terms of usage.

I intend in fact to use it for a "issue reporting tool" for the doc and for contributors to create at least one PR which then allows us to automatically count and list the DOC Writers (using the GIT api).

Do you agree with this?
Then lets delete everything in this repo, and I will write a good new Readme, then link to this from the DOC site as a "report issue for" thingy and on the contributor page on our website we can then point to this repo as of "If you are contributing to CP Docs, please commit a PR to the repo with your forum username (and other details we may require, not sure yet)"

Does that make some sense to you as well?

I mean, we could also just manually fill a CSV with the contributors and read that to produce a dynamic page with contributors, but... you know, manual jobs are not my favourite 🤦

We have https://www.classicpress.net/faq/ and https://docs.classicpress.net/faq-support/. I propose that we remove this page from the main site, and store the FAQs here under documentation, thereby unifying these two pages into one.

We also had some old FAQ material that was pretty useful, such as an email template to contact plugin authors when asking them to preserve support for WP 4.9.x and therefore ClassicPress. I can dig this up when we're ready, but we can de-duplicate the FAQs first.

Other things we might want to consider adding:

• "Which plugins can I use with ClassicPress?" See also: https://github.com/ClassicPress/ClassicPress/issues/526 / https://forums.classicpress.net/t/plugins-from-wp-4-9/2063
• Some other ideas at ClassicPress/ClassicPress-Themes#6, though we want to make sure that we include FAQs that are actually asked frequently, and avoid making this page too long!

Didn’t see anything specific in the Get ClassicPress or install documentation, for: recommended PHP, MySQL, or MariaDB versions.

For website transfers, we match software versions, then help to upgrade if needed. For new installs, it would be good to be as current as possible. Since its a 4.9 branch are PHP versions 5.1 to 5.3 supported?

Can you add this info to the Get ClassicPress page and isntallation info (unless I missed it)?

From https://forums.classicpress.net/t/php-and-db-versions/1836

Good first task for after we migrate the docs site over to Markdown.

On the Press and Branding page there are 3 unwanted files:

• README.md
• autogenerated
• bin

It would probably make sense to tweak the generate-assets.sh from the ClassicPress-Design to include a copy of the svgs.

Child pages should be added into navigation chain somehow.

For example, at the moment there is no way to discover the Security page when looking through the Docs structure. Because there is no link on its parent page Developing ClassicPress.

We might also need breadcrumbs. And (ideally) a searchform.