jack.from.canada
posted this
05 March 2022
I am just as frustrated as some of you, but from a programmer's standpoint, I can see the issue they're having. It appears that Nicepage has a "hierarchy" of components. Pages contain blocks, blocks contain elements, and elements contain content. Up until now, they've created very specific instances of "elements" that can be further sub-divided (e.g. an element called a table, or grid, or gallery), and these "special cases" give the appearance of having further sub-divisions. But the basic hierarchy remains the same.
Until they can figure out how to enclose a "block" inside an "element", or even an "element" inside another "element", there will be limitations on what can be done with Nicepage.
I think the ultimate solution is for them to define an "element" called a "sub-block" that can be inserted into another block. If they can do that, then the "recursion" needed to implement any of the other permutations becomes possible. This "sub-block" would have all the characteristics and capabilities of a regular block (almost like a separate page being displayed in an iframe). The problem is that such a construct may not be something that is supported by the CMS's that Nicepage supports. So, such a construct might work for an HTML5 rendering but may not have a corresponding translation within the other contexts.
I am just as frustrated as some of you, but from a programmer's standpoint, I can see the issue they're having. It appears that Nicepage has a "hierarchy" of components. Pages contain blocks, blocks contain elements, and elements contain content. Up until now, they've created very specific instances of "elements" that can be further sub-divided (e.g. an element called a table, or grid, or gallery), and these "special cases" give the appearance of having further sub-divisions. But the basic hierarchy remains the same.
Until they can figure out how to enclose a "block" inside an "element", or even an "element" inside another "element", there will be limitations on what can be done with Nicepage.
I think the ultimate solution is for them to define an "element" called a "sub-block" that can be inserted into another block. If they can do that, then the "recursion" needed to implement any of the other permutations becomes possible. This "sub-block" would have all the characteristics and capabilities of a regular block (almost like a separate page being displayed in an iframe). The problem is that such a construct may not be something that is supported by the CMS's that Nicepage supports. So, such a construct might work for an HTML5 rendering but may not have a corresponding translation within the other contexts.
Last edited 05 March 2022 by jack.from.canada
