marlana creed

index / 02

EBHCS Advisor Bulletin Board Community support, made easier to find

Finding help shouldn’t become another barrier. I built the board to bring school information and community support into one place. It has grown into a bilingual resource hub for students, with publishing tools that help advisors keep it useful.

role
built the public board and advisor portal
stack
Vite, JavaScript, Firebase
status
live, in production
users
adult learners, school advisors
open
ebhcsjobboard.web.app ↗
Find Help with plain-language needs, topic navigation, and resource cards
fig. 1  start with a need: “Get food help” works before someone knows an organization’s namelocal preview · oct 7, 2026

Support can exist and still be hard to reach.

For a student looking for housing support, job training, or English classes, the first obstacle can be figuring out where to start. An organization’s name alone doesn’t explain what it offers, who to call, or what to do next.

School communication had its own version of that problem. Announcements were spread across separate classrooms and channels, and advisors repeated the same information. I wanted a shared place where a student could find an opportunity and an advisor could keep it current.

Start with what someone needs today.

The Find Help directory is organized around recognizable topics and actions. Someone can browse food, housing, health, immigration, or job help, then move toward a concrete next step. Navigation and labels are in English and Spanish.

Resource entries put descriptions together with practical details: contact information, location, and hours when available. Buttons lead straight to a website, directions, a phone call, a form, or a document. The design work is in connecting information to an action.

Legal-help entries with the kind of support available, contact details, and action links
fig. 2  legal help: what’s offered, and the next action, in one viewlocal preview · public directory

Bulletins, calendar events, and advisor contacts share the same site. Students move between an announcement, an upcoming event, and ongoing support without learning a different interface for each.

The home feed with announcements and opportunities, topic labels, and dates
fig. 3  home feed: current opportunities stay visiblelocal preview · public content

Support within reach on a phone.

Students mostly use phones, so mobile was the starting point. These are the public production board at phone size.

A single-column bulletin feed with topic shortcuts and persistent bottom navigation
Keep up with the communityfig. 4a · production
Plain-language prompts and large topic buttons for finding support
Start with a familiar needfig. 4b · production

The publishing experience affects the quality of help.

There are separate publishing paths for bulletins, ongoing resources, and calendar events. Advisors start with the essentials, then add what matters: Spanish text, dates, contact information, an audience, or extra links and PDFs.

One bulletin can hold multiple sessions, so a program that meets repeatedly doesn’t need a new announcement for every date. A preview shows the advisor exactly what a student will see. Posts expire so old opportunities don’t crowd out current ones.

Shared editing lets the advisor team maintain content together. School Google sign-in and an advisor roster control who can publish.

Helping advisors keep the path to support open.

The portal brings that work together: an overview of content, a guided composer, and separate places to maintain bulletins, resources, and events. Captured from production after sign-in; nothing was created, edited, or deleted.

Post composer with bulletin, resource, and event choices beside a student-view preview
fig. 5a  composer, with student previewproduction
Bulletin management with search, status filters, sorting, and edit controls
fig. 5b  manageproduction

A useful system needs people who can maintain it.

The work goes beyond the public screen. I wrote posting guidance, director handover notes, and a succession checklist so day-to-day upkeep and ownership changes have a path. Administrators manage the advisor roster through the portal.

Checks cover content, resource links, permissions, and mobile behavior. They don’t remove the need to review information, but they make review part of the work rather than something to remember after launch.

how it’s built
site
HTML, CSS, JavaScript with Vite
backend
Firebase: authentication and shared content
access
school Google sign-in, advisor roster
tests
browser tests, permission-rule tests
docs
publishing guide, handover notes, succession checklist