Write some more basic Futatabi docs.

[nageru-docs] / monitoring.rst

diff --git a/monitoring.rst b/monitoring.rst
index 204c37a885956706769fbe96eeb5a47272f3d7f1..6165e76a717bb31c2aaee11896ad2be5b2a09303 100644 (file)
--- a/monitoring.rst
+++ b/monitoring.rst
@@ -45,7 +45,7 @@ into). However, most cheaper cameras will have none at all.
 
 Nageru does not have functionality to talk to tally lights directly (there are too
 many kinds of interfaces and standards), but it does have functionality to expose
-tally _data_. Using this, you can build your own tally light, be in through injecting
+tally *data*. Using this, you can build your own tally light, be in through injecting
 the right bits on an SDI cable, having a single-board computer set some GPIO pins
 for a LED, or simply show a red or green dot on a mobile phone with a web browser.
 
@@ -59,3 +59,7 @@ match the borders around the input in the producer's mixer display—typically
 green for on preview and red for live. This also means they can be CSS textual
 colors (like “red”), although you can of course make the theme return only
 “#ff0000” or similar if this makes your tally application simpler.
+
+Note that the tally endpoints have fully open `CORS <https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS>`_
+headers, so that they can be queried from anywhere; tally data is not sensitive,
+and this makes it significantly easier to query them from a web page.