You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The roundtrip to Sharepoint is not really needed, if we could just use the content from the import directly. This would allow for a very fast iterations.
While it could be a nice and useful feature, I think it is a slippery slope: during the import, it is important to focus on the information architecture, i.e. how do you represent each piece of content in the most intuitive way for the authors. If you start mixing the rendering part as the same time, you will certainly not come up with the same result. Even worst, if during the import you need to check the rendering to validate the structure of a block is correct, it already feels something is wrong...
Challenge
My current workflow for single url is:
import.js
Preview
import.js
, goto 1Idea
The roundtrip to Sharepoint is not really needed, if we could just use the content from the import directly. This would allow for a very fast iterations.
Sample Code that illustrates the problem
Importing https://www.volvotrucks.us/our-difference/driver-productivity/volvo-dynamic-steering/ which is quite complex and many different blocks are available.
The text was updated successfully, but these errors were encountered: