Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.

Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.

Comments on What should the "webmasters" site name and url be?

Parent

What should the "webmasters" site name and url be?

+4
−0

When SE's webmasters community was just starting out, they had a Meta discussion about what the site name should be. Although they settled on "webmasters", some of the arguments given at the time may no longer apply today.

For example, Bing still uses the term webmaster tools, but Google appears to have moved away from using the term.

If anyone has any alternative name suggestions, it might be easier to discuss possible names now, at proposal stage, rather than after the URL has been chosen.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

A very important question. Thank you for starting this discussion, trichoplax! (1 comment)
Post
+2
−2

I have personally never been all that keen on the term 'Webmaster' for 2 reasons:

  1. It implies a certain level of competency that has already been attained rather than talking of levels of knowledge that are gained over time. Thus I believe the term is off putting for those who do not feel themselves as 'master' level.
  2. The term is laden with a gender stereotype (male) which is very much out of touch with modern times.

My personal preference is Web Developers. This does not claim any form of mastery and does not come with any gender stereotyping while also loosely encompassing all of the areas of interest to this section of Codidact.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

Scope of the name (5 comments)
Can you add a URL to your proposal? `webdev.codidact.com` maybe? (1 comment)
Scope of the name
trichoplax‭ wrote over 1 year ago

I agree with both your points.

As for the proposed name "Web Developers", I wonder whether that would sound like only the code side of looking after a website. To me personally, "Webmasters" also sounds narrow - it would make me think of only the operations side and not the code side.

As the scope seems intended to be both the code and the operations sides, I wonder if there is a term that would make clear that both are included.

matthewsnyder‭ wrote over 1 year ago

Well, it used to be that websites were static, and many webmasters were also HTML devs, because given the simplicity of HTML it made little sense to divide labor there. These days, "webapps" seems to be ever growing, and typically "running" the site and building the webapp are very different things. "Web dev" tends to refer to the former only. The "webmasters" of today are not likely to write their own webapp with JS, and it's much more common to simply use existing tools to run a site.

Since JS and other frontend technologies are already covered by Software Development, it should be excluded from webmasters. Webmasters should include other things, like configuring nginx/caddy, setting up various open source servers/templates, DNS, hosting, SEO, content creation.

trichoplax‭ wrote over 1 year ago

Being on topic in another community doesn't necessarily make something off topic in this one - a few of the existing communities have overlaps. If you think that software development questions should be off topic here, it's worth raising that as a separate question to get a discussion going and see what answer the community supports.

matthewsnyder‭ wrote over 1 year ago

trichoplax‭ Wait, how's that gonna work? We'd have the same questions duplicated here and there. That seems kind of redundant to me. I thought it was assumed that if something is on topic in one place, it's not in others.

trichoplax‭ wrote over 1 year ago

Being on topic in 2 places doesn't mean it has to be asked in both places. It also doesn't hurt if it is asked in both places.

The benefit of having separate communities for different subject areas is that voting and feedback from a narrower collection of experts is more useful, and answers will be from the perspective of people focused on that particular subject area. None of this is dependent on the question never being asked elsewhere. In some cases a question from 1 person may benefit in different ways from 2 different communities. In other cases 2 different people may ask the same question for different reasons, from 2 different communities. The answers to one may not be of interest to the other.