I finally finished this project. I wish I could do better. I don't know how to optimize my code. I used the 'memo' hook but In the Navigation component, there is too much-repeated code. Also, I couldn't apply the background color transition to mobile design.
Shiva
@shivaprakash-sudoAll comments
- @sagekim6Submitted about 2 years ago@shivaprakash-sudoPosted about 2 years ago
Hello sagekim6,
I've tried to check the live site, but it seems like the styles and the images are not loading on to the site.
- This could be due to path issues when you're trying to link them into the html file.
- You need to convert the scss to css and then link the CSS file, not scss file.
- Why are you using
js
as file extensions when using react? - Try to start with mobile screens first and then go for larger screens. This way there are no need of many media queries.
- Also, try to use
min-width
in media queries, instead ofmax-width
.
Good luck!
Marked as helpful0 - @JordiM21Submitted about 2 years ago@shivaprakash-sudoPosted about 2 years ago
Hello Jordi Mantilla,
The chart component itself is looking good, but unfortunately I'm not able to see the generated chart.
I just checked in Edge browser and it is miraculously working!😂 I think the problem was with the Firefox browser, because I get the following error in my console, when I checked for any errors.
Uncaught SyntaxError: import assertions are not currently supported
. So lookout for these kind of things and try to do cross-browser testing.Anyway, after checking the bar chart in Edge, I have few suggestions.
- The bars could use some width in bigger screens, they look too skinny on my laptop screen😅.
- The hover states are working fine, but all of them are at the same height, which in my opinion, doesn't make sense in user experience wise. Also, in the design they're just above the bar, so try to achieve that. This can be done by putting the money positioned absolute to it's respective bar.
- Try to update your readme file using the readme template given along with the project files. It helps when someone else is looking at your repository.
- Try to wrap the card using more semantic tags like
section
,article
etc., and the attribution usingfooter
.
Keep up the good work!😊
Marked as helpful0 - @mouad-chakiriSubmitted about 2 years ago@shivaprakash-sudoPosted about 2 years ago
Hello Chakiri,
Your solution looks perfect!
Just a few things I'd like to suggest, if you don't mind.
- I think you forgot to add the hover eye effect to the main image, so please look into that.
- Try to use a separate file for styling, because it's better to maintain when the code gets bigger.
- Try to wrap the content using
main
, instead of justdiv
. - Usually sections are used for content which span across the full width of the screen, so here you can use
div
s inside the card and you can usesection
orarticle
for wrapping the whole card. - Try to update your readme file from the README-template file given along with project files, it helps you think about what you learnt and what you can improve on further.
Keep up the good work, I hope to see more of your work.😁
Marked as helpful0 - @celia-tosicSubmitted about 2 years ago
This challenge allowed me to practice SCSS and to use Autoprefixer !
@shivaprakash-sudoPosted about 2 years agoHello Cellmix,
The card looks fantastic on both mobile and desktop. I just have a few suggestions, if you don't mind.
- A little bit of top and bottom padding to the button on bigger screens would make it look even better.
- Try to put the attribution outside of the card and inside a
footer
. - The font sizes can be increased a little bit on bigger screens, so that they don't look small.
h1
tag is usually used for page headings and for other sections and components, usuallyh2-h6
tags are preferred.- Semantic tags can be used for the card component, like
section
,article
, etc., for better accessibility.
I hope my feedback is helpful. Good luck!
Marked as helpful0 - @Paula-CarlechSubmitted about 2 years ago
My difficulty was about creating the chart, I cound´t find a way to change the colors and fonts so I can build something like the original design. Any suggestion are welcome.
@shivaprakash-sudoPosted about 2 years agoHello Paula,
The chart component looks good on desktop screen, but there are few issues with it as given below.
- The chart doesn't seem to be very responsive, because on small screens the chart width is becoming too small to hold the bar chart.
- I see that you're using a chart library to draw the chart, I tried using chart.js, but I couldn't make it work and look like the design, since I had no experience with it, so I dropped that and drew the chart from scratch using inline styling. The only suggestion I can provide here is that, if you're not experienced with the library, try not to use it and try to solve the problem in a different way. This way you'll get to learn many new things and also how to approach a problem without using libraries.
- Regarding the usage of semantic tags, you can wrap the chart component inside a
main
tag and the attribution inside afooter
tag. - Coming to the script, you can put JS code in a different file and link to it in the head section of the html file, this way the code looks more organized and easy to maintain.
I hope the above points are helpful and I hope to see more of your work, good luck😊.
Marked as helpful1 - @Irina-DehtiarenkoSubmitted over 2 years ago
-
The only problem I think I have for now is I don't understand why doesn't it show me a new tip every time I click? Maybe it is related to getting data from api, do I have any problem in the code?
-
One more question about CSS styles and HTML structure: how else could you build these extra accesories at the bottom of the board?
@shivaprakash-sudoPosted over 2 years agoHello Iryna,
- You can get around the caching by putting the below code as a second argument in the
fetch
API.
{ cache: "no-cache" }
After I've done this in my code, I started to get a new advice every time I clicked. Let me know if it doesn't work.
Marked as helpful0 -
- @BubblecrownSubmitted over 2 years ago@shivaprakash-sudoPosted over 2 years ago
Hello BubbleCrown,
The output looks amazing, even the dark and light modes are working fantastically, good work!
Few things to consider:
- Try to change the default README from Create React App to project specific file to showcase your work and what you've learnt. A template for this can be found in the files given with the project.
- Why was
type
used as the folder name when you've created interfaces inside it?🤔 - Also, try to check your report for the site, it seems to have many issues regarding the semantic approach.
Happy coding!
1 - @TalkitiveSubmitted over 2 years ago
Nothing is difficult in this project but i just practiced some skills which will make me a better developer one day..
@shivaprakash-sudoPosted over 2 years agoHello Roy,
- The styles aren't applying to your site, this is because you've put the
link
tags inside thebody
, instead ofhead
section. - Try to change the default title of the document to the respective project or just use the template given in the project files.
- Try to have only ONE html file, instead of having multiple of them in multiple folders.
- Try not to use uppercase words for file naming, they look aggressive.
- Try to use
main
tag for main content inside the body for more semantic and accessible approach.
Happy coding!
Marked as helpful0 - The styles aren't applying to your site, this is because you've put the
- @Tammy-AjokoSubmitted over 2 years ago
- I'm learning how to use media queries to make my site also look well on mobile view.
- I noticed when I viewed my site on my mobile phone all the gap I put in the code was gone. why this is so I don't know, or I shouldn't make use of gap anymore. Any suggestion on any part of the code is very welcome.
@shivaprakash-sudoPosted over 2 years agoHello Tammy,
I have few things to say:
- Try to put the CSS in a separate file, instead of putting inside the html file.
- It's better to create new repository for a new project, instead of having all the projects in one repository. Having own repository for a particular project is easy to handle and maintain.
- Regarding the website, it only changes the layouts when the screen width is below
375px
. This is becausemax-width
property was used instead ofmin-width
in the media query. The width properties given in the design are just for reference, you don't need to code particularly for those widths. - Try to code for mobile screens first and then change the layouts accordingly for bigger screens using
min-width
property in media queries. For example, have one kind of layout until 600px (mobile screens) and then usemin-width: 600px
(tablet screens) property to change layout for screens starting with width 600px. For even bigger screens, you can use min-width of 1000 or 1100px. Try not to put too many media queries. - Finally try to wrap the main content of the site inside body in a
main
tag.
Happy coding!
0 - @om205Submitted over 2 years ago
Why cannot other people see background image (using url) in my solution from github page link url?
@shivaprakash-sudoPosted over 2 years agoHello Dubey,
GitHub looks for images using relative path, so we have to give relative path to the images instead of absolute paths. Instead of the path you've given, try
./images/your-image-name.png
. Here.
represents current folder (one dot means one step upwards into the folder structure), since the images are inside theimages
folder, you go into that to choose the image.Few notes to consider:
- Try doing the design for mobile screens first and then change the layouts for bigger screens using media queries.
- Once we code for the mobile, we don't have to repeat the same code for bigger screens too, we just change what is needed to be changed after a certain breakpoint.
- Try not use fixed widths for images or image containers, try using
max-width: 100%;
for images, so that they behave responsively. - Try to use
rem
orem
instead of pixels, to make the site easier for responsiveness.
Happy coding
0 - @OmarMAttia7Submitted over 2 years ago
Any feedback you have is appreciated. The screenshot is missing some images, apparently the platform can't handle image lazy loading correctly.
@shivaprakash-sudoPosted over 2 years agoHello Omar,
I've checked the live site and it looks really good. I like the way you used TypeScript in the components, keep up the work!
Just a small note, you could add few screenshots to the README file, so that whoever comes to that repo would know how your site would look without them having to open the live link.
Happy coding!
Marked as helpful0 - @archisvazeSubmitted over 2 years ago@shivaprakash-sudoPosted over 2 years ago
Hello Archis,
Your site looks good and everything works as expected, good work.
Few things to note:
- There are some accessibility issues, so check your report once and try to resolve those.
- Try to have the same font-family as the design, so that it looks very close to the design. Keeping the site as close as possible to the design is a good skill.
- Also, try to change the title the of the page from the default title.
- I wanted to check the code, but the link isn't working, please check that once.
P.S. I checked your movie app and the animation of the movie details on hover is a good touch.
Happy coding!
Marked as helpful1