Skip to content

Content Audit: Add the Our Locations Information to the About Page #8431

@kimberlyvaldez07

Description

@kimberlyvaldez07

Overview

We need add the Our Locations information from the events page to the About Us page to highlight that we were an active in person organization that moved to remote meetings.

Details

Since Covid 19 shutdowns are no longer active and the team is no longer doing regular in person meetups, we can modify this information and add it to the About page

Chatgpt mockup of new About page section Image

Action Items

  • Identify the Our Locations section from the events page (resource 1.03).
  • Create an html card for the `Our Locations' section in the folder for the about page (resource 1.04).
    card name
    about-card-our-locations.html
    
  • Use the content from resource 1.03 and the new text/layout guidance (resource 1.06) to make the about-card-our-locations.html
    • the image for the three locations is an include referenced inside the code of resource 1.03 which you have now added to the new "about-card-our-locations.html file. That include file (resource 1.05), will need to be copied and renamed/placed in resource 1.04 directory and the reference to it corrected from

      {% include events-page/our-locations-content.html %}
      to

      {% include about-page/our-locations-images.html %}
      
  • Create a new section in the about page (resource) and have it use the include to display the content.
  • Make sure the new section is showing on the submenu (the one that follows you on the page)
  • Save/commit the changes
  • Create a pull request.
  • Remove the dependency on issue Content Audit: Remove the Our Locations Section from the Events Page #8432

Resources/Instructions

Metadata

Metadata

Assignees

No one assigned

    Labels

    Complexity: MediumP-Feature: About Ushttps://www.hackforla.org/about/P-Feature: Eventshttps://www.hackforla.org/events/ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 1ptCan be done in 4-6 hours

    Type

    No type

    Projects

    Status

    New Issue Approval

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions