|
1 | 1 | # [My Portfolio Website](https://jstamant.com/portolio)
|
2 | 2 |
|
3 |
| -Here's the repository for my [personal portfolio |
4 |
| -website](https://jstamant.com/portfolio). |
5 | 3 |
|
6 |
| -This website is a static site generated by [Hugo](https://gohugo.io/). I figured |
7 |
| -this would be the best option for making a portfolio site, as using a platform |
8 |
| -like `Next.js` would be overkill for making such a simple, non-interactive site. |
9 |
| -The site also uses [TailwindCSS](https://tailwindcss.com/) as a CSS framework. |
| 4 | + |
| 5 | +Here's the repository for my [personal portfolio website](https://jstamant.com/portfolio). |
| 6 | + |
| 7 | +This website is a static site generated by [Next.js](https://nextjs.org/). |
| 8 | +I chose *Next.js* because of the unique nature of the website. |
| 9 | +Because this site has the potential to serve all sorts of different content, I figured using *Next* would be a good solution. |
| 10 | +This site does not serve content the way a CMS does (using layouts/templates for many pages), a more app-like approach would better serve this portfolio site. |
| 11 | +The site also uses [Tailwind CSS](https://tailwindcss.com/) for CSS styling. |
10 | 12 |
|
11 | 13 | 
|
12 | 14 |
|
13 |
| -I could've used plain HTML with a CSS framework, but I went with Hugo to |
14 |
| -separate the markdown from the content. ...Which is probably overkill for a |
15 |
| -single-page site... |
| 15 | +I could've used plain HTML with a CSS framework, but I went with *Next* to support the variety of content that might end-up on this website, as well as support any interactivity I might want to add. |
16 | 16 |
|
17 |
| -The inspiration for the design comes from [Ram Maheshwari](https://www.rammaheshwari.com/)'s |
18 |
| -[Dopefolio](https://github.com/rammcodes/dopefolio) template. |
| 17 | +The inspiration for the design comes from [Ram Maheshwari](https://www.rammaheshwari.com/)'s [Dopefolio](https://github.com/rammcodes/dopefolio) template. |
19 | 18 |
|
20 | 19 | ## Running
|
21 | 20 |
|
22 |
| -To work on the website in development, run the following commands in separate |
23 |
| -processes: |
| 21 | +To work on the website in development, run: |
| 22 | + |
| 23 | +``` |
| 24 | +npm run dev |
| 25 | +``` |
| 26 | + |
| 27 | +## Building & Deploying |
| 28 | + |
| 29 | +To build the website, run: |
24 | 30 |
|
25 | 31 | ```
|
26 |
| -npm run tailwind |
27 |
| -npm run hugo |
| 32 | +npm run build |
28 | 33 | ```
|
| 34 | + |
| 35 | +This will generate the `out/` folder, which you can easily deploy to any web server, or to Netlify or GitHub pages. |
0 commit comments