Hey J H, thank you for taking the effort to reply.
The workflow you have suggested is quite similar to what Landingpagr actually does. The only difference is that while what you are suggesting should be able to parse any page, LandingPagr has a static structure. Since most landing pages use the same oft-repeating blocks such as hero, features, pricing, faqs etc, I felt a static structure should be sufficient for most use cases.
You are right; the current approach is to compose copy using text-editors or CMSs. However, the problem with text-editors is the inability to visualise the page thus limiting the coherence and flow of messaging. With CMSs and HTML, design and coding takes centre stage while focus shifts from copy, in my experience. LandingPagr is thus supposed to bridge this gap.
Your project sounds interesting; I will check it out.
Hey J H, thank you for taking the effort to reply.
The workflow you have suggested is quite similar to what Landingpagr actually does. The only difference is that while what you are suggesting should be able to parse any page, LandingPagr has a static structure. Since most landing pages use the same oft-repeating blocks such as hero, features, pricing, faqs etc, I felt a static structure should be sufficient for most use cases.
You are right; the current approach is to compose copy using text-editors or CMSs. However, the problem with text-editors is the inability to visualise the page thus limiting the coherence and flow of messaging. With CMSs and HTML, design and coding takes centre stage while focus shifts from copy, in my experience. LandingPagr is thus supposed to bridge this gap.
Your project sounds interesting; I will check it out.