search

ClassicPress / ClassicPress-docs

ClassicPress documentation content
1 stars 5 forks source link

FAQs page #4

Open nylen opened 4 years ago

nylen commented 4 years ago

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:

Norskes commented 4 years ago

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.

Absolutely agree.

I'd also propose that we split FAQ for Users and FAQ for Developers, since they have totally different needs/interests. Later we can reference/include these content parts separately to extend our segmented landing pages of a main site. We can follow the same structure when adding any other segment ("CP for business", "CP for agencies" etc.) if needed. This model is extensible.

nylen commented 4 years ago

I'd also propose that we split FAQ for Users and FAQ for Developers,

Sounds good, this will also help us keep the length of these pages down.

smileBeda commented 2 years ago

Well, the page is still there.

Should I remove it? It takes the click of a button, but it also takes a redirect, which I cannot do.

@nylen - can you do the redirect and let me know when this is done so I can delete that page? (I refer to delete https://www.classicpress.net/faq/ and redirect it to https://docs.classicpress.net/user-guides/faq-and-support/)

I'd also propose that we split FAQ for Users and FAQ for Developers,

If we have some FAQ for developers please let me know. As for now, our doc is here https://docs.classicpress.net and perhaps this requirement is now obsolete.