I’ll link the plugin below.Īs for your development environment, personally I almost always ( except if I am doing a very quick job for someone ) use ftp to connect my IDE to the website hosting account and do my work that way. Many many WordPress developers are doing this, as you will see by the number of installations on the plugin website, 5+ million. What I have been doing personally is using a WordPress plugin called “Classic Editor” so that I do not have to use Gutenberg blocks but instead use the wysiwyg editor, then I can use good old html without the headaches of blocks. The exception to that would be when you use the same custom template on multiple pages, then you would design the custom template to accept content from the backend page editor, like the Gutenberg editor, instead of plugging the content directly into the template. Your content can go right in the template. Always – 100 percent of the time – use a child theme when building WordPress websites.Ĭoncerning backend editors, Gutenberg or Visual Composer ( WPBakery ) or Elementor, etc, because you will be building your own templates you may never need to use a backend editor much at all. Google that and you will get a full explanation. The trick, if you want to call it that, when it comes to keeping your custom code safe when the theme takes an update is to use what is called a “child theme”. Good luck either way, both routes will be very educational! And yes, not matter which way you go, build your own theme from scratch or customize an existing theme, you will need to build some PHP chops to use with your html, css and JavaScript/JQuery. So you get the stability of a well built theme, and the community support when you have to ask for a little bit of help, and you get to learn all about WordPress theme development just the way you would building your own. Same for your blog page, you would need to override the theme’s blog template and use one you write yourself. The compromise I am suggesting is that you then write custom page templates for the pages to get the look and feel you want. I’m thinking about the header and menus, and the mobile responsiveness, as well an any specialty bits and pieces the theme developer may have added. The advantage of using a well designed theme ( great reviews, large installation base, community support etc., all the usual stuff ) is that it will be mostly free of bugs, and it will have lots of good functionality already built in. ![]() Hey a compromise between using a theme and building your own might serve you best.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |