Persona Library 1.0

This merge includes:
- reference library of articles, books, tools, and videos about persona development
- persona library system for a schema-based persona definition and basic tooling
- personas for the DevRel Foundation as an example persona set
- getting started guide
- guide to using personas for content
- glossary
- contribution guide

Author: j12y

.gitignore

@@ -1,3 +1,6 @@
+# Build
+build/
+
 # Logs
 logs
 *.log

CONTRIBUTING.md

@@ -0,0 +1,104 @@
+
+# Contributing to the Persona Library
+
+We're glad to have you here and reading this because our efforts are supported by volunteers. Thank you for taking the time to contribute your expertise to the DevRel Foundation Persona Library project.
+
+This document describes some contribution guidelines for the project.
+
+> [!IMPORTANT]
+> Before you start contributing, you must read and abide by our
+> **[Code of Conduct](./CODE_OF_CONDUCT.md)**.
+
+You should also join the working group by subscribing here:
+https://lists.dev-rel.org/g/wg-resource-aggregation
+
+You'll find it easier to make contributions if you already have a GitHub account.
+
+## Types of Contributions
+
+Contribution can take several forms.
+
+**Discuss**. Joining our working group calls and sharing your opinions and expertise is a form of contribution. It keeps our group engaging and making forward progress to hear thoughts from others.
+
+**Shoutouts**. Let us know that you found resources here helpful and we'll include your show of appreciation in our testimonials.
+
+**Feedback**. Have a suggestion, let us know how to improve.
+
+**References**. If you know of a reference item (article, course, book, video, etc.) we will include it in the collection. This can be provided by creating an issue, sending an email to the working group owners, or best case is to fork the repos and submit a PR for review.
+
+**Persona**. If you've developed personas using the Persona Library System schema and are willing to share anything that is not a trade secret, the examples and user / buyer / developer insights will be appreciated by all. You can identify them as a persona set, or it might be an addition or update to a persona from the general collection. Submit an issue, send an email to the working group owners, or best case is to fork the repos and submit a PR for review.
+
+**Schema and Tools**. The schema and tools provide value to all. If you have suggestions on how to improve the schema, add additional tooling, or want to contribute an integration to a visualization or other system of record those would be welcome.
+
+## How-to Make a Contribution
+
+Choose the approach that is easiest for you. 
+
+1. Send an email to wg-resource-aggregation + owner AT lists.dev-rel.org to reach the managers who can take action on your suggestions.
+2. Start a **New Discussion** in the [GitHub Discussions](https://github.com/DevRel-Foundation/wg-resource-aggregation/discussions). There is a category for feedback and one for the Persona Library more specifically. This is a great place to ask a question if unsure.
+3. Create an **Issue** in the [GitHub Issues](https://github.com/DevRel-Foundation/wg-resource-aggregation/issues?q=is%3Aissue%20state%3Aopen%20label%3Aresource%3Apersonas) for the project with the `resource:personas` label.
+4. Assign an **Issue** to yourself or put in a PR using typical GitHub workflows for change requests.
+
+## What Should You Contribute
+
+Review the [Open GitHub Issues](https://github.com/DevRel-Foundation/wg-resource-aggregation/issues?q=is%3Aissue%20state%3Aopen%20label%3Aresource%3Apersonas) with the label `resource:personas` for some ideas. If there are tags with `good-first-issue` this helps identify smaller projects that have fewer dependencies so somebody new to the working group can pitch in.
+
+## How-to Get Help Contributing
+
+Use GitHub Discussions, Discord, or join one of our monthly working group calls to brainstorm and ask questions about how to contribute.
+
+# Orientation
+
+This section includes some additional details to help orient new contributors.
+
+## Build Environment
+
+The tools are currently JavaScript / Node.
+
+## File Structure
+
+### `/bin` 
+
+This folder contains shell scripts to execute tool commands. The logic of the commands will typically be under `/src` but this is something you might include in your `$PATH`.
+
+### `/data` 
+
+This folder contains the JSON configuration data that defines personas and references.
+
+- `/data/personas` is the general collection
+- `/data/reference` holds reference material from third-party sources
+- `/data/sets` are persona sets for different organizations / projects
+
+### `/docs`
+
+This folder contains documentation about the persona library.
+
+- `/docs/guides` are the tutorials
+- `/docs/reference` are built from the reference data
+- `/docs/traits` define various traits to support the schema definition descriptions
+
+### `/src`
+
+This folder contains the source code and schemas.
+
+## Review Process
+
+Our review process is informal so we'll add guidelines here as we learn. We maintain the right to refuse accepting any content deemed inappropriate by a two-thirds working group manager vote.
+
+### 1. Promotional Materials
+
+We want content that adds educational value to our audience. If it is deemed promotional in nature and requires purchase of a product or service then a submission may not be accepted.
+
+### 2. Paywalled Materials
+
+We want content that is accessible in the library. If access to a resource requires disclosing personal information or consuming advertisements as a condition for access then it may not be accepted.
+
+# Thank You!!
+
+We really do appreciate our contributors. We'll identify participants here who have made a significant contribution to this library.
+
+- Jayson DeLancey ([@j12y](https://github.com/j12y)) for contributing to the original design, schema, and resources of the Persona Library System.
+- *Your name could be here next.*
+
+https://github.com/DevRel-Foundation/persona-library/graphs/contributors
+

README.md

@@ -1,20 +1,76 @@
 # Persona Library
 
-A **persona** represents the type of user that may or may not engage with a product or service. The value of a persona comes from using it to align a business around expectations for current and potential buyers or customers.
+The **Persona Library** is a [DevRel Foundation](https://github.com/DevRel-Foundation) (DRF) initiative to collect resources related to the development of personas. A **persona** represents the type of user that may engage with a product, service, project or organization. The value of defining personas comes from using them to align an organization around expectations of current and potential consumers and plan a strategy for their tactics.
+
+Through the use of personas, as DevRel practioners, we can accelerate day-to-day decision-making for common operational activities.
 
 * [Requirements and Use Cases](https://github.com/DevRel-Foundation/wg-resource-aggregation/discussions/46)
+* [Glossary](./docs/reference/glossary.md) ([src](./data/reference/glossary.json))
+
+## Persona Reference Library
+
+The reference library contains links to third-party resources that may help in a deeper study of the process of creating and managing personas.
+
+- [articles](./docs/reference/articles.md) ([src](./data/reference/articles.json))
+- [books](./docs/reference/books.md) ([src](./data/reference/books.json))
+- [tools](./docs/reference/tools.md) ([src](./data/reference/tools.json))
+- [video](./docs/reference/videos.md) ([src](./data/reference/videos.json))
+
+Run `./bin/pls-json-to-md --build docs/reference --data ./data/reference/*.json` to regenerate markdown files from the source data.  Run `./bin/pls-validate --data data/reference/*.json --schema ./src/schemas/reference.json` to confirm the source data is valid.
+
+## DevRel Foundation Persona Library System
+
+The **Developer Relation Foundation Persona Library System (DEVREL-PLS)** is outlined in this section. It is an opinionated configuration framework for defining personas using a structured language (JSON) that adheres to an agreed upon standard schema.
+
+By defining personas in this way, we can establish tooling to validate, restructure, inherit, format, and exchange personas between organizations and departments. 
+
+### Learning the DEVREL-PLS
+
+The following guides explain how to build and extend a custom persona set for your organization and then how to apply them to solve common operational tasks to the Developer Relations and related roles.
+
+Developing your personas:
+* [Getting Started with the DevRel Foundation Persona System](./docs/guides/getting-started.md)
+* How-to Run a Persona Alignment Workshop (_TODO_)
+* How-to Present Personas to Your Organization (_TODO_)
+
+Using your personas:
+* [How-to Use Personas for Content Strategy](./docs/guides/content-strategy.md)
+* How-to Use Personas for Community Management (_TODO_)
+* How-to Use Personas for Event Strategy (_TODO_)
+* How-to Use Personas for Product Advocacy (_TODO_)
+* How-to Use Personas for Sales Enablement (_TODO_)
+* How-to Use Personas for Growth Marketing (_TODO_)
+* How-to Use Personas for the SDLC and Developer Experience (_TODO_)
+* How-to Use Personas for Developer Education (_TODO_)
+
+### DEVREL-PLS Persona Sets
+
+Example sets of personas created by organizations for their use and shared as reference.
+
+- [General Collection](./data/personas)
+- [DevRel Foundation Persona Set](./data/sets/dev-rel.org/README.md)
+- OpenSSF Persona Set (_TODO_)
+
+Run `./bin/pls-validate --data data/personas/*.json --schema ./src/schemas/persona.json` to confirm the source persona data is valid.
+
+### DEVREL-PLS Tools
+
+Ease of use tools such as LLMs, user-interfaces, etc. are not currently within the scope of v1.0 of this project, but will be a valuable addition to allow for more user-friendly and less technical methods of working with persona and related reference resources.
+
+- [pls-validate](./bin/pls-validate): used to validate one or more personas (JSON data) with a given schema.
+- [pls-json-to-md](./bin/pls-json-to-md): used to format reference library entries into a renderable markdown file.
 
-## How-to Use the Persona Library
+## License
 
-Details on how to use the resources of the persona library.
+All material contributed to the DRF Resources and Asset Aggregation Work Group is under [CC-BY-4.0 Licensing](https://creativecommons.org/licenses/by/4.0/deed.en).
 
-* ...
+See the [License and Intellectual Property](https://github.com/DevRel-Foundation/.github/blob/main/profile/README.md#license-and-intellectual-property) statement for instructions on how to reuse and adapt content from this repository, discussions, and issues with proper attribution to the Developer Relations Foundation.
 
 ## About the Persona Library
 
-This repository is maintained with support of the [Resource and Asset Aggregation Working Group](https://github.com/DevRel-Foundation/wg-resource-aggregation) and Developer Relations Foundation.
+This project repository is maintained with support of the [Resource and Asset Aggregation Working Group](https://github.com/DevRel-Foundation/wg-resource-aggregation) and Developer Relations Foundation.
 
-* [Contributing]()
+* [Contributing](./CONTRIBUTING.md)
 * [Report Issues](https://github.com/DevRel-Foundation/wg-resource-aggregation/issues)
 * [Questions & Feedback](https://github.com/DevRel-Foundation/wg-resource-aggregation/discussions/categories/persona-library)
 * [Project Roadmap](https://github.com/orgs/DevRel-Foundation/projects/12)

bin/pls-json-to-md

@@ -0,0 +1,2 @@
+#!/bin/sh
+npx node $(dirname "$0")/../src/scripts/json-to-md.js "$@"

bin/pls-report

@@ -0,0 +1,2 @@
+#!/bin/sh
+npx node $(dirname "$0")/../src/scripts/report.js "$@"

bin/pls-validate

@@ -0,0 +1,2 @@
+#!/bin/sh
+npx node $(dirname "$0")/../src/scripts/validate.js "$@"

data/personas/ai-dev.json

@@ -0,0 +1,48 @@
+{
+    "id": "ai-dev",
+    "parent": ["dev"],
+    "label": "AI Alex",
+    "segment": "*",
+    "organization": {
+        "maturity": "*",
+        "gtm": "*"
+    },
+    "role": {
+        "function": "dev",
+        "level": "*",
+        "responsibilities": ["coding", "reviewing"],
+        "titles": [
+            "ML Engineer"
+        ],
+        "tools": ["drf-ide", "drf-scm", "drf-cicd", "drf-ticketing", "drf-comms", "drf-test", "drf-build"],
+        "technologies": {
+            "languages": [ ],
+            "environments": [ ],
+            "skills": [ ]
+        }
+    },
+    "awareness": {
+        "channels": [
+                {"format": "social", "url": "https://news.ycombinator.com"},
+                {"format": "social", "url": "https://stackoverflow.com"}
+        ],
+        "events": [ ]
+    },
+    "adoption": {
+        "curve": "*",
+        "modality": []
+    },
+    "motivations": {
+        "x-likes": [],
+        "x-dislikes": [
+        ]
+    },
+    "strategies": {
+        "design": [],
+        "product": [],
+        "education": [],
+        "communications": [],
+        "sales": [],
+        "marketing": []
+    }
+}

data/personas/art.json

@@ -0,0 +1,66 @@
+{
+    "id": "art",
+    "label": "UX Designer",
+    "narrative": "Somebody who leans more on creativity than technical skill has a strong sense for aesthetics and user experience. They often will work paired up with development oriented teams to execute on a vision, with the ability to express the desired end state to reach a creative design vision.",
+    "organization": {
+        "gtm": "*",
+        "maturity": "*"
+    },
+    "role": {
+        "function": "art",
+        "level": "*",
+        "experience": "*",
+        "responsibilities": ["design", "writing"],
+        "titles": [
+            "UX Engineer",
+            "Creative Technologist",
+            "UI Developer",
+            "Front-end Developer",
+            "Interaction Designer"
+        ],
+        "tools": ["drf-creative", "drf-cms", "drf-ticketing", "drf-comms"]
+    },
+    "awareness": {
+        "channels": [
+                {"format": "blog", "url": "https://css-tricks.com"},
+                {"format": "social", "url": "https://reddit.com/r/UXDesign"}
+        ],
+        "events": ["drf-config.figma.com", "drf-sigchi.org"]
+    },
+    "motivations": {
+        "likes": [
+            "Wants to see visualizations, mockups, and designs to better understand concepts rather than text.",
+            "Iterative processes and gradual improvement.",
+            "Wants a better understanding of user goals",
+            "Will pick up on and appreciate moments of delight you add to your user interfaces."
+        ],
+        "dislikes": [
+            "Despises working within design constraints and brand guidelines that limit creative influence.",
+            "Bad design execution, expects form prioritized over function.",
+            "Wants to achieve a balance creative objectives with technical constraints even when mutually exclusive.",
+            "Products that have not taken accessibility into consideration"
+        ]
+    },
+    "strategies": {
+        "design": [
+            "Design products or services that are more free-form and flexible.",
+            "Provide open access to brand guidelines and design systems."
+        ],
+        "product": [
+            "Play close attention to precision in fonts, colors, and other design elements."
+        ],
+        "education": [
+            "Provide open-ended inspirational examples in tutorials or creative experiential learning.",
+            "Include graphics and pictures of user interfaces that complement source code or textual descriptions."
+        ],
+        "communications": [
+            "Use visual communicaton such as infographics and guides."
+        ],
+        "sales": [
+            "Reference customers and examples that show how well designed solutions look when complete."
+        ],
+        "marketing": [
+            "Provide gallery of inspiration from finished products."
+        ]
+    }
+}

data/personas/biz-finance.json

@@ -0,0 +1,56 @@
+{
+    "id": "biz-finance",
+    "label": "Vendor Val",
+    "narrative": "This persona has a Finance background but is required for sign-off of any purchase. Typical for larger enterprises there is separation with this role and the champion who makes the decision on which solution.",
+    "organization": {
+        "gtm": "*",
+        "maturity": "*"
+    },
+    "role": {
+        "function": "biz",
+        "level": "*",
+        "experience": "*",
+        "responsibilities": ["finance"],
+        "titles": [
+            "Chief Finance Officer (CFO)",
+            "Manager, Accounts Payable",
+            "Operations Manager",
+            "Purchasing Manager",
+            "Procurement Manager",
+            "Vendor Manager",
+            "Supply Chain Manager"
+        ],
+        "tools": ["drf-comms"]
+    },
+    "awareness": {
+        "channels": [
+        ],
+        "events": []
+    },
+    "motivations": {
+        "likes": [
+            "Wants a clear understanding of why something is valuable or interesting.",
+            "Decisions that are clear about value and risk.",
+            "Believes in the statement nobody ever got fired for buying IBM (or Salesforce, or...)"
+        ],
+        "dislikes": [
+        ]
+    },
+    "strategies": {
+        "design": [
+        ],
+        "product": [
+        ],
+        "education": [
+            "Educate on the cost savings impact in other ways after purchase to justify a return on investment."
+        ],
+        "communications": [
+        ],
+        "sales": [
+            "Provide a champion with a fact sheet they can share with purchaser to expedite the justification of an expense."
+        ],
+        "marketing": [
+            "Build a marketing page that provides all of the compliance, financial reporting (W-9) and other details that are necessary to close."
+        ]
+    }
+}