WEBVTT

00:00:00.080 --> 00:00:03.120
okay okay excellent sorry okay so

00:00:03.120 --> 00:00:06.960
uh hello everyone um and um

00:00:06.960 --> 00:00:10.080
uh nice meeting you and let me

00:00:10.080 --> 00:00:12.400
thank the the organizer for all the

00:00:12.400 --> 00:00:13.920
organization and all the work they are

00:00:13.920 --> 00:00:15.200
doing to support us

00:00:15.200 --> 00:00:18.400
my name is adolfo villaferita

00:00:18.400 --> 00:00:19.920
I'm teaching at the university of

00:00:19.920 --> 00:00:21.920
trenton I'm also

00:00:21.920 --> 00:00:24.480
work will shortly be working at

00:00:24.480 --> 00:00:26.240
shared.tech which is a comp

00:00:26.240 --> 00:00:29.359
a non-profit organization developing an

00:00:29.359 --> 00:00:30.530
applications to

00:00:30.530 --> 00:00:32.399
[Music]

00:00:32.399 --> 00:00:35.680
recover surplus food but the the

00:00:35.680 --> 00:00:38.960
reason of the talk today and the reason

00:00:38.960 --> 00:00:40.079
I'm here today

00:00:40.079 --> 00:00:42.719
is to talk about my experience in moving

00:00:42.719 --> 00:00:44.000
from jekyll uh

00:00:44.000 --> 00:00:47.200
static website generator to org mode and

00:00:47.200 --> 00:00:49.200
the reason

00:00:49.200 --> 00:00:52.079
I move to work mode is to have better

00:00:52.079 --> 00:00:53.039
support for

00:00:53.039 --> 00:00:56.800
literary programming on the websites

00:00:56.800 --> 00:00:58.399
at the university of trento where we

00:00:58.399 --> 00:01:00.480
make available the content for the

00:01:00.480 --> 00:01:04.720
the students okay so

00:01:04.720 --> 00:01:08.000
first of all what is a static website

00:01:08.000 --> 00:01:10.080
generator it is basically a tool which

00:01:10.080 --> 00:01:11.360
allows you to

00:01:11.360 --> 00:01:15.360
generate html files out of text files

00:01:15.360 --> 00:01:17.439
containing basically two types of

00:01:17.439 --> 00:01:19.280
information metadata

00:01:19.280 --> 00:01:23.119
and content metadata is let's say a

00:01:23.119 --> 00:01:26.159
set of key pairs describing the the

00:01:26.159 --> 00:01:28.560
content of the file such as the title

00:01:28.560 --> 00:01:30.000
author

00:01:30.000 --> 00:01:31.759
tags and so on and so forth and the

00:01:31.759 --> 00:01:34.560
content is what you actually want to to

00:01:34.560 --> 00:01:37.040
get published on the on the internet in

00:01:37.040 --> 00:01:38.880
the html file

00:01:38.880 --> 00:01:41.439
and usually the content is written in

00:01:41.439 --> 00:01:44.560
some kind of

00:01:44.560 --> 00:01:47.520
markup language such as markdown or

00:01:47.520 --> 00:01:49.759
possibly

00:01:49.759 --> 00:01:53.200
org mode and well jackie is a very

00:01:53.200 --> 00:01:55.759
popular website uh

00:01:55.759 --> 00:01:58.719
a static website generator it is written

00:01:58.719 --> 00:01:59.840
in a ruby

00:01:59.840 --> 00:02:03.280
and what it does it it it systematically

00:02:03.280 --> 00:02:06.840
let's say transforms all the input files

00:02:06.840 --> 00:02:09.440
by making the content into

00:02:09.440 --> 00:02:11.599
html and systematically applying a

00:02:11.599 --> 00:02:14.000
template in order to generate the

00:02:14.000 --> 00:02:17.120
html files which you can then deploy

00:02:17.120 --> 00:02:19.840
on your server of choice to make them

