This repo is no longer maintained. Consider using npm init vite and selecting the svelte option or — if you want a full-fledged app framework — use SvelteKit, the official application framework for Svelte.
svelte app
This is a project template for Svelte apps. It lives at https://github.com/sveltejs/template.
To create a new project based on this template using degit:
npx degit sveltejs/template svelte-app
cd svelte-app
Note that you will need to have Node.js installed.
Get started
Install the dependencies...
cd svelte-app
npm install
...then start Rollup:
npm run dev
Navigate to localhost:8080. You should see your app running. Edit a component file in src, save it, and reload the page to see your changes.
By default, the server will only respond to requests from localhost. To allow connections from other computers, edit the sirv commands in package.json to include the option --host 0.0.0.0.
If you're using Visual Studio Code we recommend installing the official extension Svelte for VS Code. If you are using other editors you may need to install a plugin in order to get syntax highlighting and intellisense.
Building and running in production mode
To create an optimised version of the app:
npm run build
You can run the newly built app with npm run start. This uses sirv, which is included in your package.json's dependencies so that the app will work when you deploy to platforms like Heroku.
Single-page app mode
By default, sirv will only respond to requests that match files in public. This is to maximise compatibility with static fileservers, allowing you to deploy your app anywhere.
If you're building a single-page app (SPA) with multiple routes, sirv needs to be able to respond to requests for any path. You can make it so by editing the "start" command in package.json:
"start": "sirv public --single"
Using TypeScript
This template comes with a script to set up a TypeScript development environment, you can run it immediately after cloning the template with:
node scripts/setupTypeScript.js
Or remove the script via:
rm scripts/setupTypeScript.js
If you want to use baseUrl or path aliases within your tsconfig, you need to set up @rollup/plugin-alias to tell Rollup to resolve the aliases. For more info, see this StackOverflow question.
Deploying to the web
With Vercel
Install vercel if you haven't already:
npm install -g vercel
Then, from within your project folder:
cd public
vercel deploy --name my-project
With surge
Install surge if you haven't already:
npm install -g surge
Then, from within your project folder:
npm run build
surge public my-project.surge.sh
Prompts:
PAGES:
Let's work on the content on the expanded Projects page.
- Might want to use Contentful here as well
Let's work on the content on the expanded Contact page.
- Just a form
- On submit:
- automatically emails me
- stores info in a lightweight DB that I can check
- validation around email format & existence and message existence
- name & subject can be left blank
- On submit:
RESPONSIVENESS
- zooming in <- especially this (similar/switch to mobile)
- Resume
- Blog
- Projects
- Contact
- zooming out
I'd like you to add an optional traditional menu bar on each expanded square. (especially for responsiveness.)
Flesh out mobile view
SWITCH COMPONENTS
Can we add a second switch component for Haitian Creole mode (where all of the text on the page - including the blogs - is converted to Haitian Creole)? The switcher will be the Haitian flag emoji. And the switch back will be the U.S. flag emoji.
And a third switch component for dark mode?
Are these two many swictch components?
- I'd like them all to be draggable. I think it's fun to have to have these.
- I want dragging them to involve and pressing and holding them, instead of just clicking them.
- Prompt: Can you make the switch component(s) draggable across of the screen? But always reset it at the top right when I navigate elsewhere (to a square)?
- Maybe add a fourth switcher to have one in every corner
Accessibility check on everything
Security check on everything
UNSURE ABOUT THESE
I'd you to add a preview of each square on the 2x2 grid home page.
Currently, when I click the "X" button, the navigation is based on the direction that I just came from. So for example, if I go to down from Resume to Project, then click "X", the fullScreenSquare will slide out from top to bottom as it returns to the main screen.
I don't know if this should be desirable. Wouldn't it be better to, instead, have the Project page close in the downLeft direction? Like no matter where I navigated from?
