What you need is to use the CMS in Elements. Unfortunately, it requires Markdown files.
So what you do is:
Find the MarkDownload (MD) plug-in for Safari.
On each page of your blog site, use MD to create a Markdown file of the page.
Using a Markdown editor, such as One Markdown, strip out any non-post text, and save that file in a folder somewhere.
Go through every markdown file in that folder and add the appropriate header information to it at the top. This can typically done with a macro/key substitute, though you may have to manually enter dates.
Drag all the edited Markdown files in that folder to a CMS folder in Elements, and then use the CMS components to display them. Warning: there are some tricky bits to this that you might need help with (I know I do from time to time).
@dan if you’re reading this, what would you give me if I wrote a “How to make an Elements Blog” ebook (based on the site I sent you via email that I created with the Microblog project)? Not looking for money, but the CMS is such a pain point for so many it really needs a good step-by-step, point-by-point, explanation-by-explanation resource.
Thom, speaking of the right tools, I can’t get past step 1 so far. “Find the MarkDownload (MD) plug-in for Safari.”
Where do I find the Safari Markdown plugin? When I search for MarkDownload (MD) plug-in for Safari in the App store, all kinds of apps show up that have nothing to do with saving a page as a markdown file.
I’ve downloaded Mark Down Editor but it’s not a plugin. I downloaded Single File plugin that saves the page as html and I downloaded Copy Link in Markdown that copies only the link.
It’s also unclear to me if this method will maintain photos associated with my posts.
Also note that some of the Markdown things described in Markdown Editor don’t work in the CMS.
As for images, you should get them when you clip the page with MarkDownload. But it’ll be an inline reference. One of the things that just needs more step-by-step documentation is how to handle external image references in the CMS properly.
As I noted, the process is convoluted for the moment. It involves a lot of steps for each blog page you want to move from an existing site to an Elements CMS one. But if you do the process right a few times, it starts to become second nature. For sites with a ton of blog posts, you’ll be cranking for awhile. For that I’d recommend just staying in your old site and strip all your pages into Markdown with MarkDownload into a folder somewhere, then use One Markdown to clean them all up, and only then move them into Elements.