I agree with the above approach. Some ideas as variation on that:
- save your Wordpress homepage as html and then go through the structure to create a default layout.
- you could move head, header (for nav and banner image) and footer to separate
_includesfiles so the the default.html layout file is light. - choose pages on your wordpress site that have distinct style and you want to convert to layouts. Id expect something like this: home.html, page.html, posts.html, post.html. The posts.html one would have a
forloop over posts and that logic could be used on your homepage too or instead. - Reference the default layout in each layout and of course use
{{ content }}variable. - I am not familiar with other assets for Wordpress. You might find the image, css and js links copied into head work fine but are not sustainable since they are tied to Wordpress and maybe that wordpress theme or your own wordpress site. So save those as files in your assets directory and then update head links to point to new files e.g. the “/assets/js/foo.js” file, as served from
_site - give credit to the original theme in your docs and the footer or similar.
- Also check - there may be copyright restrictions on the wordpress theme reuse, even if it’s free but especially if it is a paid theme.