00:02:19.840 --> 00:02:22.160
available on the on the internet

00:02:22.160 --> 00:02:26.160
and one of the features uh most

00:02:26.160 --> 00:02:28.480
well I would say all static website

00:02:28.480 --> 00:02:30.239
generators have

00:02:30.239 --> 00:02:32.560
is a debt of being able to let's say

00:02:32.560 --> 00:02:34.879
collect the metadata information

00:02:34.879 --> 00:02:38.400
uh of the files being part of your of

00:02:38.400 --> 00:02:39.440
your project

00:02:39.440 --> 00:02:45.280
and the reason they do that is because

00:02:45.280 --> 00:02:47.840
you sometimes want to generate pages

00:02:47.840 --> 00:02:49.280
based on the content

00:02:49.280 --> 00:02:53.200
of your um of your projects

00:02:53.200 --> 00:02:56.239
such as for instance the the list of

00:02:56.239 --> 00:02:59.040
posts you have recently published or

00:02:59.040 --> 00:03:00.400
maybe the list of tags

00:03:00.400 --> 00:03:03.840
uh you uh have defined for your post and

00:03:03.840 --> 00:03:07.280
so on and so forth so so

00:03:07.280 --> 00:03:09.760
dracula gives the possibility of

00:03:09.760 --> 00:03:12.400
generating this kind of dynamic

00:03:12.400 --> 00:03:15.760
content by using liquid which is a

00:03:15.760 --> 00:03:18.800
templating language which

00:03:18.800 --> 00:03:21.840
looks like these

00:03:21.840 --> 00:03:24.879
so basically you you have all the

00:03:24.879 --> 00:03:26.879
constructs you can

00:03:26.879 --> 00:03:29.120
expect in a programming language this

00:03:29.120 --> 00:03:29.920
for instance

00:03:29.920 --> 00:03:33.360
is a fourth cycle which

00:03:33.360 --> 00:03:37.440
iterates over all the post or the

00:03:37.440 --> 00:03:39.599
files in a specific directory of the

00:03:39.599 --> 00:03:41.040
jacket project

00:03:41.040 --> 00:03:45.040
and for each post it takes the the title

00:03:45.040 --> 00:03:48.400
and the url and generates a link

00:03:48.400 --> 00:03:51.840
okay so dracule is

00:03:51.840 --> 00:03:55.200
nice and sweet but over the years

00:03:55.200 --> 00:03:57.760
I started using more and more

00:03:57.760 --> 00:03:59.519
systematically

00:03:59.519 --> 00:04:02.959
or mode to write all my files and I

00:04:02.959 --> 00:04:05.439
moved from markdown to word mode I am a

00:04:05.439 --> 00:04:07.439
long time Emacs user so I've been using

00:04:07.439 --> 00:04:09.680
imax for 30 years now so

00:04:09.680 --> 00:04:12.799
or mode is a more recent discovery

00:04:12.799 --> 00:04:15.280
but it is a very nice uh let's say

00:04:15.280 --> 00:04:16.239
discovery I

00:04:16.239 --> 00:04:19.680
I made and the reason I like org mode

00:04:19.680 --> 00:04:22.320
is because for instance you can write

00:04:22.320 --> 00:04:23.600
formulas using

00:04:23.600 --> 00:04:26.639
mac jacks and you can generate diagrams

00:04:26.639 --> 00:04:30.320
or plots with new plots and

00:04:30.320 --> 00:04:32.240
also important is the fact that you have

00:04:32.240 --> 00:04:34.080
the possibility of let's say publishing

00:04:34.080 --> 00:04:35.919
your documents

00:04:35.919 --> 00:04:39.520
to multiple ends backhands such as pdf

00:04:39.520 --> 00:04:40.400
or

00:04:40.400 --> 00:04:43.600
maybe a review presentations or

00:04:43.600 --> 00:04:47.199
or html and this is all made possible

00:04:47.199 --> 00:04:50.479
by bubble which is

