Add a "pronouns" field
mynnx opened this issue · 2 comments
I would like to express my support for adding a pronoun field to the json-resume schema. In our increasingly diverse and globally-connected professional landscape, it is essential to recognize and respect personal identity, which includes the use of correct pronouns.
Including a pronoun field would not only be an acknowledgement of inclusivity in the professional environment but also provide clarity when individuals are referred to in recommendations, introductions, and in work-related communications. This change would allow people to be addressed appropriately without the need for assumptions or the awkwardness that can come from incorrect guessing.
I suggest the pronoun field should be an optional string to accommodate the vast array of pronouns used by individuals worldwide. In the spirit of the json-resume project, which seeks to standardize how resumes are shared and understood digitally, including this field reflects the evolution of how we understand and respect each other in professional contexts.
Here’s how it might look in the schema:
{
"basics": {
"name": "Jane Doe",
"label": "Programmer",
"pronouns": "she/her",
// other fields...
}
// additional sections...
}
I recognize that this is a duplicate of #447. To respond to @thomasdavis's comment about the lack of demand for this feature, #447 was the most-popular request for this repo before its closure. With regard to demand amongst theme developers, as a (queer) developer I anticipate becoming a theme developer because there are no themes that will display my pronouns prominently if they're stored in meta
.
Considering that the odds are slim that this feature will ever land (due to arbitrary "politics" holding it back), and issues on the topic keep getting closed, I threw together a fork. I plan to maintain it basically until kingdom come or the pronouns field gets standardized properly here, so use it in the meantime if you'd like. Or fork your own! I don't care, lol.
I listed some quick thoughts on why I personally think basics.pronouns
would be a valuable addition to the spec in this PR on that fork.
(Forgive my rudeness in sharing about a fork here. I have no idea yet what the polite convention is for "I think things need improved, this project doesn't want to change, so here's my own fork in case it's helpful for someone" kinds of things on GitHub. 😅)