171–180 of 190 posts
Sweden using Ø for 0 is so insensitive towards their fellow Scandic neighbors to the west! Such a Swedish thing to do.
Earlier quoted context omitted.
It's definitely interesting how countries have their own PR these days. And it's working, if you think of a nordic country, chances are, Sweden is the first one that comes to mind.
> Sweden is the first one that comes to mind Is it? Norway has been topping all the livability charts for at least the past decade so that's the one I've always considered "the best in the world." Then probably the Netherlands, if you stretch the definition of Nordic.
I am fascinated by typography and page design and enjoy reading about it, but I have to admit I don't understand how this level of pedantry is able to survive. The amount of documentation and attention to detail spent on typefaces and when to use them is often off the charts compared to the time spent on stuff like keeping the website running, documenting the API or even the basic functionality of the app. It's like…
Typographic documentation is for designers generally, but there is a world where this can actually help everyone. Designers should make consistent designs. By doing this Developers can create functional designs systems that have sane default behaviors. Once you can get to that point, the system serves to reduce the load from the dev, not increase. I have created a tailwind-based design system interpretation like this…
Is this the design system you created, or is this something others can use (or both)? As someone who's avoided frontend work primarily because I find CSS tedious, having a system over top of it that speaks design language sounds interesting.
Admittedly, looking at Tailwind now, looks like it's worth just trying that to start with.
Earlier quoted context omitted.
Typographic documentation is for designers generally, but there is a world where this can actually help everyone. Designers should make consistent designs. By doing this Developers can create functional designs systems that have sane default behaviors. Once you can get to that point, the system serves to reduce the load from the dev, not increase. I have created a tailwind-based design system interpretation like this…
Good points which I generally agree with, but I still think it's common to see a remarkable level of time and effort spent on typography compared to even other parts of the frontend. Not always, but surprisingly often. Many companies have these style guides around typography. Beautiful, thoughtful, very well made things for sure, yet when some backend dev makes a typo so the custom font drops to arial or whatever, it…
Brand guidelines tend to seem expansive because they have to break things down in a way that's very easy for all sorts of people to adopt with minimal hassle. From what I've seen, the moment that process gets anywhere within a thousand miles of difficult, people will say "forget it" and do what they want.
Despite all that, branding doesn't really require much in the way of ongoing resource commitments from an organization. They get put together when the brand is updated, and more often than not, the entire process is often outsourced to agencies. Either way, once it's done, it's done for a while.
It's also often publicly available. You can find brand guides for all sorts of companies and organizations available online. Technical documentation is almost always internal, unless we're talking about stuff that's been open-sourced, API documentation, etc. It's also ongoing and is in constant need of updating as code gets updated. As a result, there's no need to pretty it up beyond whatever makes it accessible to your developers. The priority is on keeping it updated as best you can, within the limits of available resources. That doesn't always happen, of course.
Different audiences merit different approaches, and because one is more visible, it may give the false impression that it's of higher importance to an organization.
Earlier quoted context omitted.
I agree with much of your comment, but take umbrage with: > the point of the entire backend of an app is to serve the front end It’s a phoney argument. Once can just as easily say “the whole point of a front end is to provide simple access to the backend, rather than doing it via APIs”. The whole system is important. Some backends have appalling frontends and are still popular. The opposite is also true.
I was kinda hoping that the OP would counter with that line and then I would agree and make exactly your point haha. My point was simply that the system is interdependent as opposed to the OP's take that the FE consistency doesn't matter.
No no, FE consistency matters for sure! I really appreciate a good brand identity document, it's really nice to have.
But using Arial everywhere would also be consistent, right?
Earlier quoted context omitted.
> Sweden is the first one that comes to mind Is it? Norway has been topping all the livability charts for at least the past decade so that's the one I've always considered "the best in the world." Then probably the Netherlands, if you stretch the definition of Nordic.
Netherlands? Are you perhaps thinking of Denmark?
Earlier quoted context omitted.
Netherlands? Are you perhaps thinking of Denmark?
I'm thinking of "Not Just Bikes" on YouTube, so definitely the Netherlands. I rarely hear about Denmark. Finland even less so.
In 2023 too, no less than six years in a row!
https://www.npr.org/2023/03/27/1166180048/finland-is-the-wor...
Earlier quoted context omitted.
I’d wager that it’s a reference to the old Swedish name for the Pacific Ocean and not Södermalm.
Söderhavet is the Pacific? But that makes no sense, geographically!
Earlier quoted context omitted.
It's definitely interesting how countries have their own PR these days. And it's working, if you think of a nordic country, chances are, Sweden is the first one that comes to mind.
Tbh, they're all nearly the same country in my mind. Minor differences, all in all.