#wordpress 2018-12-31

2018-12-31 UTC
#
GWG
pfefferle, I think people think the frustration that caused me to stop contributing to Core would have me stop contributing
#
[grantcodes]
Yes. I've skipped left, right and center for now
#
GWG
I think maybe we need more Indieweb plugins more than ever
#
[pfefferle]
More plugins with fewer people
#
[grantcodes]
Why fewer people?
#
[pfefferle]
Fewer developers
#
[grantcodes]
Why fewer developers? Is there a theory that people are leaving because of Gutenberg?
#
[pfefferle]
No, but there were more people working on WordPress some months ago
#
[tantek]
is the JS focus perhaps a bit of Ghost envy?
#
GWG
It is myself and pfefferle in our community most of the time
#
[grantcodes]
Just indieweb WordPress we're talking here?
#
[pfefferle]
I don‘t think so... ghost is 5 years old and Wordpress will not change the core to nodejs
#
GWG
I don't know
#
[pfefferle]
At least I meant the indiewordpress community
#
GWG
Are we talking about the numbers of people who left contributing to WordPress core due the current environment as well?
#
[pfefferle]
Because GWG meant: perhaps we need more indieweb plugins
#
GWG
pfefferle, we need more cohesion in what we have
#
[grantcodes]
Cool got it. Yeah can see Gutenberg making WordPress more difficult for the indieweb but for the wider WordPress community I can imagine it being successful after the transition period
#
[pfefferle]
GWG i am not exactly sure what you mean with cohesion
#
GWG
pfefferle, they need to work better. We need to smooth the parts that are difficult.
#
GWG
We don't need loads of new features
#
[pfefferle]
That makes it not really easier or less work 😉
#
[pfefferle]
Too many loose ends
#
GWG
pfefferle, how so?
#
GWG
It is still a lot of work
#
GWG
I think it has gotten better over the years
#
[pfefferle]
That’s what I was trying to say 😉
#
GWG
I want it to continue to
#
GWG
I did a lot of plumbing work, like Parse This and MF2_Post to try and make that work
#
GWG
Abstract everything
#
GWG
pfefferle, in the last Parse This improvement, I made loading conditonal. So it will only load when first needing each piece
#
GWG
pfefferle, with more optimization, it could form the core of any Parsing efforts
#
[pfefferle]
But I am still skeptical if it is the right tool for webmentions, but I will have a look
#
GWG
pfefferle, I intend to try to make it so
#
[pfefferle]
But still the problem with the overhead, like the whole rss stuff and does it support post type discovery?
[schmarty] joined the channel
#
GWG
pfefferle, it does, and the RSS is an optional flag
#
[pfefferle]
But comes with a lot of files... But we already talked about that...
#
[pfefferle]
So, time to go to bed
#
[pfefferle]
Have a happy new year altogether
#
GWG
Thanks
ben_thatmustbeme, [tantek], [nick] and [asuh] joined the channel
#
[asuh]
Adding late to yesterday’s PHP vs JS discussion, Matt Mullenweg’s vision for WordPress is best stated here in the section “With the adoption of React for Gutenberg, what do you see as the future for React and WordPress?”
#
[asuh]
He says, “I can imagine a future wp-admin that’s 100% JavaScript talking to APIs. I’m excited to see that happen.”
#
Loqi
[Matt] Update: On December 6th we released WordPress 5.0. It was definitely the most controversial release in a while, but the usage and adoption metrics are looking similar to previous releases. I’m looking forward to continuing to iterate on the new blo...
metbril joined the channel
#
[asuh]
I do wonder if his vision for 100% JavaScript is a compliment to the PHP or a complete replacement. If Gutenberg is intended to run 100% JS both client-side and server-side, then I think that spells doom for PHP’s future in WordPress
#
[asuh]
My opinion is his JS focus is to play catch up on the JS side to a system that feels more dymanic and relies less on full page reloads.
metbril joined the channel
#
[asuh]
It’s curious how WordPress can utilize the new Javascript magic from things like async/await, import/export, and the various new Object methods that push JS in a more functional programming direction without completely reduplicating everything done with PHP.
[metbril] and [pfefferle] joined the channel
#
[pfefferle]
They will not replace the php core... wordpress is still compatible with php 5.2 to be compatible with most of the shared hosting platforms today... if they switch to node, it would kill their market dominance...
#
[pfefferle]
Not to forget the complete plugin and theme ecosystem
#
[asuh]
[pfefferle] right, but if they continue a pattern of replacing feature after feature with JS-only components, like Gutenberg, they’ll force the ecosystem to adapt?
#
[pfefferle]
But only for the admin
#
[asuh]
They’re already giving big hints that WP-JSON is the future of consuming data on the front-end, which is pushing a language-agnostic approach to themes
#
[pfefferle]
Yes, but isn‘t that bad?
#
[pfefferle]
I think it will be possible to write themes and plugins with pure php
#
[pfefferle]
Except some settings stuff
#
[pfefferle]
And theme developers should already be aware of JS
#
[pfefferle]
As I mentioned above, the heavy focus/use on the API allows a lot of possibilities
#
[pfefferle]
„Classic Editor“ might be „Classic Admin“ in the end and provide the classic php admin that uses the same endpoints then the react one.
#
[pfefferle]
Or some other rich clients like automattics calypso https://github.com/Automattic/wp-calypso
#
Loqi
[Automattic] wp-calypso: The JavaScript and API powered WordPress.com
#
[pfefferle]
And I have the opportunity to learn some react ;)
#
[asuh]
[pfefferle] I agree it's bad for the old PHP devs and probably good for JS devs who like a challenge. I hope WP will not get too deep into React like it did with PHP 5.2 and jQuery with no contingency to move on. jQuery was awesome in its first decade and solved lots of problems but it and PHP 5.2 hold WP back severely.
#
[pfefferle]
Ok, I share this fear... Building on top of react may be a risk because JS frameworks are changing heavily over the last months/years
#
[pfefferle]
And don‘t get me wrong, I can understand all the skeptics... just want to bring some optimism 😉
#
[asuh]
[pfefferle] ++
#
Loqi
[pfefferle] has 31 karma in this channel over the last year (35 in all channels)
#
[asuh]
I'm trying to do the same, learning the shortcomings of what's happening and hoping I won't have to once again switch away from WP
#
[pfefferle]
I use wordpress since it was called b2... I hope so too!
#
[asuh]
haha yes, still relevant even today
#
[asuh]
can't believe that's over 2 years old already
metbril and [jgmac1106] joined the channel
#
[jgmac1106]
Mozilla did a Calypso fork for a hot minute that was supposed to replace their blogs
[xavierroy] joined the channel
#
[xavierroy]
[pfefferle] IS there a a way to hide the header image block in zenpress?
#
[jgmac1106]
[xavierroy] did you try just turning it off in customizer or do you mean on a per page post
#
[xavierroy]
i tried turnign it off, i still get a huge blank banner
#
[jgmac1106]
[davidmead] I left WordPress, just too much and not enough for me
#
[jgmac1106]
is is the featured image an not a sit header image?
#
[xavierroy]
[jgmac1106] I've no image set in the Header Image section for the theme
#
[jgmac1106]
strange it doesnt happen on my SemPress test sites...but you customized a ton
#
[xavierroy]
with zenpress
#
[jgmac1106]
.ooooh I haven't played with ZenPress as much
#
[pfefferle]
[xavierroy] not yet, but can you file an issue on github, then I will add that soon!
#
Loqi
[xavierroy] #21 header image block is displayed when there is no header image set
[Vincent] and metbril joined the channel
#
[pfefferle]
Ok, Thanks ☺
[voss] joined the channel
#
petermolnar
also somewhat relevant to the discussion: https://blog.usejournal.com/wordpress-is-at-a-crossroads-133638714a52 (and to indieweb, in general, with the "If all you’ve ever done is post on Facebook and Twitter, the leap between social media and self-hosted WordPress is huge and there are many viable alternatives in that gap." quote)
#
petermolnar
eh, forgot to scroll
#
petermolnar
relevant to yesterday
#
[pfefferle]
Thanks for the article!
#
[jgmac1106]
just read it, that does best job to date exploring the issues
jgmac1106, metbril and [davidmead] joined the channel
#
[davidmead]
[jgmac1106] I’m feeling the same way
metbril and [jgmac1106] joined the channel
#
[jgmac1106]
[davidmead] I keep a Known test site up where I can invite you and give you admin privileges
#
[jgmac1106]
I went with Known and a few static pages
metbril joined the channel
#
[davidmead]
[jgmac1106] thx. I actually used Known back when Jo & Ben were running it. I may hit you up when i run into install issues 🙂
#
[jgmac1106]
@gwg going to do the videos starting Wednesday but I am going semi offline (no chat but still documenting work on blog
#
GWG
Okay
metbril, [jgmac1106], [smerrill], [kevinmarks], [tantek], [schmarty], [nick], gRegorLove, [Vincent] and tbbrown joined the channel
#
Loqi
[David Shanske] The Twentysixteen Indieweb theme has been renamed. This is out of necessity as it was using the same slug(twentysixteen) as the item it was forked from. The new slug and repository name is IW26. While I’ll be keeping the basic style of 2016, I’ll...
[schmarty] joined the channel