00:04:50.479 --> 00:04:52.560
exactly what we just saw in the the

00:04:52.560 --> 00:04:54.639
previous talk

00:04:54.639 --> 00:04:57.440
namely the possibility of executing a

00:04:57.440 --> 00:04:59.520
snippet of code

00:04:59.520 --> 00:05:02.560
embedded in in your pages

00:05:02.560 --> 00:05:06.400
um and our model can also be used

00:05:06.400 --> 00:05:09.600
within let's say jackie and in fact

00:05:09.600 --> 00:05:10.720
there is a

00:05:10.720 --> 00:05:15.199
a nice gem a nice library called jackie

00:05:15.199 --> 00:05:18.880
org which allows you to use org modifies

00:05:18.880 --> 00:05:19.680
directly

00:05:19.680 --> 00:05:22.880
into jekyll but when you start using

00:05:22.880 --> 00:05:26.560
org mode when I started using

00:05:26.560 --> 00:05:30.560
mode I realized I could move

00:05:30.560 --> 00:05:34.240
all my workflow to or my publishing

00:05:34.240 --> 00:05:36.840
workflow to image

00:05:36.840 --> 00:05:39.520
and and and in fact

00:05:39.520 --> 00:05:41.600
org mode is also static website

00:05:41.600 --> 00:05:42.880
generator because

00:05:42.880 --> 00:05:46.240
it has got the possibility of publishing

00:05:46.240 --> 00:05:50.880
um projects made of org mode files

00:05:50.880 --> 00:05:53.840
and one of the nice things about let's

00:05:53.840 --> 00:05:55.759
say that the publishing features of work

00:05:55.759 --> 00:05:56.479
mode

00:05:56.479 --> 00:05:58.880
is that it allows you to define in the

00:05:58.880 --> 00:05:59.840
org publish

00:05:59.840 --> 00:06:03.199
project a list of the components

00:06:03.199 --> 00:06:06.479
which are part of your project and in a

00:06:06.479 --> 00:06:07.520
sense it is

00:06:07.520 --> 00:06:10.479
also more flexible than jackie lee's

00:06:10.479 --> 00:06:12.400
because it also allows you for instance

00:06:12.400 --> 00:06:12.880
to

00:06:12.880 --> 00:06:15.120
let's say publish a single file rather

00:06:15.120 --> 00:06:17.440
than having to recompile everything

00:06:17.440 --> 00:06:20.080
every time you want to publish your

00:06:20.080 --> 00:06:23.919
your project to your website however

00:06:23.919 --> 00:06:25.840
there are some short comments I would

00:06:25.840 --> 00:06:27.120
say or some some

00:06:27.120 --> 00:06:29.520
areas of improvement improvement let me

00:06:29.520 --> 00:06:30.400
say

00:06:30.400 --> 00:06:32.720
the first is that let's say support for

00:06:32.720 --> 00:06:33.600
templating

00:06:33.600 --> 00:06:36.639
is not so obvious as it is let's say

00:06:36.639 --> 00:06:39.280
in jackie or even though there are some

00:06:39.280 --> 00:06:40.560
let's say

00:06:40.560 --> 00:06:44.560
nice extensions such as argo t html

00:06:44.560 --> 00:06:46.160
for instance which allows you to use

00:06:46.160 --> 00:06:48.400
templates and

00:06:48.400 --> 00:06:51.840
more important to me was the fact that

00:06:51.840 --> 00:06:54.080
apparently there is little support for

00:06:54.080 --> 00:06:55.520
the creation of dynamic

00:06:55.520 --> 00:06:58.240
content so I was very curious and very

00:06:58.240 --> 00:06:59.360
keen to use

00:06:59.360 --> 00:07:02.800
or mode for let's say publishing my blog

00:07:02.800 --> 00:07:05.440
and my the the courses at the university

00:07:05.440 --> 00:07:08.720
but then uh I had to find a way

00:07:08.720 --> 00:07:11.440
to let's say being able to publish these

