Please forget about what I said in Let's make "research efforts" more specific: request to search the web app help, and let's start from scratch. In this post, I'm trying to integrate the feedback I got in multiple public and private conversations. Whatever other post is still "open", instead of commenting about it here, let the post author flag it for moderator attention based on the standard rules if they think that they should do that. Post author: Follow the guidelines for flagging a post for moderator attention.
Web Applications intended audience and onboarding
The question is who is the intended audience and how do they learn how to participate. Please provide a detailed answer, explaining why the answer is correct/appropriate.
Please bear in mind that Stack Exchange "sites" are not like other online discussion forums (Internet forum) and even not like other question and answer sites. Is there any difference between Web Applications Stack Exchange's intended audience and the audiences of Quora, Reddit, official web app communities, and other popular questions and answer sites? I.E. OpenAI has a discussion forum and a Discord community. Are we competing for the same audience ( askers, answerers, and viewers)? Don't forget that askers and answerers are also moderators. New users since day one they can post questions and answers, suggest edits to others' posts (with some exceptions). Once an user earn reputation, more privileges are unblocked for them including moderation privileges. Flagging of questions, answers, and comments is one of the privileges that are unblocked first.
Once we have confirmed that the active community has clear who the intended audience is and what the first that we tell them about how to participate, I would like that talk about the following:
- We have several old feature requests that have a positive score but that haven't a status tag.
- The system and process have changed, so these feature requests should be updated according to the current system possibilities and according to the current feature-request process.
This is a plan proposal (that might be discussed in detail after that we have clear who is the intended audience and that it's clear how they can participate):
- identify the most relevant community "rules": Which rules are inherited, specific for Web Applications, and might not be the same for other sites. These are "hard rules" and "soft rules".
- Hard rules are clearly defined for "anyone" in the intended audience. Always and all the time should be applied the same way.
- Soft rules are hard to be understood by outsiders and new users (people unfamiliar with this community). They might require a long time to be fully understood. They are better communicated and enforced by the core community.
- Add one answer for each relevant community "rule" that is unclear or that you suggest should be discussed and updated, explaining why using simple words and a positive, constructive tone. If you need to provide examples, avoid mentioning specific posts and users.
- If you want to complain about something or dispute a specific action over a user or post, this should be done following the regular procedure, not in this post.
- Review old posts and ancient feature requests and choose which should be discussed/updated first. Add one answer for each suggested post to be discussed, explaining why it's relevant to be reviewed/updated. At the proper time, one Community Moderator will assign status-review to a feature request ready to be reviewed under the current process as the Community Manager Team defines it.
Below is a table listing the elements based on the questions that should be asked in every beta with some additions. Some might need to consider as "discussion finished", and others might need to be reviewed and updated. Moderators might add new items "unilaterally" and based on suggestions received.
This table is not intended to change any rule; consider it a table of content, quick reference.
|Around Site Graduation
Sept. 30, 2010
|Related Meta post|
|Core Community||Area 51 Proposal Top Beta Users?||TBD|
|Community Managers / Staff||Jeff Atwood (founder), Joel Spolsky (founder) Robert Cartaino, Roberta Chernoff, Jin (designer)||V2Blast, SpencerG, JNat
Source: Users > Participation > Year (April 22, 2023 )
|Moderators||rechem, phwd, ChrisF, eagle||ChrisF, Rubén, Sathyajith Bhat||Beta:|
|Site name||Nothing to Install||Web Applications||After graduation:|
|Domain||nothingtoinstall.com||webapps.stackexchange.com||How will the domain be chosen?|
|Site blurb||Q&A; for power users of web applications
Source: Wayback Machine, November 29, 2010
|Q&A for power users of web applications|
|Logo / Design||TBD||Beta:
|Elevator pitch, Tagline, Motto||TBD||TBD||Write an Elevator Pitch / Tagline|
|Welcome banner for anonymous users||N/A||Web Applications Stack Exchange is a question-and-answer site for power users of web applications. It only takes a minute to sign up.
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
|Welcome for new users|
|Tour title||Welcome to Web Applications
Source: Wayback Machine Feb 27,2013
|Welcome to Web Applications Stack Exchange|
|Site description in tour||Web Applications is a question-and-answer site for power users of web applications. It's built and run by you as part of the Stack Exchange network of Q&A sites. With your help, we're working together to build a library of detailed answers to every question about web applications.
Source: Tour history, created Jan 16, 2013, at 18:53
|Web Applications is a question-and-answer site for power users of web applications. It's built and run by you as part of the Stack Exchange network of Q&A sites. With your help, we're working together to build a library of detailed answers to every question about web applications.
What kind of questions can I ask here? The detailed version
|About / Tour||About (Wayback Machine, July 12,2010)||Tour|
|Ask question form||How to Ask
Is your question about web applications?
We prefer questions that can be answered, not just discussed.
Provide details. Write clearly and simply.
If your question is about this website, ask it on meta instead.
Source: Wayback Machine July 10, 2010
|Asking a good question
You’re ready to ask your first question and the community is here to help! To get you the best answers, we’ve provided some guidance:
Before you post, search the site to ensure your question hasn’t been answered.
|The guidance in the "Step 1: Draft your question" box on the Ask Question page should be customized|
|FAQ / Help Center||FAQ (Wayback Machine, July 10, 2010)||Help||Private Beta: What should our FAQ contain?
Public Beta: What kind of questions can I ask here? The detailed version
|Custom post notices||N/A||N/A||TBD|
|What Outsiders Think
How hit/run users arrived
|TBD||TBD||Who do outsiders think Web Applications is for, developers/power-users or Joe-user?|
|Good Questions||TBD||TBD||Private Beta:|
- There are many posts with no upvotes, no downvotes, no comments, and no flags.
- Questions bumped "infinitely" (questions bumped more than 10 times, derived from the previous point).
- Initial core community no longer participating.
- Jargon every where.
- Terms, phrases, and supporting literature have their origin in the "programmers world", and they are still referenced in the user interface and help articles. The explanation of these language elements is hard to find and understand.
- Tags i.e., tags of programming languages
- No exemplary questions having a large number of views and high scores
Web applications nature
- Most web applications can't work if the vendor/operator stops offering the service.
- There is a small room for customizatión / extension in most web applications.
- Web applications might change without allowing users to keep using an old version.
- Most web applications have a low entry barrier for new users causing many users to get stuck because they have not understood the basics, i.e., the web app domain vocabulary (jargon/argot).
Specific developer/vendor issues
- Webapp name changes.
- Webapp name recycling (use the name of an old app for a new app, the new app hasn't had all the features of the old app).
Recurrent no good fit posts topics
- Programming / developing web apps.
- Creating / managing webapps.
- Domain name service (assign a custom domain to a website, set MX records, verify domain ownership, and like).
- Software as service/clouds.
- Help / Service desk request.
- Seeking for bug/service failure confirmation (is this happing to someone else?).
- Call for solutions (similar to give me the codez, challenges, contests).
- Teach me / guide me (looking for a mentor, user-tailored help).
- Seed questions.
Please let's build together a clear definition of who is the intended audience and how they learn how to participate. This question is intended to be answered with explanations.
After clarifying the above, let's discuss the other points shared in this post. In the mean, those willing to help refine this post, please leave a comment and let me know if you are interested in using participating in a chatroom.
Posts from Meta Stack Exchange
- Different sites for different levels of audience
- Our words are too complicated. Let's make them simpler!
- Which computer science / programming Stack Exchange sites do I post on?
- Why does Server Fault's new help system de-emphasize the professional audience?