DIY or Die... Pro tips for building your own WordPress sites!
•Transferir como PPTX, PDF•
0 gostou•355 visualizações
Are you struggling to build your own WordPress sites without the technical skills or knowledge to do it well? Does your website look more like a home-made hot tub than a professional website? Pat Ramsey shares his best tips for building your own websites using WordPress. #diyordie
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (10)
Último
Último (7)
DIY or Die... Pro tips for building your own WordPress sites!
- 1. DIY or die Pat Ramsey @pat_ramsey Marketing Clique
- 2. –wise carpenter “measure twice, cut once.”
- 3. General Tips
- 4. web hosting • host your site somewhere other than with your domain registrar • Semi-managed to managed hosting tend to have fewer issues with permissions ( “WordPress can’t write to the .htaccess file” situations ) • Unmanaged hosting ( AWS, Rackspace Cloud ) gives you wide-open opportunity but it’s on you to set everything up
- 5. Use protection • Protect your site with good regular backups • VaultPress • Protect your code with versioning • Github • Bitbucket • Gitlab
- 6. backups, versioning = ounce of prevention
- 7. Harden your site • https://wordpress.org/plugins/force-strong- passwords • https://wordpress.org/plugins/limit-login-attempts • https://wordpress.org/plugins/better-wp-security • http://wordpress.org/plugins/simple-user- password-generator
- 10. use few plugins • The more you have, the more likely there is of a conflict occurring now, or down the road ( updates ) • Tip: some good plugins do the job of many • WordPress SEO, Jetpack • Audit your plugins ( & theme )
- 11. Sliders Suck • https://yoast.com/opinion-on-sliders • http://conversionxl.com/dont-use-automatic- image-sliders-or-carousels-ignore-the-fad • http://searchengineland.com/homepage-sliders- are-bad-for-seo-usability-163496
- 12. One-page themes • Maybe not a good idea • Shareability • Search results probably not optimal
- 13. Tools & Tips
- 14. • Nice redirect URLs for PDFs, ugly links: https://wordpress.org/plugins/page-links-to/ • Resize all your images after a redesign: http://wordpress.org/plugins/regenerate- thumbnails/ • Clean up orphaned options: http://wordpress.org/plugins/options-optimizer/ • *be sure you know what you’re cleaning
- 15. View Source • Look for multiple instances of jquery. • Look for jquery not being loaded from “…/wp- includes/js/jquery/” • The body tag - does it have the class attribute? class=“page page-template”
- 16. In your theme, this is bad • <script src=“http://google.com/code/script/myscriptrawks. js></script> • WordPress, plugins, and your theme’s functions do not know that exists • Ripe for conflicts
- 17. In your theme, this is good • Use wp_enqueue_script() to load javascript instead of hard-coding links to javascript files • Use wp_enqueue_style() to load CSS ( including links to Google Web Fonts ) instead of hard- coding <style> tags
- 18. It’s a process, not a race A website, like a business, is never “done,” unless you pull the plug.
- 19. ?
Notas do Editor
- VaultPress: one-click restore, off-site backups. Github lowest paid plan gives you off-site private git repositories Bitbucket is free for up to 5 users ( private repos ) You could also install gitlab on your own server.
- Do you have a business plan? The same should be true for your website.
- The more complicated a theme or plugin’s instructions are, the more admin screens and options it has, the more it changes how WordPress looks & works in the Dashboard… all these should be warnings to proceed with caution. It doesn’t mean that theme or plugin is crap, but you should be hesitant. WordPress has coding & UI standards and guidelines. Not following those could be an indicator of a potential for conflict. It also may lead to problems for you, in 3 months, 6 months, a year, when you’ve invested time and money and now have little flexibility for new offerings on your website because the theme or plugin can’t easily accommodate your wishes.
- WordPress SEO does: 1) SEO, 2) breadcrumbs, 3) Social meta tags, 4) XML sitemaps Jetpack does: 1) custom CSS editing, 2) conditional widget display, 3) responsive & Retina-aware image carousel, 4) easy contact forms, 5) email subscriptions to new posts & comments
- I know, I know, everyone does it. Can we stop, already? What is the sound business case to be made for placing something that intrusive on your page before your actual content loads?
- There’s something here. The shareability is something I hadn’t thought of, but I think it’s legit. How do you share one of these hashtag URLs that just send someone down the page, instead of sending you to an actual page?
- There is little good case to be made for not using the built-in WordPress javascript libraries ( Masonry was one, but that’s been remedied with 3.9.1 ). Multiple instances of jQuery is a sign of bad coding in a plugin or theme. The body tag’s body_class() function should be present in your theme’s header.php file.
- WordPress is 10 years old. Hard-coding script tags should have stopped by now.
- http://codex.wordpress.org/Function_Reference/wp_enqueue_script http://codex.wordpress.org/Function_Reference/wp_enqueue_style Better yet - combine the loading of all your javascript and css into a single function and use add_action() to load them in your functions.php file. http://codex.wordpress.org/Function_Reference/wp_enqueue_style#Using_a_Hook