As the name suggests, the WordPress Design Library is a library of WordPress design assets, enabling anyone to quickly create design prototypes for WordPress UI in Figma.
These tools are useful for designers when creating new UI and for anyone looking to contribute ideas, enhancements, or even solutions to bug reports. Sometimes pictures really do speak a thousand words.
In this post, we’ll talk about some key features of Figma before diving into a practical example that demonstrates some of the WordPress Design Library utilities.
What Is Figma?
Figma is a collaborative design tool that members of the WordPress project’s design team have been using for several years to work on and share design concepts. It offers a variety of handy features such as: in-browser access, rich prototyping tools, component libraries, code inspectors, live embeds, inline commenting, plugins, and much much more.
Perhaps best of all, it is totally free to sign up and start playing around. If you join the WordPress.org Figma organization (instructions below), you’ll gain access to the WordPress Design Library enabling you to design WordPress UI in no time.
What Is the WordPress Design Library?
In Figma, you can share components and styles by publishing them, transforming your file into a library so that you can use instances of those components in other files.
It may be easiest to think of the WordPress Design Library as a visual representation of all the javascript components that compose UI in the WordPress codebase. As an end user of the library, you can use those components in a self-contained environment to create new interface designs. It’s kind of like a big LEGO box containing all the UI pieces (buttons, form inputs, etc.) that you can use to create and try out new designs.
Creating designs with these assets enables rapid ideation on new interfaces by removing mundane processes that one would ordinarily have to work through. Nobody wants to repeatedly double-check that the button they made perfectly matches the buttons rendered by the code! And on the flip-side of that coin, anyone sharing a design with others will generally endeavor to make specific elements (like buttons) match what exists in the code as closely as possible. The WordPress Design Library solves both these headaches and more.
An additional benefit to these assets visually matching what exists in the codebase is that any designs you create with them will inherently make use of the latest WordPress design language and consequently feel like WordPress with almost no effort required. Passing such designs on to developers makes them easier to interpret and implement too.
Figma Fundamentals
Before getting into the practical section of this post, let’s quickly cover some of the fundamental features of Figma libraries. This will help prepare us for working with the WordPress Design Library.
Components
As we touched on above, the library consists of “components” that serve as visual counterparts to their code-based equivalents. That is to say, there is a Button component in Figma, and a matching Button component in the WordPress codebase.
But what is a Figma component?
Components are elements you can reuse across your designs. They help to create and manage consistent designs across projects.
Let’s quickly explore some of the properties of Figma components to understand the ways they help when working on our next design.
Variants
Some Figma components offer variants. One example is Button(s) which all have the following states:
Resting
Hover
Focus
Disabled
These can be manipulated via the variants interface in Figma:
Other examples of components with variants are form inputs and menu items. Variants are a new feature in Figma, so we’ll be adding more over time.
Overrides
Although any components you insert are intrinsically linked to the master component in the library, it is possible to override some properties.
While working with an instance of the Button component, you can change things like the label, or even the background color, while maintaining the link to the master component in the library. If you’re familiar with git workflows, this is kind of like creating a local branch. Any changes you make can easily be reset in a couple of clicks.
Overrides made to your local instance will persist even when the master component is updated. So if your design calls for a button with a green background, you can apply that override safely with the knowledge that even if the master component is updated, your button can inherit those updates and remain green.
We’ve only really scratched the surface of components here. So I would recommend the official Figma documentation for more advanced information.
Figma Styles
In addition to components, styles are also published as part of the WordPress Design Library. They have similar properties to components in that a master style exists in the library and can be utilized in your local Figma file. Just like Components, Styles will receive updates when changes to the library are published.
Styles are used to define colors, typographical rules, and effects like drop-shadows present in the WordPress codebase. They enable you to apply things like text or background colors that will match other UI parts.
Using Styles from the library, you ensure that your creations match existing UI elements, making it easier to implement.
“Stickers” are simply arrangements of Components and Styles that have been combined to represent common UI elements. They are not good candidates for full componentization due to their frequent customization needs. Examples of Stickers include the Inspector sidebar and the block inserter:
Their utility is simple: find the sticker you need, peel (copy) it from the WordPress Design Library, and stick (paste) it into your local file before customizing as needed.
Stickers are not Figma features like Components and Styles, but any stickers you copy to a working file will stay up to date by virtue of their underlying assets.
Views are arrangements of components, styles, and stickers.
Designing a Block Using the WordPress Design Library
Okay, now that we have a handle on the basics of Figma libraries and their features and the utilities of the WordPress Design Library like Stickers and Views, let’s work through a practical example – designing the UI for a brand new block.
Getting Started
All you need to get started is a Figma account added to the WordPress.org Figma organization.
Once you’ve signed up at Figma, simply join the #Design channel on the community Slack and request an invite. Include your Figma username, and a friendly community member will help get you set up in no time.
Now the fun begins!
To create a fresh new design file in Figma, visit the Gutenberg project and click the “+ New” button.
Now let’s include the WordPress Design Library in our working file so that we have access to all the goodies we’ll need:
Open the “Assets” panel and click the little book icon to view the available Team Libraries.
In the modal, toggle the WordPress Design Library on. You can leave the others off for now.
After closing the modal, you’ll notice a number of components become visible in the assets panel. To insert them, they can be dragged on to the canvas:
It’s kind of like inserting a block
Creating a Pizza Block
I love to eat pizza, so for fun, I’m going to design a new block that simply allows the user to display a delicious pizza in their posts and pages. I want the block to include options for a total number of slices and different toppings.
Work Out the Flow
I always like to concentrate on individual flows when designing blocks. That is to say, the linear steps a user will take when working with that block. In this case, I want to create visualizations of the following steps/views in our Figma file:
Inserting the block from the Block Inserter
The Pizza Block placeholder state including options in the block, its Toolbar, and the Inspector
The configured Pizza Block settings
The end result – a delicious pizza sitting comfortably on the canvas
Sketch the New States
Thanks to the WordPress Design Library, I’ll be using as many existing UI components as possible, but I still need a rough idea of how they will be composed in the new interfaces that my Pizza block will require. I normally find it helpful to sketch these out on paper.
Here’s the placeholder state which users will see when they first insert the block. This should be all I need:
Prepare the Views and Stickers
Helpfully, there are Views in the WordPress Design Library I can use for each of the steps in the flow outlined above.
I open the library, navigate to the Views page, find the views I need, copy them, and paste into my working file.
It is very important to copy (not cut) Views from the library so that they remain intact and other people can still access them. If you cut them, they’ll be gone forever, so please don’t do that
I’m also going to need a block placeholder sticker, so I navigate to the Stickers page, copy the one that most closely resembles my sketch from before, and paste it into my working file.
As with views, please only copy stickers; do not cut them.
Gather the Components
Referring back to the placeholder state I sketched out on paper (it can be helpful to import this into your Figma file), I can see that I’m going to need some form elements to realize the design.
I navigate to the Assets panel, locate the components I need, and drag them into my file:
Helpful tip: Once a component has been inserted, you can transform it into another component via its settings panel. Sometimes it is easier to copy/paste a component you already inserted and transform it this way, rather than opening the assets panel over and over.
Arrange the Views, Stickers, and Components to Create a Coherent Design
Now that we’ve gathered all the individual pieces we need, it’s simply a case of arranging them so that they resemble each of the steps of the flow we outlined before. This is done with simple drag and drop.
If you’re familiar with software like Photoshop, Sketch, and others, this should feel very familiar.
Once everything is in place, our flow is complete:
I still find it incredible that we’re able to do this in just a few short moments.
Hook up the Prototype
With each step of our flow created, the last piece of the puzzle is to connect them and form a clickable prototype.
I switch to the Prototype panel and create click behaviors by selecting a layer, then dragging the white dot to the corresponding frame.
There are a variety of behaviors that the Figma prototyping tools support, such as a hover, drag, and click. It is even possible to create smart animations. Perhaps that’s something we can explore in another tutorial, but for now, I will refer you to the Figma documentation for more advanced prototyping.
Now that I’ve connected all the appropriate elements, I am able to take my prototype for a test drive by clicking the Play icon:
I tried to keep this tutorial fairly simple and concise; even though we only really got to grips with the basics here, you can see the power of Figma and the WordPress Design Library when it comes to trying out new designs.
There are a ton of content management system (CMS) options out there. And if you’re looking to find the perfect fit your website project, the search can be exhausting. Particularly if you don’t have a lot of experience with these systems.
But before you even choose a specific app, there’s another factor that needs to be considered. One that will have a major impact on your project in both the immediate and long term. Is the CMS you’re considering open-source or proprietary?
All too often, neither web designers nor website owners are fully aware of the differences. It’s only after they run into a roadblock that they realize the consequences of their choice. By then, it could be too late and too expensive to switch.
Today, we’ll fill you in on the differences between these two types of systems. The goal is to help you get the information you need to make the right choice from the very start.
The Web Designer Toolbox
Unlimited Downloads: 1,000,000+ Web Templates, Themes, Plugins, Design Assets, and much more!
Before we get too far into the weeds, let’s attempt to define what open-source and proprietary software are.
It may sound complex, but what we’re really talking about is how a piece of software is licensed. This is important because licensing determines what you can and can’t do with a particular app. Also, there could be an impact when it comes to things like content ownership, web hosting, and the ability to add additional functionality.
With that, here’s a quick (non-exhaustive) guide to each license type:
Open-Source
An open-source license grants its users access to the underlying source code of an application. This means you can typically change or extend its code to suit your needs and even redistribute it if you want. There may be rules that require you to credit the original developers, but you can feel free to add your own flavor wherever you like.
WordPress is perhaps the best-known example of an open-source CMS. You are free to hack away at the source code, create themes/plugins or even fork the software (as ClassicPress did).
One thing to note is that open-source doesn’t always mean the software is free. Think of buying a commercial WordPress theme, for example. You purchase the theme and then have the ability to customize its code. Whether that’s the right path for your project is another subject – but the option is there.
Proprietary
On the other hand, proprietary software enables the vendor (owner) to exercise exclusive rights. In practice, this means that the app’s owner can restrict its usage however they see fit. A user likely couldn’t, for example, directly modify the source code. However, they may still be able to create add-ons that enhance the software. User rights can vary greatly depending upon the particular vendor.
There is any number of other terms a user might have to agree to. With regards to a CMS, that could mean agreeing to host your website only with a particular provider or utilizing plugins from a vendor-approved marketplace.
Notable examples of proprietary CMS include Squarespace and Wix.
Pros, Cons, and Considerations for CMS Licensing
Both open-source and proprietary CMS applications have their strengths and weaknesses. Thus, some projects are a better fit for one licensing structure over the other. Then there are also plenty of differences within specific apps in each category.
But generally speaking, some major factors are endemic to the licensing structure itself. Let’s look at some areas where open-source and proprietary apps typically differ the most:
Data Portability
The ability to move your data from one CMS to another – or even one web host to another – is a pretty big deal. A license that doesn’t allow you to do this can be problematic for some. What happens if you no longer want to use that system?
This is where you need to read the licensing agreement carefully. A vendor is under no obligation to help you export your site’s design, content, and media files. Proprietary software may even disallow some or all of this completely.
Open-source software will likely offer a way to export at least some of this data. Even if it’s not built directly into the CMS, a third-party tool might also be utilized for this purpose.
If you want to move to a different system, don’t expect much leeway when it comes to design. Since themes are often tied to a particular CMS, moving between systems is not a straightforward process – regardless of licensing.
Web Hosting
Many proprietary CMS applications are based on a software-as-a-service (SaaS) model. That means the software is only licensed to run on a single web host. If you want to use the CMS, you’ll have to do so within that centralized hosting environment.
Along with the aforementioned data portability, open-source systems can usually be hosted just about anywhere. There may be some minimum server requirements (MySQL, a specific version of PHP, etc.) but your site’s files can be moved again and again.
Maintenance Updates
Every actively developed CMS will require some form of maintenance. Bugs need to be fixed and security tightened. And there is always room for new features and UI enhancements.
Licensing can often tell you a bit about how system maintenance works.
With open-source software, website owners are generally responsible for applying updates – although strides have been made in automation. Typically, you have the choice to decide when or whether to upgrade (or automate). Some managed web hosts also provide this service.
Proprietary systems often differ in that they may not offer you a choice in the matter. Some updates may be applied in the background. In other cases, a vendor might allow you to defer an update for a specified period of time.
Customization
The final area we’ll look at is the ability to customize a website’s look and functionality. The CMS licensing structure often impacts what you can and can’t do here as well.
Proprietary systems can run the gamut. Some will allow the use of custom themes and/or plugins, while others are much more closed off. Also, the availability of an official or third-party marketplace could mean more opportunities to tweak a website to meet your needs. But this all depends on the vendor.
Meanwhile, open-source systems generally allow for complete customization. You can build your own themes or plugins. You can also source these items from third parties. The back end of the software is also fair game for tweaking. There are no hard limits as to what’s allowed.
Finding the CMS That Works for You
Here’s hoping that you found the above considerations to be helpful and objective. We understand that each camp has its devoted fans – and for good reason. The decision of whether to go with an open-source or proprietary CMS can be deeply personal and depends on the past experiences we’ve had.
However, if you’re not committed to one licensing structure over the other, picking a side can be difficult. How can you be sure you’re making the right choice?
While we can’t decide for you, we can offer some advice. Think about your website project as a whole. Consider how you want to build, maintain and customize it. How much freedom and responsibility do you need or even want?
If you’re looking for low maintenance requirements and aren’t deterred by restrictive licensing, a proprietary CMS may be a perfect fit. Open-source, on the other hand, is a wonderful choice for those who want more control over every aspect of their site.
Once you’ve defined what you’re looking for, you can figure out which type of system works best for you. Good luck!
The second major release of the year is right around the corner. You might have heard a bit of buzz about full site editing around your WordPress circles, so this post will give you some big picture things to know as well as a few wayfinding links for anyone who wants to know more.
For Site Owners and Operators
If you own and operate a WordPress site, updating to version 5.8 should be a seamless experience, just like any other update. All the conversation around full site editing is very exciting, but shouldn’t be alarming—everything in the next release that relates to full site editing is opt-in. To experiment freely with it, you need a theme that is built for it. Check the links at the end to see a few examples!
For Agencies and Theme/Plugin Developers
If you extend the functionality of the WordPress CMS for clients, updating to version 5.8 should also be seamless. As always, it’s smart to spot-check custom implementations in a staging environment or fully test when the release candidate is made available. Want to test your products and get everything client-ready? Check out any of the testing options below.
For Contributors and Volunteers
If you contribute time and expertise to the WordPress project, you can join us in the interesting work leading up to the WordPress 5.8 release and update your site with the deep satisfaction of a job well done. There is a lot that goes into every release—from design and development to documentation and translation; if you’ve got some time to spare, and want to help support the project that supports the tool that supports your site (whew!), check out the links below.
Life is full of surprises. And just when you think you’ve settled into a routine, the unexpected can turn your world upside down. It can happen in the blink of an eye.
As I write this, I’m in the middle of such a disruption. Two members of my family are hospitalized with (non-life-threatening, thankfully) medical issues. With that comes not only worry but a slew of added responsibility.
Suddenly, the web designer who rarely leaves the house is rarely home. The things I typically do each day seem like a distant memory – even if it’s only been a short while since I’ve done them. Nothing feels the way it’s supposed to.
They say the last thing you should worry about in a time like this is work. But when you’re a solo entrepreneur, it’s hard to ignore. There are missed deadlines and projects in progress that have ground to a halt. Even the tiniest of tasks start piling up.
Right now, I’m trying to navigate this new normal. With that, I wanted to share some thoughts on living life and doing business during chaotic times. Of course, I’m still learning as I go. But here’s the good, bad, and ugly of it all.
The Web Designer Toolbox
Unlimited Downloads: 1,000,000+ Web Templates, Themes, Plugins, Design Assets, and much more!
If there’s one thing I’ve learned over the years, it’s that honesty truly is the best policy. Yet it can also bring conflicting feelings during a crisis. This is especially so for an introvert such as myself.
Your instincts may tell you to keep private matters to yourself. Try and act as if everything is fine – business as usual. But what does that accomplish?
It feels like you’re just burying a situation that should be front-and-center. Some things are simply too large to sweep under the rug. Like it or not, these situations are going to impact your business.
Therefore, attempting to keep a brave face is pointless. If you’re struggling to keep up with projects and answer emails, clients will likely wonder what’s going on.
It’s better to come clean and let them know what’s happening in your life. This way, your clients will know that you may not get things done as quickly as expected. And that your availability will be limited for the time being.
Additionally, it opens the door to a whole new support system. Most people will empathize with your situation and send words of encouragement. They’ll also exercise patience as you try and piece things together. This is something I’ve already benefitted from and it does make a difference.
Prioritize What Matters
When you’re the only one in your office, there’s no one else to pick up the slack during your absence. It can lead to feeling like you’re drowning in a sea of work.
That’s why it’s important to prioritize things. Not every project or task has the same level of urgency. And there are likely things outside of work that require your attention, too.
The key is to focus on the highest priority items – the things that are better done sooner than later. Take care of your biggest clients and the most time-sensitive tasks.
And try to keep expectations (yours and theirs) realistic. That goes a long way towards making peace with whatever you’re facing. Everything else can wait another day or even a week.
Don’t Ignore Your Well-Being
Even if we humans can only be in one place at a time, we still try to do it all. This has been a difficult thing for me to grasp. I want to take care of everyone and everything. It’s like trying to climb Mt. Everest with a donkey on your back.
The burden may be heavy, but you can’t forget about yourself. Because, if you’re not well, how can you help others?
Being a home-based web designer makes this all the more difficult. I’m so used to taking care of client requests as soon as they arrive. Even when dealing with other things, I still have that urge to cross items off of my to-do list. It’s frustrating when that’s not possible.
Perhaps the solution is a two-part process. The first is informing clients of your limitations, as mentioned above. The second part is a matter of putting your phone down and keeping yourself in the moment.
Then there’s also a commitment to doing little things to help yourself cope. For me, a quick workout does the trick. But whatever helps you feel a sense of normalcy, go for it. You deserve the opportunity to rest and reset.
Getting Back to Normal Is a Process
I think it’s natural to want to get back to everyday life as soon as possible. It’s something I’m looking forward to. I’ve found that I didn’t miss the daily grind until it was taken away.
However, getting there can be a process – even after you’re past the initial crisis. A pile of work may be waiting. That can take some time to catch up on. Beyond that, the mere act of reestablishing a routine isn’t so easy.
It requires a lot of patience and a sense of gratitude. Being thankful that you’re through the worst of it and for those who supported you during a tough time.
And, hard as it may be, it’s worth remembering that business is only one facet of life. Whether you’re dealing with loss, an illness, or other difficult situation – use it as an opportunity for personal growth. The possibility of coming back stronger can only help you in both business and life.
Hello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
0:39
Prior to Gutenberg, our current multi-year project that is changing the way we see WordPress, another multi-year project changed the way we saw WordPress. Starting in 2008, substantial changes to the WordPress interface came in a series of major releases, starting with WordPress 2.5. That was before my time in the project; I’ve only ever worked with the current dashboard in WordPress. But, from what I’ve read, the user testing that would have gone into it was a huge undertaking and very well coordinated. Now, WordPress has not taken on that type of robust testing project since, but starting around 2014 or 2015, a community testing practice was started. I’ve shared these calls for testing frequently, both on Twitter and in this podcast. But you may not really know why I find the testing program so valuable. So today, I’m going to explore with you the concept of co-developers in open source.
1:52
Open source software, like WordPress, is built by the people who show up. There are a few obvious groups when you think of software, the developers, designers, technical writers, folks who monitor the forums, and really, all the teams you find in our WordPress project. Co-developers or co-creators, if you’ll join me in making our tent a little bigger, refers to the users of an open source product who actively engage and contribute to the work by using the software and sharing any bugs that they find.
2:25
I mentioned this group in the episode about how WordPress improves. Specifically in that episode, I underlined that if you consider users to be part of the collaborative process, as long as people use your product, those people will have opinions about your product’s needs. And today, I’m extending that thought a bit further to say that, as long as there are opinions, there are opportunities.
2:51
When you know what isn’t working, you can focus your attention on a solution, you can focus on making sure that you can make it work. The existence of co-creators is one of the great things about open source. No designer or developer or product owner has to know every sort of user to be able to get feedback from them. If they show up, test the software and get their thoughts written down, then you can start to see patterns and common pain points. It is also, unfortunately, one of the great difficulties of being an open source project. After all, if users don’t show up, or don’t test, or don’t write down their feedback, it’s impossible to know what worked for them and what didn’t. And on top of that, with such a large percentage of the web being supported by WordPress in this case, not every problem is part of a pattern. And not all patterns are part of the current priorities.
3:54
Looking beyond that double-edged sword. Let’s say that this idea of a co-creator makes sense to you. And more than that, you feel like it describes you. What does it mean for you to show up in WordPress? There are lots of good ways to offer this sort of feedback and contribute to those patterns that can help us see through the fog. So I have for you a mini list and, of course, a bunch of links in the show notes for you.
So some good ways. First, you can participate in any of the dedicated calls for testing. They are short and frequently have a guide. I participate in them and generally find them fun. I say generally because sometimes I also find them frustrating. That’s really okay too; the frustrations helped me to identify that I found a problem. And if I can find a problem, then I have saved someone else from finding that problem in the future. The second thing you can do is file a bug report with information about what happened when you ran into a problem and how someone like me could make your bug happen on their site. Bug
5:00
Reporting is one of the things I’ve grown to really love in my time and open source; I did not love it. At first, I was really scared to do it. I mostly used to send videos of the bugs that I found to other people and ask them to file the bug reports for me. But then, of course, I never knew whether they got fixed or not. So I was scared to do it at first. But once I figured out what makes a “good report,” I felt like I was helping circle hidden treasure on a map or something. I realized also not everyone’s excited about finding hidden treasure on a map. But I play video games and finding hidden treasure on maps is, like, a thing.
5:43
A third really great way to contribute like this is that you can join any community meeting to learn more about what’s happening now and in the future, or just to see what makes WordPress work. As a heads up, these meetings go really fast. And they’re all in text. And there’s sometimes, but not all the time, a little bit of jargon that you have to head to your favorite search engine to find. But I sit in on about half of them myself and get a lot of really good information about things that I’ve been wondering about, things that looked broken, but actually are functioning exactly the way that they should. And I just didn’t want them to function that way. And more often than not, I found out that something that I thought was broken, was already identified and being fixed. Those are three great ways to show up and help give feedback that helps make WordPress better and more functional for more people.
There are also a few other ways that we see people trying to share that feedback that don’t work quite as well. And I’m going to touch on a few of them just because it’s important to know, as you’re trying to figure out how to get started with this. The first one is just tweeting your frustrations, and I get it like that’s literally what Twitter is for.
7:03
But also it’s hard to create a block from “I am frustrated, behold my hateful rhetoric.” Not that any of you, my dear listeners, ever tweet hateful rhetoric. Still, that is really hard for anyone to figure out what was actually wrong in that moment. Another thing that is not the most functional way to give feedback is review brigading. The Internet rewards this kind of behavior, but I have found at least for WordPress, those false positives and false negatives can be really confusing for our new users. And the third way, that’s not our best way, and probably is the least best way, is just by giving up and not telling anyone what broke for you.
7:45
I know that I already said it’s not possible to fix everyone’s problems. But while it’s not possible to fix everyone’s problems the moment they get shared, it’s also truly impossible to fix any problems that no one knows exist. And so giving up and not sharing an issue so that we can identify it as part of a pattern of problems is probably the least effective way to help us help you get your problem solved.
8:13
This brings me back to the question of the value of WordPress users as co creators in the development process. As WordPress grows, both in usage as a CMS and in participation as a community, it’s important for us to shed the idea that software creation is only about what literally can be done to code or what literally can be done to core or what literally can be done to the CMS. It’s also important for us to constantly remind ourselves that the best outcomes are the result of collaboration with the people who use WordPress the most. I know that not every type of user we have is showing up to give us feedback about where WordPress doesn’t work for them. And I would love to see more feedback that helps us to figure out where our patterns are.
9:03
So the bottom line is this without user feedback that has some clarity of what was expected versus what happened, the work to make a good choice involves a whole lot of guessing. So since open source software is built by the people who show up, I hope this gives you an idea of how you can show up and help improve the tool that powers your sites.
9:32
That brings us to today’s community highlight every episode or so I share either a great story of WordPress success or a great story of a WordPress contributor who helped some folks along the way. Today’s community highlight comes from @trishacodes who shared one of her early to WordPress mentors. She says “@RianRietveld was such an encouragement and helped me find the courage to speak up.” I have had myself many conversations with Rian, and that rings true for me as well.
10:00
That brings us to the moment you’ve all been waiting for, the small list of big things. It’s actually kind of a medium list. Today, I’ve got four whole things to share with you all. The first thing on my list is that WordCamp Europe is coming, that will be June 7th through the 10th. It’s a multi-day online event. I will share in the show notes a link to the main website; there you can get an idea of what will happen, the schedule, and get your hands on some tickets so that you can get it in your calendar and prepare yourselves.
The second thing I want to share is for all of our polyglots out there. The French team is planning a translation day coming up on April 30. I will share a link to that as well so that you can get an idea of what that takes if you’re feeling like you want to do some translation work. The third thing I want to share is that the Indian community in Pune actually started a new meetup series. It is a translation work along self-study – also for all of our polyglots out there. I would love to see as many people as are interested in both learning about how to do translations and certainly translating WordPress get registered for that. A final thing I want to share with you all is that if you are curious about what full site editing features will be included in the 5.8 release, that’s the WordPress release that’s coming out in the middle of July, you can check out my recap and recording of the demo that was held with Matt, Matias, and the rest of the team. There’s are also a number of other posts of next step ideas that I will share in the show notes as well.
11:51
That, my friends, is your small list of big things. Thank you for joining in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks!
Glassmorphism effects have become a staple in modern web design. They offer a sleek aesthetic and fit beautifully with just about any background color.
The exact definition of glassmorphism can vary a bit. However, it’s essentially a “frosted” or semi-transparent element that mimics the look of glass and appears to hover over the rest of the page. Thus, the container’s background is allowed to shine through. You may even see some refraction in more realistic interpretations.
Want to see what all the fuss is about? We’ve put together a collection of glassmorphism effects built with CSS and other web technologies. They range from common UI elements like buttons to more abstract creations. Enjoy!
The Web Designer Toolbox
Unlimited Downloads: 1,000,000+ Web Templates, Themes, Plugins, Design Assets, and much more!
This product card UI offers proof that glassmorphism’s beauty is in its simplicity. It takes a lovely gradient background and adds dimension. Hover your cursor over the sneaker and it breaks out of its container and practically jumps right off the page.
The frosted-glass effect is put to good use here, as it allows this login form to stand out from the page’s photo background. That is one of the main benefits of using this design technique. You can use a complex background while keeping text readable. And it doesn’t disrupt the flow quite like a solid-colored container would.
This interactive picture frame presents a layered and colorful glass look. The multicolored shapes within the frame use various blend modes, creating a 3D effect. Hovering or touching the frame allows you to rotate the object, at which point some subtle reflection comes into play.
We might never find a more natural usage of glassmorphism. This CSS beer starts out as an empty pint. Click and hold on the glass to watch it fill up with frothy, bubbly goodness. The translucent coloring and refraction make it all the more realistic. Cheers!
Here’s a neat way to add glass effects on top of text. Utilizing absolutely-positioned elements, these rounded shapes bring a unique touch to an otherwise-plain HTML heading. This could be implemented on page titles or even text-based logos.
Nominally, this snippet generates macOS wave patterns. But it also makes nice use of glassmorphism. The small container used to house a set of buttons is highly effective at making them the focal point of the page.
The use of large featured images within page titles is a popular design technique. The trouble is that it can be hard to keep text legible without ruining the whole aesthetic. This snippet shows us that a frosted-glass effect can do the job quite beautifully. Even with the busy photo background, the included text is easy to spot and read.
Calculators are often portrayed as utilitarian and devoid of compelling design. That doesn’t have to be the case. Check out this gorgeous glassmorphism-enhanced number cruncher. While the perspective-shifting hover effects may be a bit much in terms of usability, the look of the calculator itself is perfection.
It’s easy to see why web designers are continuing to adopt glassmorphism. The effect is relatively uncomplicated. Yet it adds elements of both beauty and utility.
As we saw above, even something as simple as a small container holding buttons can make an impact. You don’t have to go overboard with special effects to create a clean and effective look. It’s more about working with and enhancing the visual assets you have rather than inventing something new.
We hope you enjoyed this look at glassmorphism. If you want to check out even more great examples, visit our CodePen collection.
icon:
