readme: Sourcing SEO data from existing page content & general overhaul #58
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
jonaskuske
changed the title
jonaskuske
changed the title
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.
Was looking for a way to use existing page content for my SEO snippets instead of having to copy-paste excerpts from the content to the SEO tab and found that using extended page models is a very nice way to do so.
I suggest adding this technique to the docs as I think it's a valuable and common enough usecase to officially support – wrote the chapter Sourcing SEO data from existing page content to document how it works.
While working on this I got a little carried away and gave the entire README a facelift (and also fixed some inaccuracies, e.g. wrongly-documented defaults) :)
You can see the rendered version here, let me know what you think!
Edit: just found issue #14, guess this would fix it in a docs-only way? 😅
fix #14
fix #60