the answer for all question about Oxygen Builder plugin and WordPress
18 Comments
  1. Joel says

    here is the link to Dennis’ post from 2019: https://www.facebook.com/groups/1626639680763454/posts/2182359145191502/

  2. Mikel says

    First get good building a site with underscores and alike, then proceed to roots sage

  3. Dennis says

    What a blast from the past Joel Burrows!
    It’s actually quite interesting reading this post from now around 2 years ago.

    Not much has changed for me to be honest, I do a lot of work nowadays using Next.js, but WordPress is just always a solid bet.

    Timber is still THE shit! My whole plugin business Frontend is basically run off a single plugin folder that houses my own Twig/Tailwind framework that I use to build out new sites or expand existing ones. I don’t think you can get anywhere close to that extensibility with any pagebuilder.
    Such a system is great if you are the only one editing content or the rest of the team is versed in using Git.

    For client sites, I fully shifted to ACF Blocks/Gutenberg. It literally is the dream combo I tried to build myself so many times before. Being able to write Blocks using PHP while giving clients the possibility to edit content AS THEY SEE IT on the website without any extra work is just a dream workflow for me.

  4. Robby says

    I am a full stack developer and I develop websites/web apps from scratch from time to time, without WordPress. But since I learned about how WordPress can be easily customized using appropriate tools like Oxygen + custom field plugins etc, it makes my life easier. I can build websites faster. Thus it increases my productivity. But it doesn’t mean I stop coding websites from scratch. It really depends on the complexity of each project. If it can be done with WordPress plus Oxygen++, then I’ll go with it. Otherwise, I’ll just build it from scratch where I can do stuff with more flexibility.

  5. Corey says

    I used to build all sites with custom themes. I gave that up and moved to Oxygen… 🤷‍♂️

  6. Ryan says

    Time is money. Depends on the customers budget. But why not just export the site in html then if you need WordPress convert it into a theme with pine grow? I’ve been doing this to prevent sites breaking since the last elementor fiasco.

  7. Jeremy says

    As a company we have to be careful about the amount of time we put in, while keeping quality top tier.

    So consider the goal, and your needs, and if it’s for a client or yourself. Then use the path/tool that suits the job.

  8. Martin says

    Too heavy for the actual state of my brain BUT following.

  9. Adam says

    it’s time for you to add some new tools for new level of clients. have a look on nx.dev, keystonejs or plasmic.app. wordpress projects still occupy my 80% total projects.

  10. Pedro says

    You could build your own custom classes and design frameworks overtime and reuse them on every project? 🤔 or maybe I’m misunderstanding the discussion.

  11. Zbynek says

    Hypothetically, a client will come to you and ask for a project price valuation. You give him imaginary price “$ 3000” for awebasite based on your framework. Suddenly silence … why? Because they sent up to 5 other website creators and they agreed to $ 1,500 for the same website. By doing your original projects you eliminate “non rich” customers with “normal/simple pages” non special websites. Your customers may not know your code, but they do one thing better than you do: “Count your own money”. For me, doing a simple project, e.g. in some php framework is simply immoral … seriously immoral … it’s kind of a scam

  12. Philip says

    Joel Burrows Are you me? Really looking forward to the responses this gets.

  13. David says

    I’m probably one of the odd ones in the group. I hate most page builders.

    I’m in this group because I recently bought oxygen to play around with, mainly because I want to use it for small personal sites and I hate DIVI/Elementor.

    At the agency I work for, we have an entire team for design, UX, front-end, and back-end. Every client we have has a budget of anywhere from $50-400k USD so we’re always doing a custom built theme because it’s expected with the budget.

    Lately we’ve been doing custom themes with ACF gutenberg blocks and it has worked out really well. We’ve also done a few sites that generate a static site. We’ve played around with gatsby but are soon going to start looking into other headless options for when the time is right to use headless.. so far we haven’t had the need.

    I’d also like to try blade/twig but haven’t had the time to dig into it, but I know a lot of folks love templating engines!

  14. Vicki says

    Most sites I build are custom coded. I use Timber as I really like having the twig template files being clean without php. I also use ACF custom Gutenberg blocks. I use stout logic to make creating the ACF blocks in PHP easier (I have a bunch of files for different blocks that I can just copy into the current theme)

  15. Nils says

    Custom coded is the only way for me. I’ve been testing builders but always gotten back to the custom way. I created my own, very basic, theme which have some resemblance to an MVC framework. Even tho I like blade I haven’t utilized it in my wp projects, simply because it’s harder to train people using it.

    Someone saying it’s immoral to use code when there is builders, to me; that’s just a narrow vision of the world of web dev, so don’t worry about that.

    I mostly work with creative agencies that wants a custom design for their client, usually some custom functionality as well. They don’t want anything to do with builders, like at all.

    I’m using acf and Gutenberg blocks to create easy to edit blocks that simply has fields and forms. So the end user can’t really break the design.

  16. Javier says

    Same feeling…. I was trying for a while to create a boilerplate theme structure to deliver a custom plugin for websites using a relational database (separate DB from WP database) which for me was my main gap. Finally abandon this approach due to complexity, I wanted something easy and cheap…now happy with the combo Oxygen, Pods and PiotnetGrid, I can define a relational model and present it in the fronted, including navigating relations between the pods via PHP custom functions, but still exploring other options.

  17. Laurent says

    Joel do you know lazy blocks plugin ? It use twig if I remember

  18. Ronny says

    We are in the business for a while now and started with hard HTML sites. A while ago 😅

    Which tool you use to deliver a new website is not a customers decision. My experience was, it’s a personal favorite or type of idealism of the web dev. What he’s more comfortable with.

    The typical customer wants a personal design, a perfect UI / UX and good rankings. And >90% wants a site that is editable by a monkey after launch 😉

    I’m a full stack dev and would never look back to hard code typical websites, that make 95% of business. With oxygen it’s faster and gives us more winnings at the end. We are an agency and have to look at that point, because we have to “feed” our workers 😉 The customer gets a perfect looking and technically state of the art website, that’s editable at Frontend. Backend stays untouched.

    Stack:
    Oxygen, Automatic.css, ACF, some little helper plugins.

Leave A Reply

Your email address will not be published.

Oxyrealm Docs OxyMade - Oxygen Builder Design Set Mega collection