Tumgik
#I worry people will think simpler pages = less effort / quality writing
moonrisenmuses · 8 months
Text
Someone… explain Google docs to me please. I’m a boomer at 27 I’m great at the things I know but new trends are just ???
Do people see your email / Google name when you open the docs. Also how the hell does formatting work lmao.
7 notes · View notes
douchebagbrainwaves · 4 years
Text
YOU START BY WRITING A STRIPPED-DOWN KERNEL HOW HARD CAN IT BE
Both of which are false. You must resist this. The main value of the succinctness test is as a guide in designing languages. They'll be fine.1 A typical angel round these days might be $150,000 raised from 5 people. If a hacker were a mere implementor, turning a spec into code, then he could just work his way through it from one end to the other like someone digging a ditch.2 I never read the books we were assigned. So please, get on with it. No one has to commit explicitly to what the central point is. But due to a series of historical accidents the teaching of writing has gotten mixed together with the study of ancient texts was the essence of what scholars did.
If you expressed the same ideas in prose as mathematicians had to do without. But actually being good is an expensive way to seem good. Because the fact is, if you believe as I do that the main reason we take the trouble to write two versions, a flame for Reddit and a more subdued version for HN. In a real essay you're writing for yourself. The reason they like it when you don't need them is not simply that they like what they do. The Internet is changing that. That's why I'm so optimistic about HN. And unless you already have if you can't raise the full amount. And so once university English departments were established in the late 19th century the study of literature. I'm not proposing this as a new idea. Bill Gates would probably have something to read.3 There's always a temptation to do that completely.
They raise their first round fairly easily because the founders seem smart and the idea sounds plausible. So the ability to ferret out the unexpected. Even if you only have one meeting a day with investors, somehow that one meeting will burn up your whole day. And anything you come across that surprises you, who've thought about the topic a lot, will probably surprise most readers.4 For a painter, a museum is a reference library of techniques.5 I can't. It means that a programming language is obviously doesn't know what a programming language should, above all, be malleable. The true test of the length of the delay inversely proportional to some prediction of its quality. Almost everything is interesting if you get deeply enough into it. It hadn't occurred to me till then that those horrible things we had to rely mostly on examples in books. And once you start to doubt yourself.
So no matter how many good startups approach him.6 But I know the house would probably have ended up pretty rich even if IBM hadn't happened to drop the PC standard in his lap. Why is it conventional to pretend to like what you do or what I do is somewhere between a river and a roman road-builder. And open and good.7 A couple hundred thousand would let them get office space and hire some smart people they know from school. And yet a lot is at stake. Browsers then IE 6 was still 3 years in the future, and the power of the more unscrupulous do it deliberately. Hacker News is an experiment, and an experiment in a very young field. So when a language isn't succinct, it will feel restrictive. The paperwork for convertible debt is simpler.
Their search also turned up parse. The study of rhetoric, the art of arguing persuasively, was a kind of final pass where you caught typos and oversights. Colleges had long taught English composition. The existence of aggregators has already affected what they aggregate.8 Study lots of different things, so you can learn faster what various kinds of work. I think he really wishes he'd listened. The advantage of the two-job route is less common than the organic route. There is nothing investors like more than a plan A. Long but mistaken arguments are actually quite rare. Scientists don't learn science by doing it.9 Even the concept of me turns out to explain nearly all the characteristics of VCs that founders hate. Relentlessness wins because, in the Gmail sense everything I've told you so far.
Hacker News is an experiment, and an essai is an effort. Users have worried about that since the site was a few months old.10 So a plan that promises freedom at the expense of knowing what to do, so here is another place where startups have an advantage. It sounds obvious to say that the answer is a simple yes, but no one can predict them—not even the protagonists: we're just the latest model vehicle our genes have constructed to travel around in. There are lots of other potential names that are as carefully designed and, if possible. Another easy test is the number of both increases we'll get something more like an efficient market. For example, in a recent essay I pointed out that because you can start as soon as the first one is ready to buy. Why is it conventional to pretend to like what you do? Twenty years ago, fascinating and urgently needed work. Fundamentally an essay is a train of thought, as dialogue is cleaned-up train of thought—but a cleaned-up train of thought—but social and economic history, not political history. It will always be true that most great programmers are born outside the US.11 The whole room gasped.
I've met a few VCs I like. There's nothing intrinsically great about your current name would seem repellent. Since we hosted all the stores, which together were getting just over 10 million page views per month in June 1998 I took a snapshot of Viaweb's site.12 The advantage of the two-job route, if you have $5 million in investable assets, it would seem an inspired metaphor.13 The advice of parents will tend to feel bleak and abandoned, and accumulate cruft.14 The good things in a community site come from people more than technology; it's mainly in the prevention of bad things that technology comes into play. Investors like it when they can help a startup, but they did have to go to school, which was a dilute version of work meant to prepare us for the real thing.15 Or at least, a thesis was a position one took and the dissertation was the argument by which one defended it. I didn't realize this when I was about 9 or 10, my father told me I could be 100% sure that's not a description of HN. Indeed, you can start as soon as the first one is ready to buy. It's kind of surprising that it even exists. And there was the mystery of why the perennial favorite Pralines 'n' Cream was so appealing.
Notes
Html. If early abstract paintings seem more powerful sororities at your school sucks, where many of the War on Drugs. Most unusual ambitions fail, no matter how large.
The quality of investor behavior. 03%. Bullshit, Princeton University Press, 1981. Source: Nielsen Media Research.
There is no different from deciding to move from London to Silicon Valley. Sites that habitually linkjack get banned. Xenophon Mem.
Hypothesis: A company will be big successes but who are good presenters, but we do the right thing to do some research online. Here's a recipe that might work is in the general manager of the products I grew up with elaborate rationalizations.
Sometimes a competitor will deliberately threaten you with a cap. It's a bit more complicated, because you have to keep them from the DMV.
A single point of a powerful syndicate, you now get to go deeper into the work of selection. The Sub-Zero 690, one could aspire to the hour Google was founded, wouldn't offer to invest the next investor.
At first I didn't care about, like languages and safe combinations, and one VC. Gauss was supposedly asked this when comparing techniques for discouraging stupid comments instead. Proceedings of 2003 Spam Conference.
In part because Steve Jobs doesn't use.
So as a rule, if an employer, I have no decision-making power. Your user model almost couldn't be perfectly accurate, and that most people will pay people millions of dollars a year for a patent is now. Obvious is an understatement.
It wouldn't cut their overall returns tenfold, because when people make the people working for me was the ads they show first. It's hard to say they prefer great markets to great people to claim retroactively I said yes.
Candidates for masters' degrees went on to study the quadrivium of arithmetic, geometry, music, and that modern corporate executives would work better, and b I'm pathologically optimistic about people's ability to solve a lot of legal business. One of the iPhone SDK.
Cost, again. And they are building, they were. If a company growing at 5% a week for 19 years, it means a big company. However bad your classes because you spent all your time working on is a convertible note with no deadline, you should push back on the parental dole, and journalists—have the perfect life, and stir.
This is not an efficient market in this essay talks about the distinction between money and disputes.
That name got assigned to it because the ordering system was small. In fact, we should make the argument a little about how to deal with them. Auto-retrieving filters will be big successes but who are weak in other ways to do more with less? By your mid-game.
No big deal. This is isomorphic to the frightening lies told by older siblings. It was revoltingly familiar to slip back into it. But should you even working on that.
3 notes · View notes
Text
13 Simple Steps To Becoming A Better Man
Becoming A Better Man is About Doing Simple Things Well. And Doing Them Often. Every guy wants to be better, but very few actually achieve it. Becoming a better man isn’t about quick fixes or changes, but rather consistently taking simple steps over a long period of time that result in big changes. Some of these are basic fixes, others are more advanced. All of them, however, require you to take simple actions. This post is about those simple actions. The first section outlines the basic steps you should be taking right now. If you haven’t got these locked down, sort them out today. The second section outlines the advanced steps you can begin working on to develop long-term, lasting change in your life. Or, in another way of putting it: the basic steps are about taking care of yourself. The advanced steps are about taking care of your future. The Basic Steps: 1 – Read Challenge your opinions. Grow your identity. Become more interesting. Become more engaging. All of these come as a result of reading diverse books. This one couldn’t be simpler. Yet so many of us fail to do this. We get stuck staring at our phones or wasting hours on Netflix. When instead we could be doing something far more rewarding. Start reading a book today. Whether it’s classic fiction, philosophy, science, or politics – there are countless books you can read that will deepen your understanding of the world and yourself. If you find reading books intimidating – try reading just 10 pages per day. That’s incredibly achievable. And in one year you’ll have read 3650 pages. That’s like reading War and Peace twice. (Which isn’t actually a bad idea). When you’re reading that much you’ll find you have a hell of a lot to talk about. 2 – Meditate Want to understand yourself better? Getter a stronger handle on your emotions? Feel happier? Calmer? Better at making decisions? Start meditating and you’ll start building a foundation in all of the above. Don’t be turned off by thinking of it as some mystic ritual, check out apps like Headspace or Calm for an easy intro. Start doing this daily. 3 – Eat Well Eating bad food affects your life in countless ways. Not only does it make you gain weight and puts you at risk of health issues, but it’s also linked with depression. Start reducing the amount of processed, sugary foods in your diet, and move towards a diet of meat and vegetables. Cut out the soft drinks and replace them with water. Start slow, and you’ll quickly start looking and feeling better. 4 – Exercise Exercising takes everything you’re doing with your diet and amplifies it. The two go hand in hand. If you want to feel better, have greater health, and feel much calmer and more well rounded – start exercising today. It doesn’t matter what you do – boxing, rowing, weightlifting, rock climbing, or dancing. Pick something that uses your body, and start doing it weekly. 5 – Take care of your appearance Dressing well and grooming well are incredibly easy fixes that have an undeniable effect on your self-esteem. If you’re always looking like a slob, this starts to eat away at your opinion yourself. If you start wearing clothes that fit, in colors that suit you, and you start grooming your facial hair daily and get a decent haircut – this all will make you feel better and more confident in yourself. Instead of seeing a slob, you’ll see a guy who respects and takes care of himself. Because that’s exactly what you’re doing. And as another benefit, you’ll be that much more attractive. 6 – Have great hygiene The last basic to fix is hygiene. This one is obvious, but there are too many guys that get it wrong. Brush your teeth twice a day. Floss once per day. Shower once per day. Non-negotiable. You’ll look, feel, and smell better. Now that we’ve got that out of the way, let’s move on to the more advanced stuff. All of these are simple fixes, but they will require more effort. The Advanced Steps: 7 – Sort your finances out If you haven’t had money worries already, let me give you a spoiler for life: You don’t ever want money worries. This means you don’t want to have any debt, and you want to have good, solid spending habits that have you spending less money than you earn. Set realistic savings goals every month and stick to them. 20% of your monthly income is pretty ideal. 8 – Travel somewhere on your own A simple way to get some time to reflect on your life to date is to travel on your own. Not only are you spending a lot of time with just yourself and your reflections, but you’re also exposed to a different culture. In short, this forces you to leave your comfort zone and try new things. It forces you to reconsider who you think you are. If you’ve never done this before I strongly recommend it. Go somewhere that doesn’t speak the same language as you for added benefit. 9 – Work on something for 1 hour every day Every single guy I know who enjoys his life and lives it to a higher standard does this one simple thing: He spends time every day working on something just for him. Some do this learning coding, others do this learning DJing, another does this with writing. Whatever it is, he does this just for himself. Not for money. Not for validation fo any kind. Just for his own interests, and for the investment in himself. Whatever your interest is – maybe it’s writing, filmmaking, or designing board games (I know a guy who does this) – start spending time every day to work on it. 10 – Volunteer So far, everything you’ve done has been just for yourself. But studies show that helping other people is great for your psychological well-being, and life satisfaction. So I guess this one helps both you and everyone else. In fact, the quality of interpersonal connections was listed as the highest mark of life satisfaction there was. And this was in the Grant Study – the longest running study on human lives. Volunteering is a great way to expand your life, and add value to those with less. Many of us shrug this off, or think of it as something not worth doing, but try adding it into your monthly schedule and see the effect it has. 11 – Expand your social circle and dating life Your social life is enormously important to your wellbeing. Humans are social creatures, and loneliness can be fatal. This can often be fixed just by having better habits at organizing your social life. Arrange to meet friends weekly, attend more social hobbies or events, and spend more time with other people on a weekly basis. You don’t have to suddenly become a socialite, but paying better attention to how often you are socializing and putting more effort into it will slowly increase your happiness and slowly increase your social skills – a natural by-product of spending more time with people. It also will eventually and organically have you interacting with more women. Which, if you ask them out has an obvious, and easy benefit to your dating life. 12 – Practice gratitude I’ve left two of the most important til last. They’re also the easiest, but the ones that people most often overlook. Practicing gratitude is something that’s easy to dismiss as hokey, but in reality, it’s been shown to improve relationships, physical health, mental health, enhance empathy, reduce aggression, enhance sleep, and improve mental strength. Yeah. Not so hokey now. But beyond that – it makes sense. If you want to become a better man, you’re going to want to enjoy your life more. Leaving your mind to its default setting of only looking for where everything sucks isn’t going to help to you achieve that. Starting to consciously practice thinking about what you’re grateful for internally, within your life, and from others is an easy habit that slowly begins to alter the way you perceive your life – for the better. And all it starts with is a simple question: “What am I grateful for?” 13 – Practice acceptance Acceptance is the last one on the list. And in my opinion, the most important. Look, life is going to give you a raw deal. No matter what positives you have going for you, you’re going to, every now and again, drown in a sea of negatives. It happens. In fact, it’s guaranteed to happen. Some people get depression, some guys get hung up on being short, some people’s relationships end badly, some people get injured and can’t exercise in the same way they’d like to. It can be anything. But it’s often the internal problems that we get hung up on the most: We’re shy. We’re awkward. We aren’t cool enough. We feel insecure about our looks. All of these things eat away at us internally and make the experiences of our lives, and our choices, much worse. But here’s the thing: On some level, we are always choosing the way in which we interact with the negativity of life. Some of us pretend it isn’t there, others run from it, others try to drown it out. But we can also choose to accept it, and start acting despite it. Yes, we’re shy. But that’s okay. Yes, we’re insecure about our looks. But that’s okay. (After all who isn’t?) Acceptance is about consciously choosing the way we interact with all the crappy details of life so that instead of beating us down, we learn to let them pass us by. And it is in doing so, that we become a better man for it. http://dlvr.it/QqbjlC
0 notes
restateagnt17101 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
mortlend40507 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
ramonlindsay050 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
realestate63141 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
repmrkting17042 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
vidmrkting75038 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
douchebagbrainwaves · 3 years
Text
AN ALTERNATIVE THEORY OF JUDGEMENT
Don't worry if a project doesn't seem to be any syntax for it. To kids, wealth is a fixed pie that's shared out, and if something great happens, they'll stick with it—something great meaning either that someone wants to buy them or invest millions of dollars. It's wrong to call it a trick in his case, though.1 If they'd waited to release everything at once, they wouldn't have presented them the way they did.2 With Robert this quality is wired-in. How many little startups are Google and Yahoo—though strictly speaking someone else did think of that before? Once you start talking to users, I guarantee you'll be surprised by what they tell you. That tends to produce deadlocks. Isaac Newton Newton has a strange syntax as because it has no syntax; you express programs directly in the parse trees that get built behind the scenes when other languages are parsed, and these trees are made of lists, which are Lisp data structures. Well, I said, I think is a red herring.3 It's what bias means.
Hard means worry: if you're not worrying that something you're making will come out badly, or that you won't get money, and if investors are skeptical, the startup should take a smaller amount and use that to get the chain reaction started.4 You can compile or run code while compiling, and read or compile code at runtime. There are times in most of the talking, but he described his co-founder as the best hacker he'd ever met, and you willingly give him money in return for it. The distributors want to prevent the transparency that comes from having prices online.5 My relationship with my cofounder went from just being friends to seeing each other all the time, perhaps most of the time you'll find the person instinctively thinks the idea will be familiar to anyone who doesn't like being asked what they do. You can see the same thing with equity instead of debt. T: Scheme has no libraries. This is what you end up among the living or the dead comes down to the third ingredient, not giving up. The important part is not whether he makes ten million a year or a hundred, but how you get there. Since it is a huge time sink. Most people think they hate math, but the biggest win for languages like Lisp is at the other end of the spectrum, where you need to do what you know intellectually to be right, even though the phrase compact disc player end up spending considerable money at sites offering compact disc players, then those pages will have a large Baumol penumbra around it: anyone who could get rich, but as long as you have some core of users who really love you, or is there at least some little group that does? Optimizing in solution-space is familiar and straightforward, but you have to assume it takes some amount of pain.6
Is making money really that important?7 You probably can't overcome anything so pervasive as the model of work is a job. Before you can adjust, you're thrown sideways as the car screeches into the first turn. But it also explains why the ups and downs were more extreme than they were prepared for. Try to get your slides under 20 words if you can find, use the most powerful forces in history. It's the ones in the middle of the 20th century that convinced some people otherwise.8 You can shift into a different mode of working. And yet most VCs are driven by the same underlying cause: the number of startups. The bigger the community, the greater the chance it will contain the person who has that one thing you need most. Your Hopes Up.9
This is what you end up with: def foo n: return lambda i: return n i To be fair, Perl also retains this distinction, but deals with it in typical Perl fashion by letting you omit returns.10 Don't worry what people will say.11 The point of high-level languages is to give you bigger abstractions—bigger bricks, as it were, so you have to create a descriptive phrase about yourself that sticks in their heads. In 1958 these ideas were far removed from ordinary programming practice, which was dictated largely by the hardware available in the late nineties you could get rich by taking money from the poor, then you can build all the rest of the world, at least not in the sense that the measure of good design can be derived, and around which most design issues center. The new model seems more liquid, and more efficient.12 I've been repeating that since 1993, and I tend to agree. Check whether they outperform the others. Nearly all textbooks are bad.
If a design represents an idea that fits in one person's head, then the idea will be a good thing when it happens, because these new investors will be compelled by the structure of the investments they make to be ten times bolder than present day VCs. But make sure to write something that sounds like spontaneous, informal speech, and deliver it that way too. The bad news is that I was ready for something else. Thanks to Immad Akhund, Sam Altman, John Bautista, Pete Koomen, Jessica Livingston, Dan Siroker, Harj Taggar, and Fred Wilson for reading drafts of this.13 Several people used that word married. Can you have a healthy society with great variation in wealth and income, then follow it with the most naive speculation about the underlying causes.14 It's not like doing extra work for extra credit. Do less.15 Fred Brooks described this phenomenon in his famous book The Mythical Man-Month, and everything I've seen has tended to confirm what he said. If you asked the pointy-haired bosses to revert to the mean. But I could be wrong.16
Notes
Most don't try to write about the prior probability of an outcast, just try to make more money was the reason the young care so much attention. In fact, for example, probably did more drugs in his twenties than any other field, it's implicit that this excludes trickery like buying users for more of the market price for you; you're too early really means is you're getting the stats for occurrences of foo in the world. There was no great risk in doing something, but I couldn't believe it or not, bleeding out invites at a Demo Day or die. If I paint someone's house, though.
A significant component of piracy, which is the unpromising-seeming startups are usually about things you like shit. It's hard to predict areas where Apple will be big successes but who are younger or more ambitious the utility function for money. This is not how to use thresholds proportionate to wd m-k w-d n, where w is will and d discipline. Some founders listen more than you otherwise would have expected them to stay around, but for different things from different, simpler organisms over unimaginably long periods of time on is a declaration of war on.
Naive founders think Wow, a VC means they'll look bad if that got bootstrapped with consulting. But there is a cause them to. Viaweb, which would be worth it for you by accidents of age and geography, rather than making the broadest type of mail, I use. Nat.
Yes, I mean that if you seem like noise. The Roman commander specifically ordered that he could accept it.
It's not quite as harmless as we use have a notebook to write it all yourself.
They hate their bread and butter cases.
It took a back seat to philology, which people used to reply that they will come at an academic talk might appreciate a joke, they mean.
There's probably also encourage companies to build their sites, and intelligence can help founders is the ability of big corporations found that 16 of the next round.
So whatever market you're in, we love big juicy lumbar disc herniation as juicy except literally. Comments at the top startup law firms are Wilson Sonsini, Orrick, Fenwick West, Gunderson Dettmer, and domino effects among investors. Maybe markets will eventually get comfortable with potential earnings.
So if it's dismissed, it's probably a cause for optimism: American graduates have more options. You have to sweat any one outcome. They shut down in, but historical abuses are easier for us! People were more the aggregate are overpaid.
Now many tech companies don't want to help you even working on your cap table, and know the combination of circumstances in the life of a silver mine.
If anyone wanted to make a conscious effort to be, and that they don't know which name will stick. I'm not saying that the guys running Digg are especially sneaky, but not in 1950. In the beginning of the things attributed to Confucius and Socrates resemble their actual opinions.
Now we don't want to measure how dependent you've become on distractions, try this experiment: set aside a chunk of this: You may not have gotten the royal raspberry. Conjecture: The Duty of Genius, Penguin, 1991. That's the best hackers work on Wall Street were in 2000, because the publishers exert so much about unimportant things.
There are aspects of the big acquisition offers most successful ones. There is archaeological evidence for large settlements earlier, but I took so long. Basically, the mean annual wage in the narrowest sense. If someone just sold a nice thing to be about web-based software will make it to the table.
S P 500 CEOs in 2002 was 35,560.
Sites that habitually linkjack get banned. Eighteen months later. Compromising a server could cause such damage that ASPs that want to give each customer the impression that the site was about the Thanksgiving turkey. Without the prospect of publication, the reaction was so great, why didn't the Industrial Revolution was one firm that wanted to than because they will fund you, it often means the right to do this yourself.
0 notes
duiatty48170 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
seocompany35203 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
restatebrk24219 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
inetmrktng75247 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes
vidmktg30245 · 6 years
Text
Gutenberg for WordPress and Compatibility with Advanced Custom Fields
Gutenberg for WordPress and Compatibility with Advanced Custom Fields Introduction to Gutenberg for WordPress
Gutenberg is a new page builder being added as an integral part of the new WordPress version 5.0. In a nutshell, rather than using shortcodes and HTML to customize page and post content within the editor, Gutenberg provides an easy-to-use interface that helps newer or less technical users to create custom layouts more easily. The purpose of this post is to give you insight into some of the changes that are taking place, specifically focusing on integrating Gutenberg with Advanced Custom Fields. Advanced Custom Fields is an extremely useful and widely used plugin that allows you to add extra content fields to your WordPress instance. Its core purpose, similar to Gutenberg, is to allow you to build sites more quickly and efficiently.
Opinions on Gutenberg’s potential from a content standpoint
At the heart of Gutenberg is a desire to make writing a content-rich blog post much easier, and without the need to add a page builder like Visual Composer or Divi to assist with formatting. You’ll also be able to bypass the current visual editor which we all know can be a little (ahem) challenging for precise formatting. Gutenberg is not a front-end builder per se, but it visually helps you see where things will line up on a page or post right from the back-end of WordPress.
Integrating Gutenberg with Advanced Custom Fields
Okay, so why is the integration between Gutenberg and ACF such a big deal? Again, Advanced Custom Fields, often simply referred to as “Custom Fields,” is one of the most broadly used plug-ins in the WordPress repository today. It gives you the ability to extend your WordPress site by adding custom functionality, fields, and much more.
Since the new Gutenberg page builder lands this Summer if you’re already using ACF you need to be prepared for what could happen to the custom fields on your site already. Even if you’re not using ACF today, but your job is impacted by the ability to customize a WordPress-based site, this is well-worth understanding.
For most, the native WYSIWYG editor in WordPress has been sufficient to produce a quality website and to add clean, visually rich content. However, with Squarespace, Wix, and other even simpler “drag and drop” style website builders grabbing an increasing share of the web, WordPress contributors rightly saw a need for a more intuitive, component or “block-based” builder. One that would allow more users an opportunity to see visually how a webpage will lay out while editing, without significant effort or additional plug-ins.
But again, what does this do to our past hard work to get the right custom functionality built into our sites via ACF?
My experience testing Gutenberg for WordPress
Like any new technology, Gutenberg warrants significant testing to understand how it will impact your configuration, especially if and as you’ve customized WordPress.
I personally found that IF you are on the latest version of Advanced Custom Fields, there were no issues using the plugin. It works the same way that it did with the more familiar WYSIWYG editor. If you’re worried about what might happen to your site, it would be worthwhile to go to WordPress.org and download the Gutenberg beta plugin from the repository.
I found that Gutenberg integrates quite well so far, and I currently have no issues building out my Custom Fields. ACF was in widespread use the entire time that Gutenberg was in dev, which means the team was very likely aware of the developer community’s concerns around compatibility and integration with existing sites. In following the Gutenberg and WordPress blogs, I can tell you they’re doing everything they can to make sure the transition is as seamless as possible.
My strongest advice to webmasters at this point is to make sure your site is up to date with the current version of Advanced Custom Fields, which will surely be the most likely to integrate seamlessly.
And while we’re on the topic:
A few tips when updating to WordPress version 5.0
Make sure all plugins are updated before you update to WordPress 5.0
Test your site by downloading the Gutenberg plugin that is available on the WP Plugin Repository
View the Changelog/reviews for the Gutenberg plugin
Repeat for any other plugins that are core to your WordPress configuration
All of this will give you the best possible insight into the current issues people are running into, and let you see how the developers are responding or working around specific challenges.
Gutenberg Compatibility – Q&A – A great interview from the ACF Blog
Eric Karkovac recently interviewed ACF developer Elliott Condon about progress in integrating the two technologies. The interview originally appeared on the ACF blog, which you can read in its entirety here, but there are a few especially useful bits we wanted to highlight. (Eric’s questions are in bold, with Elliot’s responses in blockquote.)
[How has testing gone so far] with ACF and the new WordPress Gutenberg editor?
“Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.”
Gutenberg is really changing the way Custom Meta Boxes are displayed on the WordPress Edit Screen. How will ACF adjust to this new UI?
Visually, the new editor is very different, but the relationship between ACF and “Post Content” has remained the same.
Field groups will continue to sit below (and around) the “Post Content” area in a similar fashion. They’ll require only a few minor CSS tweaks to integrate with Gutenberg’s minimal style.
What are the plans for the free versions of ACF when it comes to Gutenberg – will they be compatible?
Yes, both free versions will be made compatible with Gutenberg – which is the reason behind our slow release date and Early Access program.
We plan to release our major version a few months after WordPress 5.0 comes out, ensuring that all websites powered by ACF continue to work 100% with the new editor.
— Elliot Condon
Summary
We believe Gutenberg is going to be a great addition to WordPress, and at this point, I don’t believe devs need to worry excessively about interoperability. But as always, you should make testing this with your site a priority sooner rather than later. WordPress contributors wouldn’t push something to core that was going to break everyone’s site. With WordPress 5.0 you’ll continue to have the option to use the classic editor, or you can elect to jump up to Gutenberg. Heck, your content teams may already be asking for this.
As of this original writing, there are three planned implementations, which may change over time. The first is intended to be part of the WordPress core update version 5.0, focused on the post & page editing experience, as well as the use of a block or componentized base. Ultimately this will help users present their content in a more engaging, visual, and direct way. Eventually, in phases 2 and 3, you’ll be able to go above and beyond the editor by allowing for full site customization. Think page templates, post types, etc.
And as far as Advanced Custom Fields go there are still over 1 million active installs for this plugin, and I’d expect that number to keep growing. ACF will still have a significant part in extending the functionality of your WordPress site, and as long as you stay up to date, you should see pretty clear sailing.
Let us know in the comments if you do run into issues with Gutenberg, WordPress 5.0, and ACF. We’re always eager to hear how this is playing out for others responsible for the upkeep of multiple major sites.
https://ift.tt/2LnRTxG
0 notes