ZakharDay · May 24, 2015 10:52
diff --git a/MCS101-008-Portfolio.html b/MCS101-008-Portfolio.html
 <!DOCTYPE html>
 <html lang="ru">
 <head>
  <meta charset="UTF-8">
  <title>Portfolio</title>

  <link rel="stylesheet" href="../stylesheets/reset.css">
  <link rel="stylesheet" href="../stylesheets/reset-links.css">
  <link rel="stylesheet" href="../stylesheets/portfolio.css">
 </head>
 <body>

  <section id="about">
    <header>
      <h2>About</h2>
    </header>

    <article>
      <img id="promo" src="../images/portfolio/promo-site.jpg">

      <h3>A Powerful Promo Site</h3>
      <p>The best promotional tool is a great product. Word will get out if you've got an app that people find really useful.</p>

      <h3>Go With the Flow</h3>
      <p>Be open to new paths and changes in direction. Part of the beauty of a web app is its fluidity. You don't wrap it up in a box, ship it, and then wait years for the next release.</p>
      <p>You can tweak and change as you go along.</p>

      <img id="clock" src="../images/portfolio/clock.jpg">

      <h3>Lower Your Cost of Change</h3>
      <p>Stay flexible by reducing obstacles to change. The more expensive it is to make a change, the less likely you'll make it.</p>
      <p>If your competitors can change faster than you, you're at a huge disadvantage. If change gets too expensive, you're dead.</p>

      <h3>Interface First</h3>
      <p>Too many apps start with a program-first mentality. That's a bad idea. Programming is the heaviest component of building an app, meaning it's the most expensive and hardest to change. Instead, start by designing first.</p>
    </article>
  </section>

  <section id="portfolio">
    <header>
      <h2>Portfolio</h2>
    </header>
  </section>

  <section id="contacts">
    <a href="http://facebook.com"  id="facebook"  target="_blank"></a>
    <a href="http://instagram.com" id="instagram" target="_blank"></a>
    <a href="http://vk.com"        id="vk"        target="_blank"></a>
  </section>

 </body>
 </html>
	<!DOCTYPE html>
	<html lang="ru">
	<head>
	<meta charset="UTF-8">
	<title>Portfolio</title>

	<link rel="stylesheet" href="../stylesheets/reset.css">
	<link rel="stylesheet" href="../stylesheets/reset-links.css">
	<link rel="stylesheet" href="../stylesheets/portfolio.css">
	</head>
	<body>

	<section id="about">
	<header>
	<h2>About</h2>
	</header>

	<article>
	<img id="promo" src="../images/portfolio/promo-site.jpg">

	<h3>A Powerful Promo Site</h3>
	<p>The best promotional tool is a great product. Word will get out if you've got an app that people find really useful.</p>

	<h3>Go With the Flow</h3>
	<p>Be open to new paths and changes in direction. Part of the beauty of a web app is its fluidity. You don't wrap it up in a box, ship it, and then wait years for the next release.</p>
	<p>You can tweak and change as you go along.</p>

	<img id="clock" src="../images/portfolio/clock.jpg">

	<h3>Lower Your Cost of Change</h3>
	<p>Stay flexible by reducing obstacles to change. The more expensive it is to make a change, the less likely you'll make it.</p>
	<p>If your competitors can change faster than you, you're at a huge disadvantage. If change gets too expensive, you're dead.</p>

	<h3>Interface First</h3>
	<p>Too many apps start with a program-first mentality. That's a bad idea. Programming is the heaviest component of building an app, meaning it's the most expensive and hardest to change. Instead, start by designing first.</p>
	</article>
	</section>

	<section id="portfolio">
	<header>
	<h2>Portfolio</h2>
	</header>
	</section>

	<section id="contacts">
	<a href="http://facebook.com" id="facebook" target="_blank"></a>
	<a href="http://instagram.com" id="instagram" target="_blank"></a>
	<a href="http://vk.com" id="vk" target="_blank"></a>
	</section>

	</body>
	</html>