> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/nodes-parts-and-resources/creating-content-references.md).

# Creating Content References

## Description

Content references allow you to add more information to your applications, including text, graphics, PDFs, mp4 files, and URL links. You store this content and then associate it with a logicnet node and display it when a user interacts with your application. Two common use cases for content resources are:

* Creating content references that provide information linked to specific questions to help your users understand the question being asked and/or the answer choices.
* Creating content references as a report component repository, with different the system presenting or writing content into a report based on user selections in your application.

You store content references with your project and you can edit and update them using the LogicNets Designer. It is particularly useful to incorporate content references for relatively static content that gets updated on a similar frequency to updates to the overall application. For reference information that is more dynamic or if you need to manage content outside of the LogicNets Designer interface, you should consider using the LogicNets Knowledge Center. See [Knowledge Center Overview](/release-9/platform-documentation/knowledge-center/knowledge-center-overview.md) for more information.

## Create and Edit Content References

You create and organize content references in the *resources/content* folder of your project. To create a new content reference, do the following:

1. Navigate to the *resources/content* folder of your project and click the ***New Document*** icon.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1ee1e3841d17f321b93f51a83402faf4eb9241e9%2F7d118d4b-c690-41b5-8e2b-8acb81d575f0.png?alt=media)
2. Enter the name of your content and then add the content in the body of the reference.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c74b8855f645b50507edc92d31067729524131df%2Fabbd8a01-0f95-4325-a843-fb29e01fa176.png?alt=media)
3. Using the dropdown menu, select the type of content you are including.
   * html (default) - This is for text, images, and URLs in support of Assessment Framework projects.
   * link - This is a system-level option.
   * net - This is a system-level option.
   * change - This is a system-level option.
   * custom list - This is a configuration-level option you can set in the Designer. See [Project Settings - Common Settings across Frameworks](/release-9/design-considerations-and-frameworks/frameworks/general-framework-information/project-details-common-settings-across-frameworks.md) (v8.4+).
4. Click ***save*** to save your changes.

The system displays your saved content reference in read-only mode, and it displays the content type in the top-right of the screen.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ba5e15a856990163f8e6056b7a48335990581a0f%2Fd5f4d4a8-6c52-42ef-84b2-1b992420ac73.png?alt=media)

## Format Content References

The content reference text edit box includes a menu with a number of formatting features, including text formatting options and other feature options as well.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-d68a18cb54515f1ee8b03f45e43e8ff71fac5702%2Fadbef61e-959e-4892-a4dc-68ecd04a9e35.png?alt=media)

1. **File Upload**: You can use this button to import images, documents, PDFs, and mp4 files. This also gives you the option of displaying the information in a frame or as a clickable link.
2. **Paste as Text**: This button allows you to paste content copied from Microsoft Word. It removes hidden formatting often included in pasted text.
3. **HTML View**: This allows you to view the content at the HTML level so you can manage DIVs, inline styling, and image size, for example.
4. **URL**: This button allows you to add a URL to either a publicly available or internal "intranet" web address.

**Important Notes:**

* Large media files may cause a disruption in performance while the system reads data into memory.
* You should be aware of the security risks of uploading files that could potentially contain non-approved content, HTML, or other harmful code.
* You may notice a ***Manage Linked References*** button on the bottom-right of the viewer. This is future functionality that will allow you to create a grouping of associated content references. The content resource from which you clicked the option serves as the parent and the content you selected in the *References* pop-up act as associated content.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/nodes-parts-and-resources/creating-content-references.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.