Update Retail React App Page Designer integration README

[johnboxall]

Small tweaks to the Page Designer README:

1. Sample code handles errors
2. Terser explanations
3. Note loudly that the functionality is not enabled by default

[bendvc]

Did you mean to say "It is a living" ..

Is "It" page designer? or the page designer folder?

[rsexton404]

I don't think "living folder" translates well to other cultures.

[bendvc]

I agree. But I don't have any suggestions for alternative 🤷. We could be more direct and say something along the lines of "this is where you'll place all your page designer components that you develop"

[bendvc]

I feel like I just handed in a paper to an english teacher 🤣

I'll give you the +1, I'd prefer if you addressed your uses of "It" because it's hard to know what you are referring to as mentioned in the PR comment.

Thanks

[rsexton404]

We should link to instructions on how to enable the integration.

[rsexton404]

Looks good! I added some minor suggestions.

[johnboxall]

Thanks @bendvc + @rsexton404.

It's outside the scope of how much time I had for this PR, but I think the following things are important to understand about our PD integration:

1. Your first task to integrate is to create React.js components that accept your Page Designer component serializations and render them. I'm actually unsure how our current implementation handles Page Designer component serializations that do not have a corresponding React.js component. Does it throw, warn in the console or silently discard them? What it does is important, and we should document it.
2. Next, you need to decide when/where to render PD pages. No "mapping" mechanism is included, so this is a large exercise left to the implementer. You might a) hardcode the set of PD pages b) grab a list of pages at build time or c) call a custom API at runtime time. There is no readily available API you can call to get a list of PD pages.
3. Finally, merchandisers can start working with PD in BM and seeing their changes in the PWA. You're still going to get the old rendering of components in BM. To see what things are going to look like in the PWA, you'll need to publish the page, and then open the relevant URL in the PWA.
4. The PD API is actively being worked on and there are some known bugs / constraints: a) it doesn't work when storefront protection is enabled b) if any attribute of your component serializes to null, the whole thing will c) it not currently hooked up to shopper context d) if your PD component doesn't define a .serialize() method, you'll get the default rendering, which may not be what you want ... these are being actively worked on, but they're good to know!