# Serving large amounts of static HTML using discourse?
**URL:** \
**Category:** Development\
**Created:** [8월 15, 2017, 2:43오후 UTC](https://meta.discourse.org/t/serving-large-amounts-of-static-html-using-discourse/68083 "2017-08-15T14:43:17Z")\
**Posts on this page:** 1\
**Showing post:** 8
**Author:**  [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [8월 16, 2017, 2:25오후 UTC](https://meta.discourse.org/t/serving-large-amounts-of-static-html-using-discourse/68083/8 "2017-08-16T14:25:12Z")
> [@Bas](#):
>
> The tool is modifiable, but it will always output static stuff (documentation is written in XML and outputted using several XSLTs).
That’s fine. It should then be easy to have it spit out something that will work with Discourse’s markdown engine and have it make the API call to post it in addition to writing the file to wherever it writes it.
> [@Bas](#):
>
> Our documentation is versioned and contains ~1000 documents per version; since we have a set of documents for every minor version (one released every 6 weeks or so),
Would your vision be to have a topic created for each revision and the 1000 documents be replies to that post?
> [@Bas](#):
>
> If we go the import-and-display-as-thread route, then we’ll need some extensive modification to add the left-hand navigation and remove some discourse specific things (e.g. remove the post-date, remove the author, remove the reply button).
I don’t see the problem with some user being who owns the document, though I suppose you could hide the username with CSS. Similarly, it would seem like the documents were created on a date and that knowing the date that they were produced would be helpful. Again, you could probably hide the dates with CSS.
Removing the reply button is as easy as changing the category permissions so that people can’t reply.
---
_[View the full topic](https://meta.discourse.org/t/serving-large-amounts-of-static-html-using-discourse/68083)._