00:07:11.440 --> 00:07:13.599
dynamic pages finding some kind of

00:07:13.599 --> 00:07:16.000
replacement so to speak for uh the

00:07:16.000 --> 00:07:16.720
liquid

00:07:16.720 --> 00:07:19.759
the liquid engine and and the solution

00:07:19.759 --> 00:07:20.160
was

00:07:20.160 --> 00:07:24.160
that at hand actually because

00:07:24.160 --> 00:07:27.280
basically I realized I could use bubble

00:07:27.280 --> 00:07:30.800
for exactly this purpose so rather than

00:07:30.800 --> 00:07:32.720
using bubble for generating

00:07:32.720 --> 00:07:35.759
plots or let's say my other computation

00:07:35.759 --> 00:07:37.919
or whatever I was using them for

00:07:37.919 --> 00:07:41.039
I realized they could use bubble to

00:07:41.039 --> 00:07:42.080
generate

00:07:42.080 --> 00:07:45.120
html which could be let's say

00:07:45.120 --> 00:07:48.960
uh then published uh uh

00:07:48.960 --> 00:07:52.720
in the project so uh so all I needed to

00:07:52.720 --> 00:07:53.680
do then

00:07:53.680 --> 00:07:56.240
was defining some kind of functions some

00:07:56.240 --> 00:07:58.319
kind of code in order to read

00:07:58.319 --> 00:08:01.840
all the org mode uh the metadata of all

00:08:01.840 --> 00:08:02.400
the

00:08:02.400 --> 00:08:05.759
opmod files of my web project so that

00:08:05.759 --> 00:08:09.680
I could let's say then publish uh

00:08:09.680 --> 00:08:13.280
generate the dynamic content and

00:08:13.280 --> 00:08:18.080
this is a snippet taken from

00:08:18.080 --> 00:08:21.759
one of my html projects

00:08:21.759 --> 00:08:24.800
which basically shows the way in which

00:08:24.800 --> 00:08:27.599
I generate the um the list of posts on

00:08:27.599 --> 00:08:29.360
my on my page it is uh

00:08:29.360 --> 00:08:32.560
exactly how the the liquid that we saw

00:08:32.560 --> 00:08:34.320
in a couple of a couple of slides

00:08:34.320 --> 00:08:35.680
earlier that looks like

00:08:35.680 --> 00:08:39.200
uh in inner mode

00:08:39.200 --> 00:08:42.320
and basically what I'm doing I'm using I

00:08:42.320 --> 00:08:46.720
wrote a ruby script which

00:08:46.720 --> 00:08:49.680
reads all the metadata so this uh

00:08:49.680 --> 00:08:51.040
highlighted code

00:08:51.040 --> 00:08:53.440
basically loads the script which is

00:08:53.440 --> 00:08:54.240
stored

00:08:54.240 --> 00:08:56.800
externally and then it collects all the

00:08:56.800 --> 00:08:58.320
metadata from the

00:08:58.320 --> 00:09:00.880
org mode files in the current uh in the

00:09:00.880 --> 00:09:02.240
current directory

00:09:02.240 --> 00:09:04.800
and then the the following the the code

00:09:04.800 --> 00:09:06.480
you can see here

00:09:06.480 --> 00:09:09.839
basically iterate over all the

00:09:09.839 --> 00:09:12.959
past red the at the previous step

00:09:12.959 --> 00:09:16.399
and it generates um

00:09:16.399 --> 00:09:19.519
a list with the title and uh

00:09:19.519 --> 00:09:22.959
and the urls and so basically

00:09:22.959 --> 00:09:27.440
replicating what jackie does so

00:09:27.440 --> 00:09:30.240
okay so there are some some other things

00:09:30.240 --> 00:09:32.399
I have to to deal with in order to let's

00:09:32.399 --> 00:09:33.200
say

00:09:33.200 --> 00:09:36.480
accommodate my workflow and but that was

00:09:36.480 --> 00:09:39.200
relatively easy in the sense that one of

