Chris Aldrich

@kathryn and Ola, thanks for the tweaks and the child theme! I hope that Ola is dumping the code back to Sarah or wherever you keep it internally, so that Woo support is at least partially baked in when it’s released to the .org side. I’m sure it may be on the theme’s internal roadmap, but don’t forget to declare WooCommerce support in functions.php when the final version is rolled out.

I particularly liked the careful thought to keep the theme’s buttons consistent as well as the change from 3 columns of products instead of 4. The only tweak I might further suggest is the color of the “add to cart”, “proceed to checkout”, and “pay” buttons (see https://boffosockobooks.com/product/amerikan-krazy/ which I’ve not restyled presently to highlight the existence) which all appear as purple [#a46497]. (Though the purple helps to highlight them, I wanted to make sure it was a conscious design choice rather than an oversight.) Either way, throwing the CSS code for the changes on these directly into the bundle makes it much easier for less sophisticated users to tweak the code later.

Other than that, I’ve looked through most portions fairly carefully and everything seems to be working as I’d expect it to without any glaring issues/errors. My thanks to you, Sarah, and Ola for the beautiful work that went into this as well as the after-the-fact adjustments.

@stephenwrks, A few things in the theme that you might consider taking advantage of and using on your current page are increasing the featured image opacity (25, 50, 75, or 100%) of the photos using the theme customizer/theme options/panels 1-8. This will let you “brighten” up your page without making the foreground text difficult to read and highlight the beauty of your photos.

You might also consider creating a secondary menu called “social” in the menu interface with custom items being links to your social media sites and then in the customizer/menu section setting the footer menu to use this menu. Then your social media bugs will appear in the footer of the page rather than into the second widget where it’s at now. This will help streamline and balance out your page a bit (See the Custom Menus section at https://theme.wordpress.com/themes/pique/ and https://en.support.wordpress.com/menus/social-links-menu/ for more details.)

@Stephwrks: Another separate but simple option could be to run two WP sites, one primary one running Pique theme and a secondary one living inside the first that’s running Woo and using a woo theme in similar dark colors that cross connects to the main site.

For Example, you could have https://arkvintage.com with Pique and a separate https://shop.arkvintage.com that uses Woo and a separate, but similar looking theme.

@kathryn, I think one of the more commonly encountered problems people are likely to run across is that any widgets in the left sidebar seem to get pushed to the right and down by Woo Commerce on its canonical /shop/ page and this seems to happen whether or not one is using that page with either the “Default Template” or the “Full-width Page” template.

From a UI perspective, I would expect that the “Full-width Page” template in Pique to give the content the full page and wouldn’t display any sidebar widgets at all. This apparently isn’t the case. (see https://boffosockobooks.com/shop/). If this “bug” were fixed, then most users would only run into smaller and more manageable issues like stephenwrks above which can more easily be fixed by simple CSS tweaks and modifications rather than requiring a higher hurdle of more dedicated coding.

It’s some of the recent changes that are starting to make me use it more, almost to the point that I’m ready to throw WP’s built-in post-formats out and rely solely on Indieweb Post Kinds.

Watching your evolving work and some of the others within the Indieweb/WP group makes me want to go back and brush up on my terribly old/rusty programming skills — it’s just taking me longer than I’d like with my current work schedule — particularly as this seems to me to be the right way to run the web.

Keep up the great work!!

Thanks @jwlehman, I’d tried something similar to that previously (and agree that the space could be wider in general).

Unfortunately this doesn’t seem to be the overarching problem. For some reason the entirety of what I’m seeing is only about 300px wide and it’s shifted so that the Page begins at about the midpoint of the screen.

It still seems odd to me for a WP crafted flagship theme to have this issue when no others seem to have it.

It looks like you haven’t wrapped the links with the rel=”me” tags in a <div class=”h-card”> </div>

Here’s a short sample of how mine is set up on https://boffosocko.com:

<div class="h-card">
<a href="https://facebook.com/ChrisAldrich" rel="me" target="_blank"><img src="https://domain.com/facebook.png" alt="" width="24" height="24" /> </a><a href="https://twitter.com/chrisaldrich" rel="me" target="_blank"><img src="https://domain.com/twitter.png" alt="" width="24" height="24" /></a> <a href="https://plus.google.com/+ChrisAldrich1/posts" rel="me" target="_blank"><img src="https://domain.com/google-.png" alt="" width="24" height="24" /></a>
<link href="sms:+13105551212" rel="me">
<link href="mailto:[email protected]" rel="me">
<br/><br/>
<img rel="me" class="u-photo" src="https://domain.com/site_icon.png" alt="" width="200" height="200"  /><br/><br/>
<strong><a rel="me" class="p-name u-url" href="https://domain.com">Your Name</a></strong><br/>
email: <a class="u-email" href="mailto:[email protected]">[email protected]</a><br/>
phone:<span class="p-tel"><a rel="me" href="tel:+13105551212" >+1310-555-1212</a></span><br/>
<p class="p-note">
<span class="p-job-title">President</span> at <a class="p-org" href="https://domain.com" target="blank" >Company Name</a>; <br/><br/>
<span class="p-locality">Los Angeles, CA </span><span class="p-country-name">United States</span></p>
</div>

You should be able to use this as a model to get you going. I simply cut and pasted something similar into a sidebar widget that only appears on my front page.
Note that the <link> tags contain metadata that IS NOT displayed on the page, but which return data for an h-card parser. You may need to pay attention later though if your details change, particularly since they don’t show up on the page and you may forget they’re there.

You’ll need something similar as an h-entry set up so that your “authorship” data shows up properly as well, though that one should only appear on pages on your site on which you’ve created articles/posts.

I agree wholeheartedly with Adam, though I don’t think I’d really seen any small issues except perhaps for an odd CSS issue in formatting an <h2> tag somewhere. (Note: This comment applies to v1.2.3 of Academica as on 4/2/15, the theme publisher made a DRASTIC change to the theme, so take caution in upgrading!!)

I have created a child-theme with one or two small customizations (slightly larger headings in side widgets and some color/text size changes), but otherwise have v1.2.3 working as perfectly as it was intended to. This includes the slideshow functionality on the homepage. See BoffoSocko as an example.

For those, perhaps including Adam, wanting to get the slider to work properly:

• Go to your WP Dashboard hover on the menu tab “appearance” and click on “customize”
• On the “Featured Content” tab, enter a tag you want to use to feature content on the homepage of your site. (In my case, I chose “featured” and also clicked “Hide tag from displaying in post meta and tag clouds”.)
• Go to one or more posts (I think it works on up to 10 featurable posts) and tag them with the word you just used in the featured content setting (in my case “featured”
• Next be sure to actually set a “Featured photo” for the post–930×300 pixels is the optimal photo size if I recall.
• Now when you visit your home page, the slider should work properly and include arrows to scroll through them (these aren’t as obvious on featured photos with white backgrounds).
• Note that on individual pages, you’ll still have static header image(s) which are also customizable in the “customize” section of the WP dashboard, which was mentioned in step 1.

I hope this helps.

Thanks! I’m happy to help bang on features that need testing. Just let me know.

Thanks! I’d meant to drop a note into GitHub as well, but given the growth that IndieWeb plugins have been experiencing over the past several months, I thought it worthwhile to encourage some more public-facing attention here.

Jeremy, I suspect that my settings were set to autopost to multiple social media sites and upon importing (and publishing) Tumblr posts, they all just defaulted to cross-post via my JetPack settings. I should have thought to have disabled them prior to import. The site is https://boffosocko.com if you care to look. I suspect it’s something that could/should be handled by the importer directly, though you may be able to arrange something with Samuel.

Thanks.

Perhaps you’re right.

I’ve noticed also that when the plugin does the reposting to tumblr, it does so in reverse order. Wouldn’t it make more logical sense for it to repost them in the original order? (No reply necessary, just a thought.)

As I’ve been thinking about it, perhaps importing everything as “pending approval” may be the better way to go, then one can edit/modify them and potentially add additional data/metadata in fields made available by other plugins (like Jetpack and others – SEO plugins for example). Except for people who are importing hundreds or thousands of posts, this may be far preferable – and even in those cases they can bulk edit them in the WP interface.

For usability, I previously had used WordPress and Tumblr for slightly different use-cases and some of my WP content also was cross-posted to my Tumblr account. I primarily wanted to suck in all of my Tumblr content which I hadn’t had previously. Thus some of the previous cross-posts were duplicates which I had to go in and delete out manually.

The biggest headache was calls/emails from friends/subscribers who were inundated by the social media vomit.

Thanks for the work on this otherwise excellent little plugin!

Thanks Sam, I’m noticing now that it only made copies of the original posts and then redirects them back to the new posts at WP. So it’s ultimately not as bad as I had supposed.

You should sincerely considering putting in written caveats into the importer workflow to warn heavily against turning off any social media integration (JetPack, IFTTT, etc.) to prevent this type of behavior in the future.

I’ve updated my review to reflect.