\
**Category:** Learning\
**Created:** [May 2, 2018, 1:51am UTC](https://discuss.ocaml.org/t/tools-for-postprocessing-html/1940 "2018-05-02T01:51:09Z")\
**Posts on this page:** 3\
**Page:** 1
**Author:**  [@perry](https://discuss.ocaml.org/u/perry)\
**Post date:** [May 2, 2018, 1:51am UTC](https://discuss.ocaml.org/t/tools-for-postprocessing-html/1940/1 "2018-05-02T01:51:09Z")
If one wanted to take a complicated HTML document (say the output of the OCaml manual build process) and postprocess it to alter the CSS and some of the HTML, would Lambda Soup be the correct tool for the job?
---
**Author:**  [@Armael](https://discuss.ocaml.org/u/Armael)\
**Post date:** [May 2, 2018, 7:14am UTC](https://discuss.ocaml.org/t/tools-for-postprocessing-html/1940/2 "2018-05-02T07:14:07Z")
Yes. I used it myself for post-processing the output of ocamldoc at some point, and IIRC Anton does the same for the online documentation of lambda-soup.
Whether writing a post-processor for automatically generated documentation is a good idea is another topic :-). But in any case, I believe lambda-soup is the right tool for the task.
---
**Author:**  [@perry](https://discuss.ocaml.org/u/perry)\
**Post date:** [May 2, 2018, 10:19am UTC](https://discuss.ocaml.org/t/tools-for-postprocessing-html/1940/3 "2018-05-02T10:19:31Z")
Sometimes, kludges are expedient. Sadly, for the case I have in mind, postprocessing seems to be the best of bad alternatives.