Each landing page in Pardot must have a Layout Template. This is what you need to supply the developed HTML to.
Effort should be made to ensure that text and images are edtiable, as far as is possible/sensible. There are various types of content regions which can be supplied to Pardot, so weigh up each case as to which editor to make available to the client. See http://help.pardot.com/customer/portal/articles/2126809-using-content-regions for more on this.
You will be able to upload images to Pardot for use in landing pages (as well as emails), but please try to organise these files sensibly so that they can be easily found/not overcrowd the default upload folder.
Each uploaded file can be accessed via a public URL - for Kensington, please use the URLs on the contact.kensington.com domain - ensure that the source HTML is updated with these URLs once you are ready to start putting the HTML into Pardot. You will need to supply CSS, images and JS to Pardot's file area for this purpose. Do not reference media.thisisrevere.com as a remote host/CDN.
With this in mind, you will need to adjust the final HTML to use the Pardot paths for app.css and app.js. This might mean keeping the original references in src and manually editing the dist HTML before upload each time. A painful, but necessary step.
Pardot does not support the hosting of web fonts on their environment. Typekit or another remote host (do not use media.thisisrevere.com for this purpose) would need to be used. Instructions and further information on this can be found at http://help.pardot.com/customer/en/portal/articles/2128485-using-custom-fonts-in-pardot?b_id=11139.