Getting your dataWhere does the data come from? Can Nytril pull from a product database, spreadsheet, or API at build time, and how do writers and engineers share ownership of that data? Nytril can query any local or online database to get a view. The writer supplies the SQL query and Nytril maps the view to defined structures. Nytril allows creators to connect to any Rest API or call any DotNet library. There are many open-source examples of this, shipped with the product. For security, there is a feature that allows each writer to securely cache their own access credentials on their workstation to avoid placing such credentials in source. While Nytril has the ability to easily read and map XML and structured text files, we believe that creators should consider storing their data right in Nytril source, as we have done for this Q&A example. What happens next depends on the data, of course. Nytril provides formatters for tables and charts so you can reflect the data into a document. You can use normal programming constructs like loops, switches and logic to transform your data anyway you like without leaving Nytril code. Here is an example of a research white-paper created with Nytril. The data for the paper was stored in Nytril source, exported to a program in C++ for heavy calculations, then automatically formatted to create the final paper. Nytril natively supports citations, references and bibliographies. Here is an example of a IOT Spec Sheet created with Nytril. The data for the sheet is stored in nytril code and uses local image files. All the graphics, text and logos are defined in Nytril code.