41–50 of 96 posts
Earlier quoted context omitted.
You obviously have no idea what you're talking about.
I had several websites where changing the URL schemas resulted in Google rank dropping, resulting in advertising revenue loss. I don't see I can be more honest than that. And frankly, you are not just unfair, you are being rude.
Actually, tell me a few of these websites.
Which of the following URLS are clearer? 1a. https://foo.com/ 1b. https://www.foo.com/ 2a. https://foo.com/search/products/couches/color/red 2b. https://foo.com/search?products=couches&color=red 3a. /posts?recent 3b. /posts?recent= 3c. /posts?recent=true 4a. /post/1234/products-couches-furniture-red-cheap-recent-ikea-tags 4b. /post/1234/ I can think of good reasons for picking each of these, and even good reasons for…
> 1a. https://foo.com/ > 1b. https://www.foo.com/ www for old folks, non www for all the rest. > 2a. https://foo.com/search/products/couches/color/red > 2b. https://foo.com/search?products=couches&color=red https://foo.com/search?products=couches&color=red Those are parameters, not a path. The first one has only value as an SEO optimization. > 3a. /posts?recent > 3b. /posts?recent= > 3c. /posts?recent=true /posts/rec…
That's kind of the point of the article - these are parameters for the programmer, but are UI to the user.
Separating parameters by "&", except for the first KVP which is separated by "?" from the URL is not intuitive. On the other hands, they path editing is familiar.
At some point here the collective web development world is going to realize what it lost when it tossed REST/HATEOS out in its rush to appear modern.
When did this happen, and what frameworks did the throwing out?
I made a little project taking this idea to an extreme. The idea was, that you should be able to generate "meme" image macros simply by typing a URL. That way you could create memes on the fly anywhere that you can enter a URL (Slack/Twitter/Facebook/etc.) without having to leave the app. Just type a URL of the form: http://urlme.me/ / / . http://urlme.me/
https://github.com/sammoorhouse/zendtrump/blob/master/zendtr...
@ZenDTrump
First thing with new Safari: Change default setting for URL bar to actually show URL. Because UI.
Earlier quoted context omitted.
> 1a. https://foo.com/ > 1b. https://www.foo.com/ www for old folks, non www for all the rest. > 2a. https://foo.com/search/products/couches/color/red > 2b. https://foo.com/search?products=couches&color=red https://foo.com/search?products=couches&color=red Those are parameters, not a path. The first one has only value as an SEO optimization. > 3a. /posts?recent > 3b. /posts?recent= > 3c. /posts?recent=true /posts/rec…
I disagree with 2a. No reason why this shouldn't be a path that the user can edit to go one level "up" to /search/product/couches. That's kind of the point of the article - these are parameters for the programmer , but are UI to the user. Separating parameters by "&", except for the first KVP which is separated by "?" from the URL is not intuitive. On the other hands, they path editing is familiar.
Earlier quoted context omitted.
I had several websites where changing the URL schemas resulted in Google rank dropping, resulting in advertising revenue loss. I don't see I can be more honest than that. And frankly, you are not just unfair, you are being rude.
You changed them without redirecting properly. Actually, tell me a few of these websites.
Earlier quoted context omitted.
> 1a. https://foo.com/ > 1b. https://www.foo.com/ www for old folks, non www for all the rest. > 2a. https://foo.com/search/products/couches/color/red > 2b. https://foo.com/search?products=couches&color=red https://foo.com/search?products=couches&color=red Those are parameters, not a path. The first one has only value as an SEO optimization. > 3a. /posts?recent > 3b. /posts?recent= > 3c. /posts?recent=true /posts/rec…
I disagree with 2a. No reason why this shouldn't be a path that the user can edit to go one level "up" to /search/product/couches. That's kind of the point of the article - these are parameters for the programmer , but are UI to the user. Separating parameters by "&", except for the first KVP which is separated by "?" from the URL is not intuitive. On the other hands, they path editing is familiar.
While I find it more visually pleasing, this is my issue with this style: traversing up would first include /search/product/couches/color, which doesn't make sense. I've seen alternatives like /color:red/ before - which takes away the pairing-problem but feels odd..
Which of the following URLS are clearer? 1a. https://foo.com/ 1b. https://www.foo.com/ 2a. https://foo.com/search/products/couches/color/red 2b. https://foo.com/search?products=couches&color=red 3a. /posts?recent 3b. /posts?recent= 3c. /posts?recent=true 4a. /post/1234/products-couches-furniture-red-cheap-recent-ikea-tags 4b. /post/1234/ I can think of good reasons for picking each of these, and even good reasons for…
Of course you can change it later, that's what 301s are for.