#LoqiIt looks like we don't have a page for "child theme" yet. Would you like to create it? (Or just say "child theme is ____", a sentence describing the term)
#chrisaldrichYou'd have paid money for the pro version.
#chrisaldrichjgmac1106 may have some familiarity with this as I think he used that same theme a while back.
#dmcweeneyI have the free version - I use reclaim hosting
#chrisaldrichdo you want to keep the sidebars anywhere on your site?
#dmcweeneyOnly on the front page (which is currently how I have it). I removed the sidebars from the rest of the pages and blog posts on my site
#dmcweeneyHowever, that category page I showed you has the sidebars and I don't want the sidebars on that category page - I thought the category page had a page ID but I don't see one
#chrisaldrichyou could create a custom view for that particular category in your theme and remove the code for the sidebars that is indicated in that article I indicated above. That may be the easiest way to go.
#chrisaldrichI'm curious how you removed them in all the other pages? Hopefully you didn't write a huge number of CSS Rules that hid them all on a one-by-one basis...
#chrisaldrichThat's certainly a way to do it, but since your site is processing all that data, and all the extra CSS to boot, you're doing it in the most circuitous route possible.
#dmcweeneySo my thought is that if I use the same CSS rule, it would work. Problem is, the category page ... I can't find its page ID
#chrisaldrichIn your case I'd copy the standard post page php file for your theme and use that as a custom page template for your home and then modify the standard page code to remove the get_sidebar portions.
#dmcweeneySo my thought is that if I use the same CSS rule, it would work. Problem is, the category page ... I can't find its page ID
#chrisaldrichCategories aren't done as pages, since they're archives of posts. Looks like you might do it with "category-freeyourmindblog" instead of a post ID, but you'd likely have to do it for every category on your site as well.
#[dmitshur]I see you also tried to sign in via your GitHub profile url, that was separate right?
#chrisaldrichdmcweeney, I'll note that without the sidebars taking up the screen space that your articles now take up the full width of the page and become much harder to read. Most designers would recommend between 50 and 70 characters of reading space across and your site now has almost twice that.
#Loqi[troutcolor] #911 publishing to mastoton stopped working
jeremych_, jgmac1106, [Rose], [grantcodes] and [dmitshur] joined the channel
#[dmitshur][aaronpk] As a heads up, I'm planning to send a PR to the indieauth spec to fix up some minor wording inconsistencies in a few places. It was making the spec harder to read (especially when I was much less familiar with it), and I realize by now it wasn't intentional. I found issue https://github.com/indieweb/indieauth/issues/13, which was resolved, but the fix was incomplete. My PR will just address the remaining minor issues.
#Loqi[EdwardHinkle] #13 Subheadings in Section 5: Authentication should all say Authentication rather than Authorization
#[dmitshur]As I understand, it's always "authZ endpoint" and "authZ code". However, there is both "auth{N,Z} request" and "auth{N,Z} response", and "auth{N,Z} [work]flow".
[jgmac1106], [Sadik_Shahadu], [mapkyca], [tantek] and [Michael_Beckwit joined the channel
#[dmitshur]I was motivated by a few glaring inconsistencies, but when I started fixing them, I found more... so this change is starting to look big because it takes on quite a bit. I broke it up into 4 separate logical commits (with descriptive commit messages) to hopefully make it easier to review and potentially reject certain parts but keep others, etc.