The following post is by Hugo Giraudel, a regular contributor here. In the grand CSS-Tricks tradition, Hugo found a cool effect on the web and dug into how he could re-create it in a smart way.

A couple of days ago, I saw this pen by Hugo Darby-Brown which intented to reproduce the MetaFizzy effect by David DeSandro in pure CSS with the help of Sass. Hugo did a great job and probably the most important one: digging into the original JavaScript to understand how to do it in Sass.

He succeeded, but I thought his code could be improved. Even if it was clearly far better than a vanilla CSS version, there was still a lot of repeated code. Let's find a way to make it like super-DRY!

Important! This is really just an experiment. If you ever want to do something like this, please just use JavaScript. The CSS version takes like 500 lines long and turns out to be quite heavy for the GPU. So once again, this is a Sass experiment. Just for fun.

Where do we start?

This is a question I would not be able to answer if Hugo didn't do his demo first. Here's what we need to do:

• Give our text a long shadow, progressively fading to black
• Make the color of the shadow slowly change over time
• On hover, go crazy rainbow
• Animate this rainbow quickly

So in the end, we will need a couple of things:

• An animation for the smooth shadow
• An animation for the hover state
• A list of colors for the hover state

That's pretty much it.

The smooth shadow

The keyframes

The smooth shadow is the easier of the things we'll do. All we do is output a bunch of text-shadows of one color progressively fading them to black. Then, we need an animation which will change this color over time. A perfect job for hsl()!

Because we want our Sass code as DRY as possible, we'll call a mixin in our keyframes that will handle the crapload of text-shadows for us. First, the skeleton.

@mixin text-3d($hue) {
      /* Output crazy text-shadows */
    }
    
    @keyframes text-3d-animation {
      @for $i from 0 through 10 {
        #{$i * 10%} {
          @include text-3d($i * 36);		
        }
      }
    }

All we did was create a text-3d-animation CSS animation with 11 explicit keyframes (0%, 10%, ... 90%, 100%). In each keyframe, we call a mixin named text-3d, passing $i * 36 as $hue argument (36, 72, 108, 144, 156, ...). If you are familiar with hsl() notation, you can see where this is going.

The mixin

Now we've created the animation calling the mixin, it's time to build the mixin! All it has to do is outputing a bunch of text-shadows. I went with 50 which is pretty huge already but you can pick the number you want I guess (although you have to hardcode this, I didn't define a parameter for this). Once again, we won't write our shadows manually; Sass lists and loops are meant for this.

@mixin text-3d($hue) {
      $ts: ();
      @for $i from 1 through 50 {
        $ts: $ts, $i*2px $i*2px hsl($hue + $i*1, 100%, 50% - $i);            
      }
      text-shadow: $ts, 0 0 50px, 0 0 55px;
    }

Don't panic yet! This is actually simple. Before entering our loop, we define an empty list called $ts (stands for text-shadow). Then we enter the loop. In each run, we append a new shadow to our list where:

• both horizontal and vertical offsets are set to $i * 2px to make the shadows bigger and bigger
• we don't define any blur, but you can set one if you like
• the color is defined in HSL with hue set to the given parameter (multiple of 36) + $i * 1, the saturation to 100% and the lightness to 50% - $i, meaning it progressively goes to black

Then once the loop is finally over, we simply output our $ts list as a value for text-shadow. We also add two shadows manually for the cool white "aura".

And we're done for the non-hover MetaFizzy effect! It should work like a charm.

The crazy rainbow

For the most part, the hover animation works the same as the non-hover animation. We will proceed the same way we did before, starting with the keyframes.

The keyframes

@keyframes crazy-rainbow-animation {      
        @for $i from 1 through 50 {
          #{$i * 2%} {
            @include crazy-rainbow($i, tomato yellow green blue purple);
          }
        }
      }

As you can see, this is pretty much the same thing we used for the 3D text animation except we won't use 11 explicit keyframes here but 50. Actually 51 if we want to prevent a little glitch; let's add the 0% keyframe (out of the loop of course).

