Scalability.
When we talk about sharding a MySQL database people talk mostly about multisite. I am designing a site thats more of an application. I’m using Custom posts to handle most data objects because they share many of the same fields(name, created date, author, etc.)
Currently I am looking at 1,000 posts being created a day with at least that many being modified. When we release and the plans of the company using the app I will hit 1,000,000 posts in less than a year.
This is on a single post table, all with custom meta info. Talking to folks like JJJ makes me scared that it wont be sustainable. I have a auto scaling redundant hosting setup but a 1,000,000 record table seems like its going to slow things down.
I know separate tables is devil talk in the core WP world and more of a PODS thing, but I can’t just shard off parts like multisite folks.
If we are really talking about using WordPress as a CMS beyond mom and pop stores, how do we address post tables of that size?
I would also love to see WordPress include native translation management; something implemented in the same way as Multi-Site for those of us who need it.
How do you see WordPress using its position as an industry leader to effect change in other areas?
For example, WordPress’ minimum server requirements and supported browsers will affect user behavior and have an economic impact on browser makers and hosting companies.
Also, WordPress’ innovations and usability are adopted by other developers and systems.
What are the ripples that we don’t see?
As a visually impaired person who uses the latest version of the JAWS For Windows screen reader I would like to know how much a priority are improvements specifically for keyboard and screen reader accessibility. I also use the latest version of the NVDA screen reader at times but judging by the dashboard and interface as a whole of version 3.3 it honestly does not seem anybody really cares about how the blind ‘see’ the WordPress backend. I might be wrong but version 3.2.1 was much more clean it seems. I hope the year of 2012 will be a year in which priority for improvements geared towards the blind and visually impaired are greatly emphasised.
I read this and that about how everything looks visually but people need to shut off their monitors and disable their track pads for a day so they can fully experience what I experience. If the developers of WordPress awoke one day not able to see anything how many of them would be able to use WordPress to its maximum potential? I enquire to software developers all the time with whose applications I have problems and I just hope that makes people stop and really think about [1] if they must change anything; [2] what they must change; [3] how to implement those changes no matter what the cost. Why? Because everybody deserves fair access to WordPress [for sake of discussion here].
it honestly does not seem anybody really cares about how the blind ‘see’ the WordPress backend
Please see the recent discussions on http://make.wordpress.org/accessibility/
Nice read. I hope people go places with it.
Please feel free to join in. It would be nice to get some feedback from a NVDA screen reader user instead of just JAWS users. 🙂
I will try using NVDA whilst navigating the dashboard and other aspects of the backend instead of JAWS. Do you mean to post a comment on that accessibility post in respect to feedback?
Yes please. The more feedback we can get from AT users, the better. It will all go towards increasing accessibility in future versions of WordPress.
also important: reduce memory usage/queries & increase overall speed (with 3.3, memory usage increased again by 2-3% with 128MB php memory)
thanks for offering the video town hall! looking forward to it.
- when/how/where can we check when it will be so we can tune in?
- at the town hall, in the new dev. features section, can you please make the first order of business to do live demo examples of how to use/access new features like Flexible Permalinks, the Post Slugs spec. characters fix, how to use/access the jQuery and jQuery UI 1.7.1 features, creating new admin screens in the WP_Screen API, and how to use the new features in the overhaul of the Editor API?
that’s what i’m looking for. thank you & looking forward to it.
Native JSON support… I rely on a plugin that works great, but it feel it is irresponsible to build dependable infrastructure on a user contributed item that may break with the next update.
And there might not be a big need, so how about an Automattic sponsored plugin?
Echo the comments about improved accessibility.
I’m guessing you’ll need more than that so will take a bit of time to analyse 3.3 and then post some suggestions.
It’s good to open up for thoughts now – accessibility should always been designed in, not just tacked on at the end.
Thanks
Related to previous commentator’s search question…
1. Are there any plans to give attention to enhanced search in Multisite? (options in each site on the network to search “entire network” or “search these specific sites on the network”)
2. Is it possible to include the ability to customize the user and site registration process in core? (there are many plugins out there that have attempted this and it seems that many have been abandoned or lack tight integration with core features)
3. Are there any plans for hooks/filters for Widget Titles?
What was the toughest decision you guys made in 2011?
