WordPress is an open source blog software as well as a blog hosting service.
One of many IndieWeb Projects, WordPress is web software you can use to create a beautiful website or blog. Estimates are that Wordpress powers 20% of sites for which the content management server is identifiable.
If you're interested in jumping into the IndieWeb, and you've chosen WordPress as your tool of choice, great! Here are instructions that follow the step by step, ground up approach of IndieMark.
As you complete each step, try plugging your site into indiewebify.me. It will give you instant feedback, confirming that it's working or helping you fix it if not.
Getting started with Wordpress
We'll assume you already have your own personal-domain. After that, you'll need web-hosting. There are plenty of good options. WPEngine is one of the best for both beginners and advanced hackers. #WordPress.com hosting service is solid and easy to use, but limits you to pre-approved plugins and themes.
Security and Spam Protection
One of the most important things for new users to do is to properly secure their Wordpress installation.
Account names like "admin" or "administrator" are popular targets for brute-force login attempts, and should not be used as a username.
Disable registration of new users.
Login Security Plugins
There are many options in this area...
Some individuals may prefer to disable local commenting in favor of only allowing commenting through webmentions. If local commenting is enabled, there should be some form of protection installed.
Adding Indieweb Support/Elements to a Wordpress Site
Here are steps to add IndieWeb support to a WordPress site.
See also individual articles bloggers have written about setting up their sites with indieweb support:
Once you have WordPress up and running, you'll want to set up IndieAuth. If you haven't already done so (above) install IndieAuth for Wordpress which allows users to sign in with their domain instead of a username and password. Next, you'll need to add the appropriate rel-me link(s) to your homepage. TheIndieAuth-Links plugin makes this easy, but you can also use Social Media Buttons or a Text Widget to add the needed rel-me link(s). Detail can be found at indieauth.com/setup Once you've done that, head over to indieauth.com and sign in to test that you've set things up appropriately!
You can POSSE manually, but most people automate it. WordPress has many plugins that do this. A few of the most popular are:
Other plugins that can be used to POSSE:
If you POSSE, it's good practice to include rel-syndication links on your WordPress posts. Try the rel-syndication plugin for that(Currently only supports the Social plugin, the GitHub mainline has minimal support of Tumblr, Twitter and Facebook for NextScripts SNAP ).
Once you're POSSEing, you may want to pull comments and likes on the social network posts back to your site. This is called backfeed. Many of the POSSE plugins above can do this; see backfeed#WordPress_Plugins for details.
Another option is Bridgy, a service that automatically sends webmentions for activity on your POSSEd posts inside silos (before starting to use Bridgy, make sure you first install the webmention and semantic-linkbacks plugins described below).
Which brings us to...
(Warning: Don't use pre 2.0 version of the indieweb plugin! It's an old, outdated bundle of the webmention and semantic-linkbacks plugins together, nothing more.)
For the webmention plugin to work, go to the Settings => Discussion page in your WordPress admin, and check the "Allow link notifications from other blogs (pingbacks and trackbacks)" and "Allow people to post comments on new articles" checkboxes.
More building blocks
If you've made it this far, congrats! You're a fully functioning member of the IndieWeb! Here are a few more plugins you might want to try. Many require FTP or other more technical setup.
Past or old tech plugins
Some themes that support microformats or other semantics.
Rather than a theme uf2 is a plugin that attempts to add microformats2 data to an existing theme though as the author admits it is very limited and recommends using a theme that supports microformats natively.
People using WordPress
People using WordPress on their primary or other sites.
In particular, (semi-)active IndieWeb community members using WordPress on their own sites, thus you might find them on IRC to ask about their experience (or for help).
Other independents using it on their primary site
Using on one of their sites
People using WordPress on a secondary site.
Independents that used to use WordPress on their own site but have switched away (or site stopped working)
Several projects are actively under development for use in Wordpress. Plugins/themes considered complete enough for widespread use will appear on this page.
For brainstorming on development of Indieweb themes/plugins for Wordpress and discussion of common conventions to ensure interoperability, see WordPress Development.
Problems with and criticism of using WordPress software from an IndieWeb perspective.
WordPress (and often many popular plugins) frequently has security vulnerabilities that are found and exploited in a "zero day" fashion.
Security vulnerabilities are found in many popular pieces of software, as their deployment makes them attractive targets. While there is currently limited options within the core of Wordpress, there are many security plugins that offer protection for Wordpress blogs.
Independents (quite tech smart and capable) who had their WordPress blog(s) hacked due to being unable to keep up with security updates / maintenance (too much of a hassle/chore/tax on their time).
However, since Version 3.7, Wordpress supports background updates to alleviate this issue. By default, automatic updates for minor releases and translations are enabled. There are configurable settings to allow major release updates, and updates for specific plugins.
The Core Automatic Update functionality can also be used to push critical security updates to popular plugins. This was used in April of 2014 when the popular JetPack plugin was discovered to have a critical vulnerability and the developers requested the security update be pushed via the system to all users who had not expressly disabled all updates.
Fatal Error memory exhausted
WordPress seems to run out of memory on servers sometimes, and give a message like:
Pages can not have numeric slugs
WordPress does not allow numeric page slugs, making it difficult to set up pages representing a year, such as
Switching away from
There has been a trend of folks switching away from WordPress for various reasons (e.g. problems noted above). They seem to switch to one of three options, one indieweb, and two silo.
Switched to another project
There are many folks with personal sites that have kept their personal site and webhost, but switched away from WordPress to another solution, e.g. typically a static site generator:
Many others have switched to Jekyll or are in the process of doing so, e.g.:
And a few have switched to their own IndieWeb project, e.g.
Switched to WordPress service
I know there's folks that have done this but have trouble recalling offhand who in particular.
Switched to Tumblr
Folks that were on WordPress that have moved to Tumblr
POSSE to WordPress
Tantek reply POSSE
Tantek Çelik has started experimenting with manually POSSEing reply posts to WordPress blogs to their comment sections. E.g.:
WordPress.com hosting service
WordPress.com is a blog hosting service with impressive importing and export features. See for details:
WordPress.com provides themes to change the HTML/CSS/JS and general appearance of a user's site. While users can pay for a feature to write custom CSS, they can't change their theme markup. Which means amongst other things, a user cannot specify some markup in a post to show on a permanlink page and not in the post when it's a part of a feed. For example,
If you could detect "in the feed vs permalink page", you could use
POSSE to hosted
IndieWeb POSSE Examples
Shane Becker is manually POSSEing his articles to Wordpress.com.
WordPress.com doesn't have built in support for webmentions, but Bridgy can send, receive, and display webmentions for WordPress.com blogs. You can also receive webmentions with webmention.io and maybe webmention.herokuapp.com.
On 2014-05-06 it was reported that http://indiewebify.me returned an empty result when attempting to check gabrielscheer.com. That domain is hosted on wordpress.com and it appears that wordpress.com is blocking some cURL requests based on the User-Agent. At a minimum, it appears that wordpress.com is blocking cURL requests with the Guzzle User-Agent.
This issue was previously reported on Github on 2013-05-19