Is it design completely custom or did you use a template or theme? I'm really struggling with the design side of my side projects.
Also, if you don't mind me asking, how difficult was it to get approved for Carbon Ads?
51–60 of 97 posts
Is it design completely custom or did you use a template or theme? I'm really struggling with the design side of my side projects.
Also, if you don't mind me asking, how difficult was it to get approved for Carbon Ads?
I believe your kbd example is incorrect. You suggest > To save, press Ctrl + S . But the spec (both W3C and WHATWG) suggests that individual keys should be nested inside an outer tag: "When the kbd element is nested inside another kbd element, it represents an actual key or other single unit of input as appropriate for the input mechanism." Thus, the example should be: > To save, press Ctrl + S . Cite: https://w3c.gi…
What's the point of this when already exists :/? I'd think a website like this should be opinionated and remove the tags that are useless or should be deprecated in a web 5.0 world (huhu) (great website btw)
already exists :/?Because keyboard input doesn't always mean code?
Earlier quoted context omitted.
Wow, the second example in fig 111. > File | Eat Apple... Boy that's terrible. Edit: Oh, I missed that the example immediately following it is supposedly equivalent and only uses a single outer tag. I don't really understand then, if they're equivalent then what's the point of the defined semantics above?
My reading of it is that: 1. ___ means "literal user input" 2. ___ means "this specific, atomic keypress" 3. ___ means "this specific, atomic button/action/menu item" So you can fall back to just using method 1, but it implies generic user input, inclusive of but not limited to keypresses. Thus, styling and treating a single kbd tag specifically like a keyboard button is still likely incorrect, since that precludes o…
To select all text, press
Ctrl
together with
A
or you can
right-click the empty space around the text
and
click Select All
Nevermind. After writing this now I understand why.I know a lot of people big up MDN vs W3Schools and all their arguments are basically correct but i find it (mdn) really ugly and hard to read. i often find myself going to w3schools to just copy a snippet or get a 1 line description of what i need.
mdn often feels more like a technical spec as opposed to a guide, which it kind of is i suppose.
great work on the layout!
How is this updated (manually or automatically from official specs)? Call me paranoid, but I see this diverging from actual specs, then people googling for "html reference" finding it and thinking it is something official. The result would be another W3Schools disaster[1]. In my opinion, the official W3 specification pages are not that bad, and alternatively there's the simpler MDN with strong community support (thus…
A more general/comprehensive API documentation tool (which can be also used offline) is DevDocs[1] [1] http://devdocs.io
[1]: https://zealdocs.org/ [2]: https://kapeli.com/dash
This is really great. It would be even greater if it could be used offline. Instead of hitting the server every time I choose one of the elements to view.
Earlier quoted context omitted.
It's free to you, not free to them.
If I'm supposed to let them sell my privacy and attention, I wouldn't really call it free. Money isn't the only thing of value I can give to a website.