Best strategy in producing a "read-only" output?

Great project!

Might be a silly question here, but what is the best strategy in rendering a read only view? Should I be considering a serialize call using the Html serializer?

Thanks!

[ianstormtaylor]

Ah interesting @mathieudutour! What do the islands contain? I’m down to discuss it in another issue and see if there’s a nice solution.

I’ve just added a readOnly property to editor that renders it in read-only mode. (Released in 0.1.14!)

[ianstormtaylor]

Hey @ctrlplusb, good question! I think it depends on the use case.

I think there’s a definite use case for having the Slate editor itself render in “readonly” mode, for example when a user should be able to see an existing document in the editing environment, but not edit it (like in Google Docs). For that, I just opened a new issue here: https://github.com/ianstormtaylor/slate/issues/108

And then there’s another use case, which is rendering content created in an editor elsewhere (like you’d do in a CMS). In this case, the editor is really “creating” the read-only output, so you’d want to use one of the serializers to save it somewhere, and then render that serialized state however. (The Html serializer would be a good option here.)

Hope that makes sense! I’ll look into adding the read-only mode soon.