Added docs for Custom fields #320
Merged
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
benbalter
approved these changes
Oct 16, 2024
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.
Hey Ben,
thanks for your exporter! Due to the current buzz I am now ready to migrate my last WP site to Jekyll.
Found out that you already have a filter in place to convert custom/meta fields 👍
I added some documentation, as I was using ACF (Advanced custom fields) a lot, and all fields were stored as array, some (like location field) even as serialized value inside array.
To save the next person some time, I added this new docs page.
Oh and I fixed the terms of the default content types, I was confused why they stopped working when I added the documented filter.