DIGITAL-192: Implement job board

[cathybaptista]

Jira ticket

DIGITAL-192

Purpose

This is the first stab at making Drupal create the Digital.gov Job Board. This creates a menu for the administrator to create new jobs in the Drupal administration panel under "content." If a new job is added and is in date, it will appear in the job board on the site.

Acceptance criteria (DOD):

• Use config pages to add an administration page at /admin/content/job-board that is just a single large text area. This will allow you to paste the contents of this YAML file as is.
• Add this to the description of the text area https://docs.google.com/spreadsheets/d/1VW1IxK0KPmH11DlQbxL5Hj2qc7Y3223PDpp_t5DhcG8/edit?gid=1857335212#gid=1857335212
• Create a new role 'Job Board Manager' that has permission to access the admin page.
• Create 'job_board' theme function that takes no parameters.
• Create a job-board template that migrates the [contents of the
• Create a pre_process for job_board theme that loads the field from the config page field and turns it into an array
• Use that array to power the results, ignore the paging for now.
• Update this node template for the job board to render the job_board theme function.

Includes the following PRs that must be merged first

N/A

Deployment and testing

Local Setup

1. Pull the branch
2. Drush cim
3. lando si
4. lando drush cr/uli if needed

QA/Testing instructions

• Under the administration panel, select content to open the Job Board Administration. Add a new item to the job board.
• Verify that the new item appears in the job board.
• Remove or edit a job board item and make sure everything works fine (displays Job Board.)
• Masquerade as a job board administrator to test that this user configuration is setup and working properly.

Checklist for the Developer

• A link to the JIRA ticket has been included above.
• No merge conflicts exist with the target branch.
• Automated tests have passed on this PR.
• A reviewer has been designated.
• Deployment and testing steps have been documented above, if applicable.

Checklist for the Peer Reviewers

• The file changes are relevant to the task objective.
• Code is readable and includes appropriate commenting.
• Code standards and best practices are followed.
• QA/Test steps were successfully completed, if applicable.
• Applicable logs are free of errors.

[omerida]

I merged with the latest from dev. Config export is removing a bunch of the stuff I did for the guide navigation ...

You should be able to revert that config. Same for the autologout config and there might be more config that shouldn't be affected.