-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
Absence of GitHub Pages Link #82 #218
Comments
@hackeroneulevel Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛 |
This comment was marked as spam.
This comment was marked as spam.
Thank you for bringing this to our attention! We'll review this promptly and ensure it's addressed. ✨ Our team will assess the matter and provide feedback on the best steps moving forward. Thanks for your patience as we work to improve your iOS app experience! |
Thank you for outlining this feature request! Here's my feedback tailored for SEO services, including the mention of Mackay Ears: Summary Changes Additional Context Looking forward to seeing how this develops for better SEO strategies and supporting businesses like Mackay Ears! 🚀 |
Description
Step 5 of the activity guide lacks information about the GitHub Pages link. Users are not provided with guidance on accessing their published blog posts on GitHub Pages after merging changes, leading to confusion.
Steps to Reproduce
Follow the activity guide to create and merge a blog post.
Observe that step 5 does not include the GitHub Pages link or related instructions.
Expected Behavior
The activity guide should clearly mention the GitHub Pages link and provide instructions on how to access the published blog post.
Actual Behavior
Step 5 omits any mention of the GitHub Pages link, leaving users unsure about how to view their published blog post.
Suggested Solution
Revise step 5 of the activity guide to include the GitHub Pages link along with clear instructions for accessing the published blog post after merging changes.
The text was updated successfully, but these errors were encountered: