1
1
<!DOCTYPE html>
2
2
< html lang ="en ">
3
+ < head >
4
+ < meta charset ="utf-8 " />
5
+ < link rel ="icon " href ="favicon/favicon.ico " />
6
+ < meta name ="viewport " content ="width=device-width, initial-scale=1 " />
7
+ < meta name ="theme-color " content ="#000000 " />
8
+ < meta
9
+ name ="description "
10
+ content ="Web site created using create-react-app "
11
+ />
12
+ < link rel ="apple-touch-icon " href ="favicon/android-chrome-192x192.png " />
3
13
4
- < head >
5
- < meta charset ="utf-8 " />
6
- < link rel ="icon " href ="favicon/favicon.ico " />
7
- < meta name ="viewport " content ="width=device-width, initial-scale=1 " />
8
- < meta name ="theme-color " content ="#000000 " />
9
- < meta name ="description " content ="Web site created using create-react-app " />
10
- < link rel ="apple-touch-icon " href ="favicon/android-chrome-192x192.png " />
11
- <!--
12
- manifest.json provides metadata used when your web app is installed on a
13
- user's mobile device or desktop. See https://developers.google.com/web/fundamentals/web-app-manifest/
14
- -->
15
- < link rel ="manifest " href ="favicon/site.webmanifest " />
16
- <!--
17
- Notice the use of %PUBLIC_URL% in the tags above.
18
- It will be replaced with the URL of the `public` folder during the build.
19
- Only files inside the `public` folder can be referenced from the HTML.
14
+ < link rel ="manifest " href ="favicon/site.webmanifest " />
20
15
21
- Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will
22
- work correctly both with client-side routing and a non-root public URL.
23
- Learn how to configure a non-root public URL by running `npm run build`.
24
- -->
25
- < title > Deku Web</ title >
26
- </ head >
16
+ < title > Deku Web</ title >
17
+ </ head >
27
18
28
- < body >
29
- < noscript > You need to enable JavaScript to run this app.</ noscript >
30
- < div id ="root "> </ div >
31
- <!--
32
- This HTML file is a template.
33
- If you open it directly in the browser, you will see an empty page.
34
-
35
- You can add webfonts, meta tags, or analytics to this file.
36
- The build step will place the bundled scripts into the <body> tag.
37
-
38
- To begin the development, run `npm start` or `yarn start`.
39
- To create a production bundle, use `npm run build` or `yarn build`.
40
- -->
41
- </ body >
42
-
43
- </ html >
19
+ < body >
20
+ < noscript > You need to enable JavaScript to run this app.</ noscript >
21
+ < div id ="root "> </ div >
22
+ </ body >
23
+ </ html >
0 commit comments