60

Just throwing it out there: WordPress Development


33

I agree. The answers to these questions are rarely more than link lists (and too soon out of date). How to handle old questions: Let them stay as they are. We can close or protect them, but they should not steal more of our time. And I don't want to see hundreds of flags against those old questions. :) Use close votes or make some rep instead. Addendum: ...


32

The Loop Because some topics are endless.


26

Since I can't find a contact email anywhere on their site, I've submitted a request via their "Panic Button" sales form. Since I don't know where that goes, I'm copying the text here on the off-chance that someone from Woo finds this post: Please don't just redirect your support forum to WordPress Answers It recently came to our attention that y'all ...


24

Thank you for all the work you have done for us! When I became a moderator and got a look at the history behind the scenes, I realized how much and how lonely you have been working. Very impressive! I'm grateful that you didn't throw the towel back in these days. You have been the the most reliable moderator to ask questions and discuss issues over the ...


23

Name for the site WordPress Developers


22

I am extremely disappointed that: that feedback was largely ignored that request to open new and properly visible thread for design discussion was ignored that it wasn't made clear that decision is made and no further discussion will happen (everything I thought through for it went down the drain) that this is exact repeat of situation with first design, ...


22

If i post the same question here and on stack overflow (with the 'wordpress' tag), the one on stack overflow is much more likely to be answered. Let's compare: WPSE has 70,983 questions with 18,827 unanswered, answered rate of ~74% SO wordpress tag has 110,757 questions with 50,314 unanswered, answered rate of ~55% You are significantly more likely to get ...


21

We will update the look to match the new design of Wordpress Newer model of printing press in header?.. :) Seriously though thanks, and most looking forward to new profiles. On design refresh Ehm... Uhm... NOPE. I get that it's a quick take on, but let's-abuse-WP-letters-into-logo/brand is horribly beaten track in our industry. Also capital P (WordPress)...


20

Also agree on hosting recommendations, it is incredibly opinionated and susceptible to bad info.


20

If you are struggling with plugin code and it is open source, you can ask questions about parts of the code, pasting code parts in the questions and describing in what and why you are struggling with that piece of code. You could also link the complete repository for more context. Those kind of questions are fine. Just avoid to paste walls of code and ...


19

The problem is several-fold: People really don't understand our intent/scope, and so we get both a lot of new users asking non-applicable questions, and also a lot of migrated questions that shouldn't be migrated here. We get a lot of "drive-by" questions, by users who don't understand the WPSE MO, don't come back to accept answers, and who don't ...


19

For the record, I am one of the supporters of a new name change to WordPress Development. But at the same time I have no issue with the site remaining named as WordPress Answers. Cue downvotes, now! I support either. Anyway I've said it several times before and I'll say it again, the amount of poor questions or off topic questions that get asked on this ...


19

Answers are not written for the asker only. That would be private support. They are for everyone with the same problem. So, yes, write answers to old questions, if they are good and interesting.


19

I believe the culprit here is that the question just doesn't sound very interesting, and it's got rewrite rules which scare others off. People here answer in their spare time not as a job and pick which questions to look at on a whim. There's also the hint it may be a server issue not a WordPress issue, but there's simply not enough information provided to ...


19

Design and branding for the WordPress niche This discussion keeps dodging having the one clear thread for specific discussion of WPSE design. While the current Q only asks for "bug reports" and this isn't one... I don't have a better place, so here it goes. This is something I wanted to be read before new design was launched. Or even better — before it was ...


19

Thank you for listening to feedback and working with us to iterate on it. My feedback on this version. Colors Much better fit (or rather not-wordpress-com anymore, which was main issue :) I think shade of header is a little too dark. WP org doesn't have toolbar on top like SE, it blends with it (needs divider line?). I think Tom had used a lighter shade ...


18

I am not very clear who are "many people" here. I have a lot of trust in SE administration to do, well SE administration. Groking currents, under currents and under under currents of WP ecosystem is slightly different and differently acquired skill however. "WordPress Development" fits damn well from the point of view of active users here. There wasn't ...


17

Each time you change a core file you create a fork. There is nothing wrong with forks – even WordPress started as one. We should not delete such answers – they may contain good hints for a better solution, or a fork may be just an appropriate option. We should add a comment pointing out the problems. I see no need for a voting rule. That’s up to each ...


17

Today I made the change to our FAQ. From now on choose off topic as close reason for these questions. Update If you came here after your question has been closed: Rewrite the question to get it reopened. Ask for a code solution, add your own attempts to do that. Try to write code for yourself, when you get stuck, ask a question about that specific ...


17

I’m against banning questions about a particular plugin. What happens outside of our side (lack of support from other parties) should not affect our scope. Someone else doesn’t offer support, so we do the same? I don’t get that logic. Poor answers doesn’t justify declaring a topic as out of scope. Drive-by users are welcome too. A low answer rate doesn’t ...


17

Tagline wp_get_answers() this tagline would only really make sense to WP devs/admins in the first place


17

I have upvoted every answer here and downvoted the OP, for the record. Honestly, the logic is a bit ridiculous. We can't have "WordPress Development" because some users will think that development === administration but "WordPress Answers" implies that equivalency much more strongly, in my mind. "WordPress Answers" means "ask whatever you want" and people ...


17

First - YAY! I know that site naming has always been sensitive issue for higher powers and I am very glad community managed to communicate and convince you of our strong stance on the name. Hopefully no hard feelings on some rowdy worded points in the process. :) Notes on tag line: I can't remember on top of my head are there any stacks with tag line ...


17

With the Exchanges that handle code based questions ( with the exception of Stack Overflow ) I feel you'll get more users that just grab the code and move on. Any question that isn't on the frontpage is going to get buried and only found through search when somebody is specifically looking for a solution ( unless otherwise linked ). On the other hand, UXSE ...


17

As far as I can see the only feedback that's been taken into account is the lowercase p in Wordpress becoming WordPress. Instead we have a design modelled after WordPress.com But not to worry, I have solutions! The Logo First, lets get rid of that unnecessary circular logo: The favicon can now be the capital W seen in the header above, similar to the ...


Only top voted, non community-wiki answers of a minimum length are eligible