THE ULTIMATE, AMAZING, AWESOME
Web Design & Development Blog
So a new client wants me to add a new section to his site. Shouldn't be a problem I said, thinking I could just go into the code and develop what I like.
So anyway, you might have guessed it, turns out it's built using the WP Visual Composer. I had a lot of trouble adding a full height video and thought I'd share the solution:
So what do you think? Does the visual composer make it easier or harder to set up your pages as a developer?
Most CMS's are similar. But one thing that always stands out to me is the WYSIWYG editor. It has to be good. I mean, if it is hard to understand or lacks functionality you're not really giving your client a very good product. That being said, most of the time, the main problem I see...is too much functionality! And clients having no idea where to start.
WordPress deals with this really well, by simplifying down to the essentials, and if you need more it can be extended too.
Here's an article that goes into it more: https://www.footsteps-design.co.uk/wordpress-wysiwyg-editor-awesome/
Ever done a website redesign that didn't go to plan? This article here goes into depth:
Writing sales content can be hard work, make it too pushy and you'll scare people off. Make it not pushy enough and people wont bother to take action.
In this article, writer Kendra Lee, shares with us 7 techniques for writing 'startling' sales content:
What did you think of those? Do you have any you'd like to add?
Writing sales content can be hard work. You don't want to make it sound too pushy and scare people off, but you want to make sure people know exactly what you want them to do.
Here's a great article by Kendra Lee that gives us 7 tips on writing 'startling' sales content:
Here's a great way to add a class to an element when it appears in the users viewpoint: https://www.machine-agency.com/blog/simple-jquery-scroll-reveal-script/
User Experience is something everyone says but few actually understand. If you've been working in the industry for a while you may think you understand it but 99% of the time most people really don't.
Here's a great article on User Experience and how you can get actual usable data for your next UX project: http://yokedesign.com.au/blog/take-you-out-of-ux/#more-4209
WordPress is easy to manage. When built properly clients can update image gallery's, image sliders, accordions and more all in the page they are looking at.
Because it's so easy on clients to manage, they often start to believe everything is easy in WordPress.
It's all at a click of a button.
So when it comes to updating their WordPress site they think it's just the click of a button.
And that's because it is.
However as all WP developers know, you can update it at the click of a button. Hell, you can even set all your themes, plugins and core WordPress to update automatically.
But it's not safe.
So if you're reading this because you are wondering why your designer is changing you for WordPress updates, read this article --> http://askwpgirl.com/updating-wordpress-plugins-themes-core/
That covers the steps most designers take when updating WordPress.
Thanks for reading.
It always makes me laugh inside when clients in the past have questioned why I have charged them a few hours to install a plugin. You just click plugins, add new and upload it - how does that take 2 hours, they'd say.
What takes time is finding the right one, and then setting it up.
I'll admit - I hate using most plugins. I always build it myself if I can because of the amount of time you waste trying to get a one size fits all plugin to do something specific.
They're buggy and generally suck a good 60% of the time. And that's where the hours get spent.
Here's an article that explains the process: https://smallbiztrends.com/2015/03/how-to-install-a-wordpress-plugin.html
I remember back when I was starting out learning web design, I really had a hard time understanding why we used a external stylesheet. It seemed like it was just something we done because it's the way it's suppose to be done - not that there was any logical reason why we would store all out styling in one file, to be loaded on every page - even though most of it wouldn't get used on every page.
I know a lot of people have issue with this when starting out - surely, I though, it must slow down the website if it's loading in this long css file for every page. I'll just stick all the css for my pages in the <head>
Why we use them
The reason why we stick all our CSS in one file is that it means we can make global changes. Changes to the entire websites styling in one file. Instead of potentially changing upwards of 100 pages like a lot of my clients websites.
Does this slow the pages down? Hell no! Once you visit one page your computer will download the stylesheet and store it locally. Meaning it only has to do this once (instead of doing it on every page).
It's something that seems so obvious looking back but we aren't born into this world understanding anything at all - so I forgive myself. Here is some further reading on the subject:
Thanks for stopping by.