@keyframes crazy-rainbow-animation {      
      0% {
        @include crazy-rainbow(50, tomato yellow green blue purple);
      }
      @for $i from 1 through 50 {
        #{$i * 2%} {
          @include crazy-rainbow($i, tomato yellow green blue purple);
        }
      }
    }

We pass our crazy-rainbow mixin two parameters:

1. $i as a numeric value once again (we'll see the point later)
2. the list of colors we want to see moving when hovering the text (that's right, we can customize the colors!)

The mechanics

This is where things get complicated. The animation when hovered basically looks like a striped shadows (which makes no sense anymore): one color, then another one, then an other color, and so on... But there's more, the color are moving.

The idea is to have something like this:

@keyframes crazy-rainbow-animation {
      0% {
        text-shadow: 2px 2px   color1, 4px 4px   color1, 6px 6px   color1, 8px 8px   color1,
                     10px 10px color2, 12px 12px color2, 14px 14px color2, 16px 16px color2,
                     18px 18px color3, 20px 20px color3, 22px 22px color3, 24px 24px color3;
      }
    
      2% {
        text-shadow: 2px 2px   color3, 4px 4px   color1, 6px 6px   color1, 8px 8px   color1,
                     10px 10px color1, 12px 12px color2, 14px 14px color2, 16px 16px color2,
                     18px 18px color2, 20px 20px color3, 22px 22px color3, 24px 24px color3;
      }
      
      /* And so on... */
    }

At every new keyframe, colors (not offsets) have to be moved 1 index in the list. The last color of the list comes at first, and every color is pushed of one slot to the right. So in the end, we have the same number of shadows with the same offsets except their color change.

Building the array of colors

Because of this, we need a list of colors as long as the number of shadows we want to output. If we want to use 50 shadows, we need a list of 50 colors. Creating this list manually would be a pain in the butt, so we create a function for this.

The goal of this function is to turn a list of colors into a list of colors. But the returned list should match the length we want so we can turn a list of 5 colors into a list of 50. Like this:

$given-colors: tomato yellow green blue purple;
    $returned-colors: create-list($colors);
    /*
    $returned-colors: tomato, tomato, tomato, tomato, tomato, tomato, tomato, tomato, tomato, tomato,
                      yellow, yellow, yellow, yellow, yellow, yellow, yellow, yellow, yellow, yellow, 
                      green, green, green, green, green, green, green, green, green, green, 
                      blue, blue, blue, blue, blue, blue, blue, blue, blue, blue, 
                      purple, purple, purple, purple, purple, purple, purple, purple, purple, purple;
    */

Unfortunately, I realized 50 shadows is not always a good number for this animation. It occurred to me depending on the number of colors you want to run, the animation may not be quite well completed; sometimes the colors just "jump". This is because we need the shadows from the last keyframe to match the shadows from the first.

To sum up, we need to find a number which is:

• lesser than or equals to 50 (number of keyframes)
• a multiple of the length of the color list (to make the animation loop without any jump)
• the closest to 50 as possible (to make the animation as fluid as possible)

So let's say we have a list of 6 elements, the function should return 8 (because 9 would go over 50 since 9 * 6 = 54). A list of 7 elements should return 7 (because 7 * 7 = 49). You get the idea.

@function define-max($n) {
      @for $i from 1 through 50 {
        @if $i * $n > 50 {
          @return $i - 1;
        }
      }
    }

Now back to our create-list() function. We have a list of a couple of colors and want to turn it into a list of about 50 colors? Okay, great.

@function create-list($colors) {
      $max: define-max( length($colors) );
      $l: ();
      @each $c in $colors {
        @for $i from 1 through $max {
          $l: append($l, $c);
        }
      }
      @return $l;
    }

The mixin

Okaaaaaay! So all we did until now was create a function to turn a list of colors into a longer list of colors. Let's dig into the mixin.

@mixin crazy-rainbow($n, $colors) {
      $colors: create-list($colors);
      $ts: (); 
          
      @for $i from 1 through length($colors) {
        $n: if($n > length($colors) or $n == 0, 1, $n);
            
        $ts: $ts, $i*2px $i*2px 0 nth($colors, $n);
            
        $n: $n + 1;
      }
          
      text-shadow: $ts;
    }

Same as earlier, we define a $ts empty list to store all our shadows. Then we enter the loop to add a shadow to our $ts list every time before moving the pointer of 1 index to the right ($n: $n + 1). If the index goes out of list range, we move it back to 1.

It works! Let's sum up what we did:

1. We computed the number of shadows (X) we needed to output based on the number of colors we wanted to run. This is only to make the animation loop correctly without any visual glitch.
2. We generated a big array of X colors based on the number we previously computed and on the list of colors we wanted to run.
3. At every keyframe we output X shadows starting from a different index in the array every time. This is what makes the colors move.

Improvings bits

Now that we're done with all the mechanics, we can improve things a little bit. Why not make a metafizzy mixin assigning a couple of styles to our element?

@mixin metafizzy($size, $duration: 10s) {
      font-family: 'MetafizzyLogoRegular', cursive;
      color: white;
      line-height: .9em;
      font-weight: normal;
      font-size: $size;
      animation: text-3d-animation $duration linear infinite;  
      
      &:hover {
        animation: crazy-rainbow-animation 1s linear infinite; 
        animation-direction: reverse; 
      }
    }

This mixin defines all the typography stuff, including the font family (you'll need font files though), font size, font weight, line height and so on.

Let's keep going. What about a mixin to generate our two keyframes animations? We could pass it the color list we want to use on hover.

@mixin metafizzy-animations($hover-colors) {
      @keyframes text-3d {
        @for $i from 0 through 10 {
          #{$i*10%} {
            @include text-3d($i * 36); 
          }
        }
      }  
    
      @keyframes crazy-rainbow {      
        @for $i from 1 through 50 {
          0% { 
           @include crazy-rainbow(50, $hover-colors); 
          } 
          #{$i*2%} {
           @include crazy-rainbow($i, $hover-colors);
          }
        }
      }
    }

Unfortunately, we can't include this mixin in the metafizzy one since the latter is included inside a selector (like h1). Actually we can do it, but this won't work; the @keyframes animations will be outputed inside the selector and not at root of document.

In Sass 3.3, we will have the @at-root directive that will make this kind of thing possible (@directive bubbling), but for now this isn't possible so we have to include it at root.

Usage & demo

@include metafizzy-animations(red orangered yellow lightgreen green deepskyblue);
    
    h1 {
      @include metafizzy(25em, 5s);  
      /* Other styles that please you */   
    }

Done. That's all I got folks, hope you liked it and thanks for reading!

See the Pen SCSS version of Meta Fizzy by Hugo Giraudel (@HugoGiraudel) on CodePen

MetaFizzy Effect with Sass is a post from CSS-Tricks

Flying somewhere over the Atlantic Ocean, I wondered if I was making the right decision.

I had just spent two weeks away from my business on my honeymoon, and the net result of my thoughts led me to believe that selling my web design business was the best chance I had at making a difference in the world.

What made this line of thinking strange was that my web agency, HotPress Web, was growing more and more successful every day.

The web agency had made the Top 25 Denver Web Company list for five years running.

Our revenues were growing by 40-50% each year.

I was taking home some nice profits.

My clients spanned the globe, I was getting speaking requests to share my story from companies like Adobe, and our client roster consisted of really awesome brands.

Leaning back in my airplane seat, I kept focusing on the vision of the next company I was soon to build: Create 1 million experts in the world.

I wouldn’t be able to achieve that mission if I had HotPress on my hands as well.

"Yes, selling HotPress is the only option," I decided.

High School Detention

The year was 1999 and I was a really big nerd. I carried a C++ book around with me. I was addicted to computers and had no shame about it. Instead of working on school assignments, I spent my nights building PHP apps to keep track of our LAN party registrations.

At the time, I had been running a small PC gaming website which I was having a hard time monetizing. It was my hobby in high school, but the server costs were outpacing my weekend job of stocking inventory at a local fabric store.

I needed to figure out how to make money doing web design.

After a quibble with my calculus teacher about an ambiguously written test question, I was banished to a day of lunch detention. Apparently I "didn’t have the right attitude."

Sitting in lunch detention, a guy I had been an acquaintance with for awhile, Steve Thiel, was sitting across from me.

We got to talking, and it turned out that he was making some money online by selling email lists. I told him about some of the stuff I was doing and we decided it would be a good idea to go into business together.

Fast-forward thirteen years: Steve and I had founded and started three companies together, two had failed, and the most recent, HotPress Web, was becoming a big success.

Why I Sold a Profitable Company

My primary customers for HotPress were small business owners and non-profits. A typical project brought in $5,000 to $30,000 paid up front, with some kind of ongoing maintenance, support, and marketing contract in the range of $100 to $2,000 per month.

In 2010, we launched a website called BC Gurus to help train people on how to build and sell on Adobe Business Catalyst.

BC Gurus had a completely different type of customer. BC Gurus customers weren’t looking for us to build something or market for them. They were typically like us by profession — they were web designers, web agencies, web developers, etc. — looking for education on how we built websites and how we did marketing for our HotPress clients.

In our spare time, we would work on BC Gurus. Everyone at HotPress had a day-to-day operations role that supported it.

As a Managing Partner at HotPress, I tried to connect the dots for everyone, but with competing priorities, most of my team was left working long hours to meet the demands of both sides of the company.

What’s more: I was also losing touch with our company’s vision.

We were all running on fumes and a lack of focus kept everyone from reaching their potential.

So I took this problem to an adviser of mine.

My adviser identified that I had two distinct customer segments. "This type of business is complicated to run and makes your centralized marketing message and internal directing very difficult," he said to me. "The pains of small business owners and of web designers are very different. It’s one thing to have a similar product and service that you sell to different markets, but your core service and product is completely different for each market."

"You are the cowboy riding two horses at the same time, which is fine if both horses are riding the same direction. But if one veers a hard right, you might be left with your face in the dirt."

Another indicator that alarmed me was our revenue numbers.

When we focused on the service side of the business (HotPress), those revenues would increase and product revenues would decrease.

When we focused on the product side of the business (BC Gurus), product revenues would increase and service revenues would decrease.

Not only did it affect company revenue overall, but customer happiness was also affected by the yin and yang swings. When my time would shift to BC Gurus, I would start to see fires pop up with HotPress. When I would shift to HotPress, customer complaints with BC Gurus would flair up.

I realized that focus was at the root of all major successes, and that most failures are due to a lack thereof.

Gaining Clarity

So what I did next was what anyone in this situation should do: I got married and took two weeks completely off to sit on the beach in St. Lucia and ponder my goals and have the most amazing time of my life.

But in all seriousness, getting out of the daily operations of my business was a major boon for vision development.

Imagine for a second you climb out from a forest and up to the top of a mountain peak. There I sat, looking out in the distance. From this vantage point, I was able to look out at the other peaks.

While I wasn’t actively working during my honeymoon, I was running through scenarios of how I was going to make a dent in the universe.

My brain was passively crunching through paths to tall peaks in the distance, and each of them had nothing to do with growing a thriving service business.

I wanted scale.

I wanted to do something that helped make the world a better place.

So I looked at my existing business. There were two halves: one side that received dollars in exchange for hours, and the other side that received dollars in exchange for knowledge.

One side could scale. The other side, not so much.

I realized that if I wanted to make a difference in this world, I needed to craft a plan to help expand my Guru-vision beyond Adobe Business Catalyst and into the general web professional market, and then later into other markets outside of the Web industry.

Over the course of a couple of days, I wrote out a plan to overhaul our business and re-gear toward this greater vision. It went something like this:

1. Pitch the new business direction to the team
2. Make sure everyone is on board with the new direction
3. Close out all outstanding web agency work
4. Find a buyer for HotPress and sell it
5. Incorporate as new venture, carrying over BC Gurus as one of our products
6. Launch products to help web designers become more successful via uGurus
7. Help experts in other markets become Gurus by helping them launch their own products

The Sale

During my web agency tenure, I had bought and sold several books of business, essentially acquiring or selling a list of hosting and maintenance accounts.

Each of these deals taught me one thing: Valuation is almost entirely based on existing client maintenance and recurring revenue streams, not new project revenue.

Service brands are a dime a dozen. Often it’s the people in the business that have the relationships and drive the new revenue for that business. So if those people leave, we can assume revenues will drop greatly.

On each acquisition deal I did, I was able to drive the asking price down to what revenue would be on the books if zero new sales happened.

Basically, I ignored a web design company’s new project revenue when creating my valuation of that book of business.

At the time, a big chunk of our revenue definitely came from new project work. This was work that I was out winning through networking, speaking, and blogging.

If I left, then most of this revenue disappeared.

But in 2007, we had drawn a line in the sand around recurring revenue. Our mission at that time was to build up a recurring revenue stream that accounted for at least 50% of our total revenue base. While we didn’t end up accomplishing that, because our project revenue growth way outpaced our expectations, we did end up growing a really healthy list of recurring accounts.

That was what gave our web design business its value. I was able to show on paper exactly how much net earnings were coming in over the next twelve months without any additional projects. I used that as a basis and then applied a multiplier in order to come up with a valuation.

I was willing to take a lower multiplier if the offer was cash delivered on day 1, and a higher multiplier if the cash was delivered over a one or two year term.

I was able to find multiple potential buyers (which is always a good thing), but I ended up deciding to avoid a bidding war amongst them.

One of the buyers was a better match for our customers, which was one of my top priorities in the sale. I didn’t want to put my customers in a bind by the decision I had made to move on.

Ultimately, the transaction required a little legal glue, but it was pretty straightforward.

The Transition

Once the deal was done, the transition was the next biggest hurdle.

Most everything happened pretty quickly: exchange of accounts, key client introductions, support access, asset transfers, and client briefs.

Some issues dragged out a bit, mostly related to open projects and things that had been stuck in limbo.

It’s important to note that I didn’t sell our physical assets. I only sold our revenue streams. My team, IP, office equipment, and liabilities stayed with our legal entity so we could bring what we needed to our next venture.

The biggest hurdle to the transition was with my own team. Stepping into the shoes of my team, I recognize that they were really brave.

To hear them say "sounds good" when I told them that we were doing a completely 180^o by selling half the business and working together in a completely new capacity was pretty damn cool.

Instead of making a group presentation, I decided to take each team member out of the office and present the new business individually. It took about five hours per person and allowed me a chance to fully explain how I saw each team member fitting into the new structure.

Only one member of our team decided that the opportunity wasn’t for them. The rest stayed.

Since our existing product revenue didn’t fully support our current monthly cash burn rate, I needed to find some investors to help bridge the gap. Part of our asset sale helped this, but it wasn’t enough to give me the runway I needed.

Prior to selling the web agency, I had worked really hard to line up pitch meetings. Maybe in another post I’ll detail how I went about finding a group of seed investors, but the short version is I did it in record time.

I secured funding, locked in the new venture, and for most of my team, they hardly missed a beat.

The company sale transition took resources for about three months before almost completely tapering off to maybe one or two emails a month requesting details. Now it has slowed to about one request every two months.

Most of my clients were close contacts of mine; so I’ve had no issue providing them with follow-on support to make sure that they are all taken care of.

Is Focus Worth It?

I’m writing this about a year out from the genesis of what I think is a great vision to change how the world shares knowledge.

Internally in the company, a lot has changed.

First, I got rid of all of our company phones and our collaboration is now completely virtual. I still have an office for uGurus, but our team has the option to work from home if they want.

Second, there’s something truly energizing about a bunch of people working toward a greater good. Before, with the web design business, we were each off in our own little silos working on various projects and only coming together to collaborate occasionally.

Collaboration is now a daily ritual. Each spoke helps our wheel ride smoothly, and in the right direction.

Our energy is organized around launches and releases. I create celebrations around these so that everyone knows how important they are, and I regularly remind the team of the goal we are working toward.

Third, culture only matters if there are numbers to back up the work we are doing. Here’s how our monthly product revenue looks:

By focusing on our product business and a single type of customer, we have created a snowball effect for our revenue growth. Our old business required more team members the more revenue we wanted to get to (dollar in, hour out). Whereas now, it’s all about innovation, problem-solving, and reaching a great market with a great product.

It’s less about how much we work and more about how we work. Although, I have to say, since being able to focus on a single idea, every single person on my team, including myself, has been putting in more hours than we used to.

What matters the most is that our customers get a lot more of our attention. Instead of being split between a bunch of different types of priorities, everything flows toward them now.

We get to invest more time, money, and energy into helping make our customers a success. And they feel it. That’s probably one of the biggest reasons we’ve seen a dramatic increase in our product revenues.

Focus drives execution. Since making the transition, we have been able to:

• Completely overhaul our flagship site, BC Gurus
• Build our own CMS/e-commerce/marketing engine
• Launch a new blog in the general web professional market on uGurus.com
• Launch our first paid product helping web designers sell
• Launch a product teaching people how to make money with peer to peer lending
• Ink JV and affiliate deals with some of the biggest players on the Web

I have big things in store that are just beginning to catch momentum for all of our products, but so far everything has shaped together nicely post-sale.

One million Gurus is the flag I have planted into the ground, and the further I get on this journey, the more possible it becomes (even though it sounds totally insane).

Parting Thoughts

I’m not suggesting that every web designer out there should start thinking about how they can sell their business and start a product venture. However, what I have seen in the market is a maturity that leads to that as an option.

I wouldn’t be able to execute ideas at the level I can today if I didn’t have thirteen years of web project and client experience. My ideas about developing a product came out of that experience.

For a long time, I was straddling two businesses and wasn’t sure which to jump on full time. This method of bridging a service business into a product business is not a new idea.

Building websites for people is great because you can earn revenue on day one. When you get your first deal, someone pays you up front, you do the work, and when you finish they pay you some more. If you know what you’re doing, you will also build in a recurring revenue stream for yourself that will grow over time.

Selling a product is different because you have to do all of your work up front and then hope that someone decides to actually purchase what you made.

In most cases, the product requires some kind of initial investment. In my case, I have a team of eight people. I don’t want to be in a situation where a launch fails and everyone has to go home without a job.

If you are a bootstrapped web designer without a lot of cash in the bank, then you can use your skills to earn revenue and meddle with product ideas on the side. If something catches on, like it did for me, you can take a chance and run with it full-time.

If you’re struggling to come up with an idea of what kind of product to build, regularly brainstorm about the pains and problems you experience throughout your professional day. Try solving those problems by scratching your own itch. Then work to find other people who might be interested in paying you a little money to get that same problem solved.

Related Content

• 10 Myths about Startups
• 5 Pricing Tips to Earn More on Client Projects
• How I Earned A Lot More on Projects by Changing My Pricing Strategy
• Related categories: Business and Web Design

About the Author

Brent Weaver is the CEO of uGurus, a knowledge-hub helping web professionals become more profitable. For the last sixteen years he has dedicated himself to selling websites and online marketing solutions. Follow him on Twitter: @brentweaver.

The post What It’s Like to Sell Your Web Design Company appeared first on Six Revisions.

The inspiration for Apple’s color scheme in the iOS7 beta design has been a jealously guarded secret for months.

Jony Ive, known for his rational, logical approach to design doesn’t pull things like colors out of his hat. Where then, can Apple’s design guru have drawn inspiration for the iOS7 color scheme from? And why, did so many of us feel such irrational frustration the moment we laid eyes on it?

Finally, after what we can only presume was months of gruelling research and reverse engineering carried out in a secure research facility, designer Max Wohlleber thinks he’s found the answer; view his video evidence below.

If nothing else, it explains the collective sound of thousands of foreheads hitting desks the moment the new color scheme was revealed.

Where do you think Jony Ive found inspiration for the iOS7 color scheme? Do you hope it changes before the final release? Let us know in the comments.

50 High-Quality Texture Backgrounds – only $10!