Base template: <footer> #1259

[heyitsmebev]

Ticket: #1259

Description

I was tasked to create a base template for the footer.

I've converted the footer from a macro-based approach to a single footer.html file, we now have a centralized location for all footer-related content, including links and the logo.

To QA

Uncomment line 252 in the admin_template.html. Check to see if logo, links and if it's responsive.

Changes Made

I kept a lot of the structure the same as before. I added lines 42-46 lines of code to the footer.html and moved the <div class="usa-identifier site-identifier"> into the footer tag

          {% if current_service and current_service.research_mode %}
            Built by the <a href="https://www.gsa.gov/about-us/organization/federal-acquisition-service/technology-transformation-services/tts-solutions" class="usa-link">Technology Transformation Services</a><span id="research-mode" class="research-mode">research mode</span>
          {% else %}
            Built by the <a href="https://www.gsa.gov/about-us/organization/federal-acquisition-service/technology-transformation-services/tts-solutions" class="usa-link">Technology Transformation Services</a>
          {% endif %}

TODO

• Create a base footer template
• Responsive

Notes for the future

• lines 179 - 251 in admin_template can all be deleted and replaced with {% include "new/components/footer/footer.html" %} when we are ready to use the new base footer template

Extra reading/context
#1259 (comment)

[terrazoon]

This will conflict with one of my open PRs to add the GitHub version to the footer, but otherwise looks good.

[ccostino]

@terrazoon it shouldn't conflict, at least not yet - this is a new footer file, not modifications to the existing one. :-)

That said, it's good to note this as a future change that will be needed here! @heyitsmebev, it might be easiest for us to hold on this just a bit until #1245 is fully reviewed and merged, then the changes can be incorporated here easily as well.

Does that sound good?

[ccostino]

Thanks, @heyitsmebev!

Noting here that this file will need to incorporate the GitHub hash that @terrazoon added to our current footer, but it's not a blocker to merging this now.