Hi folks! We’ve pushed out a couple of small updates to the site.
First, we’ve added a small panel underneath the comment form that tells you who you’re logged in as and gives you the option to log out (imagine that).
Second, you can now edit your comments (in-place even).
We’re using a customized version of the edit-in-place script that comes with ExpressionEngine. Why customize it? For a couple of relatively minor reasons. The original script assumes that it will be showing up directly in the HTML page, and we like to keep our functions all together in external files. We also wanted a little more control over the way the edit form was revealed and hidden again.
Next step? Adding an “edit” link to that new user panel is the obvious choice, I think. We’ll get cracking on it.
Like this:
LikeLoading…
1 Reader Comments
Great feature, animates me to take my time and comment more 🙂
Got something to say?
We have turned off comments, but you can see what folks had to say before we did so.
Every language app in your pocket inherited a teaching method built for Latin. Understanding why that happened is a more useful design lesson than anything the apps themselves can teach you.
Designers are good people. Some designs exclude people anyway. Alan Dalton offers a practical fix: accessibility personas that help you recognize problems while you're designing, not after. Homework included.
Computing was born in a Viennese café. Between 1928 and 1934, while Hitler plotted and Europe crumbled, a motley crew of mathematicians, philosophers, architects, and economists gathered weekly to puzzle out the limits of reason—and invented Computer Science in the process. What made their collaboration possible wasn't just brilliance (though they had plenty). It was amiability: the careful design of a social space where difficult people could disagree without destroying each other. Longtime Web Dev Notes contributing author Mark Bernstein mines this forgotten history for lessons that might just save today's embattled web from its worst impulses. Spoiler: it involves better coffee service and the looming threat of public humiliation.
Design systems aren't component libraries—they’re living languages. Rigid adherence to visual rules creates brittle systems that break under contextual pressure. Fluent systems bend without breaking.
Great feature, animates me to take my time and comment more 🙂