Perhaps you relate to all the reasons why you should be on the indieweb, but you're not sure how to get there.
Here are a few simple steps you can take to get you on your way to being on the indieweb. Each of these steps is a just a bit more challenging and will give you more independence.
Tools and Testkits
- Indiewebify.me is a step-by-step guidance on how to get started. It also includes tools to test and validate whatever is needed to be done.
- Tools is a list of parsers, verification services, and other useful things which are helpful for building and debugging an IndieWeb site.
Guides per CMS
Connect & getting help
Join our chat room to connect with other indieweb people who have a variety of experience:
Why? This step alone will help you quickly get questions answered about next steps. It's not required, but will almost certainly accelerate your progress.
Get a personal domain
You need your own personal domain to serve as your online identity:
- Get your own personal domain name - Ask a friend or colleague for a domain name registrar that they use and like/trust/respect etc.
- Domain Privacy - Note that most domain name registrars will make your personal information (name, mailing address, phone number and email address) publicly available via whois lookups. Some registrars offer domain privacy options, so that instead of your personal details the registrar's details will be in the whois directory. Only use domain privacy if you fully trust the provider of the service -- disputes about domain name administration or transfers may get tricky if you are not listed as the legal owner of the domain.
Why? All the reasons listed in why. This is the key first step to joining the indieweb.
Get a place for your content
You need a place for your content.
The easier, free — but limited — path is to use a free service as described in Transitional Steps.
However, ideally you should get your own web hosting provider.
Sign up for web hosting
- Sign up with a web hosting provider (ask friends and colleagues who they use for their personal websites that they're happy with, also see Lifehacker's list of 5 best web hosting companies)
- Set up your domain name to be served by your web hosting provider
You can also self-host on your own server. Interesting to hobbyists are the many Small Computers available that can be used as servers, including Raspberry Pi, Beaglebone Black, Intel Galileo, and a host of other small, low-power computers.
Set up your home page and web sign-in
The website http://indiewebify.me/validate-rel-me/ has a handy tool to validate that your domain name and profiles are linked together correctly.
Why? This ensures that it is easy to see that your profile on the social networks are all the same person as your domain name. This will also allow you to sign in to sites that support IndieAuth — like this wiki!
index.html home page to include your basic information in an h-card. This h-card can be as simple as your name.
The website http://indiewebify.me/validate-h-card/ has a handy tool to validate your h-card.
Why? When you publish content, you can link back to your home page using rel-author and your authorship information can be retrieved from the h-card.
Advantages: While you are not yet publishing content on your own site, at this point you have:
- Staked your claim on the indieweb
- Set up an identity that you own and control
These are small but important steps to declaring your independence from content silos.
Publish content on your domain
Browse the indieweb projects page, pick one, and install it.
Add microformats to your content
Add the h-entry microformat markup to your posts.
The website http://indiewebify.me/validate-h-entry/ has a handy tool to validate your h-entry.
Why? This will allow other people's software to easily read and understand your content. This is useful for a variety of things like recognizing comments, likes, reposts, and displaying reply-contexts for your posts.
Publish (on your) Own Site, Syndicate Elsewhere
Set up syndication so copies of your IndieWeb content can be published (semi-automatically) to social silos. By setting up POSSE, you can have your posts pushed to specific silos with a personal permalink/permashortlink or citation identifier back to the original on your own site.
Why? By POSSEing your content to silos, you allow those that read content on those silos to continue seeing what you have to say, while you retain ownership and control of your content on your own site.
Remember: Incremental progress is OK and encouraged! POSSE does not have to be totally automatic to be effective. If there is not a pre-existing plugin for your platform, try simply posting on your site and sharing to silos manually (include a link back to the original). This will help you figure out what works for you and what is worth the effort to automate.
- Share what you did / discovered in the process of building your IndieWeb site, even if it is only a single page, with a simple design.
- Ask what you can/should do next in the IRC channel.
- Check the list of events and join us at the next IndieWebCamp or Homebrew Website Club meetup!
- Once you can IndieAuth or log into the wiki, create your user page by wikifying yourself.
- Document what you've done and add your site and details to the IndieWeb examples section of relevant pages to share what and how you've done it with others.
Optional / Bonus Steps
Port old silo content to your site
Once you are posting on your own site and POSSE'ing out content to social silos, port your old silo content to your own site with permalinks on your site. Typically this involves a one-time export and batch import process. Here are some popular social content silos:
- Also consider sites you use which may be shutting down soon, see: site-deaths#Upcoming
Set up a personal URL shortener
- Provide discoverable permashortcitations in POSSEd notes, e.g. on Twitter, which itself enables original-post-discovery.
- POSSEing to silos that have post length limits, but don't wrap your links, e.g.
- For WordPress, install and use the Hum personal shortener plugin.
- For others, take a look at porting the existing open source Whistle algorithmic URL shortener to your system.