Originally discussed here:
T169761#3422369
and here:
T169761#3424801
This is pushing forward the notion of returning the data that clients need and remove the need for client side processing.
In particular, clients create a small number of URLs from titles. @phuedx proposed a dictionary like (I have made a few changes/additions):
```
urls: {
page: "…",
talk: "...",
summary_api: "...",
read_html_api: "...",
edit_html_api: "..."
}
```
This seems like a good path forward. We need to bike shed on a few specifics, and should do that here. Some things to consider for the final structure:
1. Clients should be able to differentiate between content URLs and API urls easily
2. We should decide on using mobile vs desktop URLs or both and clearly marking them up