Would like some judgement from a design perspective. Praise appreciated, criticism very much encouraged. Plan to revise my code with your recommendations to make my portfolio look nicer.
Why donât you give a scroll-behavior smooth to your html on the documentation website?
It will make the navigation smooth when clicking on the nav links. Speaking of which, itâd be nice if you make the nav-links look like a button.
@martinrombach88, some feedback. First off, itâs very time consuming to go through all of one personâs projects at once. Would have been better to have submitted them as you finished. Plus, it would have prevented you from making the same coding errors.
Learn to do all your styling externally.
I canât tell if you know how to do internal styling correctly because a lot of the basic elements are missing. Yes, I know codepen only expects the code youâd place in the body element but it also expects html code in one section and css in another.
@germanbobadilla@Roma Thanks for the feedback, I appreciate it. Iâll repost when Iâm happy with them. If you have time for more feedback when I do itâs always appreciated. Sorry to post all at once roma.
Here is a link for the cleaned Tribute Page. All HTML issues from the Markup Validation Service were fixed. No br, and I moved the css to the styles page.
I removed a Youtube video at the bottom of the page and replaced it with a link, I found it very difficult to find the Javascript for a responsive Youtube video that didnât look oversized on the page. Felt sad to do it, but the Tribute Page isnât about Javascript.
I made the margins and fonts change for the text depending on the max-width of the view port (740px and 420px).
The tribute page looks good @martinrombach88. Just a few things to mention;
The link to the font and the stylesheet belongs in the head element, not in the body. The link to the test script, because itâs JS, would normally go right before the closing body tag.
When using an external stylesheet you donât need the style element. And trust me when I tell you, you donât want them in codepen. They can cause an issue.
That being said, codepen provides the boilerplate for you. It only expects the code youâd put within the body element in HTML. (No need to include the body tags). For anything you want to add to <head> click on the âSettingsâ button, then HTML and add it into the âStuff for <head>â box.
The link to a font would go in the box labeled âStuff for <head>â . Thereâs not need to link to the stylesheet as thatâs part of codepenâs boilerplate.
Not sure if you noticed but even though youâre using the <strong> tag the text on your page doesnât render as such. This is because when you linked your font you only selected regular (regular 400). Go back to google fonts and add the âbold 700â to the one you have chosen and paste in the new link. Youâll see the difference it makes to your page.
Let me know if thatâs not clear.
This is a side note. You can incorporate it or not. Movie titles, book titles, a television series, are italicized in print. Shorter works like short stories, poems, and articles go in quotes. Episode titles within longer works are put in quotes.
In the future, if you want to import the same font with two (or more) different weights, just select them at the same time and youâll have them in one link. Like so; <link href="https://fonts.googleapis.com/css2?family=Baloo+Bhaina+2:wght@400;700&display=swap" rel="stylesheet">
Why donât you give it a nice background to whatâs holding the form? Or a box-shadow to the form. Make the colors be equal or similar to the main color of the image.
Then you can justify your elements inside the form to the left. Your radios and checkboxes.
Did you know that you can group elements as a column using flex display? Search: How to flex items in columns and youâll see how many things you can do with all those elements.