00:09:39.200 --> 00:09:40.240
the

00:09:40.240 --> 00:09:43.279
uh problem one of the issue I had to

00:09:43.279 --> 00:09:45.360
solve was that of let's say having

00:09:45.360 --> 00:09:48.480
a common navigation on all my

00:09:48.480 --> 00:09:51.040
pages uh but that was easily solved

00:09:51.040 --> 00:09:51.920
using

00:09:51.920 --> 00:09:54.959
uh the include feature so I basically

00:09:54.959 --> 00:09:56.000
made available

00:09:56.000 --> 00:09:57.839
and include with all the navigation

00:09:57.839 --> 00:10:00.560
which is uh embedded in all the pages of

00:10:00.560 --> 00:10:01.839
my websites

00:10:01.839 --> 00:10:04.959
uh through the could include and another

00:10:04.959 --> 00:10:06.160
nice feature which

00:10:06.160 --> 00:10:08.560
jackie las is the possibility of

00:10:08.560 --> 00:10:09.760
previewing

00:10:09.760 --> 00:10:12.800
a website before deploying it and but

00:10:12.800 --> 00:10:13.200
then

00:10:13.200 --> 00:10:16.079
Emacs also has got a node which allows

00:10:16.079 --> 00:10:17.839
you to

00:10:17.839 --> 00:10:21.200
launch a web server and in fact

00:10:21.200 --> 00:10:24.320
I wrote a quick ack

00:10:24.320 --> 00:10:26.959
which allows you to which allows to

00:10:26.959 --> 00:10:28.000
basically

00:10:28.000 --> 00:10:31.519
invoke a node on a on our

00:10:31.519 --> 00:10:34.720
mode project and start a local preview

00:10:34.720 --> 00:10:37.920
and then use rsync

00:10:37.920 --> 00:10:44.839
in order to deploy the the website

00:10:44.839 --> 00:10:46.240
um

00:10:46.240 --> 00:10:48.720
five minutes left okay okay more than

00:10:48.720 --> 00:10:51.200
enough okay

00:10:51.200 --> 00:10:53.200
thanks thank you thank you very much I'm

00:10:53.200 --> 00:10:55.440
nearly done so then I can take some some

00:10:55.440 --> 00:10:56.480
questions

00:10:56.480 --> 00:11:00.560
so okay just to give you maybe

00:11:00.560 --> 00:11:03.680
a slightly more in-depth uh

00:11:03.680 --> 00:11:06.480
view of what the pages look like so

00:11:06.480 --> 00:11:07.200
these are

00:11:07.200 --> 00:11:11.120
one of the pages or the source files

00:11:11.120 --> 00:11:14.720
of one of the websites it is

00:11:14.720 --> 00:11:18.480
in literate programming so basically uh

00:11:18.480 --> 00:11:20.399
you see there is some metadata here I

00:11:20.399 --> 00:11:22.640
mean this is a regular old mod file

00:11:22.640 --> 00:11:26.640
and this part here

00:11:26.640 --> 00:11:29.920
basically defines some common options

00:11:29.920 --> 00:11:31.519
for publication

00:11:31.519 --> 00:11:35.920
and these two includes here

00:11:35.920 --> 00:11:41.120
put some extra html in the head part and

00:11:41.120 --> 00:11:44.480
the navigation and here as you can see

00:11:44.480 --> 00:11:48.079
is the code generating the

00:11:48.079 --> 00:11:50.160
the list in chronological order it is

00:11:50.160 --> 00:11:52.240
slightly more complex than the example I

00:11:52.240 --> 00:11:53.839
made in the slide

00:11:53.839 --> 00:11:56.240
because uh there is some more

00:11:56.240 --> 00:11:57.839
elaboration to

00:11:57.839 --> 00:11:59.760
uh to do including putting some

00:11:59.760 --> 00:12:01.839
javascript to identify

00:12:01.839 --> 00:12:05.120
according to let's say the the tags

