wturrellalso, I've started removing closing tags from <img>,<meta> etc. given W3C validator says they're not necessary. Not sure if I can honestly say if having them makes code more readable or not, maybe I've just got used to it.
[Murray]@wturrell I always feel that if an HTML element cannot contain anything within its tags, then self-closing is more readable. E.g. `<img></img>` cannot ever have anything between the angle brackets, but it looks like it could, whereas `<img/>` is clear that it's standalone.
[Murray]I know its also technically fine to leave some elements open-ended, e.g. `<p>Some text` but for the same reason, I personally prefer always closing them, again to signal that hey, this content belongs to this element, and more stuff can go here too
rnknI'm building a CMS. is it unwise for me to have have the CMS file management routes (e.g. /edit,/delete, etc.) in the same namespace as user pages? like, it would mean a user can't have a page called /delete
cotsuka, mort8088, grufwub, mossymaker and slovak joined the channel
LoqiMicropub is an open web standard (W3C Recommendation) and API for creating, editing, and deleting posts on websites, like on your own domain, supported by numerous third-party clients, CMSs, and social readers https://indieweb.org/Micropub
ZodiacalComet, doesnm_ and jjuran joined the channel
[artlung]wturrell asked: _"is the <form? "name" attribute deprecated (in favour of ID)?" -_ in short, no. The name attribute on form elements provides the keys in the key value pairs of a GET request