Unlimited Wordpress themes, plugins, graphics & courses! Unlimited asset downloads! From $16.50/m Advertisement Finishing Off the Merry Christmas Web App Interface Length:LongLanguages: In this tutorial we will finish off our web app front-end so it all looks perfect and functions nicely on all screen sizes. Last time, we rounded off by styling the message boxes, leaving just the content left to do. Shall we dive right in? Ok! The Story so Far You may need to catch up with previous parts of this tutorial, in which case: The Message Content The declarations for message-content make sure the width behaves itself when the browser resizes. We need it to be 100% wide for small screen sizes so it sits nicely under the image. Once we hit our $break-two width we then need to float the content right and pull the width in slightly to compensate for that.

The other break points here just make sure the width scales nicely in relation to the browser width, so on a tablet-esque resolution our message-box is still stacked vertically but our message-content is floated inside of it which means the 75% width probably isn't wide enough. We pull it back to 75% width once we get to desktop-based sizes to account for message-box being floated and narrower.

The next styles here are really simple. We are just giving any links a $green colour with a $red hover state and overriding any margins set on the h3, p and div elements contained within message-content. The individual styles for the h3, p and div elements are a bit more fancy. The h3 is set to use title-font and has some letter-spacing set to just pull in the spacing slightly to more closely match the design. The div tag styles are all about keeping the contents contained, so we make sure the overflow is hidden and if there is any overflow we show an ellipsis to indicate there is more text. This kind of thing can be done with server side code (and probably would be) but it is nice to include it here in the CSS for the purpose of this tutorial. Save your work and head on over to the browser... That is looking awesome! We have three slightly different layouts going on, all of which are controlled by the simple styles above. That completes the CSS for the message-box so all we need to do now is copy the markup five times and change the content based on the design. If this app were to function for real we wouldn't need to do this, but for this tutorial needs must! Give yourself five minutes to copy, paste and change the code for each box. Let's just take another quick look in the browser to check our styles are working perfectly when we have more than one message-box... Beautiful! Our web app is definitely taking shape now and our message boxes are working as intended at all browser sizes. We have conquered most of our web app now, but there is still one important section left: the footer. This part of our app is important as it houses the place a user can type/post their message. There are some fairly tricky bits to this, so let's get started! The Footer First things first, let's write the following markup in our index.html file: There are a few sections to this footer. The main area of focus is the form in the middle which, although not necessarily needed here, will allow the user to post their message. The social-btns will need some layout changing styles and all of the footer content must be centered on the screen. Let's start at the top and get straight into the CSS... First of all we should set some padding on the footer to push everything away from the edges nicely. To get everything centered on the screen we just set the text-align property to center. The styles for the tagline/heading here are quite simple and are very similar to what we have done before for a title. Let's check this out in the browser! It's a good start but we still have a way to go! Let's carry on in our Sass file. Like many of our elements, the connect-box should be 100% wide for smaller screens. It should then switch, at our break-three point, to the width seen in the design which is 525px. We then set the background colour of the connected-as and connect-message to a light grey colour.

"Connected As" Section

This fair chunk of CSS is for the top section of our connect-box. The first step is to round off the top right and left of connected-as. We also want a slight separation between this box and the section below, so a simple 1px solid $white border will do the trick nicely. Lastly, we need some padding, but we need more on the left and right than we do on the top and bottom so to keep things nice and neat we simply use our $padding variable and divide by two for top and bottom, and multiply by two for the left and right. This is a great example of where changing our variable value will still keep everything in proportion nicely.

The next two declarations control the connected users' Twitter profile image and their @username. To keep things standard we set the width and height of the image in the CSS so we know it will always be a square of the correct size. To make it appear as a circle simply apply a border-radius of 50% to it. Both the profile image and @username should be floated left and we should give the @username some margin to push it away from the profile image.

Disconnect Button

The disconnect button has a few different things going on. At small-screen resolutions we need this button to be out of the way of the other text inside this box, so I decided a good option would be to absolutely position it just above and beyond its container. A position of -10px for the top and right is fine. You may wish to play around with this if you think it could be better placed. The other styles here control the look with a simple hover state adding a nice bold $red colour to emphasise the disconnect action. The one bit of responsiveness here will just kick the button back into the document flow and float it right so it sits opposite the Twitter details. This will happen for anything at and above our $break-two point.

Save, save, save! It's time to take a look again:

Looking good! We are getting very close to getting this finished now. Next up is the message box area.

The Message Box

This block should be placed after the connected-as block, but still inside the overall footer declarations.

The connect-message box has rounded corners on the bottom left and right to complete the appearance of the overall container having rounded corners. The textarea itself definitely needs some styling as browser defaults are down right ugly! These styles are fairly simple, but you can see we are adding a CSS Transition for box-shadow. The design didn't show what a focus state should look like so I decided to have a subtle shadow fade in all the way around the inside of the box. It then fades out when focus is lost.

Let's see it in action shall we?

I think that looks pretty good! The box-shadow may not be to your liking, so play around with that to get something you feel is right.

Post 'Thank You'

The all important Post 'Thank You' button! Quite simple styles here. The button should just fill the width of the container at all times. It should also be pushed away from the message area a bit, so some margin-top helps us here. We have another transition declaration, but this time it is set to all in order to animate every property that has a value change to keep everything smooth. This also means that in the future we can add other styles like a color change on hover and it will all still be animated.

Save the file and take another look:

Lovely. This is exactly what we want. Time to style those social media links.

Social Media Buttons

This code should go inside the footer block in our Sass file. The idea with these buttons is for them to be 100% wide and stacked vertically at mobile/tablet resolutions. Then as you move up the scale to desktop they should match the design. The media query for the social-buttons involved quite a bit of trial and error to achieve a "centered" look at desktop sizes. The value of 117px for the left padding was the point I found to give the desired result.

Each social-btn has some simple styles to give the base appearance. We then specify the styles for each button. In this app it is just a background color difference. Note here that I have used the hex value and not a Sass variable. There is no real reason for this other than this is the only place these colours are used, so changing them would not be much of an issue. If we had the social links elsewhere I definitely would have set them up as variables. Both buttons have a slightly lighter version of their backgrounds on hover.

Before we take a look, we may as well put our final style block in place:

As the name suggests, this block controls our small Copyright tag in the footer. The font-size responds to browser size changes here, showing 100% at \$break-three.

Save and take a look at our masterpiece!

Responsive Split

Nice! Everything is looking awesome and that just about wraps up our Christmas Web App Interface!

Bonus

This is a heavily seasonal theme, based on a Christmas and New Year concept. With just a little tweaking you could easily change it to suit your needs, for example:

Conclusion

I really hope you have enjoyed working through this web app with me. It was a fun project to build and I'm happy I was able to share my techniques on how to build it. The source code is always available via the download links so feel free to dig around and let me know in the comments any thoughts you have, or if any of you guys would improve it in any way.

Thanks to Tomas for the initial design, and thank you for reading and following along.