When updating the board elections, under the `./data/org/elections/` folder there will be a `.yml` file for each years nominees, starting with 2025. Within this file, each nominee has been defined under the base `items` property, with below being an example of the file with 1 entry. Each entry will have a corresponding image and dedicated page under the folder `./content/org/elections/{year}`, where the name of the page matches the username and the image matches what has been set in the `image` property.
```yaml
items:
webdev:
type:contributing
username:webdev
name:Eclipse Webdev
title:Developer
image:corsaro.jpg
email:dummy@eclipse-foundation.org
phone:
contact:
eclipse_affiliation:|
<ul>
<li>Eclipse Foundation</li>
<li>Eclipse Dash contributor</li>
</ul>
vision:|
<p></p>
bio:|
<p>
I'm a real person who works at the Eclipse Foundation.
</p>
affiliation:Eclipse Foundation
```
For the above properties, the following fields support HTML content for better authoring and display experience:
- affiliation
- bio
- eclipse_affiliation
- title
- vision
To keep nominee pages private while they are being finalized, the frontmatter of the page in question should have `draft: true` set in the frontmatter. Additionally, to ensure that no dead links are pushed live before ready, it is recommended that if not all nominees are ready for display, then all should be kept in draft mode, and that the `nominee-list` shortcode not be included on the nominees page.
### Declared Project Licenses
### Declared Project Licenses
This program and the accompanying materials are made available under the terms
This program and the accompanying materials are made available under the terms
