This website is built with:
-
TailwindCSS, a CSS library to rapidly design components using HTML classes.
-
Svelte, a JS library to build reactive frontend. Alongside this, application uses TypeScript.
-
Vite, a build tool that aims to provide a faster and leaner development experience.
-
Vercel, a static site hosting with amazing deployment flow using Git
This website design is inpired by Mehmet Eren Olgun. You can look at his design and his work at behance.net
-
Make sure you have NodeJs installed.
-
Fork and clone this repository
-
cd
into folder
Type the following commands
# install dependencies
$ npm install
# run up the local host
$ npm run dev
Now visit localhost:3000
Voila π . You can run the local build successfully
Just click on the button below to start developing in Gitpod.
- Add your profile picture with name
profile.png
in assets folder.
- For logo, I made one using Adobe Photoshop, if you want to use your own logo, you can add it with name
logo-dark.png
in assets folder. Or just remove this from thesrc/lib/Header.svelte
file.
- Same goes for
favicon.ico
. Replace it in thepublic
folder.
Rename biswa.json
with username of your choice
Replace with the json
below with appropriate date
Make sure you remove these comments when adding in json
Files.
Or rename it with .jsonc
- Its json
with comments.
For Icons, I have used iconify. For icons data
refer to the icon-sets.iconify.design and use that if in icon
field.
{
"name": "[YOUR-NAME-HERE]",
"tagline": "[YOUR-TAG-LINE]",
"nickname": "[NICKNAME]",
"email": "[YOUR-EMAIL-ID]",
"github": "[YOUR-GITHUB-URL]",
"twitter": "[YOUR-TWITTER-URL]",
"medium": "[YOUR-MEDIUM-URL]",
"linkedin": "[YOUR-LINKEDIN-URL]",
"instagram": "[YOUR-INSTAGRAM-URL]",
"services": [
{
"icon": "ri:flutter-fill",
"title": "Flutter Developer",
"description": "Accusam dolores voluptua amet clita nonumy, erat kasd kasd tempor dolores. Ipsum lorem kasd ipsum vero, lorem sadipscing ea ut."
},
{
"icon": "dashicons:welcome-write-blog",
"title": "Content writer",
"description": "Invidunt labore sed diam et no sed et lorem et aliquyam, voluptua accusam dolor duo amet et et. Dolores sit."
},
{
"icon": "ri:open-source-fill",
"title": "Open Source Contributor",
"description": "Ipsum takimata no dolor ea ipsum takimata voluptua sadipscing lorem, dolor magna invidunt ut diam erat amet, ipsum sea invidunt."
}
],
"skills": {
"technology": [
{
"icon": "ri:flutter-fill",
"title": "Flutter"
},
{
"icon": "simple-icons:svelte",
"title": "Svelte"
},
{
"icon": "akar-icons:javascript-fill",
"title": "JavaScript"
},
{
"icon": "cib:typescript",
"title": "TypeScript"
},
],
"tools": [
{
"icon": "cib:adobe-photoshop",
"title": "Adobe Photoshop"
},
{
"icon": "cib:adobe-xd",
"title": "Adobe XD"
},
{
"icon": "simple-icons:gitpod",
"title": "Gitpod"
}
]
},
"experience": [
{
"title": "Flutter Developer",
"company": "Presence",
"date_joining": "October 2021",
"date_left": "February 2022",
"description": "Sit lorem sed labore justo sanctus duo sed sit dolor, et voluptua ea stet est gubergren kasd, nonumy diam takimata et lorem nonumy et tempor tempor, consetetur gubergren clita et est dolor aliquyam. Diam labore dolore no duo stet elitr,."
},
{
"title": "Open Source Contributor",
"company": "Appwrite",
"date_joining": "September 2021",
"date_left": "Present",
"description": "At gubergren magna diam sanctus consetetur no dolores sed no ut, clita kasd lorem eirmod consetetur invidunt elitr sanctus stet,. "
}
]
}
That's it. Goto src/App.svelte
and check if your json file has been imported properly.
And it should workπ.
Original design : behance.net/mehmeterenolgun
This project is GPL-3.0 licensed. If you are thinking of using this website as your own portfolio or for your own uses, please do proper credit by linking back to bishwajeetparhi.dev and the designer author.
This template should help get you started developing with Svelte and TypeScript in Vite.
Check out SvelteKit, which is also powered by Vite. Deploy anywhere with its serverless-first approach and adapt to various platforms, with out of the box support for TypeScript, SCSS, and Less, and easily-added support for mdsvex, GraphQL, PostCSS, Tailwind CSS, and more.
Why use this over SvelteKit?
- It brings its own routing solution which might not be preferable for some users.
- It is first and foremost a framework that just happens to use Vite under the hood, not a Vite app.
vite dev
andvite build
wouldn't work in a SvelteKit environment, for example.
This template contains as little as possible to get started with Vite + TypeScript + Svelte, while taking into account the developer experience with regards to HMR and intellisense. It demonstrates capabilities on par with the other create-vite
templates and is a good starting point for beginners dipping their toes into a Vite + Svelte project.
Should you later need the extended capabilities and extensibility provided by SvelteKit, the template has been structured similarly to SvelteKit so that it is easy to migrate.
Why global.d.ts
instead of compilerOptions.types
inside jsconfig.json
or tsconfig.json
?
Setting compilerOptions.types
shuts out all other types not explicitly listed in the configuration. Using triple-slash references keeps the default TypeScript setting of accepting type information from the entire workspace, while also adding svelte
and vite/client
type information.
Why include .vscode/extensions.json
?
Other templates indirectly recommend extensions via the README, but this file allows VS Code to prompt the user to install the recommended extension upon opening the project.
Why enable allowJs
in the TS template?
While allowJs: false
would indeed prevent the use of .js
files in the project, it does not prevent the use of JavaScript syntax in .svelte
files. In addition, it would force checkJs: false
, bringing the worst of both worlds: not being able to guarantee the entire codebase is TypeScript, and also having worse typechecking for the existing JavaScript. In addition, there are valid use cases in which a mixed codebase may be relevant.
Why is HMR not preserving my local component state?
HMR state preservation comes with a number of gotchas! It has been disabled by default in both svelte-hmr
and @sveltejs/vite-plugin-svelte
due to its often surprising behavior. You can read the details here.
If you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.
// store.ts
// An extremely simple external store
import { writable } from 'svelte/store'
export default writable(0)