Need help with sb-admin-svelte?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

GeekyAnts
165 Stars 49 Forks MIT License 28 Commits 13 Opened issues

Description

StartBootstrap SB Admin rebuilt using Svelte + Sveltestrap

Services available

!
?

Need anything else?

Contributors list

# 62,389
iOS
Android
CSS
Svelte
20 commits

SB-Admin-Svelte

A dashboard made by using Svelte and Sapper, inspired from SB-Admin Dashboard.

Preview

Dashboard

Check the live demo here

Getting started

Clone

git clone [email protected]:GeekyAnts/sb-admin-svelte.git

Running the project

However you get the code, you can install dependencies and run the project in development mode with:

cd sb-admin-svelte
npm install # or yarn
npm run dev

Open up localhost:3000 and start clicking around.

Component Library

We have used SvelteStrap as a component library.

SvelteStrap

SvelteStrap is a UI-Component Library for Svelte. It provides many components which we can use easily, refer to docs.

Structure

Sapper expects to find two directories in the root of your project —

src
and
static
.

src

The src directory contains the entry points for your app —

client.js
,
server.js
and (optionally) a
service-worker.js
— along with a
template.html
file and a
routes
directory.

src/routes

This is the heart of your Sapper app. There are two kinds of routes — pages, and server routes.

Pages are Svelte components written in

.svelte
files. When a user first visits the application, they will be served a server-rendered version of the route in question, plus some JavaScript that 'hydrates' the page and initialises a client-side router. From that point forward, navigating to other pages is handled entirely on the client for a fast, app-like feel. (Sapper will preload and cache the code for these subsequent pages, so that navigation is instantaneous.)

Server routes are modules written in

.js
files, that export functions corresponding to HTTP methods. Each function receives Express
request
and
response
objects as arguments, plus a
next
function. This is useful for creating a JSON API, for example.

There are three simple rules for naming the files that define your routes:

  • A file called
    src/routes/about.svelte
    corresponds to the
    /about
    route. A file called
    src/routes/blog/[slug].svelte
    corresponds to the
    /blog/:slug
    route, in which case
    params.slug
    is available to the route
  • The file
    src/routes/index.svelte
    (or
    src/routes/index.js
    ) corresponds to the root of your app.
    src/routes/about/index.svelte
    is treated the same as
    src/routes/about.svelte
    .
  • Files and directories with a leading underscore do not create routes. This allows you to colocate helper modules and components with the routes that depend on them — for example you could have a file called
    src/routes/_helpers/datetime.js
    and it would not create a
    /_helpers/datetime
    route

static

The static directory contains any static assets that should be available. These are served using sirv.

In your service-worker.js file, you can import these as

files
from the generated manifest...
import { files } from '@sapper/service-worker';

...so that you can cache them (though you can choose not to, for example if you don't want to cache very large files).

Bundler config

Sapper uses Rollup or webpack to provide code-splitting and dynamic imports, as well as compiling your Svelte components. With webpack, it also provides hot module reloading. As long as you don't do anything daft, you can edit the configuration files to add whatever plugins you'd like.

Production mode and deployment

To start a production version of your app, run

npm run build && npm start
. This will disable live reloading, and activate the appropriate bundler plugins.

You can deploy your application to any environment that supports Node 10 or above. As an example, to deploy to ZEIT Now when using

sapper export
, run these commands:
npm install -g now
now

If your app can't be exported to a static site, you can use the now-sapper builder. You can find instructions on how to do so in its README.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.