Yes, yes, yes, yes, yes, yes.
Our main issue on this site is not existence of such tags, but that they are grossly misused because of auto-suggest and such.
I suppose proposed version-X tags for question that are really version specific will be allowed? Although I am not sure how viable those will be, but they are definitely less dangerous without ...
EDIT: 12/06 - Unfortunately, after broader internal discussions, we've concluded that changing the name to "Wordpress Development" will solve some problems, but cause other new ones.
I've posted a new question laying out our concerns, and opening a new discussion designed to build consensus out exactly what we need to convey, so we can keep working toward ...
As far as I can tell, the trademark policy isn't new.
Also: I see no legal or philosophical issues with a "WordPress" sub-site/network site of StackExchange.
As stated in the comments to another answer, I believe the relevant concerns are semantics, name recognition, and clarity. To that end, I propose that our formal site name be WordPress ...
Stats wise in last 90 days we had:
24 migrations to SO (8% rejected)
9 migrations to webmasters (none rejected)
These would make sense to add as migration routes, if higher powers agree and make it so.
With the new just-out-of-beta review system, after reviewing a post, you are immediately presented with a new post to review.
The Suggested Edits review queue requires minimum 2k reputation to review in general, but you're always allowed to review your own posts, regardless of reputation. In this case, your suggested edit approval was successfully submitted,...
Per new network policy:
wordpress-3.0 is not allowed, but 3.0 is. (This applies to all product-specific SE 2.0 sites, not just you.)
the form ^wordpress-?\d+.*$ is blacklisted as an intrinsic tag.
I have renamed all your existing version tags appropriately.
The acid test is to go to the ask question page, start typing wor... in the tags field and see if ...
I'm a senior product designer here at Stack Overflow. Thanks for reporting the issue. Another website reported a similar issue a couple weeks ago and I pushed a fix for this that appears to have corrected this issue as well. Huzzah!
The issue was related to the width of the search bar being too wide.
I absolutely support @toscho, but without the edge cases. WordPress gladly supports nothing than the current version and upgrading was (so far) painless and mostly successfull. Ex.: WP 2.7 will not be downloaded & used in a year and edge cases will only be old installs. Upgrading is mostly easier and even the codex gets rewritten with new versions, so ...
I have never seen a question where the version tag was really useful, and I never searched for it. So, yes, they should be banned from WPSE.
But there may be edge cases if you ban them from all networks: In Python for example, there are some … interesting differences between v2 and v3, both version are used today and it is useful to know for which version a ...
Since this is turning into an opinionated debate, I figured it would be best to just contact the WordPress Foundation and ask their official stance on the issue. Since they own the trademark after all, it's up to them whether or not we're using it according to their rules. If we aren't, then we have an official stance with which to guide both the site and ...
Assistance and Best Practices for WordPress Developers and Administrators
Assistance and Best Practices for Developers and Administrators
This is an adaptation from @mantis proposal, which I like because it makes inherently clearer what WPSE is about »assistance and best practice«. By adapting it this way I'm having several things in mind: ...
Thanks for the suggestion. I agree with the line-height issue, especially WP site tends to have a lot of code blocks in comments. I have changed it to 1.5em as you suggested. The change will be in the next deployment.