Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README: Add Comparison of Classic Editor vs. Gutenberg Exports for InDesign Imports #159

Merged
merged 1 commit into from
Oct 10, 2024
Merged

Update README: Add Comparison of Classic Editor vs. Gutenberg Exports for InDesign Imports #159

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,25 @@ Two custom roles are added by this plugin to best model a real-world print team.

![A Print Issue in "read only view". This view allows anyone with access to view a Print Issue without inducing a post lock, or being locked out by another editor. Note that the Export tools are still available in read only view.](/.wordpress-org/screenshot-3.png)

### XML Export to InDesign
### XML Export to InDesign: **Classic Editor vs. Gutenberg Exports**

When exporting content from WordPress for use in InDesign, there are key differences between **Classic Editor** and **Gutenberg (Block Editor)** exports. This section highlights how each type of export behaves in InDesign and offers guidance on how to handle these differences. You can test how this works in your version of InDesign with these sample XML files: [Gutenberg XML](https://raw.githubusercontent.com/wiki/10up/eight-day-week/BlockEditor-sample.xml), [Classic Editor XML](https://raw.githubusercontent.com/wiki/10up/eight-day-week/ClassicEditor-sample.xml)

#### **Classic Editor Exports**
- The XML structure generated by the Classic Editor is simple and straightforward, using basic HTML tags like `<p>`, `<strong>`, and `<em>` for paragraphs, bold, and italic text.
- No extra metadata or block-related comments are present, which allows for a smoother import into InDesign without any unnecessary elements.

#### **Gutenberg Exports**
- Gutenberg-based exports include additional metadata in the form of HTML comments (e.g., `<!-- wp:paragraph -->`) that wrap around content blocks. These comments contain details about block configurations and alignments.
- While the extra block metadata does not invalidate the XML, InDesign may not process these comments correctly, requiring manual adjustments to clean up or remove them.

#### **InDesign Import Differences**
- **Classic Editor**: Imports smoothly into InDesign without any issues, as the structure is simple, and no unnecessary metadata is present.
- **Gutenberg**: The extra block comments and metadata may not be recognized by InDesign and could interfere with the import. Users may need to manually clean up these comments or adjust formatting after the import to achieve the desired layout.

#### **Recommendations**
- **Classic Editor**: Ideal for seamless imports with minimal manual adjustments.
- **Gutenberg**: Recommended for users familiar with InDesign who are comfortable with making adjustments to remove unnecessary metadata or fine-tune block-specific settings after import.

- Export XML files specifically formatted for import into InDesign

Expand Down
Loading