docs: update create personal feed page #430
Closed
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
PredictiveManish
suggested changes
Nov 1, 2024
There was a problem hiding this comment.
@tobySolutions I think your image tags have some issues, try to find out and solve it I think you've given it in good style, try to add height too and also if possible then upload these images to cloudinary platform and then paste the link here as it is good practice and the images directly being fetched from that place and you don't have to upload images.
|
hi @tobySolutions and thanks for the PR. For now we decided to not proceed with this changes, but thanks anyways! |
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.
This pull request adds updates to the "creating a personal feed" flow for new users to the daily.dev platform. I did some restructuring to get in updated information relevant to new users of the platform.
I hope my branch naming will not be a problem? Please help review this, thank you 😁.
This fixes the PR #391