Hi, Currently we have a few thousand pages of documentation in static HTML files. We need a place to store this and render them. Our initial instinct was to use wordpress and use a mass-import; then link discourse and wordpress using the plugin etc. But… we kind of had a brainwave.. what if we us…

What I would do is to write an importer to pull them in. I don’t understand why you’d have trouble in the future unless you plan to continue creating static html files to import,but i don’t know why you’d do that .

Because our documentation tool spits out static HTML :neutral_face:

That’s sad. Can you fix that tool, or is it something you don’t have control over? Anyway, it seems like your solution is working for you, but my inclination would be to write a script that pumped the stuff into Discourse via the API. You wouldn’t need to worry about plugins breaking (API changes r…

Thank you for the suggestion. I’m afraid it won’t work, since the tool is heavily used (and liked) by the documentation team. To create such a plugin is beyond my capabilities, how does that generally work? Simply post the specs to the marketplace and ask for a quote?

My suggestion was to modify your tool rather than replace it. Can you modify it, or is it immutable? Yes, you can post in Marketplace . I think that you want not a plugin, but a script that uses the API to post new files as they are created.

The tool is modifiable, but it will always output static stuff (documentation is written in XML and outputted using several XSLTs). 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), I…

[imagem] 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 …

[imagem] pfaffman: Would your vision be to have a topic created for each revision and the 1000 documents be replies to that post? No, we really would need a coherent set of documents; customers will use a specific version for a year or so (so often they are 5 versions or so behind), they will…

Do you by chance know of a public Discourse install that has so extensively modified its content structure @pfaffman ?

Serving large amounts of static HTML using discourse?

Development

Bas (Bas van Leeuwen) 15 Agosto , 2017 18:37 3

Because our documentation tool spits out static HTML

Tópico		Respostas	Vistas
Custom Platform Development	16	630	25 Novembro , 2024
Converting discourse topics to read only pages Product Support	1	1292	8 Setembro , 2017
Is anyone here using their Discourse instance as their entire website? Community Building	17	5177	4 Março , 2021
A basic Discourse archival tool Development	24	15144	30 Abril , 2025
We built a static blog with Discourse as the backend Praise	5	4709	11 Setembro , 2015

Serving large amounts of static HTML using discourse?

Related topics