Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

All comments

  • @martinelias1312

    Submitted

    This was one of my longest challenges, i tried to do it all on my own. Mostly i struggled on sending props from one component to other. But anyways, i learned to fetch data, from local json in this case, communicate through components, little bit of typescript...

    I am little bit unsure of my components folders layout and i am not sure if i used best practive for scss files layout. (should i use module.scss ?)

    Thanks for feedback!

    Daily/weekly/monthly time tracking dashboard

    #accessibility#fetch#react#sass/scss#typescript

    2

    @martinelias1312

    Posted

    Anyways, first challenge with React !!

    0
  • voqh 130

    @Voqh

    Submitted

    When working on a small view port, how do you make sure your site will display the same way on a larger view port?

    Responsive Landing page using CSS Grid

    #accessibility#materialize-css#semantic-ui

    1

    @martinelias1312

    Posted

    Hello @Voqh,

    Media queries are commonly used to code your site on larger viewport. here are two good articles about your question:

    Developer Mozilla Network and CSS Tricks

    Marked as helpful

    0
  • @WildTsunami

    Submitted

    I didn't know how to make the :hover with the top image, but otherwise it was pretty simple.

    Still taking advices of course, I'm a begginer and want to improve :)

    @martinelias1312

    Posted

    Hello @WildTsunami, look at my solution how i have done it. I started with the variable cyan color and changed its opacity to 50%. (:root section).

    One more suggestion:

    • alternate text can be left blank if images are only decorative, like icons of ethereum or clock.

    If you have any questions and don´t understand something from my code, feel free to ask!

    Marked as helpful

    2
  • @martinelias1312

    Posted

    Hello @SachinShelke7, my few suggestions:

    • main content should be wrapped in <main> element
    • <div class="attribution"> can be wrapped in <footer> element
    • on larger screens than 1440px, background image is not at full size, so i´ll recommend to use background-size: 100%; at <body> element

    Marked as helpful

    0
  • Nelson 60

    @nelsonfleig

    Submitted

    How would you rate my use of Html tags and naming of css classes?

    Do you think my SCSS files are structured properly?

    Any general tips?

    @martinelias1312

    Posted

    Hello @Kokopelli84, i have some suggestions. Accessibility issues:

    • main content should be wrapped in <main> element
    • there should be <h1> heading, article here

    Marked as helpful

    1
  • @martinelias1312

    Posted

    Hello @Aryan-ki-codepanti, my few suggestions:

    • add one more media querrie with min-width: 900px and change wrapper width.
    • <h1> should be used once, article about it [here](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements).

    Anyways good job!

    0
  • @martinelias1312

    Posted

    Hello @Old1337, my suggestion isto use <a> element istead of <input>, which is usually used for forms.

    • i saw border-radius is not fixed at 768px to 1100px on .left and . right cards
    • "per month" words are also causing troubles at 430px to 1100px, style it in media queries

    Anyways good job on this challenge!

    0
  • @martinelias1312

    Posted

    Great job! Nice responsiveness and animations!

    1
  • @CEC-IL

    Submitted

    The cancel order anchor tag doesn't take padding or margin. how should I have handled that better ?? Any suggestions or help will be much appreciated

    @martinelias1312

    Posted

    Hello @CEC-IL, you have to change anchor element from inline to display: block/inline-block. Then you can use margin and padding.

    Also you should only use <a> element without <button> element.

    Another accessibility issues can be fixed like this:

    • wrap main content in <main> element. E.g. instead of <div class="content"> use <main class="content">.
    • alternate text can be left blank if images are only for decoration
    • this <div class="attribution"> can be wrapped in <footer> element for better accessibility too

    Hope this helps a bit :)

    0
  • @martinelias1312

    Posted

    Hello @Katja721, few suggestions from me:

    • <img> element should have alternate text. It´s a description of what is on image. This will fix accessibility. E.g. <img alt="User avatar">. Alternate text can be left blank while images are only for decorative usage. This can be used in this case for ethereum and time icons.
    • <body> should contain whole page, so it starts under </head> tag and ends before </html>
    • you should use <main> element instead of <div class="container">, which will fix another accessibility issue
    • <div class="attribution"> this whole code can be wrapped in <footer> element for more semantic HTML layout and accessibility
    • i will personally add media queries from 400px to 800px and style .container to be in center and be more wider

    Hope this will help you on your next challenges!

    Marked as helpful

    0
  • @mustafaalkhiat

    Submitted

    I dont really understand diffrence between padding and margin, so i use them both. Is there any specific use cases? thank you for answering from now💖💖👍

    @martinelias1312

    Posted

    Hello @mustafaalkhiat, padding is the space between the content and the border, whereas margin is the space outside the border. Recommended aritcle about it here.

    Marked as helpful

    0
  • Roshan 10

    @Roshan310

    Submitted

    Hello everyone! This is my first ever self-made project. I'm pretty new to the coding field and this was my first time coding something myself. I was following the tutorial before but not this time. Is there anything specific you would love to see? Please give any feedback you have. Hugely appreciate it.

    NFT-Card-Preview using HTML and CSS

    #accessibility#materialize-css

    2

    @martinelias1312

    Posted

    Hello @Roshan310, accessibility issues can be fixed by:

    • wrapping main content in <main> element
    • using at least one <h1> heading

    Marked as helpful

    0
  • Max Ruuen 290

    @ruuen

    Submitted

    If there was a more elegant way to achieve the grid layout than using my grid shorthand + grid-area declarations, please let me know - I would love to see alternatives!

    Also any feedback on my class names is much appreciated too.

    @martinelias1312

    Posted

    Hello @ruuendigital, i have done it like this E.g.:

    @media screen and ( min-width:1300px ) {
        .cards-wrapper {
            grid-template-columns: 1fr 1fr 1fr;
            grid-template-rows: 0.5fr 0.5fr 0.5fr 0.5fr;
        }
    
        #card-supervisor {
            grid-row: 2 / 4;
        }
    
        #card-team_builder {
            grid-area: 1 / 2 / 3 / 3;
        }
    
        #card-karma {
            grid-area: 3 / 2 / 5 / 3; 
        }
        
        #card-calculator {
            grid-area: 2 / 3 / 4 / 4;
        }
    }
    

    My solution link.

    Marked as helpful

    1
  • @martinelias1312

    Posted

    Hello @Kamasah-Dickson,

    • alternate text should be descriptive, and when pictures have decorative character you can left alt"" blank, like in this case.
    • <button> element as a descendant of <a> is unnecessary, so i suggest using only anchor and styling it
    • <h1> element should be used once per page. There are some exceptions, article about it [here](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements).
    • in this case i suggest to use h2 elements, and h1 element hidden for only screen readers.
    • you forgot about bottom border-radius to set "0" on Sedans and top border on Luxury at 375px screens
    0
  • @martinelias1312

    Posted

    Hello @osoriodev, i have one suggestion:

    • instead of using <p class="about__descrip"> and <span> in it, i recommend to use unordered list with lists in it.
    <ul>
    <li>Tutorials by industry experts</li>
    ........
    </ul>
    

    Good job on responsiveness!

    Marked as helpful

    0
  • @martinelias1312

    Posted

    Hello @DummyKen, from 376px to 655px cards are on each other.

    This is the problem and should be changed: .cards .push { transform: translateY(110px); } Media querie with max-width 975px and transform: none; at this px should fix this prob.

    And i suggest using more relative units (em, rem...) instead of px. Article here.

    Anyways goo job and hope this helps.

    Marked as helpful

    0
  • @martinelias1312

    Posted

    Hello @MSA-new,

    i suggest to:

    • change .img-container { border-radius: 10px; } to 13px, because of visible cyan borders
    • wrap <div class="attribution"> in a <footer> element for better accessibility
    • missing <h1> element, there should be also one for better accessibility. Article about it here.
    • for more responsiveness, you can use relative units - em, rem, %.. and max-width instead of width. Article here.

    Hope this helps for future projects :)

    0
  • @martinelias1312

    Posted

    Hello @subhamengine, few tips about accessibility issues:

    • main content can be wrapped in <main> element <div class="background">
    • <h1> should be on page, but used only once per page, article about it [here](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements)
    • this <div class="attribution"> can be wrapped in <footer> element
    • alt="image" alternate text should be more descriptive like: "Women sitting in an office"

    Anyways nice job and hope my suggestions help :)

    0
  • @martinelias1312

    Posted

    Hello @KhaledAhmedKassem,

    one suggestion from me is that you can use relative units em, rem, % instead of absolute units(px) and max-width instead of width.

    Article about units here

    Marked as helpful

    0
  • @martinelias1312

    Posted

    Hello @danieldudu, accessibility issues can be fixed like this:

    • main content can be wrapped in <main> element instead of your <section class="card-container bg-card">
    • you should use <h1> heading per page

    Good job anyways on this challenge!

    0
  • @martinelias1312

    Posted

    Hello @asifsalim, few tips about accessibility issues:

    • main content can be wrapped in <main> element
    • alternate text should be left blank while images are only decorative like in this case - alt=""
    • <h1> should be used only once per page, article about it here
    • heading levels should be increased by one means that if you have <h1> then you should use <h2>....<h3>....

    Anyways nice job and hope my suggestions help :)

    Marked as helpful

    1
  • @JaydenTeoh

    Submitted

    Not sure what are the actual instructions for the media component for screen vs desktop users. Both the provided images of the designs look the same when on screen vs on desktop. Do provide pointers on where to improve and make my code more efficient!

    @martinelias1312

    Posted

    Hello @JaydenTeoh, few suggestions for better semantic HTML layout and more accessible page:

    • instead of <span class = "title"> you can use <h1> heading (article here)
    • you can wrap your main content by <main> element (<div class = "container">)
    • signature <div class="attribution"> can be wrapped by <footer>
    • alternate text can be left blank while images are only decorative like in this case alt = "icon-ethereum" and alt = "icon-clock" ---> alt=""
    • also alternate text should be descriptive - what is exactly on the image (article here)
    • and for more responsive page you can use relative units em, rem, % (article here)

    Hope this will help you on next challenge :)

    0
  • @martinelias1312

    Posted

    Hello, my few suggestions:

    • for better accessibility alternate text in <img> elements should have descriptive text of what is on the picture. But if the picture is only decorative alternate text can be blank - alt=""
    • for positioning your NFT card u can use this instead of absolute positioning:
    body {
    display: flex;
    justify-content: center;
    align-items: center;
    height: 100vh;
    }
    

    Hope this tips will help for next challenge :)

    1
  • @Gioltek

    Submitted

    Hello! This is my first project after one week of learning html and css, and it's been a blast so far! I learned a lot thanks to this challenge, especially some neat grid related stuff and responsive tricks to adjust the site accordingly to a device's screen size. I really liked the challenge overall and I suggest it to other html and css beginners, it is amazing! Some of the stuff I found hard to achieve: correct grid setup, grid centering. Two things I know are incorrect: I have put the icons at the end of the box using margins, but this causes a problem regarding their position in relation to the description: if the description is one line long, the icon is shown higher in the box; if the description is two lines long, the icon is shown lower. I know there is some kind of fix to this, probably I shouldn't have used margins but something else. The other incorrect thing is the height of the page. I would've liked the page to not be scrollable, and instead be just a single page, but probably I got my sizes wrong and the page is now scrollable. I could've fixed it readjusting all the sizes, but I couldn't be bothered. Is there something easier to fix this issue? Thanks for your time!

    @martinelias1312

    Posted

    Hello Giovanni @Gioltek, i see that you have done a great job after one week of learning!

    The positioning of the picture i did like this:

    • wrap <img> element in <div class="img-wrap"> with class img-wrap
    • and CSS: flexed it
    .img-wrap {
        display: flex;
        justify-content: flex-end;
    

    And the page with scroll bar ? It´normal like David said. Hope this will help you with another options how to position your image :)

    Marked as helpful

    1