- This topic has 6 replies, 4 voices, and was last updated 3 years, 3 months ago by Paul.
May 14, 2018 at 2:49 am #574969BenMay 14, 2018 at 3:00 am #574974DavidStaffCustomer SupportMay 14, 2018 at 3:11 am #574979Ben
Cool, thanks. As you can tell, I’m still finding my way around GP! 🙂May 14, 2018 at 3:24 am #574986DavidStaffCustomer SupportMay 26, 2018 at 11:04 am #585262Paul
I found this topic while researching Aspire. I wanted to find out if anything would break in the event EP wasn’t used. Now I know.
As a recommendation, I’d love for all the GP Sites demo sites to specify which sections or features within their pages require paid versions of Elementor or Beaver Builder. “Head On” by Flint Skin does a really good job similar to this in their How To page (even though it doesn’t require a page builder). I think every one of the GP Sites should have a page that spells out what the dependencies are for various sections of their pages. I think this would help many users avoid needing to ask questions in the GP support forum when something in the theme breaks.
Also it would be great for these sites to use a lighter-weight form plugin such as Simple Basic Contact Form that doesn’t load its scripts on pages that don’t contain the forms since GP’s goal is to be lightweight and fast.
Overall, the GP Sites are great and very helpful. Thank you!May 26, 2018 at 9:24 pm #585435TomLead DeveloperLead Developer
I agree – that would be super helpful. I’ll work on that 🙂
Hadn’t heard of Simple Basic Contact Form – looks really interesting! I’ll look into it.May 26, 2018 at 11:48 pm #585453Paul
Even little icons or tags on the GP Sites main page next to the title of each theme would work. Getting each theme to spell out exactly where specific dependencies lie on each page would be even more helpful, but I realize that’s a lot more work.
Yeah, been hearing really good things about Simple Basic Contact Form lately and how lightweight it is.
- You must be logged in to reply to this topic.