Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

Shortly Responsive

next, node, tailwind-css, axios
Austin Donovan•200
@Iskarr
A solution to the URL shortening API landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

building out my backend api, next time I will probably build out the backend to work first instead of building out the design

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

hosting the URL shortener was hard because it didn't want to work with my Node server and Vercel. Luckily, I did get it to work after some tinkering with my code and changing the way that I handled routing in Node.js.

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

Probably would like to know a more efficient way to handle getting the API call for the shortly link because building an entire node server for this might not be the most efficient way to build this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,700
    @markuslewin
    Posted 4 months ago

    Next actually supports creating those types of request handlers in the same project as the rest of the app. They're called Route Handlers. It'd look something like this:

    // /src/app/api/shorten/route.ts
    export async function POST(request: Request) {
      const { url } = await request.json();
    
      // todo: fetch(cleanuri)
      console.log("Shorten", { url });
    
      return Response.json({
        success: true,
        shortUrl: "<shortUrl>",
        originalUrl: url,
      });
    }
    
    // In component: const response = await fetch("/api/shorten", ...)
    

    You could also use the newer Server Actions. They're essentially functions that get compiled to server endpoints:

    // /src/app/actions.ts
    "use server";
    
    export const shorten = async (url: string) => {
      // todo: fetch(cleanuri)
      console.log("Shorten", { url });
    
      return {
        success: true,
        shortUrl: "<shortUrl>",
        originalUrl: url,
      };
    };
    
    // In component: const result = await shorten(url);
    
    Marked as helpful

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub