> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/drep-campaign-platform/non-functional-requirements.md).

# Non-functional requirements

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

### Usability

* The DRep campaign platform should be accessible to non-technical users
* Proposal discussions should be transparent and easy to engage with
* Meet WCAG 3.0 AA accessibility standards
* Support for i18n/localization

### Scalability

* There must be enough participation to establish the legitimacy of the DRep campaign process. The tool would need to support at least 250,000 concurrent users.

### Performance

* Tool responsiveness: front page must load within 2 seconds for users accessing the website using an LTE mobile connection

### IP rights

* The code must be open source, with an open source license that permits the assets to be changed, redistributed, and used commercially (suggested: Apache 2.0 for code and CC BY 4.0 for other documents and assets)
* Any third party dependencies must not hinder or prevent the assets from being changed, redistributed, and used commercially
* The assets created for this proposal will be universally accessible on a public repository by the time the project is complete
* The assets created for this proposal must migrate into Intersect’s repositories if requested by Intersect

### Open source requirements

* While this instance is unique to the ways of working to Intersect member, IOG, open source best practice can be referenced from here: [Cardano Engineering Handbook](https://github.com/input-output-hk/cardano-engineering-handbook/tree/main)
* Guidance related to [open source policy can be referenced here](https://github.com/input-output-hk/cardano-engineering-handbook/tree/main/policy)
* Guidance related to expected [best practices can be referenced here](https://github.com/input-output-hk/cardano-engineering-handbook/tree/main/practices)

### Technical specification recommendations for FE (to support integration)

* NextJS / React
* Material UI
* i18next (or equivalent. New version support i18n without additional plugin)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/drep-campaign-platform/non-functional-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.