Skip to content
OverviewSolutions
59
Comments
14
Alex
@AlexKolykhalov

All comments

  • Alex•1,310
    @AlexKolykhalov

    Hello everyone! Any comments are welcome.

    Check app in offline mode.

  • Boots 😺•1,610
    @adityaphasu
    What are you most proud of, and what would you do differently next time?

    Hey everyone! It's been a while 😊

    Well, I'm most proud of the PWA support that I could implement within this next.js project. One more step towards progressive web apps!

    Currently, I'm using client-side API calls but for future projects, I would like to prioritize using the API dedicated routes and creating custom route handlers to enhance performance and SEO potentially ⬆️

    I also implemented a toast when the links are shortened using Sonner!

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

    The one challenge that made it difficult for me to implement the API was the API itself. I was running into CORS policy issues and the cleanuri API documentation doesn't really specify how to configure the requests... so I tested the API using postman and it did work but the result link returned by the API is very much prone to phishing attacks. As soon as I clicked that link...my antivirus started screaming at me and I decided to see the website anyway.. yup I shouldn't have... bad decision 💀

    In the end, I just opted for a different API which is actually pretty safe and public so for anyone who wants to use that instead here's the repo for it: 1pt-co

    The format returned by this API is very much aligned with this specific project so it helped a lot. One less state to maintain haha

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

    I'm still learning about accessibility and I've tried to implement it for this project but I'm still not sure if I've implemented it fully so any help with that is appreciated.

    While lighthouse does help with the main accessibility issues it doesn't help with core ones apparently so I'd also like to know which tools you guys use to analyze the page for major accessibility issues.

    It was a good project overall and I had fun! Any Feedback or suggestions are appreciated.

    P.S I used Framer motion to animate the URLs so give it a go! 🪄

    URL Shortening API || Next.js + Typescript

    #framer-motion#next#typescript#tailwind-css
    2
    Alex•1,310
    @AlexKolykhalov

    Finally, where have you been?))) Good work, by the way!!

  • Alex•1,310
    @AlexKolykhalov

    Hi, very clean solution. Do you have mobile navigation bar or am i missing something?

    Marked as helpful
  • Alex•1,310
    @AlexKolykhalov

    Hello, about positioning red dot... You can use ::before or ::after. I think this is one of the right direction you can choose.

  • Alex•1,310
    @AlexKolykhalov

    Hello! Look pretty good.

    For centering element you can apply:

    1. flex and justify-content: center and align-items:center
    2. grid and place-content: center
    3. do this with position and translate

    There are many ways.

    Here are some videos about centering

  • Alex•1,310
    @AlexKolykhalov

    Very good work!! Keep going!

  • Alex•1,310
    @AlexKolykhalov

    Hello, cool animation by the way!

    Some tip to you.

    To prevent resizing when you hover on links https://stackoverflow.com/questions/556153/inline-elements-shifting-when-made-bold-on-hover

    Marked as helpful
  • Alex•1,310
    @AlexKolykhalov

    Good luck on your looooong way!))

    Marked as helpful
  • Alex•1,310
    @AlexKolykhalov

    Perfect as always!! Did this atomic css classes tailwind framework? I'm I right?

    Nice footer!! I'll take note.

  • Alex•1,310
    @AlexKolykhalov

    Looks good, and the markup is also норм)

  • Alex•1,310
    @AlexKolykhalov

    Thank you, Vinicius!!

    You always likes my "masterpieces")))

  • Alex•1,310
    @AlexKolykhalov

    Hello, nice work!! Maybe some of my advices can help you to improve your html+css+js skills.

    First of all seperate your body <header></header>, <main></main>, <footer></footer> tags. It's for semantics.

    In your case <main> and <footer> are needed.

    Secondly, <br><br>... not needed. Configure you CSS file for the resentation of a document written in HTML.

    To remove you markup html errors you can check html in this site (just copy-paste you html). The presence of accessibility errors will show this extension

    I think some of community members can say more.))

    Keep going!!

    Marked as helpful
  • Alex•1,310
    @AlexKolykhalov

    Hi, Carolina, good job! Please add padding to the text section.

    Marked as helpful
  • Alex•1,310
    @AlexKolykhalov

    made corrections according to this comments