Setting up example routing Adding routing spike Topology proof of concept Add breadcrumb Add sections menu Add App wrapper Rebase and remove menu placeholder Sort out services routes Add all exisiting routes Linting Tests Remove bold font Change services topology and list pathnames Remove console.logs Rebuild routing for clarity and flatter dom structure Simplify strings and /create instead of /~create for new billing Rebuild routing for clarity and flatter dom structure
32 lines
1.1 KiB
HTML
32 lines
1.1 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
|
|
<!--
|
|
Notice the use of %PUBLIC_URL% in the tag 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", "%PUBLIC_URL%/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`.
|
|
-->
|
|
<title>React App</title>
|
|
</head>
|
|
<body>
|
|
<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`.
|
|
To create a production bundle, use `npm run build`.
|
|
-->
|
|
</body>
|
|
</html>
|