Currently Falls Short for Advanced Conversion Needs

[eirichmond]

Summary of Why It Currently Falls Short for Advanced Conversion Needs

• Limited to Navigation Elements: Focuses only on navigation items, lacking broader applicability.
• Single Content Element Restriction: Only supports one content element at a time.
• No Support for Archives or Custom Post Types: Doesn't consider more complex structures like archives or CPTs.
• Custom Sites Have Multiple Content Elements: Many sites rely on custom post meta and advanced field setups.

Having tried this tool, I’m not sure it meets my needs or those of real-world users who require more flexibility and advanced options for selecting source content. Custom WordPress sites often consist of multiple content elements, such as data stored in post meta or flexible content fields from Advanced Custom Fields (ACF). For example, site content isn’t always confined to post_content; it frequently relies on additional data sources.

Adding the ability to select the entire page or specific sections of a page for conversion would make the tool far more practical. Being able to group elements sequentially or as part of a predefined structure and then convert them to blocks would significantly increase its usefulness.

For example, I have a real-world use case involving the conversion of a Classic theme that uses custom post types alongside flexible ACF content. The page contains multiple elements, but try-WordPress currently focuses only on navigation and a single content block. Expanding its capabilities to allow selection and grouping of multiple elements for conversion would make it a much more powerful and versatile tool.

Here’s an example of a typical “house” page. You’ll notice there are clear, distinct sections, each of which could naturally translate into group blocks containing inner text and image blocks. This approach would lend itself well to structuring pages with reusable and customizable components.