The rationale With Full Site Editing on the horizon for WordPress, Theme creators need to start to learn how to make themes in a different way. Full Site Editing is sea change in the way that themes work. When Themes were first added to WordPress, they were simple; just a few template files and some...
This child theme accompanies the Indieweb Publisher theme. The child theme is in formatting and order influenced by the work of StudioPress and Genesis. - frankmeeuwsen/digging-the-digital
Starter content. It was a grand idea, one of those big dreams of WordPress. It was the new kid on the block in late 2016. Like the introduction of post formats…
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.