00:12:05.120 --> 00:12:08.160
so to go back to the to the presentation

00:12:08.160 --> 00:12:11.200
um so the okay so

00:12:11.200 --> 00:12:13.600
I I managed this migration uh a few

00:12:13.600 --> 00:12:14.560
months ago

00:12:14.560 --> 00:12:17.680
and then uh all my workflow is within

00:12:17.680 --> 00:12:20.399
with old mode and within imax and um

00:12:20.399 --> 00:12:23.079
I'm very happy with it because it's

00:12:23.079 --> 00:12:24.240
simplified

00:12:24.240 --> 00:12:26.800
uh quite a bit let's say my public

00:12:26.800 --> 00:12:28.480
publication process

00:12:28.480 --> 00:12:31.839
and uh one of the advantages so another

00:12:31.839 --> 00:12:34.240
advantage so the first advantage is that

00:12:34.240 --> 00:12:36.959
everything is in ork mode and dmax

00:12:36.959 --> 00:12:38.160
second advantage

00:12:38.160 --> 00:12:41.680
is that everything is based on the

00:12:41.680 --> 00:12:44.880
standard machinery provided by orb mode

00:12:44.880 --> 00:12:47.760
so in a sense it is kind of let's say

00:12:47.760 --> 00:12:50.079
more robust with respect to

00:12:50.079 --> 00:12:53.040
dependencies and possible errors and so

00:12:53.040 --> 00:12:54.320
on and so forth

00:12:54.320 --> 00:12:56.639
and um and the fact that the old mode

00:12:56.639 --> 00:12:58.240
allows you to publish

00:12:58.240 --> 00:13:00.880
a single file in a project is is also

00:13:00.880 --> 00:13:03.839
very interesting because

00:13:03.839 --> 00:13:07.839
it allows to let's say be more robust to

00:13:07.839 --> 00:13:11.040
problems you might introduce when

00:13:11.040 --> 00:13:14.079
you're changing when I'm changing the

00:13:14.079 --> 00:13:14.959
setup

00:13:14.959 --> 00:13:16.880
and another interesting thing which I

00:13:16.880 --> 00:13:18.320
realized that I

00:13:18.320 --> 00:13:21.519
uh I could have is that

00:13:21.519 --> 00:13:23.600
in a sense the specification of the

00:13:23.600 --> 00:13:24.880
website

00:13:24.880 --> 00:13:27.360
is uh can be embedded in the website

00:13:27.360 --> 00:13:28.480
itself

00:13:28.480 --> 00:13:30.800
so in a sense this is some kind of let's

00:13:30.800 --> 00:13:31.839
say self

00:13:31.839 --> 00:13:35.120
the command it's a real set documenting

00:13:35.120 --> 00:13:37.200
uh what I'm actually doing so for

00:13:37.200 --> 00:13:38.560
instance

00:13:38.560 --> 00:13:43.199
uh here on my

00:13:43.199 --> 00:13:46.399
website you can see let's say the

00:13:46.399 --> 00:13:48.240
specification of the

00:13:48.240 --> 00:13:51.519
of the of the project which is uh loaded

00:13:51.519 --> 00:13:52.320
from my

00:13:52.320 --> 00:13:55.519
initialization file but then it is also

00:13:55.519 --> 00:13:56.320
published

00:13:56.320 --> 00:13:59.440
together with my home page and it leaves

00:13:59.440 --> 00:14:01.360
with the repository where

00:14:01.360 --> 00:14:05.360
I keep all the sources of my website

00:14:05.360 --> 00:14:08.079
which is kind of nice because it

00:14:08.079 --> 00:14:09.839
basically isolates

00:14:09.839 --> 00:14:14.079
everything in a single in a single place

00:14:14.079 --> 00:14:16.880
okay so there are some examples I'm

00:14:16.880 --> 00:14:18.000
showing them

00:14:18.000 --> 00:14:20.320
more because of the let's say source

