DRAFT: Edit content field and remove type field from [INSERT FILE NAME HERE].yml file

[SAUMILDHANKAR]

Prerequisite

1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page.
2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

We want to edit the content and remove type texts from the [INSERT FILE NAME HERE].yml file so they can be better utilized in the credits.html file. This issue is tracked in the epic #2775.

Action Items

For the file _data/internal/credits/[INSERT FILE NAME HERE].yml, do the following:

• Change line [ADD LINE NUMBER WHICH HAS CONTENT] for the content field from

  content: [INSERT THE CURRENT TEXT ON THE FILE HERE]
  

  to

  content-type: image
  

• Remove line [ADD LINE NUMBER WHICH HAS TYPE] for the type field

  type: [INSERT THE CURRENT TEXT ON THE FILE HERE]
  

Resources/Instructions

File and Code links you will need to work on this issue

• Directory to find the page in once you have it in your IDE: _data/internal/credits/[INSERT FILE NAME HERE].yml

• Click on the links below to see the source file code:
  [INSERT PERMALINK FOR THE LINE NUMBER WHICH HAS CONTENT]
  [INSERT PERMALINK FOR THE LINE NUMBER WHICH HAS TYPE]

[github-actions]

Hi @SAUMILDHANKAR.

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

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 Milestone" label once it is ready for prioritization.

Additional Resources:

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

[JessicaLucindaCheng]

This was created to draft a template before actually creating it in the issues templates. Since the template has been created, this issue can be closed.