Skip to main content
Neuron’s InternetContent inventory discovers encoders, decoders, converters, and file-extension mappings from installed assemblies. The same typed object can therefore be rendered differently according to Accept.

​
Common formats

The runtime can support JSON, XML, forms, binary streams, Markdown/HTML, CSV/TSV, images, PDF, ZIP, JWT/JWS, RDF/Turtle/JSON-LD, SPARQL results, Graphviz, PlantUML, and Office documents. The exact set depends on packages and external programs.

​
Markdown pages

Markdown is an application format in Neuron, not only static documentation. Page metadata can select a master page, styles, scripts, JavaScript, author/date, navigation, and other renderer-specific features. Script expressions can make content dynamic. Use packages to deploy pages so assets, master pages, scripts, and routes are versioned together.

​
Conversion pipeline

Return 415 when input cannot be decoded, 406 when no acceptable output exists, and 422 when the decoded object cannot be processed/serialized for the requested operation.

​
Document generation

Markdown can be rendered to HTML and, with the corresponding modules, PDF and JavaScript. Graphviz and PlantUML blocks require their runtime dependencies. Treat document conversion as resource-intensive untrusted-input processing: bound size/time, disable unsafe external includes, and isolate temporary files.

​
API design

  • Send explicit Content-Type and Accept.
  • Do not label arbitrary text as JSON/XML.
  • Keep character sets explicit for text.
  • Use typed error bodies.
  • Avoid depending on an optional encoder without declaring the package dependency.