Skip to content

alpsbte web

Georg edited this page Jan 3, 2022 · 4 revisions

#Basic We don't make much in the default alpsbte-web folder. This is only if you have to edit the root html file. Otherwise we have librarys for every route or important components.

Components can be stored in two ways.

  • Shared
  • Lib/Route based

Shared

Shared components are reused components. (ex. Navbar, Footer, Buttons)

"Private*

"Private" components are saved within the route library and are only used there. This are for example gallery images

Styling

We don't use any ui library (Material UI 🤮). We style our components on our own. We don't use plain css, but scss for nested syntax. For some reason we don't use the module version and evey style sheet is global. Convention is to give the Component a unique className. (className='button') and every sub object is named classname__subname (className=button__text`). We are planing to build our own UI library, as soon as we have enough components. We align or components equal. Means the space between the side of the page an the page is consisten through out the whole page.

Language System

Short introduction into the languange system made by Behemoth. We take the language information by the URL. /en/{} = english, etc. The default language is english and the langauge switcher just changes the url. The langauge function then serves a function that displays the individual content. The langauge file structure is typesafe. Atm we cannot render links, bold text etc. But we have plans to implement it. As soon as it is on production, we will update this part. Attention: Things mentioned here, may change soon.

Clone this wiki locally