> For the complete documentation index, see [llms.txt](https://wiki.nuance.xyz/nuance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.nuance.xyz/nuance/welcome-to-nuance-your-platform-your-voice/roadmap.md).

# Roadmap

Nuance community have three goals which have guided the feature prioritisation to date:

* Fairest paid content creators on the internet
* Most trusted platform for long-form content
* Best UX for both writers and readers

The roadmap will consist of the features that will help Nuance achieve these goals.

All community members are welcome to submit ideas make proposals, any team can get funding to build and ship a feature, and it's up to the community to decide which features are built and who builds them, ensuring a truly collaborative, democratic and decentralized development process.

Nuance backlog currently has the following potential features grouped by goal:

<details>

<summary>Fairest paid content creators on the internet</summary>

***Premium Articles*** :white\_check\_mark:

Allow publishers to publish content that is behind a paywall. Access to the content is provided using an NFT minted by the publisher on Nuance and available for sale on Nuance and Entrepot ([read more](https://nuance.xyz/nuance/2762/premium-articles-by-nuance)).

***Applause*** :white\_check\_mark:

Allow readers to applaud articles and in doing so transfer tokens from their own wallet to the writer's wallet i.e. tipping the writer.

***Subscription*** :white\_check\_mark:

Allow publishers to establish a recurring payment from readers for ongoing access to content behind a paywall.

***Paywall article ownership*** :white\_check\_mark:

Allow publishers to create a single paywall for content which can be paid by one or more readers with partial ownership of the article being split with those readers.

***Advertising***

Advertising is one of the main drivers of the problems we have with web2. However some companies, like Brave, are doing non-invasive advertising and the community may wish to explore this option.

</details>

<details>

<summary>Most trusted platform for long-form content</summary>

***Content moderation*** :white\_check\_mark:

Nuance has content rules and we integrate with Modclub to ensure content is compliant with the content rules.

***Fact-checking***

So-called “fake news” is difficult to determine so introducing Factive to help the community determine facts from fake will help readers trust the content.

***Full-text responses***

To encourage thoughtful contributions to the platform we allow writers to respond to other articles with their own articles. Commenting does not encourage proponents or opponents to properly respond to an article.

***Reputation***

Using the applause as a crowd-sourced reputation metric writers will earn a reputation on the topics (tags) of their articles.

</details>

<details>

<summary>Best UX for both writers and readers</summary>

***Email notification***

Allowing publishers to push content to readers via email.

***Article protocol***

Creating a standard article protocol allows writers to write their content on Nuance and distribute the content wherever they prefer.

***Custom editor***

Provide the best writing experience imaginable.

***Commenting*** :white\_check\_mark:

Enable readers to comment on articles.

***SEO*** :white\_check\_mark:

Search engines supercharge organic growth and getting content discovered is critical to enable monetization.

***Scaling*** :white\_check\_mark:

Finding product market fit and overcoming the cold start problem will result in rapid growth that Nuance will need to accommodate.

***Security*** :white\_check\_mark:

Although the blockchain itself is natively secure the Nuance application may have vulnerabilities which may need to be addressed.

***Backup restore***

Disaster recovery requires a backup.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.nuance.xyz/nuance/welcome-to-nuance-your-platform-your-voice/roadmap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.