Showcase
A Laravel package which adds the ability to create "showcases", or view boxes which contain cards "trophies" of items. It also includes an admin panel to manage displays and trophies, which can only be accessed by a logged-in Auth user. Intended for use by Laravel 5.4+, (*1)
Still being developed!, (*2)
Installation
Install the package
composer require brokerexchange/showcase
To include the assets, you have two options:, (*3)
-
@import "vendor/brokerexchange/showcase/resources/assets/build/public"; in your main stylesheet, which will include the styles as part of your app's compiled styles., (*4)
-
php artisan vendor:publish --tag=showcase-assets and link to /vendor/showcase/public.css in the <head>., (*5)
If you want to publish all the assets:, (*6)
php artisan vendor:publish --tag=showcase
If you only want to publish specific pieces:, (*7)
php artisan vendor:publish --tag=showcase-assets
php artisan vendor:publish --tag=showcase-config
php artisan vendor:publish --tag=showcase-views
TODO: Finish this section and fix things so you don't have to use public/vendor, (*8)
Install the package development environment
git clone [the-url]
composer install
npm install
Test Project
To create a test project:
bash build-test-project.sh, (*9)
This can also be used to rebuild the test project if you messed something up., (*10)
If you want to use a different DB, change the credentials at the top of build-test-project.sh to match your desired credentials., (*11)
Update
To update the test project with package changes:
bash update-test-project.sh, (*12)
This will also dump composer's autoload and clear the Laravel cache and compiled views., (*13)
Flags you can use:
- --migrations: run database migrations
- --rundev: run the package npm run dev before updating the test project, (*14)
Authentication
The test project generates Auth during the build. A default user is created with the test project:, (*15)
email: homestead@test.email
password: secret, (*16)
You will need this to access the Showcase admin panels, as they are secured behind the Auth middleware by default. This can be changed from the config file., (*17)
Assets
To build the package JS and SCSS assets during development, just use the --rundev flag when running the update script. It will take care of compiling your assets and moving them to the proper locations in the test project., (*18)
You will still need to add a link for the showcase stylesheets to the test project head, as outlined in the package install instructions., (*19)
Use
Showcase is designed to be as simple to use as possible., (*20)
Displays
Using displays on your frontend is easy. First, get a display and pass it into the view:, (*21)
$display = \Showcase\Showcase::display('Sample Box'); // display($id) works as well!
...
return view('view.name', compact('display'));
To use it in the view, simply use the @showcaseDisplay() directive:, (*22)
@showcaseDisplay($display)
The display's template will be rendered automatically., (*23)
Trophies
If you look in the default display component views, you'll notice that they each call showcaseTrophy($trophy, $display). This directive renders a trophy component view, which renders a trophy's component view (or the display's default trophy component view, if force_trophy_default is set to true)., (*24)
Both display and trophy component views can be customized., (*25)
Note: Currently, there is no "sort" functionality, but you can still sort trophies within a display by detaching/attaching trophies from a display, which will put a particular trophy last in the sorting order. This is for alpha functionality only, and proper sorting will be in place for 1.0, (*26)
End User Customization
Display Components
After you've installed the package, you can use php artisan vendor:publish --tag=showcase to publish the package resources., (*27)
Modify Existing Views
Once the resources are published, you can find them in the resources/views/vendor/showcase directory. You can modify any of the package views, including the admin panels., (*28)
Add Custom Display Component
If you want to add a custom component, just create a new file in resources/views/vendor/showcase/public/components. Then, when creating or editing a display, your custom component will show up in the dropdown selection!, (*29)
Custom CSS
Just target the Showcase selectors with your CSS to customize the styling. To make the custom styling show up on the admin panels, make sure you add a link tag for your CSS to the _stylesheets include in resources/views/vendor/showcase/app/includes., (*30)
Configuration
There are some configuration options exposed for you in the config file showcase.php.
- table_prefix sets the prefix used by Showcase tables
- middleware sets what middleware Showcase routes go through (comma delimited)
- description_length sets a character limit on the description field
- route_prefix sets the prefix used for Showcase routes and named routes, (*31)
Table Prefix
By default, all showcase tables are prefixed with showcase_. You may change this to whatever you desire., (*32)
Middleware
By default, all admin routes for Showcase are passed through web and auth. You may change this array in config to add or remove middleware as you want., (*33)
Wallogit.com
