►
From YouTube: Product Analytics frontend sync - Oct 24th, 2022
Description
The Product Analytics FE team goes through the foundational frontend work made to date.
A
So
welcome
everyone
be
Thief,
the
frontal
a
product
analytics
thing.
So
what
we
want
to
do
with
this
meeting
is
basically
go
over
everything
we
did
since
the
foundation
of
the
of
the
group
regarding
front
end.
So
in
the
agenda
I
listed
out
a
few
things
like
for
context,
basically
like
trying
to
understand.
Where
do
we
come
from?
The
first
thing,
I
linked
was
the
the
first
PLC
or
even
the
first
sample
of
work
we
had
here.
This
was
a
outer
by
team
on
around
July
at
the
start
of
July.
A
That
was
a
with
that
that's
what
we
are
still
using
now
and
it
it
covered
the
tracking
and
getting
data
from
multiple
sources,
and
this
was
basically
getting
data
from
jigsaw
directly
and
also
from
possible
in
the
example,
and
it
also
allow
a
few
data
transformation
that
we
didn't
go
a
lot
into
detail
there
on
the
on
the
demo.
But
then
clickhouse
for
the
storage
and
and
queue
for
the
for
DBI.
All
of
the
implementation
on
that
PLC
Mr
is
basically
hard-coded.
A
A
We
also
talked
there
about
a
funnel
analysis.
For
example
like
there
are
a
lot
of
other
as
a
PLC.
It
was
more
of
an
investigation
research
in
work.
So
if
you,
if
you
go
through
the
demo,
you're
going
to
see
like
other
uses,
but
a
Contours
and
chart
data
are
like
the
the
things
that
are
more
closely
to
our
hands
and
then
we
have
the
the
first,
let's
say
formal
PLC
of
dashboarding,
and
it
is
close
in
it
never
got
merged
right
this
one.
Let
me
confirm.
B
A
A
Oh
sorry,
I
went
to
the
yeah
we
were.
We
were
handing
the
idea
of
multiple
dashboards
there.
If
you
see
the
screenshot,
we
had
like
these
a
default
dashboard
and
a
button
to
add
new
dashboards
and
charts,
and
of
course,
all
of
these
was
mostly
empty
design
without
any
any
actual
functionality,
and
one
of
the
highlights
was
to
add
in
Greek
stock
that
basically
for
for
making
these
dashboard
View
editable.
A
A
A
And
this
is
this
is
basically
what
what
it
has.
It
is
not
live
data
it
is,
it
is
not
live,
but
we
have
it
there.
We
also
introduced
the
the
first
dashboard
definition
that
again
looks
pretty
similar
to
what
we
have
now
and
beside
the
metadata.
We
we
use
the
word
charts
before
now.
We
use
widgets
and
the
main
structure
is
well
an
ID
for
identification,
of
course,
that
I
mentioned
this
is
all
related
to
grid
stack.
A
Basically,
where
are
we
going
to
put
this
chart
at
that
time
and
the
rest
of
of
information
to
to
feed
the
data
to
feed
the
query?
The
query
Runner
and,
as
you
can
imagine,
a
these
props
that
we
pass
here
were
used
to
in
a
child
component
to
to
actually
get
this
capacity
to
Cube
and
and
get
the
data.
A
We
decided
to
split
that
work
into
two
parts:
the
main
dashboard
structure,
the
the
basic.
Sorry,
that's.
If
you
go
to
the
email
you're
going
to
see
that
we
only
have
like
a
like,
basically
defining
the
road,
creating
a
an
empty
element,
an
empty
page.
Where
is
it
yeah?
This
one
I
mean
doesn't
have
anything
at
all
and
rob
complemented
it
with
the
with
the
actual
real
structure.
A
C
A
C
A
I
believe
we
have
a
yeah,
we
have
a
screenshot
yeah.
This
is
this
is
what
what
what
Rob
is
saying
like?
We
only
have
a
dummy
widget
and
we
we
did
this
Rob
and
I.
We
did
this
review
of
the
of
of
actual
usage
where
we
went
and
tried
to
fit
this
Mr
with
live
data
and
with
real
data
and
well
it
you
can
see
a
video
there.
A
So
in
this,
in
this
case,
we
move
out
from
multiple
dashboards
and
we
only
had
like
a
like
a
single
one.
You
can
see
that
we
don't.
Even,
although
we
use
the
word
dashboards
in
plural,
we
don't
have
like
several
several
dashboards.
We
only
have
a
a
single
one
and
we
introduce
the
the
the
name,
widget
and
I,
also
link
here.
A
C
If
you
go
to
it,
that's
the
only
structure
we've
got
in
the
widget
space
at
the
moment.
Obviously,
we've
just
had
that
big
conversation
around
file
based
schemas
So.
Eventually
this
is
gonna
move
into
that
whatever
that
ends
up
being,
but
for
now
just
so
we
can
progress
forward
in
a
way
that
also
optimizes
signed
off
on
as
a
initial
basis.
This
is
what
we
went
with,
and
this
issue
is
to
then
lead
on
to
as
you
creating
a
cube
based
widget.
C
The
first
one
being
a
line
chart
was
the
main
name:
I,
don't
know
who's,
doing
that
I'm
busy
doing
UI
stuff,
so
I
know
it's
probably
going
to
be
either
ux
or
yuyan.
I'm,
not
sure
who
I've
asked
Dennis
to
tell
me-
and
he
hasn't
said
anything
yet
so
feel
free
can't
be
assigned
to
me,
but
feel
free
to
take
over
any
point
that
you
feel
like.
If
you,
if
you
get
assigned
to
work,
I,
don't
know
who's
doing
it.
A
Yes,
yes,
that's
right!
Thank
you!
Thank
you
Rob
and
the
discussion
is
it
and
yeah
I
wanted
to?
Thank
you
rob
like
you
were.
You
have
been
moving
the
discussion
ahead.
So
that's
it's
pretty
refreshing
to
to
read
all
of
your
insights
and
actual
answers
to
to
those
important
questions,
and
and
do
you
want
to
take
it
from
Europe
until
yeah.
C
So
it's
a
premium
plus
essentially,
that
has
just
I
just
had
the
left-hand
navigation
for
that
being
merged,
so
that
will
show
up
under
the
SE
guide
that
I
nav
soonish,
once
that's
all
deployed
and
stuff,
but
for
now
it's
only
accessible
directly
through
the
links
which
explains
how
to
set
up
the
dashboards
as
they
are.
If
you
wanted
to
create
your
own
custom
dashboard
right
now,
with
what
we've
got
and
just
to
point
out,
we
are
all
Cube
based
queries
for
the
widgets
need
to
run
through
our
Cube
proxy.
C
This
is
because
we
need
to
add
security
contexts
to
the
query
and
the
easiest
way
for
us
to
do
that
and
get
a
token
and
all
that
sort
of
stuff
is
to
do
it
in
the
back
end,
where
we
can
make
a
direct
connection
with
the
cube
instance,
rather
than
having
to
run
all
the
authentication
processes.
Checking
that
you
own
the
project
on
the
front
end.
C
That's
a
pain,
much
simpler
to
do
it
in
the
back
end,
where
we
know
where
we
have
all
that
information,
so
you
send
the
query
to
cube
just
so
it
it
plugs
into
the
cube.js
the
exact
same
way
as
the
conventional
cube.js
endpoints
would
so
you
just
plug
in
the
gitlab
cube
instance,
and
it
handles
all
the
Cube
stuff.
How
keyboard
and
returns
will
keep
would
test.
So
the
qgis
library
just
works,
as
is.
A
A
Yeah
yeah,
let
me
let
me
go
through
all
these
two
things
and
let
me
jump
forward
so
and
the
other
two
things
that
I
wanted
to
mention
are
that
we
have.
We
had
a
previous
product,
analytic
page
before
that
was
basically
on
on
Project
monitor
and
it
was
never
used.
It
was
pushed
forward,
but
never
actually
used.
So
we
ended
up
removing
it.
A
If
you
there,
we
have
this
animal
with
a
lot
of
deletions
that
you
can
go
through
and
see,
but
it
was
basically
like
a
like
an
initiative
that
it
seems
never
so
actual
light,
and
the
other
is
that
we
are
also
talking
about
the
the
where
to
put
our
menu
item
for
for
analytics,
and
we
have
a
lot
of
interesting
discussion
here.
We
don't
have
like.
A
We
don't
have
like
a
an
actual,
a
solution
for
that
like
right
now
and
we
we
do
have
a
few
proposals
that
might
move
forward,
but
this
is
not
ready
for
development.
Yet,
although,
although
Dennis
told
me
that
I
might
just
push
forward
and
pull
something
as
polish
anymore
and
get
the
discussion
there
for
as
a
bias
for
action,
but
yeah
those
those
are,
those
are
also
related
to
this.
So
I'm
going
to
stop
sharing
and
if
you
have
any
any
question
like
a
specific
question
yeah
before
before.
C
I
just
want
to
say
in
terms
of
the
left
sidebar.
The
reason
it's
complicated
is
because
multiple
groups
are
involved
in
especially
optimized
in
terms
of
analytics
in
general
and
how
that's
all
structured
in
the
left-hand
menu
plus
the
actual
left-hand
menu
and
what
goes
in
it
is
owned
by
foundations.
So
not
only
do
we
need
to
get
signed
off
from
foundations
that
this
works
on
the
ux
UI
sort
of
foundation,
foundational
gitlab
product
level,
but
also
needs
to
work
within
the
aims
of
of
optimize
as
well
as
us.
C
So
there's
a
lot
of
discussion
and
trying
to
figure
out
the
best
path
forward
between
all
that,
but
yeah.
We
might
have
a
Way
Forward
where
we
can
just
add
product
analytics
just
somewhere,
so
we
can
get
the
dashboards
on
the
page.
Even
if
we
can't
add
the
full
structure
that
we
want
to
add
just
yet.
A
B
C
A
C
C
We'll
just
need
to
plug
that
into
the
details
into
the
Mr,
slash
the
environment,
variables
of
the
Hugo
deployment,
so
it
uses
internal
handbook,
uses
Hugo
to
do
all
that
sort
of
stuff
in
terms
of
any
other
things.
To
note
is
we
currently
technically
product
intelligence
is
going
to
take
this
over,
but
they
don't
have
a
front-end
engineer
so
for
now
we
own
the
JS
SDK.
That's
you
going
to
be
used
to
connect
the
user's
products
with
our
analytics
platform
through
the
Gypsy
implementation.
C
There
are
issues
in
that
just
SDK
project
that
we
can
work
on
as
a
group
things
like
enabling
is
it
Anonymous
mode
by
default?
Something
like
that.
It's
I
think
this.
No,
it's
not
Anonymous,
it's
a
mode
to
reduce
the
amount
of
tracking
we
do
by
default,
which
we
don't
need
all
the
details
and
it's
a
bit
more
secure
things
and
various
other
issues
that
you
can
take.
A
look
at
deployment
is
done
manually
via
npm
publishing.
C
You
have
to
be
added
to
the
gitlab
group
and
you
have
to
have
a
npm
account
if
you,
if
anyone
does
do
work
and
use
it
deployed
and
doesn't
have
that
or
I
had
to
go
through
Tim
to
get
that
or
if
you
just
want
me
to
do
it.
I
have
full
publishing
rights,
so
I
can
do
it,
but
we
really
should
also
make
that
at
some
point,
because
I
have
to
version
bump
our
SDK
manually
and
do
a
git
push
to
master
for
it,
which
isn't
ideal
and
final
points.
C
Big
discussions,
exporting
of
data
and
figure
out,
as
we've
discussed
in
the
previous
meeting
figuring
in
the
previous
section
meeting
file
based
dashboard,
schemas
so
front
end.
Input
is
welcome
on
all
those
points
across
the
group
yeah.
So
that
covers
history
and
what's
going
on
right
now,
we
should
probably
look
at
the
board,
though
shouldn't
we
at.
C
Yeah,
the
answer
to
that
is,
first
iteration.
Just
get
a
dashboard
up
with
a
widgets,
keep
it
simple,
specifically
specifically
two
widgets
audience
and
sessions,
which
is
users
over
time
and
sessions
over
time.
Essentially,
if
those
are
the
two
that
we
just
wanted
to
get
up,
it's
a
pretty
it's
a
proof
of
concept
that
using
the
internal
handbook
live
data.
We
can
show
on
a
widget
on
a
dashboard
the
users
over
time
and
the
sessions
over
time,
and
that
proves
the
concept
that
the
SDK
works,
that
the
infrastructure
Works.
C
C
Yes,
okay,
great
and
there's
actually
an
MR
perfect
that
is
working
on,
which
involves
also
the
schema
discussion,
where
he's
using
routing
and
dynamic
Imports
to
import
a
specific
dashboard
configuration
to
then
render
a
dashboard
which
we're
in
discussion
I
mean
discussing
with
now.
It
is
jumping
ahead
a
little
bit,
but
it's
something
we
need
to
do
and
also
contributes
to
The
Wider
schema
conversation
that
needs
to
happen
as
well,
making
sure
we
cover
that
exactly.
C
C
Right
yeah,
it's
a
Json
object
based
off
the
schema
from
the
dashboard
widget
structure,
Mr
and
the
cube
query,
rendering
widget
issue
So
based
off
of
that
there's:
a
widget
file
which
contains
a
widget
structure
which
defines
what
sort
of
data
it
uses
this
title
and
its
grid
stack
dimensions.
A
few
other
things,
customization
options
line,
colors
that
sort
of
thing
and
then
those
are
then
added
to
imported
into
the
Json
file
for
each
individual
dashboard
from
what
I
can
gather.
Okay.
C
I'm
trying
to
think
of
the
top
of
my
head
spoke
about
the
SDK,
so
it
should
do
now.
I
think
that
pretty
much
covers
where
we're
at
currently
in
this
Smorgasbord
of
front
end
range
of
stuff
I'll,
just
I,
it's
in
the
notes,
I
realize
I
haven't
raised
it.
I
am
working
on
the
onboarding
flow
for
creating
UI
on
board
info.
There
is
a
link
in
the
document
to
the
flowchart
of
what
I'm
building,
essentially
that
needs
that
I'm
converting
into
UI.
B
Yeah
I
think,
if
you
want
to
you,
can
quickly
share
it
or
I
can
quickly
share
it
to
my
screen,
just
as
we're
talking
over
it
for
the
sake
of
the
recording
but
I
had
a
look
at
this
when
I
joined
seems
sensible,
seems
nice
once
again,
thanks
for
putting
walls
of
text
into
something,
visual
really
helps
me
and
I
think
it
helps.
Basically,
everyone
consuming.
B
C
A
So
no,
the
the
thing
that
I
thought
it
was
missing
was
filled
by
you.
That
was
like.
What's
what
what
were
the
direct
follow-ups
of
from
our
work
on
the
on
the
dashboarding
foundation,
Mrs
and
and
yeah?
No,
in
fact,
in
fact,
I
I
believe
I'm
even
more
clear
about
a
roadmap
So
yeah.
Thank
you.
Thank
you
for
filling
the
details.