Home

Welcome to the fire-svelte wiki!

Here, you can find tutorials, guides, and learning resources to make the most out of your Fire/Svelte template.

Fire for Svelte features:

• TailwindCSS
• Routing, SPA, Advanced HTML monolith boilerplate
• Fully functioning mobile burger menu

Getting Started

Installing

To install, first clone the fire-svelte repository:

git clone https://github.com/blazed-space/fire-svelte

Then, run the following command at the root of the directory:

npm install

Live Development Server

To run a local development server, first ensure you have NPM installed on your machine.

Then, run the following command:

npm run dev

Demo App

View our live demo app to see what a newly installed Fire Svelte boilerplate looks like.

Deploying

To deploy to Netlify, simply create a new site using this repository as a template. Or, you may use the following button to deploy with one click:

Get Involved

If you would like to contribute to Fire for SvelteKit, you are in luck, because this project is open source! We welcome all types of contributions, project management, development, and testing.

Project Management

• Submit feature requests in the Discussions section of this repo.
• Join the Blazed Development Group, and post directly to the group.

Development

• Fix bugs found in the Issues section of this repo.
• Submit an implementation of an approved feature request. To submit code:

1. Fork this repo.
2. Commit your update.
3. Submit Pull Request

• Don't forget to link PR to issue if you are solving one.
• Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a Blazed team member will review your proposal. We may ask questions or request for additional information.
• We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
• As you update your PR and apply changes, mark each conversation as resolved.
• If you run into any merge issues, checkout this git tutorial to help you resolve merge conflicts and other issues.

4. Your PR is merged! Congratulations 🎉🎉 The Blazed Development Group thanks you ✨. Once your PR is merged, your contributions will be publicly visible on the Fire Svelte repo.

Testing

• If you come across a bug, fluke, or unsavory UX story; please do not hesitate to create a new Issue. Of course, first check if the issue has already been raised by using the search feature.
• If you would like to share your user experience story, even if it was purely positive, you may do so in the Discussions section of this repo.