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

  • P
    Nico 330

    @Nico243

    Submitted

    What are you most proud of, and what would you do differently next time?

    This was my greatest challenge I've had. It took mistakes and errors and constantly adapting to new techniques and methods to help me through this. The inspection tool was my best friend for the grid layout.

    Now that I have an Idea how the structure is going to look and how I could achieve the layout, I'm going to look a little more deeper on how I could right this code cleaner for readability and accessibility.

    What challenges did you encounter, and how did you overcome them?

    CSS Layout Alignment

    Challenge: One of the difficult parts initially in aligning elements within the testimonial grid and handling images and text properly.

    Solution: By playing around with CSS properties such as display: grid, grid-template-areas, and using flexbox (display: flex), I was able to control the layout and position elements next to each other. For precise positioning, I've learnt how to adjust margins, padding and align-items.

    Background Image Positioning

    Challenge: There was a problem of getting the SVG (quotation pattern) to appear at the right place in the first testimonial.

    Solution: After trial and error, I have learned that adjusting background-position and background-size can put SVGs where they should be. This needed deep knowledge on functioning of CSS background properties as well as exactly how pictures ought to be aligned.

    Media Queries for Responsive Design

    Challenge: It was complicated because my layout shifted dramatically when applying different screen sizes, making it hard to use grid-template-areas in media queries for responsive design of testimonial layouts.

    Solution: I tried out several alternatives for grid-template-areas setups and found that by changing configurations differently for certain screen width ranges, you could keep things consistent across all devices.

    Font Sizing and styling in css

    Challenge: Ensuring font size and weight using CSS variables and the second had different styling.

    I've learned how to apply specific classes and make use of CSS ('var(()') to manage typography. I've also used inline styles to override inherited styles when needed

    SVG handling & Positioning

    Challenge: Intergration of SVG image inside a specific testimonial and aligning it perfectly.

    Solution: using a testimonial:nth-child(1) to place the svg in it's correct container

    Frustration and Overwhelmed

    Challenge: Feeling overwhelmed by the complex system of CCS layouts, when smaller changes would drastically alter my design.

    Solution: I've persisted through, frequently asking questions to gain clarification, watching tutorial videos. By breaking the challenges into smaller, more manageable tasks, I made progress step by step.

    using advanced CSS techniques

    Challenge: The us of advanced techniques like nth-child, grid-template-areas and media queries felt unfamiliar and difficult to implement

    Solution: I've practiced wit examples, Adjust my layout based on feedback from others, and slowly became more comfortable using these techniques.

    It comes down to persistence to testing different solutions, asking the correct questions, breaking the complex layout into smaller tasks which helped me overcome these challenges

    @SemptechVzla

    Posted

    Very nice!

    0
  • @SemptechVzla

    Posted

    Amazing! But i am not sure why you using @media screen

    0
  • @SemptechVzla

    Posted

    Semantic HTML and CSS Flexbox

    0
  • P

    @jguleserian

    Submitted

    What are you most proud of, and what would you do differently next time?

    Greetings, Everyone!

    Thank you for taking the time to take a look at my work and give me some feedback. I know your time is valuable, so I am grateful for you critical eye and subsequent suggestions.   While much of this project was straight forward, I did find some challenges with formatting the bullet points correctly. I feel happy that I was able to get a better sense on how to manipulate them more competently. In addition, this was the first project that I took advantage of HTML ``, and I think it worked out pretty well.

    Finally, I feel like I am more comfortable with GitHub, although it still makes me want to pull out what's left of my hair, as I explain below.

    What challenges did you encounter, and how did you overcome them?

    My first challenge was the formatting of bullet points. I don't know why this has eluded me so much. The problem comes in trying to create an li::before in the CSS. Once the source is referenced, the problem has been getting the bullet point to sit correctly on the line to match the text to the right. I had to resort to negative margins to help put it in the right place.

    My second challenge, as has been consistent with several projects I've done, is my struggle with GitHub. While it is a wonderful tool, I notice that when everything looks good launching my site from VS Code, the same code launched from GitHub may have things missing. This usually occurs when a resource is found in another folder, such as the elipse (used for the bullet point), as referenced in the stylesheet as a "content" resource. It also seems to occur elsewhere, but this is where I noticed it this time. Sometimes taking off the forward slash, /, solves the issue, but sometimes it does not. Got this reason, if you look at the solution on GitHub, two sections are missing the bullet points, but you will of course see them in the screenshot I provided.

    Anyway, if anyone has any help with respect to either of these, I would greatly appreciate it, especially navigating the labyrinth of GitHub pages.

    What specific areas of your project would you like help with?

    As mentioned above, I would be so grateful if someone could take a look at my code and let me know how I can improve, in any area, but specifically with respect to the bullet points and GitHub.

    Thank you so much for taking a look at my submission. I appreciate any encouragement or insight.

    Happy coding!

    @SemptechVzla

    Posted

    great! , i would like to learn how you did this.!

    0
  • @SemptechVzla

    Posted

    it's blank

    0
  • @SemptechVzla

    Posted

    it's perfect! but, i couldnt watch the code it's say page not found 404

    0
  • @hcolmenares

    Submitted

    What are you most proud of, and what would you do differently next time?

    I considered using a "mobile first" approach, but since the component is simple, I decided to use some responsive aspects like relative widths (e.g., 90%) and the use of rem.

    @SemptechVzla

    Posted

    Very nice Job.! Wondering if you use any framework or it is pure css native.

    0