I just wish they had better SEO than say W3Schools
The future of MDN: a focus on web docs
81–90 of 113 posts
Re: The future of MDN: a focus on web docs
#82A small feature in chrome you might like, there is a quick write up about it at the link listed below. Basically configure the URL search bar for MDN to be a searchable website. Change the keyword from the full Mozilla link into something simple like mdn. Then simply when searching in the url instead of going to google.ca just type 'mdn' and space then it will use the configuration of the search query to look inside…
Not saying that people shouldn't do it. Just offering a possible simpler alternative to be tested as well
Re: The future of MDN: a focus on web docs
#83Earlier quoted context omitted.
Any reasonable web browser lets you assign keywords to searches. No need to go through a third-party.
Which mobile browsers allow this? Does it synchronise them? I've used these a lot in the past, but switched to DDG's bangs largely because it was such a pain to change browsers/devices, and none of them ever worked for me on mobile. DDG's bangs are still a little unwieldy (! isn't a very convenient character to type, especially on mobile), so an alternative would be nice. For now though, the consistency everywhere fa…
Unfortunately the UI isn't too great -- on desktop, the suggestions between the awesomebar show you that a keyword search will happen (just like when you type something matching an open tab it tells you that it will switch to tab unless you hit the down arrow to choose something else). On mobile there is no such indication, but hitting enter after typing the keyword followed by the query still works fine and does the keyword search thing.
I might try to fix that.
Re: The future of MDN: a focus on web docs
#84Yeah for this statement, "...often Web developers are looking for quick examples...", I don't even care if the examples are higher up on the page or not...I just would like more and more examples. Sometimes the examples are too few or don't fully exemplify options of particular functions, etc. Nevertheless, I'm absolutely grateful to all the folks who put in so much work into MDN. If you are one of those people, know…
This is one of the only reasons I sometimes end up back at w3schools after reading the mdn docs: when I'm looking for a quick, working, live example. A short example is worth a thousand words.
Re: The future of MDN: a focus on web docs
#85I'd guess they could have kept the acronym to mean Mozilla Documentation Nexus.
It's possible the name change is for SEO reasons. Although they shouldn't need to; Google really ought to swallow their competitive pride and make MDN one of their previewed snippet sources, or else create their own webdev documentation source of equal or better quality.
Re: The future of MDN: a focus on web docs
#86A small feature in chrome you might like, there is a quick write up about it at the link listed below. Basically configure the URL search bar for MDN to be a searchable website. Change the keyword from the full Mozilla link into something simple like mdn. Then simply when searching in the url instead of going to google.ca just type 'mdn' and space then it will use the configuration of the search query to look inside…
I have found doing this unnecessary (for me) because just searching for "mdn whatever" in google gets me the MDN results I wanted as the top result with the rest of the page being populated by other related MDN results. Not saying that people shouldn't do it. Just offering a possible simpler alternative to be tested as well
Re: The future of MDN: a focus on web docs
#87Can we please have a comments section on every page of documentation?
MSDN has this, and I have never seen a comment there that actually provided value to a reader of the page. It makes even less sense on MDN, because MDN is a wiki; if you think something is missing, you can get it added.
https://secure.php.net/manual/en/function.htmlspecialchars.p...
https://secure.php.net/manual/en/function.preg-replace.php#u...
https://secure.php.net/manual/en/function.header.php#usernot...
Re: The future of MDN: a focus on web docs
#88I just wish they had better SEO than say W3Schools
It already appears usually in higher positions than w3schools in Google, at least for me.
Re: The future of MDN: a focus on web docs
#89Earlier quoted context omitted.
If DuckDuckGo is your default search engine, you can just do !mdn and get the MDN search results page. You can also do the same for stuff like !gweek And get google results limited to the last week (or StartPage ones if you swap the g for and s). It's amazing.
Any reasonable web browser lets you assign keywords to searches. No need to go through a third-party.
Re: The future of MDN: a focus on web docs
#90Yeah for this statement, "...often Web developers are looking for quick examples...", I don't even care if the examples are higher up on the page or not...I just would like more and more examples. Sometimes the examples are too few or don't fully exemplify options of particular functions, etc. Nevertheless, I'm absolutely grateful to all the folks who put in so much work into MDN. If you are one of those people, know…
This is one of the only reasons I sometimes end up back at w3schools after reading the mdn docs: when I'm looking for a quick, working, live example. A short example is worth a thousand words.