Poet's Elixir Using Nextjs

This is a reproduction of PoetsElixr made with Nextjs. You can check out the repo to that work using this link. I'll keep updating this README as I continue working on it.

Stages

Made my first commit which was the design of the homepage and deployed it on Netlify.
Designed the admin page and also carried out minor code changes here and there.
Preloaded the fonts to improve user experience.
Made the contact page
Made the account page, changed from using ordinary functions for things like toggling the navbar to using the useState react hook, and also tweaked the UI (changed things things like background colors and made things a little consistent)
Made the categories dropdown. This required that I keep track of which links were to have dropdowns (this was achieved by adding an isDropdown property in the links objects). Then I had to look for a way to prevent the default tag action, toggle the dropdown, and then for links that didn't have dropdown still keep the same functionality of closing the the navigation container on smaller devices and also apply the active class to the current route (current page).
Refactored the dropdown element to use states for controlling it's visibility.
Created custom breakpoints to make the site more responsive.
Made the category page that lists all the posts for a given category (the category is gotten from the categories dropdown)
Created a custom api in the api folder for fetching different posts for each category. This was achieved using Next's getStaticProps and getStaticPaths functions. It took a while for me to figure out that with getStaticPaths I don't need the query string of the api. For example, I wouldn't do something like:

    export const getStaticPaths = async (context) => {
        const req = await fetch(`http://localhost:3000/api/category/${context.params.category}`);
        const category = await req.json();

        // Code logic here
    }

This is because according to this dicussion, "getStaticPaths generates static files, which means they can't access querystring at generation time." The solution which almost left me frustrated was just to do:

    export const getStaticPaths = async () => {
        const req = await fetch(`http://localhost:3000/api/category`);
        const category = await req.json();

        // Code logic here
    }

Harmonized the dropdown active indicator to match that of other links in the navbar.
Added a jsconfig.json file to make imports less error-prone and also more readable. I didn't start using it immediately yet.
Added the posts api to get specific posts by the user.
For close to a week I had problems deploying the site to production. This was because I was using the fetch api directly in my getStaticProps and getStaticPaths functions. I even had to create a custom JSONPlaceholder api endpoint to no avail. I stumbled upon a post from stackoverflow which had a question about deployement failing. I then had to refactor my code and the solution all along was to use the same logic I was using to fetch my datat from my api directly in my getStaticProps and getStaticPaths.
Chanegd the index posts to to valid posts and also added more post to the postsApi and update it accordingly in the categoryApi file.
Made the post page to display individual post's.

The live demo of my progress can be found on https://poetselixir.netlify.app or https://poetselixir.vercel.app

detachedsoul/poetselixir-nextjs

Poet's Elixir Using Nextjs

Stages