<p>I see 3 options, none of which warrant the creation of a plug-in:</p>

<ol>
<li><ul>
<li>Get <em>Craft</em> to output all your URLs as a simple, unformatted list. Easy enough to do this with Twig templates, right (ask if not!)? Save this as <code>pages.txt</code></li>
<li>Install <code>wget</code>. Simple to do on Linux (<code>apt-get install wget</code> probably), if you're on a Mac you can install it using <code>brew install wget</code>.</li>
<li><code>wget -i pages.txt</code></li>
<li>You should now have all the pages as lovely static <code>.html</code> files.</li>
</ul></li>
<li><ul>
<li>Get <em>Craft</em> to output pages as a big <code>.json</code> data file. Again, easy enough to do with Twig templates.</li>
<li>Use a 'Static CMS' to read in this JSON and use it to build out a reproduction as a static website. Personally, I'd use <em>Middleman</em> or <em>Assemble.io</em> if I was doing this - but I guess it depends if you're more comfortable with Ruby or Node.js respectively.</li>
</ul></li>
<li><p>Ask yourself why you're doing this? Is it performance? Security? Maybe if you get up to date with use of the <code>{% cache %}</code> tags you'll have a much easier time!</p></li>
</ol>

CC BY-SA 3.0
2017-03-24T08:36:29.777Z
Thanks ianp for your quick post! The craft instance is to edit and create static landingpages. I need a user/editor friendly solution. I had play with wget, but there are some issues and inter alia because of this it is no solution for an editor.
Sanbo
CC BY-SA 3.0
2017-03-24T11:36:49.973Z
No worries. I'm sorry I don't know what you mean by "inter alia"?

I don't understand why you can't just let Craft output the pages directly. Maybe if you could explain your setup a little clearer? I think you could rigger wget using Craft, which might make it a little 'editor friendly'-er.
ianp
CC BY-SA 3.0
2017-03-24T11:47:59.277Z
Amongst others (sorry for my bad english).
Sanbo
CC BY-SA 3.0
2017-03-24T12:10:42.330Z
np. My previous question still stands!
ianp
CC BY-SA 3.0
2017-03-23T18:55:52.630Z
2017-03-23T19:15:16.020Z
2017-03-23T19:15:16.020Z
ianp
<p>For a client I need to export websites as static html (/w images, CSS, JS etc.), which I have created in Craft.</p>

<p>Unfortunately, I cannot find a plugin for this.</p>

<p>Can someone give me a hint, how do I start with this?</p>

<plugin-development>
Export static html including images, CSS, JS etc
# Export static html including images, CSS, JS etc

(Asked by: username_0 on 2017-03-23)

For a client I need to export websites as static html (/w images, CSS, JS etc.), which I have created in Craft.

Unfortunately, I cannot find a plugin for this.

Can someone give me a hint, how do I start with this?

**Tags:** plugin-development


---

## 1 answers

### Answer by username_1 on 2017-03-23. Score: 4

I see 3 options, none of which warrant the creation of a plug-in:

1. * Get *Craft* to output all your URLs as a simple, unformatted list. Easy enough to do this with Twig templates, right (ask if not!)? Save this as `pages.txt`
   * Install `wget`. Simple to do on Linux (`apt-get install wget` probably), if you're on a Mac you can install it using `brew install wget`.
   * `wget -i pages.txt`
   * You should now have all the pages as lovely static `.html` files.
2. * Get *Craft* to output pages as a big `.json` data file. Again, easy enough to do with Twig templates.
   * Use a 'Static CMS' to read in this JSON and use it to build out a reproduction as a static website. Personally, I'd use *Middleman* or *Assemble.io* if I was doing this - but I guess it depends if you're more comfortable with Ruby or Node.js respectively.
3. Ask yourself why you're doing this? Is it performance? Security? Maybe if you get up to date with use of the `{% cache %}` tags you'll have a much easier time!

> **Comments:**
> **username_0**: Thanks username_1 for your quick post! The craft instance is to edit and create static landingpages. I need a user/editor friendly solution. I had play with wget, but there are some issues and inter alia because of this it is no solution for an editor.  
> **username_1**: No worries. I'm sorry I don't know what you mean by "inter alia"?  I don't understand why you can't just let Craft output the pages directly. Maybe if you could explain your setup a little clearer? I think you could rigger wget using Craft, which might make it a little 'editor friendly'-er.  
> **username_0**: Amongst others (sorry for my bad english).  
> **username_1**: np. My previous question still stands!  

---

