[asuh]I’ve forked the Roots Sage theme and, using GWG’s Indiewebified TwentySixteen fork as a base, applied many of the same updates to Sage. This is a work in progress as they go from Beta to final over the next few weeks. At that time, I will make a hard fork in its own repo.
Loqi[asuh] sage: The best WordPress starter theme with a modern front-end development workflow. Based on HTML5 Boilerplate, gulp, Bower, and Bootstrap.
[asuh]If you’re a WordPress theme developer, Sage is cutting edge but fascinating in the ways it pushes the boundaries. Trellis, Bedrock and Sage make up the Roots ecosystem, which is basically a Vagrant virtual server all-in-one dev environment. I figured it can’t hurt to have Indieweb experience on another theme.
ZegnatDo you need the hard fork? Some of the changes you seem to have made there feel like they would be nobrainers for acceptance upstream. Like the H1/P switch for header title you did in header.blade.php
[asuh]Zegnat I should do a pull request on various pieces like that but the guys in charge are very opinionated and often reject these types of changes
[prtksxna]asuh You should be able to go to a new branch `git checkout -b exp` set it back to the original commit from upstream `git reset --hard sha1here` and then cherry-pick your commit piece-by-piece using `-p` like `git cherry-pick theothersha1 -p`. I think that should work. Or else unstage the commit and then `git add -p`.
Loqi[xavierroy] Also getting these on the post page:
Warning: require_once(/home/xavroy1/xavierroy.com/wp-content/plugins/indieweb-post-kinds/templates/reply-metabox.php): failed to open stream: No such file or directory in /home/xavroy1/xavierroy.com/wp-includes...