Title: WordPress Codex vs developers
Last modified: August 31, 2016

---

# WordPress Codex vs developers

 *  [Gooly](https://wordpress.org/support/users/gooly/)
 * (@gooly)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/wordpress-codex-vs-developers/)
 * However I think that this question must be asked a dozen times before, I can’t
   find the answer anywhere. And yes, maybe I was living under a rock, but I really
   need an answer to this; What is going on with the WordPress Codex pages? I noticed
   that I’m frequently redirected to a ‘developer’ page when I visit one of the 
   codex pages.
 * Is there some migration going on that I should know of (or lacked to take notice
   of)? The codex pages are my WordPress bible, I could find anything I need there.
   These new developer pages are very brief. To me personally it’s a difference 
   between: “Know every detail about it” to “Nice to knows”
 * Just as an example; I use the codex pages often for functions which allow parameters
   with argument-arrays. As in: “Which arguments can I use here and for what do 
   I need to find or build another solution?”
    These arguments are most of the time
   enumerated in the codex pages. These developer pages only tell me that arguments
   are possible, period.
 * Please understand this right; it’s not a criticism, the ‘problem’ could be all
   on my side, but I’d like to know what the plans are, and I also could use tips
   on how to find the information I’m looking for.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Moderator [James Huff](https://wordpress.org/support/users/macmanx/)
 * (@macmanx)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/wordpress-codex-vs-developers/#post-7287547)
 * Everything in the Codex will be moved over to [https://developer.wordpress.org/](https://developer.wordpress.org/)
   and when that is finished (as well as the HelpHub which sort of ties it all together
   with user documentation), the Codex will be shut down.
 * We’re always looking for more volunteers to help out, so please feel free to 
   stop by [https://make.wordpress.org/docs/](https://make.wordpress.org/docs/) 
   and #docs channel on Slack: [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
 *  [Hemant Arora](https://wordpress.org/support/users/hemantkumararora/)
 * (@hemantkumararora)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/wordpress-codex-vs-developers/#post-8605551)
 * No… please don’t kill Codex.
 * Like Toine said, its a WordPress bible!
 * Codex is for hardcore programmers, and developer, as of now, is for amateurs.
 * I think you’re going to do it anyway, just make sure you copy all of Codex into
   it.
 * P.S. I personally liked the look of Codex.
 *  [rjksn](https://wordpress.org/support/users/rjksn/)
 * (@rjksn)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/wordpress-codex-vs-developers/#post-8836318)
 * Why are we killing Codex? Developer.wordpress.com is really really really badly
   organized. What is the “benefit” of moving to a less useful format?

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘WordPress Codex vs developers’ is closed to new replies.

 * In: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/)
 * 3 replies
 * 4 participants
 * Last reply from: [rjksn](https://wordpress.org/support/users/rjksn/)
 * Last activity: [9 years, 4 months ago](https://wordpress.org/support/topic/wordpress-codex-vs-developers/#post-8836318)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics