owncast/web
2022-10-03 09:51:28 +02:00
..
.storybook
.vscode
assets/images
components moved borders to the right for own msgs. Closes #2074 2022-10-03 09:51:28 +02:00
docs
interfaces
pages
public
services Do not point to localhost 2022-10-02 11:02:33 -07:00
stories
style-definitions added chat bg variable and updated bg color to match design 2022-09-30 09:56:10 +02:00
styles added chat bg variable and updated bg color to match design 2022-09-30 09:56:10 +02:00
types
utils
.env.development
.env.production
.eslintignore
.eslintrc.js
.gitignore
.prettierignore
.prettierrc
favicon.ico
LICENSE
next-env.d.ts
next.config.js
package-lock.json fix(deps): update dependency antd to v4.23.3 2022-10-01 04:33:00 +00:00
package.json fix(deps): update dependency antd to v4.23.3 2022-10-01 04:33:00 +00:00
postcss.config.js
README.md
renovate.json
tsconfig.json

Owncast Web Frontend

The Owncast web frontend is a Next.js project with React components, TypeScript, Sass styling, using Ant Design UI components.

Getting Started

First, install the dependencies.

npm install --include=dev

Components and Styles

You can start the Storybook UI for exploring, testing, and developing components by running:

npm run storybook

This allows for components to be made available without the need of the server to be running and changes to be made in isolation.

Contribute

  1. Find a component that hasn't yet been worked on by looking through the UIv2 milestone and the sidebar of components in storybook.
  2. See if you can have an example of this functionality in action via the Owncast Demo Server or Owncast Nightly Build so you know how it's supposed to work if it's interactive.
  3. Visit the Docs tab to read any specific documentation that may have been written about how this component works.
  4. Go to the Canvas tab of the component you selected and see if there's a Design attached to it.
  5. If there is a design, then that's a starting point you can use to start building out the component.
  6. If there isn't, then visit the Owncast Demo Server, the Owncast Nightly Build, or the proposed v2 design for some ways to start.
  7. If no design exists, then you can ask around the Owncast chat for help, for come up with your own ideas!
  8. No designs are stuck in stone, and we're using this as an opportunity to level up the UI of Owncast, so all ideas are welcome.

See the extra how-to guide for components here: Components How-to.

Run the web project

Make sure you're running an instance of Owncast on localhost:8080, as your copy of the admin will look to use that as the API.

Next, start the web project with npm.

npm run dev

Update the project

You can add or edit a pages by modifying pages/something.js. The page auto-updates as you edit the file.

Routes will automatically be available for this new page components.

Since this project hits API endpoints you should make requests in componentDidMount, and not in getStaticProps, since they're not static and we don't want to fetch them at build time, but instead at runtime.

A list of API end points can be found here: https://owncast.online/api/development/

Admin Authentication

The pages under /admin require authentication to make API calls.

Auth: HTTP Basic

username: admin

pw: [your streamkey]

Learn More

To learn more about Next.js, take a look at the following resources: