This has reached a user-testing phase where we await feedback on if it meets requirements.
Matt Walter changed status to In Progress
Team•
Apr 21, 2020
Matt Walter
Team•
Mar 6, 2020
Post updated to note what we would offer for Blog migrations. Original content: "Having a tool that would update some of the regular content from blogs and maybe pages to their siteglide equivalent would be awesome. For example, images & media download references within the {page_content} area, being updated on import or even an external tool that would re-write any asset reference to the new format… This way we can focus on getting the site templates via manual re-build for page speed/layout improvements, but when we have 500 or 600 blog posts, we can massage the data with bulk asset upload from CLI and import the posts with a json file."
Matt Walter
Team•
Nov 15, 2019
What we can offer is rebuilding file/database structure.
So for Pages we'd take the HTML file, and convert to Liquid with YML so they show in Siteglide and on the instance itself.
For Blog Posts we can, in one-click, install our Blog Module, and convert BC Blog Posts to fit the new database structure.
What is difficult to offer is conversion of tags (e.g. {tag_name} -> {{this.name}}) as it's not standardised. Different people will write Liquid/HTML in different ways, so it's near impossible to cover all bases, whereas we know how to convert BC structure to Siteglide structure.
Log in to comment and vote
Comments7
Jul 7, 2020
This tool passed user testing, and has now been released -> https://help.siteglide.com/en/articles/4230677
Matt Walter
Jun 5, 2020
https://app.clickup.com/t/4efyu0
Matt Walter
Jun 5, 2020
This has reached a user-testing phase where we await feedback on if it meets requirements.
Apr 21, 2020
Matt Walter
Mar 6, 2020
Post updated to note what we would offer for Blog migrations.
Original content:
"Having a tool that would update some of the regular content from blogs and maybe pages to their siteglide equivalent would be awesome. For example, images & media download references within the {page_content} area, being updated on import or even an external tool that would re-write any asset reference to the new format…
This way we can focus on getting the site templates via manual re-build for page speed/layout improvements, but when we have 500 or 600 blog posts, we can massage the data with bulk asset upload from CLI and import the posts with a json file."
Matt Walter
Nov 15, 2019
What we can offer is rebuilding file/database structure.
So for Pages we'd take the HTML file, and convert to Liquid with YML so they show in Siteglide and on the instance itself.
For Blog Posts we can, in one-click, install our Blog Module, and convert BC Blog Posts to fit the new database structure.
What is difficult to offer is conversion of tags (e.g.
{tag_name}->{{this.name}}) as it's not standardised. Different people will write Liquid/HTML in different ways, so it's near impossible to cover all bases, whereas we know how to convert BC structure to Siteglide structure.As discussed in this thread on pOS Slack -> https://platformos.slack.com/archives/G9XNSSSMB/p1573603811135700 - It's probably worth looking into building a personalised script locally to handle these conversions for you.
Nov 15, 2019