Use this example to create a digital flyer board in Slate. The example uses a portal to display rotating flyers and event information, a form to collect flyer submissions, the File Library to store flyer files, and form communications to notify staff when a submission needs review.
This proof of concept can support campus activities, athletics, engagement offices, or other teams that need a shared display for timely campus information.
Try Slate examples 💼
Copy these Suitcase IDs and paste them in Database → Suitcase Import to import the example portal and form.
Flyer Board portal
07b24ad0-85f4-49b6-ab47-0291dec62c57:slate-success-showcaseFlyer Board form
2965195f-db25-40f8-9c0a-efc54bc7d578:slate-success-showcase⭐ Get Inspired
This article was adapted from a post by Technolutions staff in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? Let us know!
How the example works
The Flyer Board portal is designed as a digital display for flyers, events, weather, athletics, dining, shuttle schedules, or other campus content. In the source example, the portal uses one query, one view, and two instruction blocks: the active Flyer Board block and an inactive Read Me block with customization notes.
Store flyers in the File Library
The portal displays flyer files stored in the File Library. Staff can update displayed flyers by uploading new files or replacing existing files in the File Library.
⭐ Best practice
When the same recurring flyer should stay connected to the portal, keep the file name and reference consistent. Replace the file rather than creating a new unrelated file, then test the portal display.
Collect flyer submissions with a form
The example includes a Flyer Board Collection Form. In the source example, a student submits a club flyer and indicates when it should appear on the board and when it should be removed.
Use the form as a starting point. Update the fields, prompts, instructions, and access controls so the collection process matches your campus workflow.
Notify staff for review
Use form communications to notify designated staff when a flyer submission needs review. Staff can then review the submission, upload or replace the file in the File Library, and confirm that the portal display updates correctly.
Customize before launch
Review the imported portal query, view, and instruction blocks.
Update the carousel speed, ticker behavior, included content types, labels, and styling.
Replace example files with your campus files and confirm that each file loads in the portal.
Update the collection form fields and confirmation messaging.
Configure form communications so the right staff receive review notifications.
Test the portal on the display device or browser that will show the flyer board.
📝 Note
This example is a starting point. Review the imported configuration, file references, and form process carefully before using it for a live public display.