Should I use a page builder for creating content?

[tuongpg]

I have plan to build my website. I do not know php code much.
My friend suggest me use a page builder for content creating.
Should I use that? Do they make website slow?
I found some one in wordpress.org
Beaver
KingComposer

[edited by: travelin_cat at 2:05 pm (utc) on Nov 2, 2016]
[edit reason] Removed Links [/edit]

[travelin cat]

tuongpg,
I've been using a page builder for a long time, however it's not one of the ones you mentioned.

I have never noticed any speed slow down and it saves a tremendous amount of time constructing a site.

[DavidWP]

This post is a little old, so not sure if you still need a reply, but Beaver Builder is arguably the best out there. The one thing I would recommend though would be to watch the titles. Sometimes page builders will have DIY elements that misalign your H tag assignment (e.g. the main title on your page is an H7 or something like that).

As for speed, page builders can slow down your pages (especially when compared to a flat coded template file), but shouldn't be too detrimental.

[ambt]

I use Fusion Builder and Visual Composer because they were bundled with the premium themes that I bought.
I like both of them, they make life easier. But I realize that switching to another solution at some point in future will not be easy. The shortcodes will break and you may have to fix all the pages.

Therefore it is a good idea to choose one that is likely to still be around in a few years and that will continue to receive updates. For that reason I think that paid ones should be safer, because the developers have some kind of motivation to keep them up-to-date.

[tangor]

All points above are great. What you want to do is determine YOUR coding requirements, ease of page insert, number of pages, whether you will need scripting (js, php, etc) and your own time, effort, and skill level. The long term best way is to learn flat coding (ie, do it all by hand) to develop a complete understanding of how things work, and won't work.

[NickMNS]

@tangor totally agree. I learned that the hard way. I started with a crappy builder, once things broke I needed to figure out how to fix them. I find you always learn more debugging, but it is not a very elegant way to learn and it is cognitively painful.

w3school is a great resource for learning.

One also needs to remember that these builders are designed for ease of use, not for creating efficient and well written code.