.container
element
<nav>
and it looks like this. Not sure if that's what you wanted, but it is aligned to the flex-end
.container
code block in your CSS to nav
. Alternatively, you can just apply the .container
to your nav element and remove the <div>
altogether.
@Nooy90 Let me know if that solves your issue
@sjames1958gm my bad!
// <ul> default styles
display: block;
list-style-type: disc;
margin-top: 1em;
margin-bottom: 1 em;
margin-left: 0;
margin-right: 0;
padding-left: 40px;
// from https://www.w3schools.com/cssref/css_default_values.asp
@Mdezigned Quickest solution to any problem like this:
Learn how to use Chrome DevTools
Whenever I have a problem related to styling, CSS, or Javascript, the solution is almost always solved by popping over to Chrome DevTools. Namely, the "Select An Element To Inspect" saves my life all the time. I'll attach a GIF to show you how your problem could have been solved in less than 5 seconds using DevTools.
All depends on what your goals are, if you want to be able to design your own UI's from the ground up then practice building stuff better via different techniques and what not like any artist. If you don't really care to much and are fine using existing designs then look into ones you could leverage and stick with it.
I personally totally suck at design and thus usually stick with an off the shelve UI lib and or UI guidelines. I'd rather build the functionality then design the UI
@seesykescode It depends on the job, if your just doing front-end work, usually you need to be pretty decent or at least versatile in design, as you will be building custom UI's. For people/clients that are less picky on the UI either want a lot of custom functionality, or are cheap. The cheap people are the ones that wouldn't mind someone building out their website using wordpress or wix or the like, and as such developing a site from the ground up doesn't make as much sense.
So that leaves custom functionality situations where people/clients want something along the lines of a web-app, this is where functionality and full stack comes in. So if you are ok in the UI department, but still want to stay relevant, being able to build full stack usually is the next best bet.