A twitter clone project, built to learn front-end development skills, such as HTML, CSS, JS, jQuery, and AJAX and their back-end development skills such as Node, Express, and MongoDB.

1. Install using the npm install command.
2. Start the web server using one of the following command:
   • npm run local in development environment, or
   • node server/index.js in production environment
3. Go to http://localhost:80/ in your browser.

• Express
• Node
• body-parser
• chance
• devDependencies
  • nodemon

External libraries that were used were jQuery 2.2.3, normalize 4.1.1, and google fonts (Bungee and Source Sans Pro).

Navigation bar is composed of a fixed-positioned and height nav element with two floating elements within it. One floating left (id="logo") and the other right (id="navToggler").

<nav>
    <span id="logo">tweeter</span>
    <div id="navToggler">
    <span>
        <a>Write</a>
        a new tweet
    </span>
    <div>
        <div></div>
    </div>
    </div>
</nav>

The arrow was animated with css keyframes, where a div of fixed size and background continously moves up and down via transform: translateY property, as seen below.

#navToggler > div {
  width: 35px;
  min-height: 35px;
  background-image: url("/images/icons/double-chevron-down.svg");
  background-repeat: no-repeat;
  animation: vTranslate 1.5s infinite ease-out;
}

@keyframes vTranslate {
  0%, 100% {
    transform: translateY(50%);
  }

  45% {
    transform: translateY(-20%);
  }
}

Sliding effect was achieved via jQuery.

// Add event listener for Navbar toggle button
$('#navToggler').on('click', function(e) {
    $('#new-tweet').slideToggle();
    e.stopPropagation();
});

Simillar to the Top Nav bar, this is a fixed-positioned div element at the bottom-right corner, with a background-image. The div is only displayed when scrollTop property is is over 700px. Also, top navigation bar is hidden when the bottom one is displayed.

/*************************
* Bottom of page scroller
*************************/
#scrollUp {
  background-image: url('/images/icons/arrow-up.svg');
  background-repeat: no-repeat;
  width: 100px;
  min-height: 100px;
  margin: 20px;
  position: fixed;
  bottom: 0;
  right: 0;
  z-index: 100;
  cursor: pointer;
  display: none;
}

// bottom scroller 
$(window).scroll(function() {
    if ($(this).scrollTop() > 700) {
        $('#scrollUp').css('display', 'block');
        $('#navToggler').css('display', 'none');
    } else {
        $('#scrollUp').css('display', 'none');
        $('#navToggler').css('display', 'block');
    }
});

$('#scrollUp').on('click', function(e) {
    $('html, body').animate({scrollTop: 0}, 'fast');
    e.stopPropagation();
});

Rather than using npm moments library, an inhouse version of it was used, with the following outputs, based on the input _date, # ms from unix epoch:

• just now: if less than first 3 seconds ago.
• {x} seconds ago: if between 3 seconds to 60 seconds ago.
• {x} minutes and {y} seconds ago: if between 1 min to 6 min ago.
• {x} minutes ago: if between 6 min to 60 min ago.
• {x} hours and {y} minutes ago: if between 1h to 24h ago.
• {x} days and {h} hours ago: if between 24h to 3days ago.
• {x} days ago: if between 3 days to 1 month ago.
• {x} months ago: if between 1 month to 12 month ago.
• {x} years ago: if between over 12 monthes ago.