Title: codex – Make WordPress Support --- # Tag Archives: codex [ ](https://profiles.wordpress.org/nacin/) [Andrew Nacin](https://profiles.wordpress.org/nacin/) 1:57 am _on_ October 14, 2014 Tags: codex, Status    # 󠀁[The Codex went read only a few minutes…](https://make.wordpress.org/support/2014/10/the-codex-went-read-only-a-few-minutes/)󠁿 The Codex went read-only a few minutes ago, for a MediaWiki upgrade. I’ll update this post in a few minutes when the upgrade is complete. [#codex](https://make.wordpress.org/support/tag/codex/), [#status](https://make.wordpress.org/support/tag/status/) [ ](https://profiles.wordpress.org/siobhan/) [Siobhan](https://profiles.wordpress.org/siobhan/) 9:20 pm _on_ November 27, 2012 Tags: codex    # 󠀁[Hi all I’ve made a list of all…](https://make.wordpress.org/support/2012/11/hi-all-ive-made-a-list-of-all/)󠁿 Hi all! I’ve made a list of all of the things in the codex that I think need to be updated for WordPress 3.5: https://make.wordpress.org/docs/2012/11/27/if-all-goes-to-plan- wordpress-3-5-will/ It’s in progress so please feel free to add to it. But what’s most relevant, is that some of the updates will be relevant to the user manual too. We’re already aware of the updates to media, but there have been a number of changes to the Settings as well. I’m not sure if they were considered when we created the manual. [#codex](https://make.wordpress.org/support/tag/codex/) [ ](https://profiles.wordpress.org/andrea_r/) [Andrea Rennick](https://profiles.wordpress.org/andrea_r/) 10:48 pm _on_ November 8, 2012 Tags: Chat, codex    # 󠀁[Codex chat](https://make.wordpress.org/support/2012/11/codex-chat/)󠁿 During our regular meeting in IRC we discussed some changes to the codex, based on the roundtable discussion at the WordPress Community Summit. Before we started ripping things apart, I thought it would be good to look at some stats, if possible, and also to get community input. Because it’s one thing to come up with a good idea, but it’s another to make sure that’s what is needed based on numbers and user feedback. So this is basically our gut check. 😉 To that end, here are the top 40 visited Codex pages in the last month or so: /Function_Reference/ /Installing_WordPress, /Template_Tags/, /Version_3.4.2, /First_Steps_With_WordPress,/ Class_Reference/, /Editing_wp-config.php, /Main_Page, /Plugin_API/, /Theme_Development,/ Using_Permalinks, /Pages, /WordPress_Lessons, /Glossary, /New_To_WordPress_-_Where_to_Start,/ Moving_WordPress, /Giving_WordPress_Its_Own_Directory, /Changing_File_Permissions,/ Child_Themes, /WordPress_Backups, /Getting_Started_with_WordPress, /Using_Themes,/ Create_A_Network, /Changing_The_Site_URL, /Roles_and_Capabilities, /Introduction_to_Blogging,/ The_Loop, /Blog_Design_and_Layout, /Conditional_Tags, /Using_Custom_Fields, /Formatting_Date_and_Time,/ Function_Reference, /WordPress_in_Your_Language, /Template_Hierarchy, /Creating_a_Static_Front_Page,/ Post_Types, /Writing_a_Plugin, /Template_Tags, /ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox., /Updating_WordPress, And for perspective, the top page (function reference) got over 1.9 million hits, while the second page was hit only 280,000 times. To me this backs up our earlier conclusion of a divide between users and devs and where they go and what they look for. So the user handbook will likely be well received. Ipstenu made us a shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. for the Codex so we can start marking pages that will considered for removal and send users to the user manual instead. The other thing we talked about, before we go too far, is to create a poll to get feedback on codex reorganization. Some suggested poll items: * I like the codex just as it is, it need some love! * separate user docs from dev docs * something else Your suggestions for poll options are welcome! Without it turning into an actual poll here… 😉 [#chat](https://make.wordpress.org/support/tag/chat/), [#codex](https://make.wordpress.org/support/tag/codex/) [ ](https://profiles.wordpress.org/andrea_r/) [Andrea Rennick](https://profiles.wordpress.org/andrea_r/) 10:44 pm _on_ July 26, 2012 Tags: codex, [docs ( 2 )](https://make.wordpress.org/support/tag/docs/) # 󠀁[Codex work](https://make.wordpress.org/support/2012/07/codex-work/)󠁿 We should probably get a conversation going not only about needed Codex work but* how* to approach a better structure and how to get the work done. I’m leaning towards a re-org and maybe a bit of a division between users docs and programmer notes. A good example of this the [Pages](https://codex.wordpress.org/Pages) page. It starts out as a user doc then jumps right into code. Things like Handbooks need to be sorted out and linked to as well. I think if we could sort out the right approach first and focus on specific pages or topics later, then we’d start making big progress. Possible if we even approached it like a WP dev cycle, with clear targets and a deadline. Possibly a mentorship program as well, wehre we could round up people to help and start handing out assignments and being there to keep people on task and for any questions they have. All thoughts welcome here. 🙂 [#codex](https://make.wordpress.org/support/tag/codex/), [#docs](https://make.wordpress.org/support/tag/docs/)