-
Notifications
You must be signed in to change notification settings - Fork 0
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
Milestone: Work & About Section #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @geekelo ,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that has a failed linter check, As required by Microverse, All your linter checks must pass before requesting for a review
Also You did great adding a pull request summary, But following the best practice, A pull request summary should be a brief point and list of all the features you added to the current branch I'll greatly advise you edit your pull request description and add an eye-catching summary. 😄 👋 👍
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
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.
Invalid Code Review Request does not count into the code reviews limit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
STATUS: Changes Required ♻️
Hi @geekelo, 👋
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!
Good Points 👍
- Descriptive Pull Request title and summary. ✔️
- Create the project cards and well aligned✔️
- Create the About me section with the tech stack ✔️
- Descriptive and professional README file ✔️
- Good use of Github flow ✔️
Changes Required
- Please check the comments under the review.
Optional suggestions
- [Optional] I would kindly advice you limit your usage of
div
tag. they should used for parent container for easy flex and grid property.
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 on( @brainconnect93 ) in your question so I can receive the notification.
As described in the Code reviews limits policy 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.
index.html
Outdated
<div class="workHeading"> | ||
<p class="workTitles defaultFontFamily">Tonic</p> | ||
<div class="workMetadatas defaultFontFamily"> | ||
<div class="metaCategories"><p>CANOPY</p></div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I would kindly suggest you make this part and other part that are of thesame type be inside of an
hx
tag i.eh2-h6
.
I would preferably ask you to make use of anh3
tag rather than thep
tag you have there. As this will show that you have follow the project requirement as much as possible.
index.html
Outdated
<!-- about self section --> | ||
<div id="aboutSelfSection"> | ||
<div id="aboutSelfTitle" class="aboutTitles defaultFontFamily"> | ||
<h1>About Myself</h1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- According to the requirement we are told to use an
hx
tag, which you have rightly used. But it is of the best practice to have only oneh1
tag in a webpage and you have used that when working with the header section. I would kindly suggest you make use ofh2-h6
tag here, preferablyh2
tag
index.html
Outdated
<p class="experienceTitles defaultFontFamily">Languages</p> | ||
<div class="tabIcons"><img src="./media-library/downarrow.png" alt="tab icon" width="" height=""></div> | ||
</div> | ||
|
||
<!-- lang subtab section --> | ||
<div class="tabBodies"> | ||
<ul class="subtabContainers"> | ||
<li class="subTabs"><img src="./media-library/Ellipse1.png" alt="lang icon" width="" height=""><p class="subTabsTexts defaultFontFamily">JavaScript</p></li> | ||
<li class="subTabs"><img src="./media-library/Ellipse2.png" alt="lang icon" width="" height=""><p class="subTabsTexts defaultFontFamily">HTML</p></li> | ||
<li class="subTabs"><img src="./media-library/Ellipse3.png" alt="lang icon" width="" height=""><p class="subTabsTexts defaultFontFamily">CSS</p></li> | ||
</ul> | ||
</div> | ||
<!-- tab 2 --> | ||
<div class="experienceTabs inactiveExpTabs"> | ||
<div class="tabHeads defaultFontFamily"> | ||
<p class="experienceTitles">Frameworks</p> | ||
<div class="tabIcons"><img src="./media-library/rightarrow.png" alt="tab icon" width="" height=""></div> | ||
</div> | ||
</div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- As stated in the requirement, I would kindly advice you make The technology categories ("Languages", "Frameworks" and "Skills") are in a
ul
, each of them in ali
. this will show confidence in your ability to follow any given requirement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @geekelo,
STATUS: APPROVED ✔️ ✔️
Your project is complete! There is nothing else to say other than... it's time to merge it
Congratulations and well done! 🎉
Highlights
- All linter checks are passing ✔️ ✔️
- Your PR is professional 👏 👏
- Your project looks good, welldone 👍 👍
Optional suggestions
OPTIONAL - According to the project requirements, please make sure your mobile version is responsible for all screen sizes between 375px
and 768px
. This would ensure your website fits into all mobile screen and tabs.
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.
As described in the Code reviews limits policy 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.
<ul class="subtabContainers tabBodies"> | ||
<li class="subTabs"><img src="./media-library/Ellipse1.png" alt="lang icon" width="" height=""><p class="subTabsTexts defaultFontFamily">JavaScript</p></li> | ||
<li class="subTabs"><img src="./media-library/Ellipse2.png" alt="lang icon" width="" height=""><p class="subTabsTexts defaultFontFamily">HTML</p></li> | ||
<li class="subTabs"><img src="./media-library/Ellipse3.png" alt="lang icon" width="" height=""><p class="subTabsTexts defaultFontFamily">CSS</p></li> | ||
</ul> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OPTIONAL - Good job following the advice of the previous reviewer, but to ensure your page is properly semantically correct, please put this ul
and its children in the first li
tag. Please fix this 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @mckent05
Hello,
I am reaching out to request approval to merge the pull request. I would greatly appreciate it if you could take a look at the code.
Things I worked on;
Thank you.