Advantages:
- Focused approach in finding the content
- Easy to experiment
- Reduces a ton of designing effort
- Builds the foundation for the project
- Helps develop a storytelling experience
How to start:
- Define the purpose.
Is it to sell or inform or convert? Write in one plain line.
For example: The goal of the website was to generate leads.
- Define the tone according to the message.
For example: As the goal was to generate leads from business women therefore went a bold + modern layout/tone with the focus on using elements to assist the message.
- List number of sections.
For example: Brainstormed following sections based on the website goal:
Header
Reinforcement section
Features section
Call to action
Credibility section
Subscription section
Footer
The sections between header and footer can vary on your goal.
- Start with the header
For example: Started with the header and used the rectangle as the primary element.
The approach is to wireframe the header section and then build over it.
Here's the header wireframe for you:
- Pick one shape and carry
Here are the wireframes of the of the sections 2 - 5:
Look how rectangular buttons, rectangular images, and rectangular blocks have been used.
The tip is to have one shape. Be it rounded, be it rectangular, be it any polygon.
One shape approach is good for building simple and elegant wireframes.
If you feel like building an online experience, feel free to use shapes/SVGs that enhance the message and purpose.
Here are the wireframes of the sections 6 and 7:
- Experiment
Experiment a lot till you satisfy yourself and the wireframe flows with the message.
The goal is to have multiple sections targeting the goal.
Let's have a recall:
- Wireframe before web design
- Write the goal
- Decide the tone
- Decide the number of sections
- Start with header
- Pick one shape and carry
- Experiment a lot
Quick quedtion:
Would you read if I wrote a more detailed blog post?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The will-change property hints the browsers what properties are going to change.
Therefore, helping the browser set up optimizations before an element is actually changed.
This is great for optimizing animations / transitions.
Here's how it's done
Although it seems cool to use will-change as much as you can to optimize the performance of the page.
It's recommended to use on elements that are sure to change like sliders, modals.
Moreover, will-change property should only be used to tackle performance issues not anticipate them.
Optimizations use machine resources to accelerate the rendering process and it can become a lot labor intensive for browser to optimize unnecessary elements.