<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Matthias Ott</title>
    <description>The latest articles on DEV Community by Matthias Ott (@matthiasott).</description>
    <link>https://dev.to/matthiasott</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F154579%2Fdff2887f-7b01-4542-ad6b-069a16559793.jpg</url>
      <title>DEV Community: Matthias Ott</title>
      <link>https://dev.to/matthiasott</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/matthiasott"/>
    <language>en</language>
    <item>
      <title>:focus-visible Is Here</title>
      <dc:creator>Matthias Ott</dc:creator>
      <pubDate>Sat, 10 Oct 2020 21:52:08 +0000</pubDate>
      <link>https://dev.to/matthiasott/focus-visible-is-here-pp7</link>
      <guid>https://dev.to/matthiasott/focus-visible-is-here-pp7</guid>
      <description>&lt;p&gt;&lt;em&gt;This post was first published &lt;a href="https://matthiasott.com/notes/focus-visible-is-here" rel="noopener noreferrer"&gt;on my personal website&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;One of the most important features of a website that is built with accessibility in mind is that it can be &lt;a href="https://www.a11yproject.com/posts/2013-01-11-navigate-using-just-your-keyboard/" rel="noopener noreferrer"&gt;navigated with a keyboard&lt;/a&gt;. Most blind users and many users with motor disabilities rely on keyboard navigation, either with a standard keyboard or with a device that mimics the functionality of a keyboard. Providing strong visual indicators that highlight the element that currently has keyboard focus is therefore indispensable. In CSS, the focus styles for an element can be changed via the &lt;code&gt;:focus&lt;/code&gt; pseudo-class.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;a:focus {
  outline: 3px solid blue;
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Hiding Focus Styles Is Bad Practice
&lt;/h2&gt;

&lt;p&gt;Besides accessibility requirements, there are also design considerations to be made, though: For some users, a strong visual focus indicator once they click an element with a mouse or touch it with their finger can be irritating or feel “clunky”. Often, the focus highlight is only visible for a short time just before a page change occurs. This is an additional visual change in the interface that users have to process and understand. Without the knowledge that this highlight around the element is actually an accessibility feature, people might be distracted or irritated. Sometimes, it is even perceived as an error. And while some designers certainly are far more sensitive to the aesthetic qualities of an interface than its users – and would be well-advised to get used to a bit more accessibility-oriented, contrasted designs –, it is still relatable that focus indicators can feel like an intrusive break in an otherwise carefully balanced visual design.&lt;/p&gt;

&lt;p&gt;Many clients and designers, therefore, insist that developers remove the focus styles altogether for purely aesthetic reasons.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;a:focus {
  outline: none;
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is bad. It is an uninformed decision that actively excludes people and should not be an acceptable solution in 2020 anymore. So don’t do that. We have to do better. But how?&lt;/p&gt;

&lt;p&gt;One way out of this dilemma would be to cleverly design the focus state of an element so that it is perceived as a natural part of the transition from one state of the interface to the next. This, however, is not always easy or possible.&lt;/p&gt;

&lt;h2&gt;
  
  
  :focus-visible to the Rescue
&lt;/h2&gt;

&lt;p&gt;Luckily, there is now another option: The &lt;code&gt;:focus-visible&lt;/code&gt; pseudo-class. According to &lt;a href="https://drafts.csswg.org/selectors-4/#the-focus-visible-pseudo" rel="noopener noreferrer"&gt;the spec&lt;/a&gt;, “the intent of :focus-visible is to allow authors to provide clearly identifiable focus styles which are visible when a user is likely to need to understand where the focus is, and not visible in other cases.” Or, in other words, it lets you show focus styles only when they are needed, using the same heuristic that the browser uses to decide whether to show the default focus indicator:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/* Hide focus styles if they're not needed, for example, when an element receives focus via the mouse. */
:focus:not(:focus-visible) {
  outline: 0;
}

/* Show focus styles on keyboard focus. */
:focus-visible {
  outline: 3px solid blue;
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://blog.chromium.org/2020/09/chrome-86-improved-focus-highlighting.html" rel="noopener noreferrer"&gt;Chrome 86 just shipped&lt;/a&gt; with support for :focus-visible, &lt;a href="https://developer.mozilla.org/en-US/docs/Web/CSS/:-moz-focusring" rel="noopener noreferrer"&gt;Firefox supports it via the &lt;code&gt;:moz-focusring&lt;/code&gt; pseudo-class&lt;/a&gt; since 2011 and Mozilla is &lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1445482" rel="noopener noreferrer"&gt;currently working on adding support&lt;/a&gt; for &lt;code&gt;:focus-visible&lt;/code&gt;, too. So you can start using it now. And once more, &lt;a href="https://matthiasott.com/notes/progressive" rel="noopener noreferrer"&gt;progressive enhancement&lt;/a&gt; is your friend here. You can define regular focus styles for &lt;a href="https://caniuse.com/css-focus-visible" rel="noopener noreferrer"&gt;non-supporting browsers&lt;/a&gt; and then overwrite them for browsers that support &lt;code&gt;:focus-visible&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
:focus {
  outline: 3px solid blue;
}

:focus:not(:focus-visible) {
  outline: 0;
}

:focus-visible {
  outline: 3px solid blue;
}

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can try it out in this Codepen:&lt;/p&gt;

&lt;p&gt;&lt;iframe height="600" src="https://codepen.io/matthiasott/embed/LYZEwBJ?height=600&amp;amp;default-tab=result&amp;amp;embed-version=2"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;Note that &lt;code&gt;:focus-visible&lt;/code&gt; always applies in combination with &lt;code&gt;:focus&lt;/code&gt;. So if you inspect it in Chrome’s Developer Tools, for example, make sure to tick both boxes to see the appropriate focus styles.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fkxfw5imfxojqfk0zi0a1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fkxfw5imfxojqfk0zi0a1.png" alt="focus-visible-in-Chrome-Develpoer-Tools"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A Polyfill for Older Browsers
&lt;/h2&gt;

&lt;p&gt;If you need to support a wider range of browsers, including Safari, &lt;a href="https://github.com/WICG/focus-visible" rel="noopener noreferrer"&gt;there is also a polyfill&lt;/a&gt;. It simply adds a &lt;code&gt;focus-visible&lt;/code&gt; class to all focused elements in situations in which otherwise the :focus-visible pseudo-selector would match.&lt;/p&gt;

&lt;p&gt;Once the script is added to your page, the code looks much like in the examples above. The only difference is that now we are using classes to define the visible focus styles in our CSS:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;.js-focus-visible :focus:not(.focus-visible) {
  outline: none;
}

.js-focus-visible .focus-visible {
  outline: 3px solid blue;
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you decide to use the polyfill, make sure to pay attention to how it behaves in combination with your existing focus styles. It might still be a valid choice to only use the polyfill until Safari also adds support for &lt;code&gt;:focus-visible&lt;/code&gt;. But regardless of which method you decide to use, it is fabulous that we now have a solution to a problem that was often “fixed” by developers and designers by making websites less accessible. &lt;code&gt;:focus-visible&lt;/code&gt; now offers a solution that is accessible and makes users, designers, and developers happy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://drafts.csswg.org/selectors-4/#the-focus-visible-pseudo" rel="noopener noreferrer"&gt;The Focus-Indicated Pseudo-class: :focus-visible&lt;/a&gt;, W3C CSS Selectors Level 4&lt;/li&gt;
&lt;li&gt;&lt;a href="https://blog.chromium.org/2020/09/giving-users-and-developers-more.html" rel="noopener noreferrer"&gt;Giving users and developers more control over focus&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://developer.paciellogroup.com/blog/2018/03/focus-visible-and-backwards-compatibility/" rel="noopener noreferrer"&gt;:focus-visible and backwards compatibility&lt;/a&gt;, by Patrick H. Lauke&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/WICG/focus-visible" rel="noopener noreferrer"&gt;focus-visible Polyfill&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://caniuse.com/css-focus-visible" rel="noopener noreferrer"&gt;Can I use :focus-visible CSS pseudo-class?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.a11yproject.com/posts/2013-01-11-navigate-using-just-your-keyboard/" rel="noopener noreferrer"&gt;Navigate using just your keyboard&lt;/a&gt;, by Dave Rupert&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://css-tricks.com/focusing-on-focus-styles/" rel="noopener noreferrer"&gt;Focusing on Focus Styles&lt;/a&gt;, by Eric Bailey&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>a11y</category>
      <category>css</category>
      <category>usability</category>
    </item>
    <item>
      <title>Into the Personal-Website-Verse</title>
      <dc:creator>Matthias Ott</dc:creator>
      <pubDate>Fri, 17 May 2019 11:17:01 +0000</pubDate>
      <link>https://dev.to/matthiasott/into-the-personal-website-verse-2m7m</link>
      <guid>https://dev.to/matthiasott/into-the-personal-website-verse-2m7m</guid>
      <description>&lt;p&gt;&lt;em&gt;More and more people are rediscovering their personal websites as an alternative to social media that provides more control and freedom of expression. It's time to connect our sites even further and create a decentralized fabric of interconnected personal sites that enables each individual to engage in an open discussion – answering, challenging, and acknowledging the ideas of others through a universe of personal sites.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;&lt;a href="https://alistapart.com/article/nothing-fails-like-success/"&gt;Social media in 2019 is a garbage fire&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;What started out as the most promising development in the history of the Web – the participation of users in the creation of content and online dialogue at scale – has turned into a swamp of sensation, lies, hate speech, harassment, and noise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your Unfriendly Neighborhood
&lt;/h2&gt;

&lt;p&gt;Craving for attention and engagement, our timelines have changed. Algorithms now prioritize content from people with a huge following and everything that is loud and outrageous. It’s all about what the masses and the bots “want”, what they will like, share, and click. This strategy might be driving sales of ads because traditional online marketers are obsessed with quantity and it is – besides selling user data – the only answer they found for venture capital constantly demanding a bang for the buck. Yet it leads to an experience that is so often just more of the same and at the same time much less predictable, less organic, and less adjustable to your own preferences. As &lt;a href="https://craigmod.com/essays/newsletters/"&gt;Craig Mod writes&lt;/a&gt;, “social networks seem more and more to say: You don’t know what you want, but we do.”&lt;/p&gt;

&lt;p&gt;Consequently, it has become substantially harder for people with a small to medium following to get their voices heard and find a practical and creative use for services like Twitter or Medium. Twitter, for example, used to be that place where you would meet nice and brilliant people from the web community and make new friends, where you could find and share ideas and inspiration. But Twitter has changed so drastically and I’ve seen so many people turning quiet or leaving completely, that I don’t know how long this journey will continue. As with so many technologies before, the initial hopeful enthusiasm that accompanied the rise of social media has given way to disillusionment.&lt;/p&gt;

&lt;p&gt;One day, Twitter and other publishing platforms like Facebook, Instagram, or Medium will indeed die, &lt;a href="https://indieweb.org/site-deaths"&gt;like so many sites before them&lt;/a&gt;. And every time this happens, we lose most of the content we created and with it a fair amount of our collective cultural history. &lt;/p&gt;

&lt;p&gt;Data loss isn’t our only problem, though. If you decide to publish your work on a platform like Medium, you’re giving away control over it. What if Medium suddenly decided to extend the already existing paywall to all articles? There’s not much you could do about it. Simply because you don’t own your content anymore.&lt;/p&gt;

&lt;p&gt;Maybe this wouldn’t be a big issue if owning your content today wasn’t more important than ever. Especially, but not only, if you are working as an independent or freelancer, your content is not just something you happen to have created – and for which you own the copyright of, by the way – but it is also part of your identity. It is part of who you are, what you’re thinking about, what you believe in, and what you’re up to. It is part of the story you are about to tell. It is part of the change you seek to make. Your content is one of your most valuable assets and thus owning it is invaluable.&lt;/p&gt;

&lt;p&gt;So it comes as no surprise that more and more people are looking for alternatives. Not only for alternatives to Twitter or Medium per se but to the way social media currently works in general. Many are craving for more control, less noise, and for having more real and meaningful conversations again.&lt;/p&gt;

&lt;h2&gt;
  
  
  Homecoming
&lt;/h2&gt;

&lt;p&gt;There is one alternative to social media sites and publishing platforms that has been around since the early, innocent days of the web. It is an alternative that provides immense freedom and control: The personal website. It’s a place to &lt;a href="https://matthiasott.com/notes/out-there"&gt;write, create, and share whatever you like&lt;/a&gt;, &lt;a href="http://brendandawes.com/blog/permission-to-write-anything"&gt;without the need to ask for anyone’s permission&lt;/a&gt;. It is also the perfect place to explore and try new things, because, as Seth Godin likes to say, we now live in a &lt;a href="https://matthiasott.com/notes/unlimited-bowling"&gt;world of “unlimited bowling”&lt;/a&gt;. It is totally up to you what you create and because you have unlimited shots on the Web, you can try out different formats, different styles, different topics. Regardless of what other people might think and although it might not work. Creation is free.&lt;/p&gt;

&lt;p&gt;A personal website is also a powerful playground to tinker with new technologies and discover your powers. Take &lt;a href="https://rachelandrew.co.uk/archives/2017/01/05/its-more-than-just-the-words/"&gt;Rachel Andrew’s&lt;/a&gt; and Sara Soueidan’s word for it:&lt;/p&gt;


&lt;blockquote class="ltag__twitter-tweet"&gt;

  &lt;div class="ltag__twitter-tweet__main"&gt;
    &lt;div class="ltag__twitter-tweet__header"&gt;
      &lt;img class="ltag__twitter-tweet__profile-image" src="https://res.cloudinary.com/practicaldev/image/fetch/s--fyqpd9hG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://pbs.twimg.com/profile_images/1010126354078208001/MpkO7-qK_normal.jpg" alt="Sara Soueidan profile image"&gt;
      &lt;div class="ltag__twitter-tweet__full-name"&gt;
        Sara Soueidan
      &lt;/div&gt;
      &lt;div class="ltag__twitter-tweet__username"&gt;
        @sarasoueidan
      &lt;/div&gt;
      &lt;div class="ltag__twitter-tweet__twitter-logo"&gt;
        &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--P4t6ys1m--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://practicaldev-herokuapp-com.freetls.fastly.net/assets/twitter-f95605061196010f91e64806688390eb1a4dbc9e913682e043eb8b1e06ca484f.svg" alt="twitter logo"&gt;
      &lt;/div&gt;
    &lt;/div&gt;
    &lt;div class="ltag__twitter-tweet__body"&gt;
      &lt;a href="https://twitter.com/mmatuzo"&gt;@mmatuzo&lt;/a&gt; - My first &lt;a href="https://twitter.com/hashtag/CSS"&gt;#CSS&lt;/a&gt; Grid implementation was on my own site&lt;br&gt;- My first service worker implementation was on my own site&lt;br&gt;- My first real-world CSS Variables implementation was/is on my own site (WIP)&lt;br&gt;- My first Variable Fonts implementation will be on my own site&lt;br&gt;- ...
    &lt;/div&gt;
    &lt;div class="ltag__twitter-tweet__date"&gt;
      08:01 AM - 08 Feb 2019
    &lt;/div&gt;


    &lt;div class="ltag__twitter-tweet__actions"&gt;
      &lt;a href="https://twitter.com/intent/tweet?in_reply_to=1093781826815119360" class="ltag__twitter-tweet__actions__button"&gt;
        &lt;img src="https://practicaldev-herokuapp-com.freetls.fastly.net/assets/twitter-reply-action.svg" alt="Twitter reply action"&gt;
      &lt;/a&gt;
      &lt;a href="https://twitter.com/intent/retweet?tweet_id=1093781826815119360" class="ltag__twitter-tweet__actions__button"&gt;
        &lt;img src="https://practicaldev-herokuapp-com.freetls.fastly.net/assets/twitter-retweet-action.svg" alt="Twitter retweet action"&gt;
      &lt;/a&gt;
      5
      &lt;a href="https://twitter.com/intent/like?tweet_id=1093781826815119360" class="ltag__twitter-tweet__actions__button"&gt;
        &lt;img src="https://practicaldev-herokuapp-com.freetls.fastly.net/assets/twitter-like-action.svg" alt="Twitter like action"&gt;
      &lt;/a&gt;
      45
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/blockquote&gt;


&lt;p&gt;I couldn’t agree more. Building things for your own site is so worthwhile because you are allowed to make mistakes and learn without pressure. If it doesn’t work today, well, maybe it’ll work tomorrow. It doesn’t matter. And so it was on my own site that I, too, wrote my first service worker, that I first tried out CSS Grid, that I designed and implemented a &lt;a href="https://matthiasott.com/notes/colorful-code-adding-syntax-highlighting"&gt;custom syntax highlighting theme&lt;/a&gt;, that I set up an &lt;a href="https://matthiasott.com/notes/adding-json-feed-to-my-craft-cms-site"&gt;RSS/Atom and JSON feed&lt;/a&gt;, that I wrote three plugins for Craft CMS in PHP/&lt;a href="https://www.yiiframework.com/"&gt;Yii&lt;/a&gt;, and &lt;a href="https://https://twig.symfony.com/"&gt;Twig&lt;/a&gt;, with one of those plugins &lt;a href="https://github.com/matthiasott/webmention"&gt;adding Webmention support to my site&lt;/a&gt;. I also learned a ton about accessibility, performance optimization, or web font loading. All of which I then could put to use in my day-to-day work as a designer and developer.&lt;/p&gt;

&lt;p&gt;But maybe the most compelling reason why a personal website and also learning how to build one is incredibly valuable is this: community. Since the days of “guest books”, personal websites have been a place to receive feedback and discuss ideas and concepts with others. Often by the means of comments, sometimes even by writing a series of follow-up articles back and forth.&lt;/p&gt;

&lt;p&gt;Now imagine, for a moment, an environment where a decentralized fabric of connected personal sites allows everyone to publish their own content but also enables each individual to engage in an open discussion – answering, challenging, and acknowledging the ideas of others through this universe of personal sites. &lt;/p&gt;

&lt;p&gt;As idealistic as this vision of the Web might seem these days, it isn’t that far out of reach. Much of what’s needed, especially the publishing part, is already there. It’s also not as if our sites weren’t already connected in one way or another. Yet much of the discussions and establishment of connections, of that social glue that holds our community together – besides community events in real life, of course –, mostly happens on social media platforms at the moment. But: this is a choice. If we would make the conscious decision to find better ways to connect our personal sites and to enable more social interaction again, and if we would then persistently work on this idea, then we could, bit by bit, influence the development of Web technologies into this direction. What we would end up with is not only a bunch of personal websites but a whole interconnected personal-website-verse.&lt;/p&gt;

&lt;h2&gt;
  
  
  Weaving Our Web
&lt;/h2&gt;

&lt;p&gt;It’s, of course, safe to assume that a web of personal websites will never be an equivalent substitute for a social network like Twitter. But that’s also not the goal. Personal websites are called personal websites because they are just that: personal. Thus, the primary objective still is to have a place to express ourselves, to explore ourselves, a place that lasts while the daily storms pass by. A place of consideration, and yes, a place of proudly sharing what we do, what we think, and what we care about. A place to contribute your voice and help others. A home on the internet. A place to tell &lt;em&gt;your&lt;/em&gt; story.&lt;/p&gt;

&lt;p&gt;But on top of that, we have the chance to (re-)establish personal websites also as central elements of online discourse and as entry points for people who are new to the web community. For this, we need to find ways to create an ecosystem that lives up to the diversity of the personal-website-verse. Consequently, what will hold our sites together, is most possibly not one technology to rule them all, but a multitude of different and ever-evolving technologies. Things like hyperlinks, comments, Webmentions, and RSS, of course, but also other technologies that have yet to be invented. Not only would this leave enough room for individual preferences, but it would also make the whole construct more resilient while still being flexible enough to evolve over time. &lt;/p&gt;

&lt;p&gt;The first step of this is to explore more ways to establish new and strengthen existing connections – and also to improve findability. We don’t have to reinvent everything from scratch but can build on so much that already exists. Some things that can serve as good starting points are:&lt;/p&gt;

&lt;h3&gt;
  
  
  Quote people and link to other sites.
&lt;/h3&gt;

&lt;p&gt;Whenever you stumble upon an interesting thought on another site, write about it and link to it. Not only is it respectful to link to the person you quoted, but hyperlinks are also the magic force holding the Web together. They are both helpful and powerful. You can also add a links section to your site, where you collect interesting links you found on the web and over time build an archive for yourself and others.&lt;/p&gt;

&lt;p&gt;By the way: What happened to the blogroll? Remember? That little box in the sidebar of blogs that would link to the websites of friends and fellow bloggers. The blogroll isn’t dead yet – some people still use it. So how about adding a little section or page to your site that does exactly the same? Link to the personal websites of people you respect and appreciate, maybe with a little description? While we’re on it, we could also &lt;a href="https://bryanlrobinson.com/blog/2019/02/07/bring-fansites-back-to-the-web/"&gt;bring webrings back&lt;/a&gt;. Charlie Owen recently also wrote &lt;a href="https://www.sonniesedge.net/posts/webrings"&gt;about them&lt;/a&gt; and Max Böck &lt;a href="https://mxb.dev/blog/webring-kit/"&gt;was so inspired he built a starter kit for hosting your own webring&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Use RSS feeds and readers.
&lt;/h3&gt;

&lt;p&gt;RSS has been pronounced dead over and over again, yet it is still not dead and I doubt that it ever will be. In fact, it is witnessing a little comeback from time to time. Personally, I have started to use it more regularly again and others have, too. RSS is a great way to follow the people whose posts, ideas, and opinions matter to you. So if you write or put any kind of content on your site, also make sure to add an RSS feed. And then go and add some sites to a feed reader like &lt;a href="https://feedbin.com/"&gt;Feedbin&lt;/a&gt;, &lt;a href="https://feedly.com"&gt;Feedly&lt;/a&gt;, or Michael Scharnagl’s &lt;a href="https://feediary.com/"&gt;Feediary&lt;/a&gt;. If you use a Mac or iOS device, also have a look at &lt;a href="http://reederapp.com/"&gt;Reeder&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Use website directories.
&lt;/h3&gt;

&lt;p&gt;There are a few really helpful directories that list RSS feeds or personal sites and that can help you find interesting content. For example, Andy Bell’s &lt;a href="https://personalsit.es/"&gt;personalsit.es&lt;/a&gt;, Dave Winer’s &lt;a href="http://feedbase.io/"&gt;feedbase&lt;/a&gt;, the &lt;a href="https://indieweb-directory.glitch.me/"&gt;IndieWeb Directory&lt;/a&gt;, or RSS lists like the ones of &lt;a href="https://github.com/simevidas/webplatformnews-feeds/blob/master/feeds.opml"&gt;Sime Vidas&lt;/a&gt; or &lt;a href="https://github.com/sturobson/myRSS/blob/master/subscriptions.xml"&gt;Stuart Robson&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Use Webmentions and Microformats – and join the IndieWeb.
&lt;/h3&gt;

&lt;p&gt;Another powerful technology which can glue our sites together is &lt;a href="https://indieweb.org/webmention"&gt;Webmention&lt;/a&gt;. Webmention &lt;a href="https://www.w3.org/TR/webmention/"&gt;is a W3C recommendation&lt;/a&gt; that describes a simple protocol to notify any URL when a website links to it, and for web pages to request notifications when somebody links to them. The mentioned site can then grab a snippet of the HTML of the website that links to it and, if it is enriched with &lt;a href="http://microformats.org"&gt;Microformats&lt;/a&gt;, display the mention somewhere, for example under a blog post like this one. Aside from all questions of data protection, Webmentions are a powerful tool and one of the many technologies that originated in the IndieWeb community. If you don’t know about the IndieWeb yet, take a look at &lt;a href="https://matthiasott.com/articles/going-indie-reclaiming-content"&gt;my article on reclaiming control over your content&lt;/a&gt;, or head over to &lt;a href="https://indieweb.org"&gt;indieweb.org&lt;/a&gt;. Built around the basic idea that you should own your content, the IndieWeb community is the birthplace of a few powerful technologies that all have the goal to make your personal website the center of a more open, decentralized web.&lt;/p&gt;

&lt;p&gt;Webmentions are a great way to connect and intertwine two sites and thus, two ideas. You could even build something like a commenting system around Webmention – if only it still wasn’t a bit complicated for mere mortals to implement them. Luckily, there are plugins available for content management systems like &lt;a href="https://github.com/pfefferle/wordpress-webmention"&gt;Wordpress&lt;/a&gt;, &lt;a href="https://github.com/gRegorLove/ProcessWire-Webmention"&gt;ProcessWire&lt;/a&gt;, or &lt;a href="https://docs.grabaperch.com/addons/blog/webmentions/"&gt;Perch&lt;/a&gt;. I will update my own &lt;a href="https://github.com/matthiasott/webmention"&gt;Webmention plugin for Craft CMS&lt;/a&gt; over the coming weeks so that it supports the latest version 3 of Craft CMS.&lt;/p&gt;

&lt;h3&gt;
  
  
  Go to meetups and conferences and spread the word.
&lt;/h3&gt;

&lt;p&gt;There are meetups for everything and they are a great place to meet like-minded people, exchange, connect, and tell others about how great having a personal website is. So look up if there’s maybe a meetup about blogging in your city. Also, meetups on topics like WordPress, writing, or publishing in general could be worth a visit. Then there are more and more &lt;a href="https://indieweb.org/Homebrew_Website_Club"&gt;Homebrew Website Clubs&lt;/a&gt; emerging. Homebrew Website Clubs, which are also an IndieWeb idea, are a great opportunity to work with others on your personal sites once or twice a month. And if you don’t find an appropriate meetup or event near you, how about starting one? &lt;/p&gt;

&lt;h2&gt;
  
  
  “Don’t do it like me. Do it like you.”
&lt;/h2&gt;

&lt;p&gt;As you can see, there are many ways and many good reasons to start building your site today. But whatever you start, keep in mind that you don’t have to build something from start to finish to show it to the world. To the contrary, it can be a great idea to start as simple and rudimentary as possible, to get the fundamentals right before diving too deep into over-complicated solutions. Take your time to think about how to build a site that’s truly tailored to you and your work. What are you really trying to achieve? What content do you want to create? Who is your audience? And how does a website look like that reflects all that in terms of structure, hierarchy, complexity, visual design, and scope?&lt;/p&gt;

&lt;p&gt;Kylie Timpani, for example, who &lt;a href="https://css-tricks.com/design-v17/"&gt;recently worked as the lead designer on v17 of CSS-Tricks&lt;/a&gt;, is now &lt;a href="https://dribbble.com/shots/5993693-Personal-Website-2019-WIP-001-In-the-Wild"&gt;doing an open redesign of her website&lt;/a&gt;. So she is building the website out in the open, starting with some blank and raw HTML, and will be documenting what she’s learning along the way. This, by the way, is generally a great thing to do on your site: Document your process and share all the things you learn. &lt;a href="https://amberwilson.co.uk"&gt;Amber Wilson is doing this on her site&lt;/a&gt;, too. Since she decided to become a web developer, she regularly writes about her experience and &lt;a href="https://amberwilson.co.uk/blog/wilt100days/"&gt;what she learned&lt;/a&gt;. Not only is this a great way to help others find their way, but it also shows that we all have to learn and we all have things we don't know. Don’t let that stop you.&lt;/p&gt;

&lt;p&gt;Also, don’t hesitate to write about little ideas and observations that might seem too small or unimportant to share. We all have our unique perspectives and even the smallest experience is worth sharing. Someone else might be in a similar situation as you or also in a completely different situation. They both might learn something new from reading about your experiences. Each contribution to the community, even the smallest one, is useful and will make a change. So &lt;a href="https://www.sarasoueidan.com/desk/just-write/"&gt;just write&lt;/a&gt;. By the way: If you are struggling to find something to write about and feel blocked, remember that there is &lt;a href="https://itunes.apple.com/de/podcast/akimbo-a-podcast-from-seth-godin/id1345042626?l=en&amp;amp;mt=2&amp;amp;i=1000405208122"&gt;no such thing as writer‘s block&lt;/a&gt;. The more you write and create, the easier it will get.&lt;/p&gt;

&lt;h2&gt;
  
  
  To Begin, Begin
&lt;/h2&gt;

&lt;p&gt;When I studied design back in the early 2000s, my digital media professor, Tom Duscher, held the view that every designer should have their own blog. It was still the early days of blogging but he already saw the potential and power of writing about your craft and reflecting on your experiences. At the time, I thought I understood what he meant, but it took me over 10 years to finally overcome (or simply ignore) the fear of being wrong and start to publish on my site. I won’t ever look back.&lt;/p&gt;

&lt;p&gt;Building and maintaining your personal website is an investment that is challenging and can feel laborious at times. Be prepared for that. But what you will learn along the way does easily make up for all the effort and makes the journey more than worthwhile. But most importantly, having a website makes you part of an amazing community of creators, forming new friendships, new connections, and new opportunities. This is invaluable.&lt;/p&gt;

&lt;p&gt;Personal websites are the backbone of the independent Web of creators. Even after all those years, they remain a vital part of what makes the web the most remarkable and open medium to date. We shouldn’t take this for granted, though. If we don’t pay enough attention and care about the open web enough, we might lose this valuable asset. So let us protect the Web as a source of inspiration, diversity, creativity, and community. Let us maintain what we have and work together to make this little part of the magic of the Web sparkle even brighter. Let us help new members of the community to start their journey. Let us build, prototype, publish, and connect.&lt;/p&gt;

&lt;p&gt;Let’s start today.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;This post was originally published &lt;a href="https://matthiasott.com/articles/into-the-personal-website-verse"&gt;on my own website&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;The header image illustration is based on photographs of the &lt;a href="https://www.flickr.com/photos/rvr/22572526695/"&gt;Apple Lisa by Victor R. Ruiz&lt;/a&gt; and the &lt;a href="https://www.flickr.com/photos/mwichary/2283395560/"&gt;Apple Lisa mouse by Marcin Wichary&lt;/a&gt;, both released under a Creative Commons license (Attribution 2.0 Generic, CC BY 2.0).&lt;/em&gt;&lt;/p&gt;

</description>
      <category>websites</category>
      <category>blogging</category>
      <category>indieweb</category>
      <category>takebackyourweb</category>
    </item>
  </channel>
</rss>
