search

ajm324 / natalia

We will be analyzing Natalia Lafourcade's albums Musas Vols. 1 and 2 and Un Canto por Mexico Vol. 1 for their use of folk-inspired natural imagery in representing a connection to country and latinx identity.
0 stars 0 forks source link

Project Update 4/02 #8

Open jog141 opened 3 years ago

jog141 commented 3 years ago

Last week we were able to get everything on our list accomplished and each individual completed their deliverables. This week now is important because we are trying to set up the rest of our site so when we are equipped with the skills to conquer the the graphs and details that require more knowledge than what we have so far, the other things will be out of the way. We have delegated the tasks of linking new site pages to the CSS, formatting and adding content to the "About" page, creating a drop-down menu from each tab in the menu bar, and fixing some errors we developed with the pages in the menu bar.

gec34 commented 3 years ago

It looks like your in good shape to continue structuring your website. I really like the color scheme of your home page, it's very visually appealing. It's a good idea to start adding more content to the site through the About page since it's not necessarily subject to drastic change as you spend time analyzing your results. I'm excited to see how the site continues to develop as well as some conquered graphs.

otakunaomi commented 3 years ago

Looks like your group has a good idea when it comes down to the layout of your website. My group had a similar type of layout with a drop down menu. Each page will most likely have similar CSS, but based off the specific page some parts may need to be added (this is why my group made each page have its own css in case any additions needed to be made for a specific page). It might be good to also start thinking about formatting an XSLT for your xml documents, which would be beneficial for one of your pages I am assuming.

djbpitt commented 3 years ago

@otakunaomi If most of your pages will have largely the same CSS (which is recommended for providing internal consistency), sometimes with small, page-specific modifications, the recommended way to do that is to put all of the general project formatting in a single main CSS page and link all HTML pages to it. Then, within the individual HTML pages, you can also link to a second, page-specific CSS stylesheet that specifies only the page-specific features. (If the page-specific features are very slight, it might be easier to put them inside a <style> element inside the <head> of the HTML). CSS rules specified in a <style> element have a higher precedence than imported stylesheets, and if multiple imported stylesheets define rules for the same selectors, the last CSS stylesheet loaded wins. This means that you can easily override the defaults (specified in the main, shared stylesheet) with page-specific modifications.

This approach is preferable to having completely separate CSS for all pages because if you have completely separate CSS and want to change any of the shared styling (which will normally be most of your styling), you have to make the changes separately in every CSS file. If you use a shared file for the general site formatting that the pages all have in common, you would have to make that modification in only one place. There's also a small benefit in using a shared CSS file for most of your styling where it comes to the time it takes a page to load, since once your browser has downloaded the shared file, it won't have to download it again when it's linked to a different page.

otakunaomi commented 3 years ago

@djbpitt That is helpful to know, thank you!