+
+In this vignette we will focus on using the `teal_transform_module` for transforming the input data using the `transformators` argument in `teal::module` function.
+
## Creating a data transformation module
Let us initialize a simple `teal` app by providing `iris` and `mtcars` as input datasets.
diff --git a/vignettes/customizing-module-output.Rmd b/vignettes/transform-module-output.Rmd
similarity index 80%
rename from vignettes/customizing-module-output.Rmd
rename to vignettes/transform-module-output.Rmd
index cd18778d10..64658fa2f5 100644
--- a/vignettes/customizing-module-output.Rmd
+++ b/vignettes/transform-module-output.Rmd
@@ -1,11 +1,11 @@
---
-title: "Customizing Module Output"
+title: "Transform Module Output"
author: "NEST CoreDev"
output:
rmarkdown::html_vignette:
toc: true
vignette: >
- %\VignetteIndexEntry{Customizing Module Output}
+ %\VignetteIndexEntry{Transform Module Output}
%\VignetteEngine{knitr::rmarkdown}
%\VignetteEncoding{UTF-8}
---
@@ -19,39 +19,42 @@ library(ggplot2)
## Introduction
The outputs produced by `teal` modules, like graphs or tables, are created by the module developer and look a certain way.
-It is impossible to design an output that will satisfy every possible user, so the form of the output should be considered a default value that can be customized.
-Here we describe the concept of _decoration_, whereby a `teal_transform_module` can modify an output created by a `teal_module`, enabling you to tailor outputs to your specific requirements without rewriting the original module code.
+It is hard to design an output that will satisfy every possible user, so the form of the output should be considered a default value that can be customized.
+In [Transform Input Data](transform-input-data.html) we described how `teal_module`'s input data can be modified using `teal_transform_module`. Here we present how to utilize `teal_transform_module` to modify an output created by a `teal_module`, enabling you to tailor outputs to your specific requirements without rewriting the original module code.
-While it is not required, reading [this vignette](data-transform-as-shiny-module.html) may give you a fuller understanding.
+
+## How to Transform outputs?
-## Decorators
-
-Decorators are created with `teal_transform_module` and thus they are `shiny` modules.
+Custom transformations for the output objects can be created with `teal_transform_module()` and thus they are `shiny` modules.
They are passed to `teal_module` constructors as arguments (see below).
Their server logic will be used to modify objects such as plots or tables that exist in the server function of a `teal_module`.
-A `ui` function can provide interactivity but that is optional, an app developer is free to use decorator modules that do not require user input.
+A `ui` function can provide interactivity but that is optional, an app developer is free to transform outputs objects of a `teal` module that do not require user input.
### Requirements and Limitations
-Using decorators requires the following:
+Transforming `teal` module output requires the following:
1. **Module Support**: