Content Audit: Remove the `Our Locations` Section from the Events Page

[kimberlyvaldez07]

Dependency

• Content Audit: Add the Our Locations Information to the About Page #8431 must be complete

Overview

We need to remove the Our Locations section from the events page to ensure only active events/meetups are noted.

Details

Since Covid 19 shutdowns are no longer active and the team is no longer doing regular in person meetups. Remove the entire "Our Locations" section including the title, the description section, and the images. Also remove any note of COVID 19 shut downs.

• This information will be moved to the About Us page Content Audit: Add the Our Locations Information to the About Page #8431

Action Items

• For the file /pages/events.html (resource 1.01), identify all mentions of COVID-19 and the Our Locations section, including the title, the description section, and the images.

   <h2 class="events-page-header title2">
     Our Locations
   </h2>
   
   <div class="fullwidth-background-container">
     <div class="notification-banner">
       <p class="meetings-message">
         In light of the COVID-19 pandemic, Hack for LA has suspended its in-person
         events below. The organization remains fully active, and all events are
         now being conducted remotely using Zoom at the days/times listed above.
       </p>
   </div>
  
     <div class="getting-started-mobile-page">
       <h2 class="event-title-1">
         <img class="vector-img" src="../assets/images/hack-nights/locations.svg" alt="">
         See our Locations
       </h2>
     </div>
   </div>
  
   <div class="mobile-locations-dropdown">
     {% include events-page/our-locations-content.html %}
   </div>
  

• Remove all mentions of COVID-19 and the 'Our Locations' section, including the title, the description section, and the images.
• Ensure that the section formatting is correct. The final code should look something like this

  ---
  layout: default
  title: Events - Hack for LA
  permalink: /events/
  ---
  <!--refactored javascript link-->
  <script src="/assets/js/events.js" defer></script>
  
  <!-- Google Tag Manager (noscript) -->
  <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-PMQK7VL" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
  <!-- End Google Tag Manager (noscript) -->
  <div class="header-container header-container--events">
    {% include events-page/header-container-content.html %}
  </div>
  
  <section class="events-page content-section content-section--events">
  
      <h2 class="events-page-header title2">Our Events</h2>
      <div class="flex-page-card">
        <div class="column-card-lg--events">
          {% include events-page/left-col-content.html %}
        </div>
  
        <div class="column-card-lg--events">
          {% include events-page/right-col-content.html%}
        </div>
      </div>
  
  </section>
  

• Remove the file containing the images for the Our Locations section from the _includes/events-page
  • The file being deleted is called _includes/events-page/our-locations-content.html (resource 1.02)
• Use Docker to test changes locally, in both desktop and mobile views

Resources/Instructions

• 1.01 Events code: https://github.com/hackforla/website/blob/gh-pages/pages/events.html
• 1.02 Our Locations images code: https://github.com/hackforla/website/blob/gh-pages/_includes/events-page/our-locations-content.html
• 1.03 Events page: https://www.hackforla.org/events

[github-actions]

Hi @kimberlyvaldez07.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels