please help me with the nav bar
if you can record a video explaining it please do
thank you
Every believer has received grace gifts,
so use them to serve one another as faithful stewards
of the many-colored tapestry of Godβs grace.
1 Peter 4:10
On Sat, Jul 2, 2022 at 12:03 AM Okoroji Victor Ebube <
@.***> wrote:
You have done a great job so far! πͺ π
You still need to work on a few issues before moving on to the next
project, but you're almost there!
Top highlight π―
The Pull Request is following the GitHub Flow β
The PR title and description are professional and descriptive β
Every comment with the [OPTIONAL] prefix is not crucial enough to stop
the approval of this PR. However, I strongly recommend you to take them
into account as they can make your code better.
You can also consider:
Cheers and Happy coding!πππ
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification.
Please, do not open a new Pull Request for re-reviews. You should use the
same Pull Request submitted for the first review, either valid or invalid
unless it is requested otherwise.
+Contributions, issues, and feature requests are welcome!
+
+Feel free to check the issues page.
+
+Show your support
+Give a βοΈ if you like this project!
+
+## Acknowledgments
+Hat tip to anyone whose code was used
+Inspiration
+etc
+
+## π License
+This project is MIT licensed.
You have a good readme structure and kudos for following the
Microverse template π . The MIT license you added ought to be a link
to the MIT file which is missing in your project. Please add the MIT file
so it can be referenced through the MIT link you will create in your readme.
I think you should consider adding a more personalized detailed
description of your portfolio project and its purpose. This will make your
project look more professional and anyone accessing your repo will have a
good understanding oof what your project is all about. Please look into it.
KIndly ensure that your sub-title ("Software Developer") is wrapped
in a header tag hx (i.e h2-h6). This is particularly good to make your code
semantic π and also helps screen readers have a better interpretation
of the content in the header(hx) tagπ
i.e
if you are referring to the hamburger being wrapped in a nav tag, this is what you are expected to do:
<nav>
// hamburger image
</nav>
This is so because the hamburger will contain the menu items which you will add later on in your project
This blog post will give you more insight. Kindly go through it.
hello
ihave tried to fit the image it has refused what can I do
Every believer has received grace gifts,
so use them to serve one another as faithful stewards
of the many-colored tapestry of Godβs grace.
1 Peter 4:10
On Tue, Jul 5, 2022 at 10:02 PM Daniel Maina @.***>
wrote:
Good job so far!
There are some issues that you still need to work on to go to the next
project but you are almost there!
Highlights
βοΈ No linter errors
βοΈ Github flow was correctly used
Required Changes β»οΈ
Check the comments under the review.
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop
the approval of this PR. However, I strongly recommend you to take them
into account as they can make your code better.
Cheers and Happy coding!πππ
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification.
Please, do not open a new Pull Request for re-reviews. You should use the
same Pull Request submitted for the first review, either valid or invalid
unless it is requested otherwise.
i have done this
Every believer has received grace gifts,
so use them to serve one another as faithful stewards
of the many-colored tapestry of Godβs grace.
1 Peter 4:10
On Wed, Jul 6, 2022 at 1:26 PM TufoinNkuo @.***> wrote:
There are some issues that you still need to work on to go to the next
project but you are almost there!
To Highlight
β You used the correct Github flow
β Descriptive pull request message
β linter error checks validated
β Documented your work professionally
Required Changes β»οΈ
Check the comments under the review
Optional suggestions
_Every comment with the [OPTIONAL] prefix won't stop the approval of this
PR. However, I strongly recommend you to take them into account as they can
make your code better.
Cheers and Happy coding!πππ
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification.
Please, do not open a new Pull Request for re-reviews. You should use the
same Pull Request submitted for the first review, either valid or invalid
unless it is requested otherwise.
As described in the Code reviews limits policy
https://microverse.zendesk.com/hc/en-us/articles/1500004088561 you have
a limited number of reviews per project (check the exact number in your
Dashboard). If you think that the code review was not fair, you can request
a second opinion using this form. https://airtable.com/shrQAqnBwek5a0O0s
please run it again because i dont want to redo
Every believer has received grace gifts,
so use them to serve one another as faithful stewards
of the many-colored tapestry of Godβs grace.
1 Peter 4:10
On Wed, Jul 6, 2022 at 1:47 PM Edith Oga @.***> wrote:
i have done this
Every believer has received grace gifts,
so use them to serve one another as faithful stewards
of the many-colored tapestry of Godβs grace.
1 Peter 4:10
On Wed, Jul 6, 2022 at 1:26 PM TufoinNkuo @.***>
wrote:
There are some issues that you still need to work on to go to the next
project but you are almost there!
To Highlight
β You used the correct Github flow
β Descriptive pull request message
β linter error checks validated
β Documented your work professionally
Required Changes β»οΈ
Check the comments under the review
Optional suggestions
_Every comment with the [OPTIONAL] prefix won't stop the approval of this
PR. However, I strongly recommend you to take them into account as they can
make your code better.
Cheers and Happy coding!πππ
Feel free to leave any questions or comments in the PR thread if
something is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification.
Please, do not open a new Pull Request for re-reviews. You should use the
same Pull Request submitted for the first review, either valid or invalid
unless it is requested otherwise.
As described in the Code reviews limits policy
https://microverse.zendesk.com/hc/en-us/articles/1500004088561 you
have a limited number of reviews per project (check the exact number in
your Dashboard). If you think that the code review was not fair, you can
request a second opinion using this form.
https://airtable.com/shrQAqnBwek5a0O0s
Thanks for the feedback how can i merge?
Every believer has received grace gifts,
so use them to serve one another as faithful stewards
of the many-colored tapestry of Godβs grace.
1 Peter 4:10
On Thu, Jul 7, 2022 at 9:28 AM ismail courr @.***>
wrote:
βοΈ No linter errors
βοΈ Used Github Flow
βοΈ Work documented professionally
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this
PR. However, I strongly recommend you to take them into account as they can
make your code better. Some of them were simply missed by the previous
reviewer and addressing them will really improve your application.
Cheers and Happy coding!πππ
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification.
New pull request