
# Deploy

As you now know this website is deployed on vercel,
and for some reason, I F\*\*k'd up a single import :

```js
import Hero from '/components/HomePage/Hero';
```

This was working perfectly fine on Local, but not on deploy, because the right import must have been :

```js
import Hero from '/components/homePage/Hero';
```

Based on Linux, vercel is case sensitive, but first I ignored my mistake because the first code was perfectly working locaaly, then, when I realize my mistake, change the case, that was still not working :

```shell
Module not found: Can't resolve "/components/homePage/Hero" in
"/vercel/path0/blog/pages"
```

After Hours of reaserch and internet digging, i finnaly foud the glitch ..
git push cache too, as far as I understood.

you "just" need to put it away, like that :

```git
git rm -r --cached .
git add --all .
git commit -am "Fix casing discrepancies."
git push origin branch_name
```

This [page](https://github.com/vercel/next.js/discussions/18176#discussioncomment-145539)saved me hours of digging, and prevent my brain to blow up.


Git Vs. Vercel


# Experiencing MarkDown

Well, this project has been featured, initily, it was only a Next project.

Impossible as well to be only a NextJS project without any front end frameword, here it's React.

During the developpement I enjoyed to play with Node, I never did before, I mean, I did, but i only thought it was a server, not a library funny to play with.

Like here :

```js
const postsDirectory = path.join(process.cwd(), 'posts');

const getPostData = (fileName) => {
  const filePath = path.join(postsDirectory, fileName);
  const fileContent = fs.readFileSync(filePath, 'utf-8');
  const { data, content } = matter(fileContent);

  const postSlug = fileName.replace(/\.md$/, '');
  const postData = { slug: postSlug, ...data, content };
  return postData;
};
```

A 'Simple' function, to parse a file into an object that you can play with


Let's enjoy Markdown


NextJS is a **framework for ReactJS**.

Wait a second ... a "framework" for React? Isn't React itself already a framework for JavaScript?

Well ... first of all, React is a "library" for JavaScript. That seems to be important for some people.

Not for me, but still, there is a valid point: React already is a framework / library for JavaScript. So it's already an extra layer on top of JS.

## Why would we then need NextJS?

Because NextJS makes building React apps easier - especially React apps that should have server-side rendering (though it does way more than just take care of that).

In this article, we'll dive into the core concepts and features NextJS has to offer:

- File-based Routing
- Built-in Page Pre-rendering
- Rich Data Fetching Capabilities
- Image Optimization
- Much More

## File-based Routing

![Create routes via your file + folder structure](nextjs-file-based-routing.png)

... More content ...


Hi, I'm Guillaume

Featured Posts

Git Vs. Vercel

Let's enjoy Markdown

Getting Started with NextJS