Hi Jan Dembowski @jdembowski),
Thanks for letting me know this is the right place for website feedback.
Can you please make it more obvious that this “is” the place for website feedback?
Is it “only” for website feedback?
Or is website feedback in the same area as anything else that is not specifically handled?
As a start to improving the flow of website feedback and refinement,
here are some suggestions;
a) in the footer that appears at the bottom of every page on this website,
have a link with a label clearly indicating direct relevance to website feedback.
This can handle any type of feddback about anything to do with the website, it may try to categorise the feedback (for ease of handling by the team), but it will also have the ability to receive anything and feed it through to where ever it needs to go (like a really friendly and helpful receptionist).
You name it, I hope to find it (soon?).
b) Buttons to report problems with pages and processes “Report a problem(s) with this page?”, “Report a problem(s) with this section?”, “Report a problem(s) with this process?”. These may be placed on every page. But if the site team is not so keen to use these universally (because the team thinks they will not be needed), then they are at least available if there are any areas (pages,plugins,menus,features,systems,processes,etc) where roll-out/prototyping is going on, or where there has been some alerting to problems. These are very good at detecting problems (that may not be with the code functions) related to UI interaction with U.
This “button” method could be set up, so anybody who is developing anything can create a label for the button, and insert it into the area they are developing.
When the button is clicked on, it therefore knows which department to send its information to, which includes which page, and area the problem got reported from (the user does not have to spent effort describing their menu path, or circumstance surrounding an event).
c) make a separate area for the website feedback handling. It can be associated with the everything basket. But some people in the team may be specialising in the website, so they will be assisted not having to pass over the rest of the everything topics.
Perhaps this could be achieved by grabbing the code that is used for “categories” in the wordpress forum, and creating a different list of categories (one of which is website feedback).
The categorisation system could be made finer resolution, by having separate topics/subtopics for UI, possible code errors, ideas, feature requests, bug reports, process flow, etc.
Also
It’s not just a matter of “having” the features and functions, it is also important to “have them at hand”, and that they are “obvious”, and preferably intuitive to use.
This website is (the) a tool for the development process of WordPress.
If this website is hobbled in its performance, then the rate of development will be similarly effected.
Can I swing some topics that I have raised elsewhere, over to here, and have the website team see them?
In a way, I am interested in helping this site become a model of the way a best of breed website can be. And that means fixing up the shortcomings (irrespective of how brilliant other things are/may be).
Thank you for your help.
