Concept

Web pages on screens

Make a web page built for people work as signage: shape it, reach it when it is private, and let it adapt per screen.

A great deal of what goes on screens is web pages: a dashboard, an intranet page, a live report, a status board. But a web page is built for a person at a browser, not a display on a wall, and the page you want is often behind a login or on your own network.

These pages cover how Screenly bridges that gap: running your own code on a page to make it fit, giving a screen a way to reach pages that are not public, and passing each screen its own context so one page can serve many.

Topics

4 topics · 4 min read

1 Built for people, not a wall A web page assumes a person at a browser. A screen is the opposite, so showing a page well takes more than pointing at a URL.
2 Shaping the page Running your own code on a page lets you log in, clear a banner, or focus the part that matters, so a page built for people works on a screen.
3 Reaching pages that aren't public A screen can prove who it is, so it can load pages behind a login or on your private network, not only what is open to everyone.
4 A page that knows its screen Screenly can pass a page details about the screen it is on, like its name, so one page adapts itself per screen instead of you building many.

Start reading →