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 solutions

  • Submitted


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

    My fluency is layout and JS calculations is going up rapidly.

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

    I tried to make all of the elements keyboard accessible but I am not sure how to make the radio button grouped. I added an 'aria-label' but I'm not sure that's enough.

  • Submitted


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

    I am improving my use of semantic HTML and adding roles for accessibility. I am understanding better how tab-indexing works and including it in my functionality. I feel like I leveled up on this project and I'm getting faster and more confident in my coding.

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

    Lightbox was a challenge to add to the finished site, fun to learn. Lots of JS tricks implemented and a lot of media changes in the mobile version.

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

    a11y and ARIA headers.

  • Submitted


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

    I'm proud that I used anchor positioning for the first time (using it on the mobile hamburger menu). I strengthened my a11y code with strong use of semantic headers.

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

    ensured the page was SR friendly

  • Submitted


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

    I didn't nail the a11y this time but I worked out a decent solution with keyboard navigation and screen reader.

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

    Lots of reading about a11y form best practices. It was hard to combine what I've learned to this point with how to structure a11y syntax. It's a long process to synthesize the two.

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

    more fluent a11y code

  • Submitted

    FAQ Accordion

    • HTML
    • CSS
    • JS

    1


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

    I'm proud of working through the solution and some tricky spots like having it expand on clicking the question or the plus-sign in the same function. I'm still struggling with a11y and I'm not fluent in what to do yet.

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

    Lots of bugs along the way that I worked through with patience and experience.

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

    a11y

  • Submitted


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

    I'm proud that I took time to work out solutions to the form submission and checkbox responsiveness and pseudo-elements myself. I started with the JS structure but the design and layout was more interesting to me and got me sidetracked. I want to complete the JS first before building the layout in the future. I'm excited with how the animations turned out.

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

    adding a11y and tabindex functionality was tricky. I was able to get tab entry working but it's not perfect. I have a lot of div headers that I couldn't make any more semantic.

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

    The a11y output isn't perfect and and jerry-rigged a lot of it at the end, adding random 'aria-labels'.

  • Submitted


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

    I'm proud of working through lots of JS challenges and slowdowns. I had to use a lot of external resources and found experts I wouldn't have found otherwise. I get stuck with trying to have multiple JS threads going and I figured out how to have one, but it might be a long thread that repeats a couple of times.

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

    I got stuck for a long time on working with both the data from the json file and the input from the user coming together. I got frustrated with local variables and not being out to scope them globally but I worked out a creative solution where I tie the correct answer to the button itself, I was excited when I figured out how to do it.

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

    My JS code can be wordy and this one possible repeats. I re-fetch the data list everytime an answer is clicked by the user and that seems like it wouldn't be efficient for future large projects I work on (but it works fine here with a smaller data file).

  • Submitted


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

    I am excited about the custom checkboxes I built that kept the green theme, and the animated labels that appear after copying or hitting the button with no boxes checked. I am not confident in my JS solution with the long characters arrays that I push into one long array. Also, I am sure there's a way to reduce the conditionals for the box colors but I can't see how to re-factor those.

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

    JS script has long blocks that I couldn't figure out how to re-factor. Long arrays and conditionals. It works and I'm looking for feedback.

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

    Re-factoring my JS to more concise, targeted syntax.

  • Submitted


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

    the color scheme is different than the template because I made two versions I'm happy with the final output. I grinded through a lot of JS coursework to get it right. I had trouble with the values filtering into one 'calculate' function, I learned that I can add a call to a single function from multiple events.

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

    generally I struggled with the JS, but worked hard to figure out the best solution. Looking forward to hearing feedback.

  • Submitted


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

    I'm proud that I came up with some solid data fetch syntax. I'm worried that I used the fetch syntax three times, one for each timeframe. I couldn't think of a way to reduce that to one fetch overall, which maybe can be done on "DOMLoaded" event. I also wasn't thrilled with how many lines of JS was required for each data point and I'm looking for ways to reduce all of those lines to keep it cleaner code.

  • Submitted


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

    I'm proud of solving all the details related to the email error messaging, like using JS to change the styles. I also liked building out a modal that's useful

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

    I had to use a lot of outside resources and learning platforms to get up-to-speed on inputs, and I had a lot of issues with the submit button and the correct form syntax. I wrestled with it and feel good about the outcome.

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

    JS is going to take a while to become fluent in.

  • Submitted


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

    mapped out the mobile width and media queries better. I got the mobile footer overlay done but I never could sync it with the arrow button. Also frustrated the tooltip doesn't load on first click, maybe I need to add another element over it that's transparent.

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

    too much code, wrote many lines, ready to move on

  • Submitted


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

    I spent too much time in the weeds fine tuning pixels, gaps, box-widths, etc in order for it to work on three media queries. I'd like to spend more time planning next time.

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

    Learned a lot about the usefulness of 'justify-self' when moving images around within grid. Had to undo a Flex layout for a Grid layout on the hero section for the tablet, figuring out how to move the text button the circle images was tricky

  • Submitted


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

    I wish I had done a mid-sized width with two columns, it's a huge switch from 4 columns to one. Proud that I tested my skills and text wrap edits.

  • Submitted


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

    I'm proud that I used both flex and grid, got the border color and height just right, and used absolute positioning for the image icons.

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

    in the smaller width media query, it took me a minute to realize I have to 'reset' the grid-template-rows or the grid tries to force itself into the bigger pattern even at one column.

  • Submitted


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

    Loved using Grid combined with responsiveness

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

    spacing and general grid sizing in responsive mode

  • Submitted


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

    I planned the layout ahead of time, and took advantage of sections and Flexbox layout.

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

    Centering a div, image widths can be tricky. Learned how to style a table, still didn't do it perfectly.

  • Submitted


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

    I should have planned more at the start instead of diving right in. I solved it as I went, and feel like my good mobile adjustments were more luck than planning ahead. I could have made the container wider but it's hard to know the dimensions when just eyeballing it.

  • Submitted


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

    I refined my CSS block-building skills. I enjoyed learning about 'inline-block' as a way to make sure an element box doesn't extend across the whole container width (for adding a background to the "Learning" text).