Update readme.txt: Add comparison of Classic Editor vs. Gutenberg exports for InDesign imports #160
+15
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Gutenberg exports for InDesign imports.
Merged
4 tasks
dkotter
approved these changes
Oct 10, 2024
dkotter
deleted the
feature/update-readme-with-classic-vs-gutenberg-exports
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
This PR updates the readme.txt to include a new section that details the differences between Classic Editor and Gutenberg (Block Editor) exports when imported into InDesign. The goal is to help users understand how each type of export behaves during import, particularly regarding additional block metadata in Gutenberg exports and the potential need for manual adjustments when importing into design tools like InDesign.
Closes #43 (and addresses note from @dkotter here)
How to test the Change
Changelog Entry
Credits
Props @frankiebordone @dkotter
Checklist: