Just a quick post to let you know that our latest premium WordPress theme, Public Opinion is live. If you are on the lookout for a magazine theme, look no further! Here’s a rundown of some of the theme’s features.
Mark your best posts as featured and display them above the rest, choose from 11 eye catching layouts to achieve the best reading experience for your visitors.
Strategically placed widgetized areas throughout the theme will allow you to place advertising banners exactly where needed to increase revenue without annoying the reader.
Do you have an awesome layout in mind which is not built in Public Opinion? No problem, we have built two custom Elementor modules to help you pull featured posts or category content and place it wherever you please.
Public Opinion also includes unlimited color variations, a news ticker, a weather module, and custom widgets, pretty much everything you need is there. Check it out today!
Do you need to show an extra navigation menu on your WordPress site? Or perhaps you need to show a bunch of links someplace? No matter your use-case, WordPress provides navigation menus that are very easy to create, manage and display. If you like the drag and drop interface of the navigation menus management screen, and you so you figured you’ll create a menu to show them.
However, you neither want to show them in the sidebar (“Custom Menu” widget), nor in the content (“menu shortcode” plugin), and your theme doesn’t quite allow you to display it exactly where you want. What do you do? You need to register a new menu location. Let’s see how.
The WooCommerce checkout page comes with most of the required fields to allow you to get all the required information in order to dispatch an order to a client. What if something is missing? You might need a couple of extra fields, a checkbox, a drop-down or another text input field, how can you get them? You can always add new fields programmatically as described in WooCommerce’s documentation here, but there is an easier way by using a plugin.
If you allow registrations on your WordPress site, chances are you need to gather some more information about your users. If you absolutely need this information, the best way to get it is to make it required during registration, otherwise there are slim chances that your users will actually visit their profile page and provide that optional information.
The WordPress dashboard contains a lot of options that most users won’t ever use. In fact the plethora of options can some times be confusing or even dangerous if some of the available options allows an inexperienced user to break their site. WordPress tries to minimize both the clutter and prevent accidents by restricting access to necessary options depending of the user role. What if you want to create a tailor made experience for your clients though? You have a few options, you can use the roles & capabilities API to customize what each user role can do on your site, or even create custom roles for your users, more info on how to do that here. However, for more fine grained dashboard customization there is a purpose built plugin and it’s called Adminimize.
It’s been quite a while now since we’ve completely abandoned vanilla CSS for a CSS preprocessor (more than four years actually) and more specifically for Sass (with SCSS syntax). There are quite a few reasons why we did that, and the main one is improved DX (developer experience) along with easier plugin integrations.
Simply put, Sass used to be (and still is) a much more powerful language than vanilla CSS, especially if you’re concerned with older browser support (i.e… IE ¯\_(ツ)_/¯). I’ve found that the need for variables, conditionals, mixins, rule nesting, along with color functions and all the goodies a preprocessor comes with is much more apparent within the WordPress theming context where you wish to provide multiple color schemes for your theme or tame popular WordPress plugins to match your theme’s design and layout.
That said, I’m not here to sell you on CSS preprocessors right now, this piece is an overview on how we use Sass with Gulp in our theme and plugin development workflow, and how to incorporate the same workflow to your theme, if you so wish.
A well crafted and easy to read font is a great asset for any website. It will catch the readers eye and it won’t tire them while they consume your content. There are many plugins that can help you add fonts to your WordPress site, but perhaps you want to avoid using them and prefer to do this the old fashioned way. It’s pretty easy, let’s take a look.
If you’ve ever built a WordPress site from the ground-up, chances are that at some point you needed to do something that your theme and plugins couldn’t or wouldn’t do. You probably already know that you can add code directly to your theme, in a child theme, or in a site-specific plugin. But each approach comes with its pros and cons. Do you know when and why you should choose each one?
Landing website pages have been all the rage for a while now and although many of them come with a great design they can also come with a caveat: long body heights. This usually means that after users are done going through our awesome content they are forced into a scrolling sprint back to our website’s header in order to examine more navigation options (which also kinda means our landing page should have more interesting calls to action, but that’s a different story).
One way to mitigate this terrible experience and improve our website’s user friendliness would be to make our header sticky (which we’ll cover in another tutorial), but that’s something that’s not always desirable. Another way, one which we’ll cover in this tutorial, is to add a so-called “back to top” button which stays fixed as we scroll down and smoothly transitions us back to the very top when it gets clicked. This kind of “scroll to top” behavior is so necessary in some use-cases that iOS even has it embedded as a feature in pretty much the core of the OS (by tapping the status bar).
Let’s go ahead and see how simple it is to add this kind of functionality to any website with a simple button.
Hi could you tell us a little about yourself and background?
I’m a non tech guy who graduated from Dauphine, in Economics. Then I started my career in Finance, in merger and acquisition advisory. After 3 years, I thought I was not learning enough anymore, so I decided to try starting a company. But I had no specific and no partners. That’s when I met Rémy Berda (co-founder of Weglot), who had an idea, a first user and a strong background as an engineer and entrepreneur. It was the first step of the Weglot journey :).