> For the complete documentation index, see [llms.txt](https://bcds.gitbook.io/handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bcds.gitbook.io/handbook/digital-scholarship-methods/overview/hypertext.md).

# ¶ Hypertext

A hypertext is a digital text that links to sections or pages within the text, to other texts, to media elements,  and the like. Websites are the most common hypertext example. EBooks and eJournals are also often hypertextual, though not always with the same level of intricacy as a website. When designing a hypertext there are a number of technical and intellectual considerations including, but not limited to, information architecture, information organization, taxonomies, wayfinding, and navigation. All of these considerations impact usability and user experience. In digital scholarship, hypertexts are ways of publishing scholarship, e.g., making data visualizations and analysis available online. Through their structure, design, and the inclusion of media, they are also used to present scholarly arguments and tell narratives.


---

# 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://bcds.gitbook.io/handbook/digital-scholarship-methods/overview/hypertext.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.