00:14:20.320 --> 00:14:21.760
code which

00:14:21.760 --> 00:14:25.519
you can grab from the git repositories

00:14:25.519 --> 00:14:26.160
if you are

00:14:26.160 --> 00:14:28.399
interested of course I'm also available

00:14:28.399 --> 00:14:30.079
to provide some

00:14:30.079 --> 00:14:32.959
support and help if you are interested

00:14:32.959 --> 00:14:34.480
in this kind of stuff

00:14:34.480 --> 00:14:37.760
the the next step for me will be that of

00:14:37.760 --> 00:14:38.560
let's say trying

00:14:38.560 --> 00:14:41.600
making this kind of machinery available

00:14:41.600 --> 00:14:45.199
for more general use at the moment

00:14:45.199 --> 00:14:47.120
if you are interested in trying out my

00:14:47.120 --> 00:14:48.800
suggestion is let's say grabbing the

00:14:48.800 --> 00:14:49.839
sources

00:14:49.839 --> 00:14:52.959
or one of the let's say websites to see

00:14:52.959 --> 00:14:56.000
what how they look like and maybe try

00:14:56.000 --> 00:14:56.720
and

00:14:56.720 --> 00:15:00.160
customize it for your purposes

00:15:00.160 --> 00:15:02.720
and this is basically the content of my

00:15:02.720 --> 00:15:03.839
talk so

00:15:03.839 --> 00:15:06.959
I'm open to two questions and thank you

00:15:06.959 --> 00:15:07.279
for

00:15:07.279 --> 00:15:10.880
your attention you are now unmuted uh

00:15:10.880 --> 00:15:12.880
thank you very much adolfo for your

00:15:12.880 --> 00:15:14.480
awesome presentation

00:15:14.480 --> 00:15:17.360
um I think we have time for maybe like

00:15:17.360 --> 00:15:19.360
one or two questions

00:15:19.360 --> 00:15:21.279
um and then the rest maybe you could

00:15:21.279 --> 00:15:22.880
take up um

00:15:22.880 --> 00:15:26.639
after the stream after sure

00:15:26.639 --> 00:15:30.000
uh I we should do um would you like me

00:15:30.000 --> 00:15:31.839
to read you the questions

00:15:31.839 --> 00:15:35.199
uh yeah probably better because

00:15:35.199 --> 00:15:40.399
I kind of lost there okay no problem um

00:15:40.399 --> 00:15:42.480
okay so someone asks do you have any

00:15:42.480 --> 00:15:45.440
opinion on fern

00:15:45.440 --> 00:15:48.639
fan I I don't know fans

00:15:48.639 --> 00:15:51.839
so I'll give it a try and uh and uh

00:15:51.839 --> 00:15:55.040
and check it out okay

00:15:55.040 --> 00:15:57.839
thanks and um people are also asking do

00:15:57.839 --> 00:15:59.680
you discuss this for example in a blog

00:15:59.680 --> 00:16:01.279
or anywhere else they could find more

00:16:01.279 --> 00:16:02.800
about it

00:16:02.800 --> 00:16:05.600
oh yes I'm going to publish the let's

00:16:05.600 --> 00:16:08.560
say the talk and the content on the

00:16:08.560 --> 00:16:11.120
on my website and then I'll link it from

00:16:11.120 --> 00:16:12.320
the max conf

00:16:12.320 --> 00:16:14.720
conference so that it will be easier for

00:16:14.720 --> 00:16:15.680
people to

00:16:15.680 --> 00:16:19.040
to reach it so I will shortly make it

00:16:19.040 --> 00:16:22.880
available right after the conference

00:16:22.880 --> 00:16:25.440
wonderful and I think that's all for the

00:16:25.440 --> 00:16:26.160
questions

00:16:26.160 --> 00:16:28.560
thank you very much okay thank you very

00:16:28.560 --> 00:16:29.600
much thank you

00:16:29.600 --> 00:16:34.800
and cheers bye cheers bye