> For the complete documentation index, see [llms.txt](https://developers.laws.africa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.laws.africa/tutorials/about-the-tutorial.md).

# Content API legislation reader

This advanced tutorial guides you through building a small Django application that lets a user read and interact with legislation loaded from the Laws.Africa Content API.

The functionality includes:

* Fetching and storing legislation from the Laws.Africa Content API
* Listing legislation
* A legislation detail page with a Table of Contents and well-styled text
* Interactivity and enrichments using the Laws.Africa Law Widgets

The tutorial is divided into three modules:

1. [Module 1](/tutorials/module-1-build-a-legislation-reader.md): building the app basics; data modelling; fetching and storing data; listing legislation; reading and styling legislation
2. [Module 2](/tutorials/module-2-enrichments-and-interactivity.md): basic and advanced enrichments and interactivity
3. [Module 3](/tutorials/module-3-text-extraction-for-search-and-analysis.md): extracting text from Akoma Ntoso XML for full-text search and machine learning

The full code for the Django app is available at <https://github.com/laws-africa/legislation-reader>

[Let's get started](/tutorials/module-1-build-a-legislation-reader.md)!


---

# 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://developers.laws.africa/tutorials/about-the-tutorial.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.