Seems like one would be plenty:
asked Mar 16, 2012 at 3:05
1 Answer
Similar as to what kotekzot said in the comments above, you can simply see it as:
A webpage is a page on the web. A website is a site hosting pages on the web.
A webpage is not really ambiguous, you're watching one right now. A website can be interpreted somewhat ambiguous; in fact, look at the interesting different results Google provides us:
Excuse me for no freehand circles and guiding text, there isn't much place for that.
So, according to the dictionary a website is a computer. However, this is really incorrect as a computer can host multiple websites. If you also look at the other result, you get something more serious; but it's still loaded with stuffing words like set and related.
Putting that detail aside, we can at least assume two approaches:
Hosting a website
Browsing a website
Thus the website tag could be ambiguous because you can approach a website in (at least?) two ways.
From a slant look through that tag, I see questions about...
... uploading something to a website. (browsing / hosting)
... getting a website working. (browsing)
... website framework / system recommendations. (hosting)
... hosting a website in a certain way. (hosting)
... downloading / blocking / translation / ... (browsing)
... programming / design of a webiste. (programmer / designer)
So yeah, the tag is indeed used in a somewhat ambiguous way. However, it doesn't look bad to have this tag to me on the other hand; because introducing more tags like this wouldn't be a good idea.
Looking at webpage, these all seem indeed related to one webpage but I feel like they fit under the getting a website working type of questions (and similar) from the above list.
So, there is indeed the tricky question whether we would need this specific tag.
These are the options here:
We keep them both, making sure that webpage is applied to questions regarding a single page. Because I think there are questions in website which could also be tagged webpage.
We throw both of them away and use better tags like for example browsing and hosting.
However, this leaves me undecided. The first one breaks the usefulness of having them separated, the second could be kinda annoying to follow-up on and the third one takes categorization into account but would require thinking out in which tags we divide them in (and get rid of the off-topic stuff).
Thinking out the third point could lead to something, unless someone feels convinced by #1 or #2...
-
2I don't see the usefulness in having them separated if the meaning is not clear. Therefore, 1 seems reasonable. I like 3, but people won't use "browsing" when they ask a question about a random "website" (i.e. that probably won't occur to them when tagging).– slhckCommented Mar 16, 2012 at 15:01
-
@slhck: If you set up a synonym from website to a more general tag like browsing (just an example, perhaps better tags exist?) it would show up to them. #1 could be a solution as the separation isn't really that important, but is it on the other hand important to have one tag instead of two... Commented Mar 16, 2012 at 15:05
-
-
@slhck: If only meta.stackexchange.com/questions/125234/… existed. :( Commented Mar 16, 2012 at 15:08
-
1I think
[webpage]is a valid tag, especially if you are talking about "save as webpage" or working with a web file (e.g. HTML). I think[website]is too vague and something like[browsing]or[server]would be better.– iglvzxCommented Mar 16, 2012 at 22:52
.htmlpage (webpage) and the content presented to you when you enter a given URL into your browser (website). But I would have assumed that this distinction varies between people.