Watch a demo with Cameron Jones from WP Theme Components and Nathan Wrigley from WP Builds What is a theme component? Theme components are bite sized code snippets that can be reused across multiple themes. Using theme components makes it easier to reuse the same code across multiple themes. What is...
Theme components are bite sized code snippets that can be reused across multiple themes, but are either too small or don’t make sense to be released as a plugin. Stop cluttering up your functions.php file and start using theme components! Who are theme components for? Th...
Let’s get together as a community and host a theme raising (a play on the idea of the old barn raising). We can all work/hack together to make some of the popular WordPress themes more IndieWeb friendly. We’ll discuss methods for adding the necessary Microformats and best ways to indieweb-ify a WordPress theme.
Either bring your own favorite theme or work from one on a list.
All levels are welcome!
Beginners and those without coding experience are welcome/encouraged to attend. We’ll try to help newcomers learn to begin tinkering with some WordPress theme code. If you don’t have a GitHub account yet, you might create one beforehand and we’ll show you how to use it for development, but even without it you can still do a lot with just a text editor.
When: 2020-09-26 9:30 – 11:30 AM (Pacific) / 12:30 – 2:30 PM (Eastern)
hashtag: for social media and used to create an Etherpad for the session: #WPandMicroformats
Etherpad: https://etherpad.indieweb.org/WPandMicroformats for note taking during the session
Streaming video/audio platform: Zoom (link to come)
Demos: Yes – when we’re done, show off how well your new hacked theme works on your site.
Newcomers can post a comment on this post below or reply yes via Twitter to https://twitter.com/ChrisAldrich/status/1300562134699393024. Or you can feel free to just show up on the morning of the event.
Bring your own theme or a theme you’d like to make more IndieWeb friendly by adding Microformats v2 support. Ideas for possible themes can be found at https://indieweb.org/WordPress/Development#Themes
(Optional) Create a GitHub account which you can use/learn during the process. Those who don’t want a GitHub account can simply use their text editor of choice to modify the relevant theme files.
We’re always happy to have additional help! If you’d like to volunteer or help organize and run the session, please touch base with Chris Aldrich or David Shanske in the IndieWeb Meta chat room.
I look forward to seeing everyone there!
I have been thinking a lot about digital gardens this week. A blog post by Tom McFarlin re-introduced me to the term, which led me down a rabbit hole of interesting ideas on creating a digital space…
My blog posts were merely random thoughts — bits and pieces of my life. ❧
Annotated on August 12, 2020 at 09:52AM
Despite having something that worked sort of like a blog, I maintained various resources and links of other neat ideas I found around the web. It was a digital garden that I tended, occasionally plucking weeds and planting new ideas that may someday blossom into something more. ❧
The idea of a thought space hiding in here….
Annotated on August 12, 2020 at 09:53AM
“The idea of a ‘blog’ needs to get over itself,” wrote Joel Hooks in a post titled Stop Giving af and Start Writing More. “Everybody is treating writing as a ‘content marketing strategy’ and using it to ‘build a personal brand’ which leads to the fundamental flawed idea that everything you post has to be polished to perfection and ready to be consumed.”
It is almost as if he had reached down into my soul and figured out why I no longer had the vigor I once had for sharing on my personal blog. For far too long, I was trying to brand myself. Posts became few and far between. I still shared a short note, aside, once in a while, but much of what I shared was for others rather than myself. ❧
For many, social media took over their “streams” of thoughts and ideas to the point that they forgot to sit, reflect, and write something longer (polished or not).
Personal websites used for yourself first is a powerful idea for collecting, thinking, and creating.
Getting away from “branding” is a great idea. Too many personal sites are used for this dreadful thing. I’d much rather see the edge ideas and what they flower into.
Annotated on August 12, 2020 at 09:56AM
Personal websites can be so much more than a progression of posts over time, newer posts showing up while everything from the past is neatly tucked on “page 2” and beyond. ❧
This is an interesting idea and too many CMSes are missing this sort of UI baked into them as a core idea. CMSes could do a better job of doing both: the garden AND the stream
Annotated on August 12, 2020 at 09:57AM
While I lament the loss of some of the artistry of the early web and lay much of the blame at the feet of blogging platforms like WordPress, such platforms also opened the web to far more people who would not have otherwise been able to create a website. Democratizing publishing is a far loftier goal than dropping animated GIFs across personal spaces. ❧
WordPress has done a lot to democratize publishing and make portions of it easier, but has it gone too far in crystalizing the form of things by not having more wiki-like or curation-based features?
Annotated on August 12, 2020 at 10:01AM
Throughout the platform’s history, end-users have remained at the mercy of their WordPress theme. Most themes are built around what WordPress allows out of the box. They follow a similar formula. Some may have a fancy homepage or other custom page templates. But, on the whole, themes have been primarily built around the idea of a blog. Such themes do not give the user true control over where to place things on their website. While some developers have attempted solutions to this, most have never met the towering goal of putting the power of HTML and CSS into the hands of users through a visual interface. This lack of tools has given rise to page builders and the block editor. ❧
an apropos criticsm
Annotated on August 12, 2020 at 10:02AM
I also want them to be able to easily build something like Tom Critchlow’s wikifolder, a digital collection of links, random thoughts, and other resources.
More than anything, I want personal websites to be more personal. ❧
Those in the IndieWeb want this too!! I definitely do.
Annotated on August 12, 2020 at 10:03AM
P2 powers internal collaboration at WordPress.com — and now it’s free for everyone. As more collaboration is happening remotely and online — work yes, but increasingly also school and persona…
Within higher education, requests to build websites for individual faculty members sit at the absolute bottom of the work queue for most marketing/communications teams. If this type of product is offered at all, it typically uses a self-service model; the institution will provide the platform while the faculty member will provide the content. And while this is the most sustainable model for most small and mid-sized web teams, it tends to produce multiple websites that are ineffective at communicating even simple messages. Worse, they have a high tendency to become the poorest reflections of the institution with a high rate of abandonment or misuse.
Let's fix that tendency together. With a careful examination of what really matters to faculty members who are looking to create and maintain their own websites, we can begin to build better sites. With better sites (and a little luck), you can start to derive value from the project at the bottom of your work pile.
Together we'll talk about:
- A simple analysis of the types of content that you'll typically find within a faculty website.
- A "wish list" for the types of content that you (as a marketer) would really like to see from these types of sites.
- A working example of a theme that delivers on these key concepts and adds some "quick wins" which makes for a better experience.
- How to leverage the capabilities of WordPress multisite to produce more value from collections of these type of sites.
I totally want to start using something like this myself to not only test it out, but to build in the proper microformats v2 mark up so that it’s IndieWeb friendly. Perhaps a project at the planned IWC Pop-up Theme raising session?
Registering a sidebar gives our theme an area where dynamic content can be added by Widgets and managed by the site owner using a drag an drop interface. This can include menus, custom HTML, Images and additional features introduced by Plugins. In this post we’ll register a sidebar, that will then be assigned dynamic widgets and displayed on our site’s footer.
Adding or Registering menus to a WordPress website has frequently been a challenge which is why I believe it deserves its own post as we learn about register_nav_menus() then adding those Navigation Menus to our theme.
Creating a WordPress theme only requires three files. style.css, index.php, functions.php. However since we’ll be needing them later lets include header.php and footer.php.
I’m a fan of using WordPress to build custom websites. So I’ve decided to start a tutorial series and share how I go about building a theme from scratch. No frameworks or starter themes.
Below are my initial thoughts and problems.
/home/ page has a lot of errors and warnings. (Never a good sign.)
It took me a few minutes to figure out where the Wik-it! bookmarklet button was hiding. Ideally it would have been in the start card that described how the bookmarklet would work (in addition to its original spot).
The Wikity theme seems to have some issues when using for http vs. https.
- Less seems to work out of the box with https
- The main card for entering “Name of Concept or Data” didn’t work at all under https. It only showed the title and wouldn’t save. Switching to http seemed to fix it and show the editor bar.
- Nothing seemed to work at all when I had my site as https. In fact, it redirected to a URL that seemed like it wanted to run
update.phpfor some bizarre reason.
- On http I at least get a card saying that the process failed.
- Not sure what may be causing this.
- Doesn’t seem to matter how many cards it is.
- Perhaps it’s the fact that Aaron’s site is https? I notice that his checkbox export functionality duplicates his entire URL including the https:// within the export box which seems to automatically prepend http://
- Copying to my own wiki seems to vaguely work using http, but failed on https.
Multiple * in the markdown editor functionality within WordPress doesn’t seem to format the way I’d expect.
Sadly, the original Wikity.cc site is down, but the theme still includes a link to it front and center on my website.
The home screen quick new card has some wonky CSS that off centers it.
Toggling full screen editing mode in new cards from the home screen makes them too big and obscures the UI making things unusable.
The primary multi-card home display doesn’t work well with markup the way the individual posts do.
The custom theme seems to be hiding some of the IndieWeb pieces. It may also be hampering the issuance of webmention as I tried sending one to myself and it only showed up as a pingback. It didn’t feel worth the effort to give the system a full IndieWeb test drive beyond this.
Doing this set up as a theme and leveraging posts seems like a very odd choice. From my reading, Mike Caulfield was relatively new to WordPress development when he made this. Even if he was an intermediate developer, he should be proud of his effort, including his attention to some minute bits of UI that others wouldn’t have considered. To make this a more ubiquitous solution, it may have been a better choice to create it as a plugin, do a custom post type for wiki cards and create a separate section of the database for them instead of trying to leverage posts. This way it could have been installed on any pre-existing WordPress install and the user could choose their own favorite theme and still have a wiki built into it. In this incarnation it’s really only meant to be installed on a fresh stand-alone site.
I only used the Classic Editor and didn’t even open up the Gutenberg box of worms in any of my tests.
The Wikity theme hasn’t been maintained in four years and it looks like it’s going to take quite a bit of work (or a complete refactoring) to make it operate the way I’d want it to. Given the general conceptualization it may make much more sense to try to find a better maintained solution for a wiki.
The overarching idea of what he was trying to accomplish, particularly within the education space and the OER space, was awesome. I would love nothing more than to have wiki-like functionality built into my personal WordPress website, particularly if I could have different presentations for the two sides but still maintain public/private versions of pieces and still have site-wide tagging and search. Having the ability to port data from site to site is a particularly awesome idea.
Is anyone actively still using it? I’d love to hear others’ thoughts about problems/issues they’ve seen. Is it still working for you as expected? Is it worth upgrading the broken bits? Is it worth refactoring into a standalone plugin?
Theme for NHS organisations based on the NHS Digital frontend framework. Highly customisable for all types of NHS organisations, from campaign sites to primary care providers to arms length bodies to community practices. This can also be used for non NHS organisations.
There’s a brand new, open source, theme for WordPress users in the NHS.
Nightingale 2.0 – https://t.co/h4nKAqVfq3
Responsive, accessible, free, and gorgeous.
Great work by the NHS Leadership Academy Digital Team.
— Terence Eden (@edent) April 30, 2020
From what I can tell, they’re creating the content to help users realize how to set up a separate front page and a separate blog page which isn’t always intuitive to newcomers to the platform. Fortunately they haven’t made too much useless content and new users can simply either edit the front page the theme creates to something that suits them or just delete that page and create something of their own.
The only other content I can see that one might want to modify are the two footer widgets that you can either edit or simply delete or replace.
In all I think they’ve taken this route simply to give new users an idea about how they could set up their sites and give them an idea about the way the theme uses the Gutenberg editor. (It’s not too different from the long standing “Hello World” introductory post or the “Hi, this is a comment.” first comment on a fresh install.) For people new to WordPress this is probably pretty helpful, though for older hands it may be annoying. Fortunately the content the customizer creates is pretty minimal and easy to get rid of.
I'm in the process of gradually enhancing my site's markup with microformats, in order to "indiewebify" my site further. On thing I noticed while working on this at the Düsseldorf Indiewebcamp, is that WordPress (or the way my theme handles) tags on posts has no way to get an additional class insid...