Simple Slides is a responsive and text-first presentation tool that keeps your audience engaged, and is built with:
- Laravel
- Vue + TypeScript
- PostgreSQL
Presentations built with Simple Slides typically focus on:
- Prioritizing text-content
- Low amount of content per slide
- Many slides, and changing through slides quickly
Ideally, you should set an alias for the sail
command, to make it much shorter to use:
alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'
Note: If you have run a Laravel Sail project before, you may have already created this alias.
- Locate the .env.example file in your project directory.
- Create a new file named .env in the same directory.
- Copy the entire content of the .env.example file and paste it into the newly created .env file.
Note: This file will hold your environment variables.
Run below commands in your terminal
composer install
sail npm install
sail artisan key:generate
This project uses Laravel Sail, which is basically a built-in Docker wrapper for Laravel applications. View their documentation for more details.
# In one terminal, to run the app:
sail up
# Then, in another to run the migrations and seeders (this command will end)
sail artisan migrate:fresh --seed
# Then, build, watch, and hot reload for front-end changes
sail npm run dev
To log in, use any of the following credentials (found in database/Seeders/DatabaseSeeder.php):
- Email:
[email protected]
for an admin user, or[email protected]
for a non-admin user. - Password: Both accounts use
password
.
Via Laravel pint, which is a code-formatter following Laravel's best practices. Note: This is not a linter.
# Laravel
sail pint
Linting on the back-end (e.g. Laravel) is done via larastan, which is a PHPStan wrapper for Laravel.
Linting on the front-end (e.g. Vue w/ Typescript) is done with vue-tsc
, which
is a first-party wrapper for Vue around tsc
. See more here:
https://vuejs.org/guide/typescript/overview
# Back-end (Laravel)
sail bin phpstan analyse
# Front-end (Vue)
sail npx vue-tsc
Tests on the back-end (e.g. Laravel) are written using Pest, and are a mostly integration and end-to-end tests, with some unit tests sprinkled in. Currently there are no browser tests.
Tests on the front-end (e.g. Vue w/ Typescript) are written using vitest, along with some other test utilities like Vue Test Utils and Mock Service Worker.
# Back-end (Laravel)
sail artisan test
# Front-end (Vue)
sail npx vitest
This uses puppeteer and Browsershot, which requires some extra config on top of Laravel Sail. To configure this, you need to run the following commands:
sail root-shell ./docker/sail-extra.sh
sail npx puppeteer browsers install chrome
- VS Code + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
TypeScript cannot handle type information for .vue
imports by default, so we replace the tsc
CLI with vue-tsc
for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue
types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensions
from VSCode's command palette - Find
TypeScript and JavaScript Language Features
, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Window
from the command palette.