Open brbenji opened 11 months ago
<title>
addition is a good idea, but a better solution to this problem would involve pulling out the value of the first H1 tag in the post. The last item in the post's path
should just be the URL path, and it's arguably a flaw in the app that setting the custom URL feels like you're naming it. Feel free to either get the H1 out or just remove the <title>
idea for now, I've got it in the to-do list either way.<body>
tag, but…) Two questions:
<head>
tag to all archived posts without getting a state change in +on-load
involved?Given the points above I wonder if we should put this on the shelf for now and spec out a much more wide-ranging issue to improve the HTML for posts.
I'm interested in helping with better HTML overall.
Is there a reproducible before/after where the post looks bad on mobile before this change and better after, that can't be blamed on the CSS?
This is asking the question backwards, in my opinion. The CSS is applied to the HTML. The CSS will behave differently with and without that tag. You should start with great HTML and do as much at that level as reasonable, and then layer in the CSS as-needed.
Great HTML would include this viewport meta tag. If you can reduce CSS as a result, great! If you need to modify it, that's OK.
Mobile First
This magic tag keeps a design consistent across desktop to mobile.
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Looking nice on mobile was the main reason for adding the
tag into %blog. As a bonus, I also added a%blog-action
s. The title is seen in the tabs of the browser.@bonbud-macryg We can expand this to include a favicon. You may enjoy designing one of those. It would look like adding
<link rel="icon" type="image/png" href="focus/assets/tile/png">