Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Watch it now! A full stack movie website

next, react, swr, tailwind-css, fetch
Abhishek Prajapati•130
@bhishekprajapati
A solution to the Entertainment web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My First React/Next js Project

I've put in a lot of effort in developing this application while learning both react and nextjs on the go. I haven't followed the design strictly by choice and extended the ui on my own.

Project doesn't have much features to cover every use-case for the end-user but it has enough which makes it usable.

Project Info

  • Name: WatchItNow
  • Scope: Full-stack
  • Website: https://www.watchitnow.fun
  • Repo: https://github.com/bhishekprajapati/watchitnow
  • Tech Stack: NextJs, Tailwindcss, vercel

Project Objectives

  • To learn react
  • To learn nextjs
  • To learn more about ssr and ssg
  • To explore component composition patterns
  • Implement performance optimization techniques

My journey of learning both react and nextjs was painful. since I decided to not to take a video course, just stay away from tutorial hell instead I mostly focused on learning from official documentation, blogs, youtube videos, etc. Overall, it was all worth it.

Guys, Checkout the project! I'll really appreciate some feedback on the project codebase.

Thank you for reading 😄 and happy new year 🎉 ❤️

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Svitlana Suslenkova•5,340
    @SvitlanaSuslenkova
    Posted over 1 year ago

    The arrow buttons on the top of the site work in opposit direction: when you click to the right, you want to see the picture that is to the right, so your images should move to the left. I'm not a pro, so I'm not 100% sure.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub