E34: BrowserHistory with Semantic UI

Prior to starting this WOD, you should merge your ‘columns’ branch from BrowserHistory3 back into master.

Also, be sure to have gone through the Semantic UI Hello World reading.

In this WOD, you will use Semantic UI to create a three column layout and a navbar. When finished, it should look like this (click to see full size):


  1. Start your timer.

  2. Create a branch off your local browserhistory repo master branch called ‘semantic-1’, and checkout that branch locally. You will do your work for this WOD in that branch. (If you are doing it for the second time, name it ‘semantic-2’.)

  3. You will not use LiveReload for this WOD. Instead, use the Chrome Preview facility within IntelliJ IDEA

  4. Load the Semantic UI and JQuery files following the instructions in Semantic UI Hello World. You can delete the google fonts link element. Keep the style.css link, but delete its contents.

  5. Wrap the page in a Semantic UI Container to improve the margins.

  6. Convert the navigation bar into a Semantic UI Menu. The menu elements should link to the appropriate places in the text as before. Use the “fixed top inverted four item menu” classes.

  7. You’ll notice that the page title is now hidden under the menu. Add 50px of margin to the body element to make the page title visible.

  8. You’ll now notice that the page title font’s color is black, while the other section titles are blue. Figure out the hexadecimal code for that blue color, then style the title to match that color.

  9. Use Semantic UI Image to float the three logos. Try “ui floated left image”.

  10. Use Semantic UI Grid to put the three browser descriptions into columns. Surround those sections with a “ui equal width grid”, then surround each interior section with a “ui column”.

  11. Get rid of the extraneous divs referencing the classes from BrowserHistory3.

  12. Check to see that your page looks like the screen image above.

  13. Now commit your branch to GitHub, and check to see that it’s there.

  14. Stop your timer and record your time. Be sure to record it, because you will need your WOD time data when you write your technical essay.

Rx: <15 min Av: 15-20 min Sd: 20-25 min DNF: 25+ min


Once you’ve finished doing the WOD a single time, watch me do it:

Standard WOD Caveats

You’ll learn significantly less from watching me solve the WOD if you haven’t attempted the WOD yourself first.

While it’s an achievement to finish the WOD no matter how long it takes, you might experience “diminishing returns” if you work longer than the DNF time. Thus, it is usually strategic to stop working at the DNF time and watch my solution.

After watching my solution, I recommend that you repeat the WOD if you have not achieved at least Av performance. If so, be sure to:

Feel free to keep trying until you make Rx if that’s of interest to you.

Submission Instructions

By the time and date indicated on the Schedule page, submit this assignment via Laulima.

Your submission should contain:

You will receive full credit for this practice WOD as long as you have attempted it at least once and submitted the email with all required data before the due date. Your code does not have to run perfectly for you to receive full credit. However, if you do not repeat each practice WOD until you can finish it successfully in at least AV time, you are unlikely to do well on the in-class WOD. To reduce the stress associated with this course, I recommend that you repeat each practice WOD as many times as necessary to achieve at least AV before its due date.