add Github link, update About section

This commit is contained in:
Ondrej Synacek 2019-10-24 20:45:34 +02:00
parent 9d279fa890
commit 1c697df772
5 changed files with 18 additions and 12 deletions

View File

@ -1,4 +1,4 @@
// Worker v4
// Worker v5
self.addEventListener('install', (event) => {
event.waitUntil(
@ -7,8 +7,8 @@ self.addEventListener('install', (event) => {
'/',
'/favicon.ico',
'/scripts.js?3',
'/style.css?3',
'/about?1',
'/style.css?4',
'/about?2',
])
})
)

View File

@ -18,11 +18,9 @@ body {
min-height: 100vh;
font-size: 16px;
margin: 0px;
max-width: 800px;
}
header, footer, article {
padding: 5px;
max-width: 600px;
box-sizing: border-box;
}
footer {

View File

@ -4,7 +4,6 @@
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="/style.css?3">
<link rel="manifest" href="/manifest.json">
<link rel="apple-touch-icon" sizes="180x180" href="/icon-180.png">
<title>Facebook Events to iCal Converter | about</title>
</head>
@ -16,7 +15,10 @@
Not too long ago I deactivated my Facebook account. While I do not miss the social network very much, plenty of local events are only announced on Facebook.
</p>
<p>
To my surprise, I found out that the company discontinued the ability to expor events to <em>iCal</em> files. This app aims at enabling you to do just that. <strong>It only works with public events</strong>. Unfortunately I haven't had the time to enable you to export your own events (but it's definitely possible).
To my surprise, I found out that the company discontinued the ability to export events to <em>iCal</em> files. This app aims at enabling you to do just that. <strong>It only works with public events</strong>. Unfortunately I haven't had the time to enable you to export your own events (but it's definitely possible).
</p>
<p>
I tried to keep the code and build as simple as I could. It does not have fancy build pipeline, code coverage or typing system, not even design (yeah you probably noticed that, right?)
</p>
<h3>How it works?</h3>
@ -49,6 +51,6 @@
If you want to let me know about any problems or improvements, you can contact me via my website, or even better create an issue on Github (link are on the main page in the footer).
</p>
<a href="/">Go back</a>
<a href="#" onclick="window.open('', '_parent', '');window.close()">Close</a>
</body>
</html>

View File

@ -73,8 +73,8 @@
</article>
<footer>
Created by <a href="https://ondrejsynacek.com">Ondrej Synacek</a> ◆
<a href="#" title="Source code coming soon">Source</a> ◆
Created by <a href="https://ondrejsynacek.com" target="_blank">Ondrej Synacek</a> (2019)
<a href="https://github.com/comatory/fb2iCal" target="_blank" title="Github">Source</a> ◆
<a href="/about" target="_blank" title="About the project">About</about>
</footer>

View File

@ -14,6 +14,12 @@ Run development server: `npm run start:dev`.
Run development server with debugger `npm run start:dev:inspect`.
### Static assets
There is no clever way to invalidate static assets (HTML, CSS, JS), so if you make any changes, just increment query parameters in view template(s) and service worker. Changing service worker should trigger new _update_ event that should also re-fetch new assets.
Sorry I wanted to keep the app simple so this is done manually. No big deal for me though.
## Deployment
The command `npm run start` will start the server in production mode.