Update Credits yml file template

[JessicaLucindaCheng]

Overview

As a member of the team, we need to ensure the Wiki is an up to date and accurate resource. For this issue, we will update the Credits yml file template.

Action Items

This will be an issue worked on and discussed during development team meetings.

• Figure out why there are two name values for (content and type) which seem the same
  • You may want to see how (if anywhere) content and type are used in our code
• Update the Credits yml file template
• Release dependency on Edit content field and remove type field from 404.yml credits file #2633
  • Update action items in the dependency issue if needed

Resources/Instructions

• Credits yml file template
• pages/credits.html
• This issue might be helpful in figuring out what the difference between content and type are: Create Credits page #571

[github-actions]

Hi @JessicaLucindaCheng.

Good job adding the required labels for this issue. 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]

All action items are completed, so I'm closing this issue.

[JessicaLucindaCheng]

Note about decisions made: For the Credits yml file template, originally, it had both the content and type field, which seemed similar in terms of its use, and neither field was used in the code itself. Thus, we decided to remove the type field because only one of the fields is necessary if they contain the same information. Also, we changed the content field to the content-type field to make the field name clearer for what its purpose is, which is type of content. In addition, we decided the content-type field should be standardized to only certain choices; for now, those are image, video, or audio but other types of content can be added in the future if necessary and should be added to the template so that every credit we create will use the same values for content-type. This will allow developers a way to differentiate easily between different content types in the future and display them correctly on the website if we start using different content types.