@MaflacsSubmitted 2 months ago
Alingggg
@AlinggggAll comments
- @psychederikSubmitted 29 days agoWhat are you most proud of, and what would you do differently next time?
Aside from being proud of how the app turned out, both visually and functionally, I am proud I took the extra steps of fetching the data dynamically instead of implementing it statically and proud of the fact that I used yet another form of CSS which was new to me, CSS Modules. I'm aware the CSS Modules is basically vanilla CSS but it was nice to have my code more compartmentalized for easier readability and debugging.
Next time I will spend more time analyzing the structure of my JSX (HTML) to ensure I have a proper DOM structure and make applying my styles much simpler.
What challenges did you encounter, and how did you overcome them?I had several small roadblocks with this project but the most notable one would be the early steps of structuring the app. I initially had one additional component called Dashboard and was trying to fit the Layout component inside but in the end I wasn't sure which harbors which, the Dashboard or Layout. Finally, I scrapped the Dashboard component and just stuck with the Layout component and things started progressing so I just stuck with that structure.
What specific areas of your project would you like help with?My primary weakness now lies in the earliest stages of development, deciding which elements I want to break down into components. One example would be the UserProfile component. I wasn't sure whether to include the navbar in there, or create a Navbar component, or just include the navbar in the layout since this is a small project.
Once I gain more experience thinking in React, however, I believe the mental image of the app structure should come more clearly to me and I would have an easier time organizing my files as such. If there are any good resources on how to approach the early stages of app development, please feel free to share! I will also look into this on my own time.
- @m-maher97Submitted about 1 month ago
- @AdriverionSubmitted about 1 month ago
- @alemdaphelanSubmitted about 2 months ago
- @kvruntimeSubmitted about 2 months ago
- @tomwinskellSubmitted about 2 months ago@AlinggggPosted about 2 months ago
Nice work! It looks exactly the same. We both used sass but I think you really maximized the use of its features than I did. Keep it up
0 - @yours-truly68Submitted about 2 months ago
- @DeadvLoperSubmitted 2 months ago
- @Howslifem8Submitted 2 months agoWhat are you most proud of, and what would you do differently next time?
I am proud of the fact that it is up & running. Not an insanely hard project but I was disappointed with how much I've already forgotten how to do. I believe I relied too much on AI for the start up with the layout. I hope to use AI less on my next project. I wouldn't say that I abused it though, I definitely solved problems for this website. I just want to rely on it less for the start up.
What challenges did you encounter, and how did you overcome them?I encountered a weird bug with Github. My blog page was being displayed fine on a live server on my local machine, the problem was once I uploaded it to Github, no photos were displayed. I fixed this by messing around with the photo file destinations until I fixed it.
What specific areas of your project would you like help with?I would like to understand Mobile Response better, I honestly didn't even try it for this project. I have forgotten how to even begin implementing such a feature, I remember I need queries but I'll have to relearn.
- @Exterminator737Submitted 4 months ago@AlinggggPosted 4 months ago
It looks just the same and the code is also good. Well done!
0
