
Sign up to save your podcasts
Or


Matt Medeiros finishes Season 8 with this interview of Robby Mccullough, who is a co-founder of the Beaver Builder page builder and is from the Bay area. Matt and Robby discuss how the Gutenberg release in WordPress 5.0 may impact Beaver Builder, whether Automattic could have looked at purchasing Beaver Builder, and how a small business owner deals with the ups and downs of running and growing a remote business. Listen to the end of the episode to find out the original name consideration of the Beaver Builder theme.
Download file | Play in new window | Duration: 00:56:05
What you will learn in this Episode:
Future of WordPress with Gutenberg changes:
Robby – Realizes that it is impossible to predict the future of WordPress. He supports the Gutenberg editor with the block approach to the editing experience. The Beaver Builder page builder was created because of the demand in the WordPress space where the need for faster and easier website building was not being met. There was a real concern of what would happen to Beaver Builder once Gutenberg launched. (1:46)
Matt – Asks the question of whether Beaver Builder could have been bought by Automattic. (3:22)
Robby – Explains that the discussion of the purchase of Beaver Builder by Automattic never came up. (3:40)
The vision of the Gutenberg editor in the latest update of WordPress did not line up with how Robby sees Beaver Builder growing with the community. (6:00)
Matt – The innovators of WordPress (people who have created and supported page builders) have come from third-party developers. (6:47)
Robby – Beaver Builder has been in the problem-solving space. Big companies can absorb smaller companies but this was not to be with Automattic and a page builder. (9:15)
Software creators with SaaS and WordPress:
By Matt Report & Matt Medeiros4.9
133133 ratings
Matt Medeiros finishes Season 8 with this interview of Robby Mccullough, who is a co-founder of the Beaver Builder page builder and is from the Bay area. Matt and Robby discuss how the Gutenberg release in WordPress 5.0 may impact Beaver Builder, whether Automattic could have looked at purchasing Beaver Builder, and how a small business owner deals with the ups and downs of running and growing a remote business. Listen to the end of the episode to find out the original name consideration of the Beaver Builder theme.
Download file | Play in new window | Duration: 00:56:05
What you will learn in this Episode:
Future of WordPress with Gutenberg changes:
Robby – Realizes that it is impossible to predict the future of WordPress. He supports the Gutenberg editor with the block approach to the editing experience. The Beaver Builder page builder was created because of the demand in the WordPress space where the need for faster and easier website building was not being met. There was a real concern of what would happen to Beaver Builder once Gutenberg launched. (1:46)
Matt – Asks the question of whether Beaver Builder could have been bought by Automattic. (3:22)
Robby – Explains that the discussion of the purchase of Beaver Builder by Automattic never came up. (3:40)
The vision of the Gutenberg editor in the latest update of WordPress did not line up with how Robby sees Beaver Builder growing with the community. (6:00)
Matt – The innovators of WordPress (people who have created and supported page builders) have come from third-party developers. (6:47)
Robby – Beaver Builder has been in the problem-solving space. Big companies can absorb smaller companies but this was not to be with Automattic and a page builder. (9:15)
Software creators with SaaS and WordPress:

32,246 Listeners

229,674 Listeners

30,609 Listeners

71 Listeners

25 Listeners

113,121 Listeners

8,876 Listeners

107 Listeners

10,254 Listeners

1 Listeners

1 Listeners

0 Listeners

1 Listeners

0 Listeners

2 Listeners