<commit_before><!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="UTF-8" />
		<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> 
		<meta name="viewport" content="width=device-width, initial-scale=1.0"> 
		<title><NAME>, Web Designer | Process | </title>
		<meta name="description" content="I design websites that function beautifully on all screens." />
        <!--[if lt IE 9]><script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
        <script src="//use.typekit.net/wgd7qxf.js"></script>
        <script>try{Typekit.load();}catch(e){}</script>
		<link rel="stylesheet" type="text/css" href="../assets/screen.css" />
	</head>
<body class="process-page-post">

<div class="site-wrapper">

<header role="banner" class="page-header">
    <div>
        <h1>Prototyping with Web Safe Colors</h1>
        <time class="post-date" datetime="2015-06-26">26 June 2015</time>
    </div>
</header>

<main role="main" class="main">

    <section class="post-content">

        <p>These days, you can use any color you like on the web but should you? When I prototype a design, I start with old school <a href="https://en.wikipedia.org/wiki/Web_colors#Web-safe_colors">web safe color schemes</a>.</p>

        <p>For me, it’s an easy way to set some contrast and hierarchy in interface early on in the design process, especially with links and navigation and layout.</p>

        <p>Even if you end up diverging from the web safe colors you started with, it’s useful as a visual effect approximation process and results in more meaningful and more concise color schemes.</p>

        <p>Take a look at <a href="http://websafecolors.info">websafecolors.info &rarr;</a></p>

    </section>
   
</main>

</div>

<nav class="site-navigation">
<commit_msg>copy edit<commit_after><!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="UTF-8" />
		<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> 
		<meta name="viewport" content="width=device-width, initial-scale=1.0"> 
		<title><NAME>, Web Designer | Process | </title>
		<meta name="description" content="I design websites that function beautifully on all screens." />
        <!--[if lt IE 9]><script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
        <script src="//use.typekit.net/wgd7qxf.js"></script>
        <script>try{Typekit.load();}catch(e){}</script>
		<link rel="stylesheet" type="text/css" href="../assets/screen.css" />
	</head>
<body class="process-page-post">

<div class="site-wrapper">

<header role="banner" class="page-header">
    <div>
        <h1>Prototyping with Web Safe Colors</h1>
        <time class="post-date" datetime="2015-06-26">26 June 2015</time>
    </div>
</header>

<main role="main" class="main">

    <section class="post-content">

        <p>These days, you can use any color you like on the web but should you? When I prototype a design, I start with old school <a href="https://en.wikipedia.org/wiki/Web_colors#Web-safe_colors">web safe color schemes</a>.</p>

        <p>For me, it’s an easy way to set some contrast and hierarchy in interface early on in the design process, especially with links and navigation and layout.</p>

        <p>Even if you end up diverging from the web safe colors you started with, it’s useful as an approximation process and results in color schemes that are more concise, meaningful and visually effective.</p>

        <p>Take a look at <a href="http://websafecolors.info">websafecolors.info &rarr;</a></p>

    </section>
   
</main>

</div>

<nav class="site-navigation">

{'fraction_non_alphanumeric': 0.16152349179872116, 'fraction_numerical': 0.013344453711426188, 'mean_word_length': 3.8425302826379544, 'pattern_counts': {'":': 0, '<': 99, '<?xml version=': 0, '>': 99, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4220551', 'n_tokens_mistral': 1201, 'n_tokens_neox': 1123, 'n_words': 340}