├── .github
└── ISSUE_TEMPLATE
│ ├── bug_report.md
│ ├── custom.md
│ └── feature_request.md
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── package-lock.json
├── package.json
├── public
├── about.jpg
├── back-button.png
├── facebook.png
├── favicon.ico
├── homepage.jpg
├── index.html
├── logo.png
├── robots.txt
└── twitter.png
└── src
├── App.js
├── App.test.js
├── app.css
├── components
├── about
│ ├── socials.jsx
│ └── styles
│ │ └── socials.css
├── articles
│ ├── article.jsx
│ └── style
│ │ └── article.css
├── common
│ ├── card.jsx
│ ├── footer.jsx
│ ├── logo.jsx
│ ├── navBar.jsx
│ └── styles
│ │ ├── card.css
│ │ ├── footer.css
│ │ ├── logo.css
│ │ └── navBar.css
├── homepage
│ ├── article.jsx
│ ├── styles
│ │ ├── article.css
│ │ └── works.css
│ └── works.jsx
└── projects
│ ├── allProjects.jsx
│ ├── project.jsx
│ └── styles
│ ├── allProjects.css
│ └── project.css
├── data
├── articles.js
├── seo.js
├── styles.css
├── tracking.js
└── user.js
├── index.css
├── index.js
├── pages
├── 404.jsx
├── about.jsx
├── articles.jsx
├── contact.jsx
├── homepage.jsx
├── projects.jsx
├── readArticle.jsx
└── styles
│ ├── 404.css
│ ├── about.css
│ ├── articles.css
│ ├── contact.css
│ ├── homepage.css
│ ├── projects.css
│ └── readArticle.css
├── reportWebVitals.js
└── setupTests.js
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | **Screenshots**
24 | If applicable, add screenshots to help explain your problem.
25 |
26 | **Desktop (please complete the following information):**
27 | - OS: [e.g. iOS]
28 | - Browser [e.g. chrome, safari]
29 | - Version [e.g. 22]
30 |
31 | **Smartphone (please complete the following information):**
32 | - Device: [e.g. iPhone6]
33 | - OS: [e.g. iOS8.1]
34 | - Browser [e.g. stock browser, safari]
35 | - Version [e.g. 22]
36 |
37 | **Additional context**
38 | Add any other context about the problem here.
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/custom.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Custom issue template
3 | about: Describe this issue template's purpose here.
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 |
11 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | /node_modules
5 | /.pnp
6 | .pnp.js
7 |
8 | # testing
9 | /coverage
10 |
11 | # production
12 | /build
13 |
14 | # misc
15 | .DS_Store
16 | .env.local
17 | .env.development.local
18 | .env.test.local
19 | .env.production.local
20 |
21 | npm-debug.log*
22 | yarn-debug.log*
23 | yarn-error.log*
24 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | mail@tharindu.dev.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
129 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | Contributing Guidelines
2 |
3 | Thank you for your interest in contributing to our project! We welcome contributions from everyone. By participating in this project, you agree to abide by the following guidelines:
4 |
5 | Code of Conduct:
6 | Please review and adhere to our Code of Conduct, which establishes a welcoming and inclusive environment for all contributors.
7 |
8 | Types of Contributions:
9 | We welcome different types of contributions, including but not limited to:
10 |
11 | - Bug fixes
12 | - New features or enhancements
13 | - Documentation improvements
14 | - Test cases
15 | - Translations
16 | - Feedback and suggestions
17 |
18 | Getting Started:
19 | To get started with contributing, follow these steps:
20 |
21 | 1. Fork the repository and clone it to your local machine.
22 | 2. Install the necessary dependencies.
23 | 3. Create a new branch for your contribution.
24 | 4. Make your changes or additions.
25 | 5. Run tests and ensure that everything is working as expected.
26 | 6. Commit your changes with a clear and descriptive commit message.
27 | 7. Push your changes to your forked repository.
28 | 8. Submit a pull request (PR) to our main repository, clearly explaining the purpose and details of your contribution.
29 |
30 | Code Style and Standards:
31 | Please ensure that your code adheres to our coding style and standards. Review our style guide and follow the established conventions for formatting, naming, and documentation.
32 |
33 | Documentation:
34 | Update relevant documentation to reflect your changes. This includes README files, code comments, and any other supporting documentation.
35 |
36 | Issue Reporting:
37 | If you encounter any bugs or issues, please submit a detailed bug report, including steps to reproduce and any relevant information. You can also search for existing issues and contribute to their resolution.
38 |
39 | Community Feedback:
40 | We value feedback and suggestions from the community. Join our discussion forums, participate in conversations, and share your ideas for improving the project.
41 |
42 | Thank you for your contributions and for helping make this project better!
43 |
44 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2023 Tharindu N. Madhusanka
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Reactfolio V1.2 👩🏽🚀
2 |
3 | Reactfolio is a modern and customizable personal portfolio web template built using the popular React library. It provides an easy way for developers, designers, and creatives to showcase their work, skills, and achievements in a professiona and visually appealing way. With its responsive design and clean code, Reactfolio can be easily tailored to suit individual needs and preferences, making it an ideal choice for anyone looking to create a stunning online portfolio.
4 |
5 |
6 |
7 |
8 |
9 | Live demo here: reactfolio.tharindu.dev
10 |
11 | - [Features](#-features)
12 | - [Getting started](#-getting-started)
13 | - [Installation and Setup Instructions](#-installation-and-setup-instructions)
14 | - [Folder structure](#-folder-structure)
15 | - [Configurations](#-configurations)
16 | - [Google Analytics](#-google-analytics)
17 | - [Building the React App](#-building-the-react-app)
18 | - [FAQ](#-faq)
19 | - [Contribution](#-contribution)
20 |
21 | ## 📙 Features
22 |
23 | - 📖 Multi-Page Layout
24 | - Home
25 | - About
26 | - Projects
27 | - Articles
28 | - Contact
29 | - 📱 Fully Responsive
30 | - 🛠 Easy configurations
31 |
32 | ## 📚 Getting started
33 |
34 | Clone down this repository. You will need `NodeJS` and `git` installed globally on your machine.
35 |
36 | ## 🛠 Installation and Setup Instructions
37 |
38 | 1. Installation: `npm install`
39 |
40 | 2. Run the project: `npm start`
41 |
42 | Runs the app in the development mode.\
43 | Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
44 | The page will reload if you make edits.
45 |
46 | ## 📁 Folder structure
47 |
48 | - `/public`: publicly accessible contents (ex: images, media).
49 | - `/src`: all the components used in this project.
50 | - `/src/components/`: each reusable components of each pages.
51 | - `/src/data`: configurations of the web app.
52 | - `/src/pages`: pages that include in the web app.
53 |
54 | ## ⚙️ Configurations
55 |
56 | Since this is a public and open source project, you can make any changes to it. If you are a ReactJS developer you can do it easily. But if you are a beginner, I have extracted the configurable data into a single directory, so you can edit the files in that directory to configure the entire web application.
57 |
58 | Directory: `/src/data/`
59 |
60 | - `user.js`
61 |
62 | From this you can change the content of each page of the web application.
63 |
64 | - `articles.js`
65 |
66 | From this you can add your articles to the web application.
67 |
68 | Instructions:
69 |
70 | - Add new article
71 |
72 | 1. Create a new function starts with `article_`. For example you can add new function named `article_3`.
73 |
74 | 2. Then add the data accordingly.
75 |
76 | - Add `` tag and it's closing tags in body.
77 | - In React there has no keyword `class`, so you should use `className` to define html classes.
78 |
79 | ```js
80 | function article_3() {
81 | return {
82 | date: "7 May 2023",
83 | title: "The Benefits of Cloud Computing",
84 | description: "Why businesses are turning to the cloud.",
85 | style: `
86 | .random-image {
87 | align-self: center;
88 | outline: 2px solid red;
89 | }
90 | `,
91 | body: (
92 |
93 |
94 |
95 | Content of article 1
96 |
97 |
102 |
103 |
104 | ),
105 | };
106 | }
107 | ```
108 |
109 | 3. In the last lines you will see an array to which you need to add your new `articles` function.
110 |
111 | ```js
112 | const myArticles = [article_1, article_2, article_3];
113 | ```
114 |
115 | - `seo.js`
116 |
117 | The SEO.js file is a module that contains an array of objects, with each object representing metadata for a specific page of a React website. The purpose of this file is to centralize and manage the SEO (Search Engine Optimization) information for different pages.
118 |
119 | Each object in the SEO array has the following properties:
120 |
121 | `page`: Represents the page name or identifier. It helps in mapping the SEO data to the appropriate page.
122 |
123 | `title`: Specifies the title of the page. This title is typically displayed in the browser's title bar and is an important element for search engines.
124 |
125 | `description`: Provides a concise and informative description of the page content. This description is often displayed in search engine results and can greatly influence click-through rates.
126 | keywords: Contains an array of keywords relevant to the page's content. Keywords can help search engines understand the topics covered on the page and can impact its visibility in search results.
127 | By storing the SEO information in the SEO.js file, you can easily manage and update the metadata for different pages of your React website. This approach allows you to keep the SEO data separate from the components and reuse it across the application, ensuring consistent and optimized metadata for each page.
128 |
129 | Example:
130 |
131 | ```js
132 | const SEO = [
133 | {
134 | page: "home",
135 | description:
136 | "I am a backend developer with expertise in Node.js. I have experience in building scalable, secure and reliable web applications using various frameworks and technologies.",
137 | keywords: ["Tharindu", "Tharindu N", "Tharindu Nayanajith"],
138 | },
139 | ];
140 | ```
141 |
142 | - `styles.css`
143 |
144 | From this you can change the font colors and font families of the web application.
145 |
146 | ```css
147 | :root {
148 | /* ------- colors ------- */
149 | --primary-color: #27272a;
150 | --secondary-color: #65656d;
151 | --tertiary-color: #acacb4;
152 | --quaternary-color: #e4e4e7;
153 | --link-color: #14b8a6;
154 | /* ---------------------- */
155 |
156 | /* ------- fonts ------- */
157 | --primary-font: "Heebo", sans-serif;
158 | --secondary-font: "Roboto", sans-serif;
159 | /* --------------------- */
160 | }
161 | ```
162 |
163 | ## 📈 Google Analytics
164 |
165 | Add your Google Analytics 4 MEASUREMENT ID to `/src/data/tracking.js`.
166 |
167 | How to find the Google Analytics 4 MEASUREMENT ID ?
168 |
169 | [https://support.google.com/analytics/answer/9539598?hl=en](https://support.google.com/analytics/answer/9539598?hl=en)
170 |
171 | ## 🚀 Building the React App
172 |
173 | To build the React app, you can use the `npm run build` command. This will create a production-ready build of your app in the `build/` directory.
174 |
175 | Here are the steps to follow:
176 |
177 | 1. Open a terminal window and navigate to the root directory of your React app.
178 | 2. Run the `npm run build` command to create a production build of your app. This will generate a static bundle of your app in the `build/` directory.
179 | 3. Copy the contents of the `build/` directory to your server's public directory. You can do this using an FTP client or by running a command like `scp` to transfer the files to your server. Make sure to replace `example.com` and `/var/www/html` with your server's domain name and public directory, respectively:
180 |
181 | ```bash
182 | scp -r build/* user@example.com:/var/www/html
183 | ```
184 |
185 | 4. Your portfolio app should now be accessible from your server's domain name. You can verify this by opening a web browser and navigating to http://example.com (replace example.com with your server's domain name).
186 |
187 | That's it! Your React portfolio app should now be up and running on your server. Note that you may need to configure your server's web server (e.g., Apache or Nginx) to serve the index.html file in the build/ directory as the default page for your domain.
188 |
189 | ## 🤔 FAQ
190 |
191 | **Q1. Subpages can only be accessed through links on the homepage or navigation bar, but those pages are not accessible through direct links.**
192 |
193 | If you are using Apache as your web server, you can insert this into your .htaccess file:
194 |
195 | ```c
196 |
197 | RewriteEngine On
198 | RewriteBase /
199 | RewriteRule ^index\.html$ - [L]
200 | RewriteCond %{REQUEST_FILENAME} !-f
201 | RewriteCond %{REQUEST_FILENAME} !-d
202 | RewriteCond %{REQUEST_FILENAME} !-l
203 | RewriteRule . /index.html [L]
204 |
205 | ```
206 |
207 | ## 🌱 Contribution
208 |
209 | If you have any suggestions on what to improve in Reactfolio and would like to share them, feel free to leave an issue or fork project to implement your own ideas
210 |
--------------------------------------------------------------------------------
/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "reactfolio",
3 | "version": "1.1.0",
4 | "description": "Personal portfolio template built using Reactjs",
5 | "author": {
6 | "name": "Tharindu N. Madhusanka",
7 | "email": "mail@tharindu.dev",
8 | "url": "https://tharindu.dev"
9 | },
10 | "license": "MIT",
11 | "private": true,
12 | "dependencies": {
13 | "@fortawesome/fontawesome-svg-core": "^6.4.0",
14 | "@fortawesome/free-brands-svg-icons": "^6.4.0",
15 | "@fortawesome/free-regular-svg-icons": "^6.4.0",
16 | "@fortawesome/free-solid-svg-icons": "^6.4.0",
17 | "@fortawesome/react-fontawesome": "^0.2.0",
18 | "@testing-library/jest-dom": "^5.16.5",
19 | "@testing-library/react": "^13.4.0",
20 | "@testing-library/user-event": "^13.5.0",
21 | "react": "^18.2.0",
22 | "react-dom": "^18.2.0",
23 | "react-ga4": "^2.1.0",
24 | "react-helmet": "^6.1.0",
25 | "react-router-dom": "^6.11.1",
26 | "react-scripts": "5.0.1",
27 | "styled-components": "^5.3.10",
28 | "web-vitals": "^2.1.4"
29 | },
30 | "scripts": {
31 | "start": "react-scripts start",
32 | "build": "react-scripts build",
33 | "test": "react-scripts test",
34 | "eject": "react-scripts eject"
35 | },
36 | "eslintConfig": {
37 | "extends": [
38 | "react-app",
39 | "react-app/jest"
40 | ]
41 | },
42 | "browserslist": {
43 | "production": [
44 | ">0.2%",
45 | "not dead",
46 | "not op_mini all"
47 | ],
48 | "development": [
49 | "last 1 chrome version",
50 | "last 1 firefox version",
51 | "last 1 safari version"
52 | ]
53 | },
54 | "prettier": {
55 | "useTabs": true,
56 | "tabWidth": 4
57 | }
58 | }
59 |
--------------------------------------------------------------------------------
/public/about.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/truethari/reactfolio/7429ed872c8b843b01ab84326272ddca758c487a/public/about.jpg
--------------------------------------------------------------------------------
/public/back-button.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/truethari/reactfolio/7429ed872c8b843b01ab84326272ddca758c487a/public/back-button.png
--------------------------------------------------------------------------------
/public/facebook.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/truethari/reactfolio/7429ed872c8b843b01ab84326272ddca758c487a/public/facebook.png
--------------------------------------------------------------------------------
/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/truethari/reactfolio/7429ed872c8b843b01ab84326272ddca758c487a/public/favicon.ico
--------------------------------------------------------------------------------
/public/homepage.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/truethari/reactfolio/7429ed872c8b843b01ab84326272ddca758c487a/public/homepage.jpg
--------------------------------------------------------------------------------
/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 | Reactfolio
9 |
10 |
11 |
12 |
13 |
14 |
15 |
--------------------------------------------------------------------------------
/public/logo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/truethari/reactfolio/7429ed872c8b843b01ab84326272ddca758c487a/public/logo.png
--------------------------------------------------------------------------------
/public/robots.txt:
--------------------------------------------------------------------------------
1 | # https://www.robotstxt.org/robotstxt.html
2 | User-agent: *
3 | Disallow:
4 |
--------------------------------------------------------------------------------
/public/twitter.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/truethari/reactfolio/7429ed872c8b843b01ab84326272ddca758c487a/public/twitter.png
--------------------------------------------------------------------------------
/src/App.js:
--------------------------------------------------------------------------------
1 | import { useEffect } from "react";
2 | import { Routes, Route } from "react-router-dom";
3 | import ReactGA from "react-ga4";
4 |
5 | import Homepage from "./pages/homepage";
6 | import About from "./pages/about";
7 | import Projects from "./pages/projects";
8 | import Articles from "./pages/articles";
9 | import ReadArticle from "./pages/readArticle";
10 | import Contact from "./pages/contact";
11 | import Notfound from "./pages/404";
12 |
13 | import { TRACKING_ID } from "./data/tracking";
14 | import "./app.css";
15 |
16 | function App() {
17 | useEffect(() => {
18 | if (TRACKING_ID !== "") {
19 | ReactGA.initialize(TRACKING_ID);
20 | }
21 | }, []);
22 |
23 | return (
24 |
37 |
38 | ),
39 | };
40 | }
41 |
42 | function article_2() {
43 | return {
44 | date: "7 May 2023",
45 | title: "Artificial Intelligence in Healthcare",
46 | description:
47 | "AI is transforming the healthcare industry, from improving patient outcomes to streamlining operations. Discover the latest applications of this game-changing technology.",
48 | style: ``,
49 | keywords: [
50 | "Artificial Intelligence in Healthcare",
51 | "Tharindu",
52 | "Tharindu N",
53 | "Tharindu Nayanajith",
54 | ],
55 | body: (
56 |
57 |
Content of article 2
58 |
59 | ),
60 | };
61 | }
62 |
63 | const myArticles = [article_1, article_2];
64 |
65 | export default myArticles;
66 |
--------------------------------------------------------------------------------
/src/data/seo.js:
--------------------------------------------------------------------------------
1 | const SEO = [
2 | {
3 | page: "home",
4 | description:
5 | "I am a backend developer with expertise in Node.js. I have experience in building scalable, secure and reliable web applications using various frameworks and technologies.",
6 | keywords: ["Tharindu", "Tharindu N", "Tharindu Nayanajith"],
7 | },
8 |
9 | {
10 | page: "about",
11 | description:
12 | "I am a backend developer with expertise in Node.js. I have experience in building scalable, secure and reliable web applications using various frameworks and technologies.",
13 | keywords: ["Tharindu", "Tharindu N", "Tharindu Nayanajith"],
14 | },
15 |
16 | {
17 | page: "articles",
18 | description:
19 | "Chronological collection of my long-form thoughts on programming, leadership, product design, and more.",
20 | keywords: ["Tharindu", "Tharindu N", "Tharindu Nayanajith"],
21 | },
22 |
23 | {
24 | page: "projects",
25 | description:
26 | "I've worked on a variety of projects over the years and I'm proud of the progress I've made. Many of these projects are open-source and available for others to explore and contribute to.",
27 | keywords: ["Tharindu", "Tharindu N", "Tharindu Nayanajith"],
28 | },
29 |
30 | {
31 | page: "contact",
32 | description:
33 | "If you're interested in collaborating on a project, feel free to reach out to me. I'm always open to new ideas and opportunities.",
34 | keywords: ["Tharindu", "Tharindu N", "Tharindu Nayanajith"],
35 | },
36 | ];
37 |
38 | export default SEO;
39 |
--------------------------------------------------------------------------------
/src/data/styles.css:
--------------------------------------------------------------------------------
1 | :root {
2 | /* ------- colors ------- */
3 | --primary-color: #27272a;
4 | --secondary-color: #65656d;
5 | --tertiary-color: #acacb4;
6 | --quaternary-color: #e4e4e7;
7 | --link-color: #14b8a6;
8 | /* ---------------------- */
9 |
10 | /* ------- fonts ------- */
11 | --primary-font: "Heebo", sans-serif;
12 | --secondary-font: "Roboto", sans-serif;
13 | /* --------------------- */
14 | }
15 |
--------------------------------------------------------------------------------
/src/data/tracking.js:
--------------------------------------------------------------------------------
1 | // Google Analytics Tracking ID
2 | // https://github.com/truethari/reactfolio#-google-analytics
3 | export const TRACKING_ID = "";
4 |
--------------------------------------------------------------------------------
/src/data/user.js:
--------------------------------------------------------------------------------
1 | const INFO = {
2 | main: {
3 | title: "Reactfolio by truethari",
4 | name: "Tharindu N.",
5 | email: "mail@tharindu.dev",
6 | logo: "../logo.png",
7 | },
8 |
9 | socials: {
10 | twitter: "https://twitter.com/",
11 | github: "https://github.com/",
12 | linkedin: "https://linkedin.com/",
13 | instagram: "https://instagram.com/",
14 | stackoverflow: "https://stackoverflow.com/",
15 | facebook: "https://facebook.com/",
16 | },
17 |
18 | homepage: {
19 | title: "Full-stack web and mobile app developer, and amateur astronaut.",
20 | description:
21 | "I am a backend developer with expertise in Node.js. I have experience in building scalable, secure and reliable web applications using various frameworks and technologies. I enjoy solving complex problems and learning new skills. I am passionate about creating high-quality code that follows best practices and industry standards. I am always looking for new challenges and opportunities to grow as a developer.",
22 | },
23 |
24 | about: {
25 | title: "I’m Tharindu N. I live in Sri Lanka, where I design the future.",
26 | description:
27 | "I've worked on a variety of projects over the years and I'm proud of the progress I've made. Many of these projects are open-source and available for others to explore and contribute to. If you're interested in any of the projects I've worked on, please feel free to check out the code and suggest any improvements or enhancements you might have in mind. Collaborating with others is a great way to learn and grow, and I'm always open to new ideas and feedback.",
28 | },
29 |
30 | articles: {
31 | title: "I'm passionate about pushing the boundaries of what's possible and inspiring the next generation of innovators.",
32 | description:
33 | "Chronological collection of my long-form thoughts on programming, leadership, product design, and more.",
34 | },
35 |
36 | projects: [
37 | {
38 | title: "Project 1",
39 | description:
40 | "Lorem ipsum dolor sit amet. Et incidunt voluptatem ex tempore repellendus qui dicta nemo sit deleniti minima.",
41 | logo: "https://cdn.jsdelivr.net/npm/programming-languages-logos/src/javascript/javascript.png",
42 | linkText: "View Project",
43 | link: "https://github.com",
44 | },
45 |
46 | {
47 | title: "Project 2",
48 | description:
49 | "Lorem ipsum dolor sit amet. Et incidunt voluptatem ex tempore repellendus qui dicta nemo sit deleniti minima.",
50 | logo: "https://cdn.jsdelivr.net/npm/programming-languages-logos/src/python/python.png",
51 | linkText: "View Project",
52 | link: "https://github.com",
53 | },
54 |
55 | {
56 | title: "Project 3",
57 | description:
58 | "Lorem ipsum dolor sit amet. Et incidunt voluptatem ex tempore repellendus qui dicta nemo sit deleniti minima.",
59 | logo: "https://cdn.jsdelivr.net/npm/programming-languages-logos/src/html/html.png",
60 | linkText: "View Project",
61 | link: "https://github.com",
62 | },
63 |
64 | {
65 | title: "Project 4",
66 | description:
67 | "Lorem ipsum dolor sit amet. Et incidunt voluptatem ex tempore repellendus qui dicta nemo sit deleniti minima.",
68 | logo: "https://cdn.jsdelivr.net/npm/programming-languages-logos/src/javascript/javascript.png",
69 | linkText: "View Project",
70 | link: "https://github.com",
71 | },
72 |
73 | {
74 | title: "Project 5",
75 | description:
76 | "Lorem ipsum dolor sit amet. Et incidunt voluptatem ex tempore repellendus qui dicta nemo sit deleniti minima.",
77 | logo: "https://cdn.jsdelivr.net/npm/programming-languages-logos/src/javascript/javascript.png",
78 | linkText: "View Project",
79 | link: "https://github.com",
80 | },
81 | ],
82 | };
83 |
84 | export default INFO;
85 |
--------------------------------------------------------------------------------
/src/index.css:
--------------------------------------------------------------------------------
1 | @import url("https://fonts.googleapis.com/css2?family=Heebo:wght@300&family=Roboto:wght@500&display=swap");
2 | @import "./data/styles.css";
3 |
4 | body {
5 | margin: 0;
6 | font-family: var(--primary-font);
7 | -webkit-font-smoothing: antialiased;
8 | -moz-osx-font-smoothing: grayscale;
9 | }
10 |
11 | code {
12 | font-family: source-code-pro, Menlo, Monaco, Consolas, "Courier New",
13 | monospace;
14 | }
15 |
--------------------------------------------------------------------------------
/src/index.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import ReactDOM from "react-dom/client";
3 | import "./index.css";
4 | import App from "./App";
5 | import reportWebVitals from "./reportWebVitals";
6 | import { BrowserRouter } from "react-router-dom";
7 |
8 | const root = ReactDOM.createRoot(document.getElementById("root"));
9 | root.render(
10 |
11 |
12 |
13 |
14 |
15 | );
16 |
17 | // If you want to start measuring performance in your app, pass a function
18 | // to log results (for example: reportWebVitals(console.log))
19 | // or send to an analytics endpoint. Learn more: https://bit.ly/CRA-vitals
20 | reportWebVitals();
21 |
--------------------------------------------------------------------------------
/src/pages/404.jsx:
--------------------------------------------------------------------------------
1 | import React, { useEffect } from "react";
2 | import { FontAwesomeIcon } from "@fortawesome/react-fontawesome";
3 |
4 | import { faFaceSadTear } from "@fortawesome/free-regular-svg-icons";
5 |
6 | import NavBar from "../components/common/navBar";
7 | import Logo from "../components/common/logo";
8 |
9 | import INFO from "../data/user";
10 |
11 | import "./styles/404.css";
12 |
13 | const Notfound = () => {
14 | useEffect(() => {
15 | document.title = `404 | ${INFO.main.title}`;
16 | }, []);
17 |
18 | return (
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 | Oops!
32 |
33 |
34 | We can't seem to find the page you're looking
35 | for.
36 |
37 | The requested URL "{window.location.href}" was
38 | not found on this server.
39 |
43 | Let's Get in Touch: Ways to Connect with Me
44 |
45 |
46 |
47 | Thank you for your interest in getting in touch with
48 | me. I welcome your feedback, questions, and
49 | suggestions. If you have a specific question or
50 | comment, please feel free to email me directly at
51 | {" "}
52 |
53 | {INFO.main.email}
54 |
55 | . I make an effort to respond to all messages within
56 | 24 hours, although it may take me longer during busy
57 | periods. Alternatively, you can use the contact form
58 | on my website to get in touch. Simply fill out the
59 | required fields and I'll get back to you as soon as
60 | possible. Finally, if you prefer to connect on
61 | social media, you can find me on{" "}
62 |
67 | {INFO.socials.instagram}
68 |
69 | . I post regular updates and engage with my
70 | followers there, so don't hesitate to reach out.
71 | Thanks again for your interest, and I look forward
72 | to hearing from you!
73 |
42 | Things I’ve made trying to put my dent in the
43 | universe.
44 |
45 |
46 |
47 | I've worked on a variety of projects over the years
48 | and I'm proud of the progress I've made. Many of
49 | these projects are open-source and available for
50 | others to explore and contribute to. If you're
51 | interested in any of the projects I've worked on,
52 | please feel free to check out the code and suggest
53 | any improvements or enhancements you might have in
54 | mind. Collaborating with others is a great way to
55 | learn and grow, and I'm always open to new ideas and
56 | feedback.
57 |