@Igorsimic1988Submitted about 2 months ago
P
KMS56135
@KMS56135All comments
- @Sudhanshu943Submitted about 2 months ago
- @astnioSubmitted 2 months agoWhat challenges did you encounter, and how did you overcome them?
This project was fine for the most part. I learned a lot about styling forms and setting up displays for errors.
The biggest challenge I had was actually self-inflicted, as I wanted the elements to move across the screen as a transition from submitting your email to having the success message. Before this point, everything was styled and working fine, but in order to get the transition to work I had to change everything to absolute positioning. I'm sure there was a better way to handle this, but this was just how I figured it out. One of the major issues with this is the fact that the major sections are no longer easily centered on the screen, and I had to use some magic numbers to get them to look right. It also messed up the views from desktop to mobile, which required some more magic numbers to get to look right on mobile view.
Overall I cannot say I am particularly proud of the solution I made, but it looks well enough so long as the format doesn't change too much. I would like to invest in researching better solutions for transitioning elements around like that in the future.
- @juliengDevSubmitted 4 months agoWhat are you most proud of, and what would you do differently next time?
I really enjoyed the challenge presented by this project, which encouraged deep reflection on the behavior of the share component and how it adapts and positions itself in both desktop and mobile versions. For the desktop version, I used TypeScript to manage the display of the component with an event listener and a toggle class to show/hide the element, applying CSS properties tailored to this effect. For the mobile view, I used pure CSS to manage the component's behavior. This project allowed me to reinforce my HTML and CSS skills while also providing an opportunity to implement TypeScript in a practical context. The contrast between using TypeScript for interactive elements on desktop and relying on CSS for mobile layout adaptations was particularly instructive, showcasing different approaches to responsive design.
What challenges did you encounter, and how did you overcome them?The main challenge I encountered was the initial planning phase. It took some time to reflect and devise an effective solution to the problem presented in this challenge. I had to carefully consider different approaches for both desktop and mobile versions, weighing the pros and cons of various techniques
What specific areas of your project would you like help with?I would greatly appreciate if the community could take a detailed look at my code and provide feedback on potential improvements or alternative solutions. I'm particularly interested in hearing about more efficient or elegant ways to handle the responsive behavior of the share component. Some specific areas I'd like input on include:
The efficiency of my TypeScript implementation for the desktop version. The CSS approach used for the mobile layout - are there better techniques I could have employed? Overall code structure and organization - how could it be improved for better maintainability?
I'm open to all constructive criticism and suggestions. Your insights could help me refine my skills and approach future projects more effectively. If you'd like to connect further or see more of my work, feel free to follow me on GitHub . I'm also active on LinkedIn, and I'm always eager to network with fellow developers and learn from their experiences. Thank you in advance for your time and expertise!
- @raswondersSubmitted 3 months agoWhat are you most proud of, and what would you do differently next time?
I'm proud how the hero section layout came out.
What challenges did you encounter, and how did you overcome them?I had some trouble with bg images and their sizing especially inside flexbox. In the end i went with sizing relative to parent and viewport. Another thing which caught me off-guard was bg overlay in footer. I did it with absolute positioning but it took me a while.
What specific areas of your project would you like help with?Accessibility / responsiveness mainly but anything will do.
- @Agus27111Submitted about 1 year ago
I learned a lot about the grid module in this section using tailwindscss, thank you very much
- @petrihcourSubmitted 4 months agoWhat are you most proud of, and what would you do differently next time?
I was able to apply the Tailwind CSS classes on mobile and desktop utilizing flex fairly quickly. I was worried about the desktop version and the way that the boxes are laid out, but I ended up wrapping the middle two boxes in a div and applying flex to that, and it worked out perfectly. It took me 1 hour less than what I had expected, so I'm happy I'm getting the hang of this.
What challenges did you encounter, and how did you overcome them?My main challenge was ensuring the box sizes on desktop and tablet didn't drastically change sizes. I ended up utilizing Tailwind CSS's min-width and max-width properties to ensure the boxes are the same size.
What specific areas of your project would you like help with?Any feedback would be great!
- @archana-singh12Submitted 3 months ago
- @suzzy-dszySubmitted 3 months agoWhat are you most proud of, and what would you do differently next time?
- Proud of being able to implement appropriate semantic HTML elements.
- Implementing new pseudo elements like
::markerto target bullet points so as to style them appropriately.
- Styling the list items and bullet points to appear as required was a bit confusing and required some researching and trial and error. I had to make use of
padding,margin, and pseudo-element::markerto style the lists as needed.
- I made sure to use the proper semantic HTML elements, if I have made a mistake any feedback would be appreciated.
- Any feedback regarding the structure of my code especially the CSS would be greatly appreciated.
- @iCloudBMXSubmitted 3 months ago
- @ElkuchWaltzSubmitted 3 months agoWhat are you most proud of, and what would you do differently next time?
I'm most proud that this time I was able to look at previous code I had written and didn't have to look at code from others (as much) to complete the challenge.
What challenges did you encounter, and how did you overcome them?Interfacing with GitHub was a bigger challenge for me again. Initially, only the readme appeared in GitHub, but then I was able to get the html and css code there, but it took a long time before the assets folder made it. I'm not sure if my attempts to push from Visual Studio were the issue, or if it was simply a timing issue and I needed to wait longer to see the results.
What specific areas of your project would you like help with?I feel okay with the code on this one, but if there are some mistakes or inefficiencies, I'd be happy to hear about them. Mostly, I think I need more practice to get faster and grapple with more complicated issues.
- @Basheer-1Submitted 3 months ago
