fe15fc076a
User-facing strings: - "Twake Calendar" -> "Workavia Calendar" in 4 locales (en/fr/ru/vi) - public/index.html <title> - public/manifest.appdata (name + short_name) - VALARM description string (sent to participants in iCal) Defaults / neutralization: - Video conference fallback URL: meet.linagora.com -> meet.jit.si (still overridable via window.VIDEO_CONFERENCE_BASE_URL or .env.js) Kept intact (design system / non user-facing): - @linagora/twake-mui package + TwakeMuiThemeProvider class (primary colors preserved per requirement) - public/calendar.svg, app-*.svg icons (no embedded text)
40 lines
1.6 KiB
HTML
40 lines
1.6 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<link rel="icon" href="<%= assetPrefix %>/favicon.ico" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
<meta name="theme-color" content="#000000" />
|
|
<link rel="apple-touch-icon" href="<%= assetPrefix %>/calendar.svg" />
|
|
<link rel="manifest" href="<%= assetPrefix %>/manifest.appdata" />
|
|
<!--
|
|
Notice the use of <%= assetPrefix %> in the tags above.
|
|
It will be replaced with the URL of the `public` folder during the build.
|
|
Only files inside the `public` folder can be referenced from the HTML.
|
|
|
|
Unlike "/favicon.ico" or "favicon.ico", "<%= assetPrefix %>/favicon.ico" will
|
|
work correctly both with client-side routing and a non-root public URL.
|
|
Learn how to configure a non-root public URL by running `npm run build`.
|
|
-->
|
|
<link rel="stylesheet" href="<%= assetPrefix %>/fonts/fonts.css" />
|
|
|
|
<title>Workavia Calendar</title>
|
|
<script src="<%= assetPrefix %>/.env.js"></script>
|
|
<script src="<%= assetPrefix %>/appList.js"></script>
|
|
</head>
|
|
<body>
|
|
<noscript>You need to enable JavaScript to run this app.</noscript>
|
|
<div id="root"></div>
|
|
<!--
|
|
This HTML file is a template.
|
|
If you open it directly in the browser, you will see an empty page.
|
|
|
|
You can add webfonts, meta tags, or analytics to this file.
|
|
The build step will place the bundled scripts into the <body> tag.
|
|
|
|
To begin the development, run `npm start` or `yarn start`.
|
|
To create a production bundle, use `npm run build` or `yarn build`.
|
|
-->
|
|
</body>
|
|
</html>
|