search

ClassicPress / Documentation-Issue-Tracker

Issue tracker for ClassicPress documentation.
https://docs.classicpress.net
GNU General Public License v2.0
0 stars 0 forks source link

Updating wp-config.php API #30

Open bahiirwa opened 2 years ago

bahiirwa commented 2 years ago

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 https://github.com/ClassicPress/Documentation-Issue-Tracker/issues/3#issuecomment-1200900074

joyously commented 2 years ago

I think there will be a lot of these questions, because WP split docs into developer info and user info. For the config file, that's a difficult line to draw.

viktorix commented 2 years ago

We do have user guides and developer guides, so it may be right to keep them separate. User guides are lighter, how-tos. While developer guides are more in-depth, technical information they need to build websites, plugins, and themes. If a user looks at the user guides, they wouldn't see wp-config.php article since it will be under developer guides.

I'll leave feedback specifically on the editing wp-config.php issue.