WordPress is designed for everyone… Just not for us

แชร์
ฝัง
  • เผยแพร่เมื่อ 29 ก.ย. 2024

ความคิดเห็น • 53

  • @maxziebell4013
    @maxziebell4013 ปีที่แล้ว +10

    Amazing insight into the evolving landscape of WordPress and its challenges! It's refreshing to hear a comprehensive perspective that covers the experiences of website owners, developers, and web designers. Your commitment to understanding and adapting to these changes, even when they're frustrating, is commendable. Looking forward to the live session with Jonathan Jernigan and your future content. Keep up the great work! 👍🖥

    • @AdamLoweIO
      @AdamLoweIO  ปีที่แล้ว

      Thanks for the kind words. When I hear developers, freelancers, and agency owners complaining about WordPress in groups I have to force myself to remember that WE are not the target audience for the platform, we are just the people who implement it.

  • @visualmodo
    @visualmodo ปีที่แล้ว

    Truly good job!

  • @Line49Design
    @Line49Design 8 หลายเดือนก่อน +1

    This is such a well written and accurate summary of the reason and approach taken by WP in response to market competition. Nicely done 👍

  • @codingtostopprocrastinatio9748
    @codingtostopprocrastinatio9748 8 หลายเดือนก่อน +1

    Subscribed. Useful video.

  • @martinkaspar5095
    @martinkaspar5095 7 หลายเดือนก่อน

    Adam - thats just awesome - your vids are very inspiring 😳📷 and each of your vids - is amazingly packed with ideas and tips😍 sensational 👏👏💥 🎆💥🎆
    i really love your approach - to say - WordPress is designed for everyone… Just not for us:

  • @wpeasy
    @wpeasy ปีที่แล้ว +3

    Hey Adam, I like your content.
    John Lydgate - “You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”.”
    “designed for everyone.” is like saying anyone can use a hammer. Both are true, but what can you do with that hammer?

    • @AdamLoweIO
      @AdamLoweIO  ปีที่แล้ว

      “Designed for everyone” may work for simple and tools like a hammer or pencil. It may even work for software like a word processor. But WordPress is complex and specialized software with a relatively narrow use case. I think they’d be much better off my defining their target audience. Of course, doing that doesn’t make for a very catchy marketing phrase.

    • @wpeasy
      @wpeasy ปีที่แล้ว +1

      @@AdamLoweIO Agreed, but another way of looking at it is “Designed for everyone” to do what?
      I think we are looking at “Designed for everyone” to build websites. But some users just want to add blog posts, testimonials, photos etc.

    • @AdamLoweIO
      @AdamLoweIO  ปีที่แล้ว

      Yeah, the "designed for everyone" thing is a genius marketing message, isn't it?

  • @PierluigiFerrara
    @PierluigiFerrara 6 หลายเดือนก่อน +1

    I couldn't agree more with you. I feel the same frustration, as a "designer". Sometimes I think Matt declared war to agencies and developers (all kind of developers...)

    • @AdamLoweIO
      @AdamLoweIO  6 หลายเดือนก่อน

      It sure feels that way. Of course, I doubt it’s as malicious as that. My guess is that they aren’t hearing from agencies and freelancers, so they are blind to our needs. The large companies, React developer community, and backend dev communities are the ones that are most active in their official channels so they are the ones with the voices. I think Matt even said something similar a week or so ago when he asked that agencies and freelancers take our needs the proper channels instead of just complaining on social media.

    • @PierluigiFerrara
      @PierluigiFerrara 6 หลายเดือนก่อน

      @@AdamLoweIOYou are right: "declare war" is too much. "Don't care at all" is a better definition. I am wondering if Matt asked for proper channel and he mean it OR he will just go on fighting Wix and its clones, period.
      Agencies and developer, part of the WordPress echo system are often competing with each other so it could be difficult to have a proper channel grouping their voices.
      I still think that on his (Matt's) path there will be many casualties: freelancers, small agencies, big agencies and even big developer companies that, in the last years, did contribuite a lot to the success of WordPress.
      I hope I am wrong :)

    • @WebMatros
      @WebMatros 19 วันที่ผ่านมา

      @@PierluigiFerrara I can't believe Matt Mullenweg (and team) has let UI "slip" the way they have, with the actual implementation of blocks and FSE. There are so many things that could be improved usability-wise.
      That's my own biggest pet-peeve with WP anno 2024.

  • @Permaslug
    @Permaslug ปีที่แล้ว +1

    Really great video - frustratingly accurate, as well!

  • @MJSWP
    @MJSWP ปีที่แล้ว +2

    Terrific video, Adam. Very interesting times in the WP world. Looking forward to your videos on FSE vs page builders. I'm still unsure of what can and can't be done with FSE.

    • @AdamLoweIO
      @AdamLoweIO  ปีที่แล้ว +1

      I’m actually surprised at how much can be done with FSE and custom blocks. In some (many!) cases it’s harder than with Classic Themes, but haven’t run into any real show stoppers yet. Of course I’ve only created 10’ish or so FSE themes and none of them were truly complicated.

  • @modemlooper
    @modemlooper 7 หลายเดือนก่อน

    I feel the complete opposite of the opinion of this video. I thought Gutenberg was trash when it first came out and it confused people because of the classic editor and the UI of the old WordPress but I think in recent updates with full editing they really took it to another level and developers are going to have it a lot easier because they can set up things and then the client won’t screw up the site.

    • @AdamLoweIO
      @AdamLoweIO  7 หลายเดือนก่อน

      It sounds like we may actually be on the same page. Gutenberg has a lot to offer (React) developers, as you mentioned. And new things like Partially Synced Patterns are going to deliver more options for content editors. It's the web designers, and a lot of small agencies with very front end development experience, who are being left behind by Core WordPress. Thankfully, page builders like Oxygen and Bricks fill that gap so they aren't using end-user tools like Elementor, but WordPress isn't doing much to bridge that gap between designer and developer.

  • @DesignwithCracka
    @DesignwithCracka ปีที่แล้ว +1

    Interesting perspective!

  • @apatsa_basiteni
    @apatsa_basiteni ปีที่แล้ว +1

    2023 we still don't have a native feature to duplicate/clone a post in WordPress.

    • @AdamLoweIO
      @AdamLoweIO  ปีที่แล้ว +3

      There are so many missed opportunities for them to improve the user experience.
      As for this example, I have to imagine it’s difficult for them to decide what to code into the CMS and what to leave to developers to add. For example, a snippet to duplicate posts is only about 70 lines long or it can easily be added as a plug-in from the repository. I’m hoping their “canonical plugin” concept will get implemented and make this better.

    • @apatsa_basiteni
      @apatsa_basiteni ปีที่แล้ว

      @@AdamLoweIO Good to see the return of features like being able to add custom fonts as a native feature in the upcoming Wordpress 6.4. But the amount of simple stuff that requires external plugins sometimes can be frustrating.

    • @AdamLoweIO
      @AdamLoweIO  ปีที่แล้ว +1

      Agreed 100%

  • @DPlugins
    @DPlugins ปีที่แล้ว

    Nice summary. Will be join to the session as well.

  • @martinkaspar5095
    @martinkaspar5095 8 หลายเดือนก่อน

    Adam - its amazing! 🚀I wanna truly thank you for making this for us all. 🙏🙏🙏😊👍🏻You've put a huge amount of time and effort into making it, is so useful! Thanks SO MUCH!!

    • @AdamLoweIO
      @AdamLoweIO  8 หลายเดือนก่อน

      Thank you so much, Martin. It takes a lot of time and effort, so I really appreciate the feedback.

  • @williammindreaders1029
    @williammindreaders1029 ปีที่แล้ว

    i wanted to put 100 likes on that one !

  • @carlosrosalesrojas6788
    @carlosrosalesrojas6788 ปีที่แล้ว

    What do think about pinegrow and WP in the near future? I mean once WP goes FSE...

    • @AdamLoweIO
      @AdamLoweIO  ปีที่แล้ว

      I actually did a TH-cam live with Jonathan Jernigan last friday where we discussed this. (th-cam.com/users/liveRbF54uKQryo?si=arguDfWuTNUMXBHU). -- Long story short, FSE is hard to do with core blocks only and I think Pinegrow is well positioned to create custom blocks to help make Block Themes easier. I've been doing this since WP 5.9 and it's been going well.

  • @dzulhelmi81
    @dzulhelmi81 ปีที่แล้ว

    Agreed!