►
Description
In this session, we discuss the proposed architecture and possible editor candidates and how they measure against our evaluation criteria.
A
Awesome,
okay,
hello,
everyone.
So
this
is
a
an
issue
requirement
session
of
the
statistic
a13
and
today
we
are
going
to
be
talking
about
researching
and
evaluating
one
of
the
athers.
Well,
we
are
gonna
evaluate
an
update
or
alternative
that
we
are
looking
at
to
replace
our
current
music
with
eight
in
the
in
the
south
side
later
so.
A
A
Okay,
so
a
little
bit
of
context
with
we've
been
evaluating
the
we've
we've
been
looking
at
some
extra
alternatives,
because,
after
the
the
time
that
we've
been
developing
the
the
studies
at
either,
we've
noticed
that
the
we
see
with
hatred
that
we
are
using
right
now
trust
ui
does
not
satisfy
some
of
the
technical
requirements
that
that
we
have.
So
in
a
previous
requirement
session,
we
created
this
evaluation
matrix
where
we
defined
some
technical
requirements
and
ux
requirements.
A
So
the
idea
is
that
we're
going
to
use
this
this
session
to
fulfill
or
or
work
on
on
some
of
the
evaluation
criterias
for
I
specificator
in
this
case
today
we
are
going
to
focus
on
on
tiptop
and
frostmeter,
so
the
idea
is
that
we
are
not
going
to.
We
are
not
going
through
all
of
the
the
evaluation
criteria
and
the
tabling
order.
Some
of
them
are
very,
are
very
easy
to
determine,
for
example,
the
maturity
of
eight
or
and
also
browser
support.
A
A
So
those
are
the
accessibility
one
where
we
are
going
to
evaluate
the
extensibility
of
the
markdown
parser
and
how
accessible
you
say,
the
reciprocator
that
we
are
evaluating
and
also
the
the
ux
pictures.
So
we
are
trying
to
find
a
balance
between
how
extensible
and
are
the
capabilities
of
the
visible
creator,
but
also
how
many
pictures
the
editor
provides
built
in.
So
we
don't
have
to
start
for
implementing
those
pictures.
C
A
A
A
A
And
besides
that,
other
statistic:
generators
also
include
templating,
syntax
hugo
has
a
templating
syntax.
In
the
case
of
middleman,
it
uses
erp
that
allows
embedding
a
ruby
privilege,
syntax
putting
within
your
marketing
documents
and
in
the
case
of
caspian
new
unknox.
You
can
use
a
react
and
view,
so
we
discovered
that
this
is
spacer
generator.
That's
right.
A
There
are
other
syntaxes
that,
for
example,
crown
down
the
hat
that
have
attribute
definitions
are
will
not
be
supported
by
that
parser.
So
the
idea
is
that
we
can
build
extensions
and
I'll
create
custom
tokenizers
in
the
parser
to
support
those
extensions
and
create
a
custom
notes
in
the
abstract,
syntax
string
that
is
generated
by
the
parser.
A
So
this
is
pretty
much
what
this,
what
this
diagram
diagram
tries
to
to
outline.
So
in
the
case
of
primark,
there
is
another
markdown
parser.
That
is
not
what
tito
uses
free
mark
usually
has
an
of
extensions
for
the
parser,
for
example.
One
very
popular
extension
is
every
mark
and
dx
and
dx
is,
is
an
extension
of
markdown
that
allows
using
react
like
jsx
within
marketing.
So
there
is
a
package
for
that
and
then
there
is
a
focus
for
front
matter
and
a
package
for
the
the
table
of
content.
A
A
A
So
here
in
the
in
this
diagram,
which
is,
is
a
rich
content
paper,
it
could
be
prospector,
it
could
be
a
3ds,
it
could
be
any
editor.
What
matters
is
that
it
has
an
ecosystem
to
bring
support
for
other
features
like
video
support,
and
then
we
can
implement
our
own
extensions.
So
we
want
to
implement
an
image
viewer
component.
A
C
So
when
we,
when
we're
talking
about
pros,
mirror
slash
tiptap
today,
we're
essentially
talking
about
the
part
there.
We,
which
shows
cool,
js
and
and
and
thinking
about
it
in
in
the
terms
of
how
it
can
render
all
of
this
stuff
with
parse
and-
and
you
know
what
you
know,
what
it's
its
ecosystem
looked
like
in
terms
of
allowing
us
to
create
custom,
extensions
and
and
community
use
community
extensions.
A
A
C
So
just
stop
on
that,
maybe
that
that
feels
like
an
action
that
we
shouldn't
miss
out
on
so
who
can
commit
to
double
checking
enrique's
initial
evaluations,
I
mean
I
I
can
definitely
on
the
maturity
one.
I
I
mean
that
that's
something
that
I
can
definitely
help
double
check.
There's
gonna
be
some
other
ones
that
will
probably
be
better
for
the
likes
of
chad
or
derrick
to
the
validate.
C
B
C
A
Okay,
so
before
jumping
into
the
accessibility,
I
want
to
to
make
a
quick
remark
about
themes
in
in
the
case
of
ross
miranda
and
picture.
So
these
editors
do
not
provide
a
user
interface.
They
have
some
minimal
components,
let's
let's
go
through
through
first.
What
what
tipped
up
and
and
purpose
meter
is
quickly.
A
So
these
libraries
are,
these
frameworks,
actually
are
not
we
see
with
eight
per
se,
they
are
attacking
to
build
a
reciprocater.
Tiptop
is
built
on
top
of
cross,
mirror
and
transmitter.
What
provides
is
a
document
model
on
top
of
of
dom
and
some
very
basic
beautiful
components
to
to
implement
and
we
switch,
and
it
provides
a
an
architecture
to
to
track
changes
that
that
are
introduced
by
the
user
like
typing
or
formatting
in
in
terms
of
transactions
and
commands.
A
C
A
So
we
have
a
a
button,
look,
we
have
the
the
floating
menu
component
and
then
we
just
need
to
add
a
button
and
assignment,
and
if
it
is
active,
they
provide
the
api
to
indicate
that
it's
active
and
then
they
also
provide
a
command
api,
an
interface
to
just
call
that
that
api,
when
the
button
is
clicked.
So
all
of
this
is
very
simple.
A
D
My
my
gut
feel-
and
I
said
this
in
one
of
the
comments
above-
is
that
in
general,
this
is
a
good
approach.
The
more
decoupled
and
cohesive
we
make
these
parts
and
the
individual,
cohesive
hearts
being
really
powerful,
like
tip
tap,
looks
to
be
is
going
to
be
a
big
win
in
the
long
run,
because
dejean's
question
the
perceived
effort,
it
seems
like
the
perceived
effort
is
pretty
low,
but
the
real
effort
is,
as
we've
seen
with
the
other
one.
A
A
Okay,
so
those
that
was
the
comment
on
theme
and
okay,
let's
go
with
with
extensive
meaning.
So,
as
I
mentioned
before,
our
main
concluding
sensibility
is
is
having
a
way
person
of
extending
the
the
the
markdown
parser.
So
I
have
a
a
comment
about
the
marketing
parser
and
about
transmitter.
So
I'm
gonna
find
an
example
of
trust
meter.
A
A
A
What
they
say
is
that
html
is
it
has
well,
it
is
very
flexible
and
you
have
you
have
many
ways
of
achieving
the
same
thing.
So
they
have
this
document
model
built
on
top
of
html.
Where
you
indicate
hey,
we
have
this
node
of
type
paragraph
and
that
modified
paragraph
of
type
paragraph.
We
have
a
content
that
is
that
consists
of
inline
text,
or
it
can
consist
of
images
and
other
things
like
that.
A
So
the
idea
of
the
of
the
burden
parser
of
the
prosperity
market
culture
is
that
it
quickly
it
easily
allows
you
to
map
a
note
of
the
var
dynasty,
syntax
string
to
a
note
of
the
approach
lever
document
model
by
default.
It
provides
this
library
provides
a
default
markdown
parser,
where
they
they
do.
Some
mapping
of
the
common
market
spec
to
the
to
the
most
basic
crossmember
document
model
so
like
what
I
see
us
doing
is
that
we
will
want
to
to
implement
some
support
for
non-standard
markdown
syntaxes.
A
Like
a
few
definitions,
reference
definitions,
developed
contents.
We
can
use
markdown
to
identify
sus
syntaxes
and
they
have
some
plugins
that
are
already
implemented,
for
example,
tables
a
strikethrough
and
a
lot
of
other
programs
that
are
implemented
by
the
community,
and
we
just
need
to
to
specify
hey
approach,
mirror
those
node
types.
They
are
gonna
maps
to
some
transmitter,
node
types
that
are
implemented
here
or
we
can
say,
hey.
They
are
gonna
map
to
some
of
the
node
types
that
are
implemented
by
titan.
A
A
No,
the
only
example
that
I've
seen
of
doing
something
like
that
is
with
mdx,
that
is
for
ghastly.
So
let
me
go
but
go
up
here
a
little
bit,
so
one
of
the
most
more
attractive
things
about
remark
is
that
remark
is
used
by
by
gatsby
and
it
is
used
by
by
netflix
to
implement
to
implement
ndx
support.
So
there
is,
there
are
packages
to
support
this
syntax,
but
I
don't
think
that
our
there
is
support
to
implement
er
or
health
and
planning
syntax.
C
C
C
A
B
That
correct
me,
if
I'm
wrong
but
kind
of
put
another
way,
is
we
would
be
able
to
extend
mark
down
it
in
this
particular
example
such
that
like
so
right
now
we
create
custom
renders,
whereas
we
just
assume
we
just
let.
However,
it
was
parsed,
be
as
it
is,
which
is
a
shortcoming
and,
for
example,
the
the
table
of
contents
cram
down
is
basically
just
a
paragraph,
but
then
we
parse
it.
B
But
we
then
now
parse
that
special
paragraph
to
see
if
it,
if
it's
kind
of
a
unique
style
paragraph,
and
then
we
have
a
custom
renderer.
The
difference
with
this
is
that
we
are
able
to
identify
it
upstream
that
it's
a
proper
type
and
have
like
a
first
class
type
so
that
we
don't
have
to
do
that
kind
of
hacky
thing
downstream
and
then
and
correct
my
enrique.
It
sounds
like
we're.
Also
gonna
define
the
the
note
itself
so
that
it
can
do
a
just
a
mapping
for
us
kind
of
automatically.
A
Right
so
we
are
going
to
do
the
this
package,
the
of
this
markdown,
so
this
buy
down.
Personally
from
breakdown,
we
are
gonna
customize
a
mask
the
markdown
to
identify
upstream
those
custom
syntaxes
we
are
gonna,
assign
a
node
type.
We
are
gonna,
you
know
set
all
of
the
correct
metadata
and
then
we
are
gonna
say:
hey
map
this
node
type
to
approach
mirror
nodes
and
in
the
serializer
we
are
gonna.
B
Cool
yeah,
I
think
obviously
we'll
we'll
want
to
test
like
this
sounds
awesome.
Obviously
we
will
definitely
want
to
test
it
on
like
one
of
our
unique
cases
and
like
see
how
what
that
experience
is
like
right
before
we
dig
all
go
all
in.
I
think
it's
probably
worth
doing
that.
Maybe
you've
already
done
that.
I
don't
know,
but
that's
obviously
something
we
want
to
test
because.
A
B
A
Definitely
yeah,
I
I'm
gonna
share
the
demo
later.
I
don't
know
if
I
I
shared
around
here,
I'm
gonna,
just
you
know
I
should
share
in
on
the
slack,
but
I
the
cool
thing
about
the
demo
is
that
it
demonstrates
how
we
implement
a
tokenizer
in
a
parser
to
identify
the
custom
syntax
and
we
convert
that
into
a
note
in
the
and
then
we
supplicate
it.
A
A
A
A
D
A
C
A
That's
a
good
question:
I
think
that
that
we
should
use
tipta,
but
I
have
I
have
score.
I
have
concerns
with
with
titan,
for
example,
one
of
the
things
that
I
that
I
notice
notice,
while
evaluating
the
the
maturity
of
the
library,
is
that
it
doesn't
have
a
robust
test
suite
most
of
the
extensions
are
contributed
by
the
community,
but
they
are
not
configured
with
without
without
specification,
but
I
think
that
if
we
don't
do
that,
we
will
have
to
the
cost
of
development
will
increase
dramatically.
A
So
I
think
that
we
we
kind
of
start
with
that.
We
did
that
we
can
try
to
find
a
way
of
of
finding
some
way
of
decoupling
or
from
that
library
and
understanding
that,
on
you
know
below
that,
we
are.
We
are
relying
actually
approach
mirror
to
to
build
it,
and
there
are
other
aspects
like
the
the
collaboration
component.
A
What
I
mean
by
that
is
that
a
pros
meter
defines
a
document
model
and
you
have
to
define
a
schema
like
where
you
say:
hey,
we
have
this
type
of
nodes
and
they
have
this
and
they
allow
this
kind
of
relationships
so
tip
that
implements
a
whole
new
schema
and
we
will
have
to
to
implement
a
code
to
match
the
marginal
syntax
tree
to
tick.
That
document
model
right.
I
think
that
we
should
decide
with.
C
So,
yes,
you
know
tests,
so
I
I
found
issue
547
in
tiptap's
github
repo,
which
speaks
about
tiptop
version
two
and
how
they've
started
in
december
last
year.
They
started
working
on
version
two
so
which
is
a
complete
rewrite
after
that
they're
gonna
be
used,
write
rewrite
in
typescript
and
they
talk
about
tests,
and
so
on
my
I
guess
my
my
concern
is
to
you
know
like
it
feels
like
they
they've
realized
some
limitations
of
of
their
current
kind
of
like
architecture
or
design
or
whatever,
and
they
want
to
make
it
good.
C
So
I
guess
that
the
part
that
I'm
uncomfortable
with
tiptop
is
they're
likely
going
to
be
changing
things
drastically
soon.
Who
knows
how
drastic?
I
don't
know
exactly
you
know
from
what
I
can
read.
It
doesn't
look
like
it's
massive.
It
looks
mostly
reef
like
refactoring
type
of
things,
but
they
they
definitely
producing
new
features
and
so
on,
and
so
when
we
make
a
it
makes
me
uncomfortable,
making
a
commitment
to
a
library
that
I
know
is
likely
going
to
change
soon
and
where
they
acknowledge.
C
C
C
Feels
like
yes,
I
understand
what
it
that
it
that
it
brings
us
a
lot
of
plumbing,
that
we
would
have
to
do
ourselves
if
we
didn't
use
it,
but
how
you
know
are
we
building
on
top
of
something
that
is
going
to
be
stable
and
robust
for
for
a
long
time
like?
Are
we
going
to
have
to
re-architect
something
when
they
do
version
two
and
they
stop
supporting
version
one,
because,
for
whatever
reason,
they've
made
fundamental
changes?
C
I
mean
they're,
rewriting
the
they're
talking
about
rewriting
and
typescript,
and
so
I
expect
they're
not
going
to
be
maintaining
version
one
for
for
much
longer.
Once
who
knows,
when
version
two
hits?
I
mean
it's,
it's
been,
it's
been
a
while
in
terms
of
for
me
for
me
that
the
the
part
that
I
that
I,
like
pros
mirror
seems
to
have
very
good
support
commercial
support.
Even
you
know
from
even
even
though
it's
an
open
source
project,
it's
got
a
great
commercial
support.
C
My
my
worry
is
that
tip
tap
is,
is
kind
of
like
this
labor
of
love
from
this
company
called
overdoses
who
needed
a
view,
view
editor
and
they
kind
of
like.
I
don't
see
any
other
from
community
contributions.
I
don't
I
don't
see
anything
anybody
else
really
committing
to
the
tap
in
the
scenes
of
you
know
we're
gonna
make
sure
that
there's
continued
development
and
something
a
little
bit
bigger
than
just
community
contributions.
A
A
But
then
it
has
like
these
very
dubious
support.
It
has
really
literally
they
say
that
they
have
functional
testing.
But
let
me
show
you
look
at
the
at
the
commands
library.
They
don't
have
any
kind
of
testing
support
here
and
if
you
open
any
of
these
packages,
you'll
see
that
the
only
package
that
has
a
this
specification
is
this
one,
the
core
component.
It
only
has
one
strict
file.
C
A
C
D
What
do
you
think
about
the
the
idea
of
this
was
a
good
for
the
session
to
talk
about,
pros,
mirror
and
tip
tap.
I'm
still
a
little
bit
vague
on
the
mapping
of
both
of
those
libraries
to
the
others.
What,
if
we
converted
this
into
a
spreadsheet
format,
where
we
can
have
all
of
these
criteria
for
multiple
different
things
and
be
able
to
look
at
them
side
by
side
and
in
addition
to
future
things
that
we
look
at?
If,
if
we
do.
A
D
I'm
I'm
still
vague
on
the
the
split
between
tip,
tap
and
pro's
mirror
and
like
what
part
of
that
would
be
replaced
by
remark
or
or
what
part
we
would
have
to
build
from
scratch.
If
we
didn't
use
chip
tap
and
used
pros
mirror
directly,
I
guess
is
like
would
be
another
completely
different
option
to
compare.
A
A
They
have
they
provide
three
different
types
of
floating
menu.
This
is
something
also
that
we're
going
to
include
that
that
we
would
like
to
to
implement
in
the
science
center,
if
I
remember
correctly,
this
type
of
contextual
formatting
and
they
implement
a
different
off.
This
is
a
the
third
type
of
menu,
so
this
is
a
functionality
that
we
will
have
to
implement
from
scratch
that
the
array
provides
also
the
shortcuts
here.
So
they
have
this.
C
What
say,
for
instance,
I
mean
I
nothing
in
that
issue
that
I
read
points
to
drastic
external
changes
that
you
know,
external
being.
You
know
the
api
they
surface
for
and
how
you
use
it,
but,
however,
safe
for
instance,
we
we
run
into
challenges
with
tip
tap.
What
is
our
alternative?
If,
if
we
want
to
replace
tiptap
with
something
else
and
still
keep
our
you
know,
froze
mirror
and
our
the
rest
of
our
architecture
in
place?
Do
we
have
an
alternative
to
tiptap?
C
Do
we
is
it
about
us
having
to
roll
our
own
kind
of
like
functionality
on
top
of
pros
mirror,
because
my
initial
searches
didn't
really
kind
of
like
show
too
many
view?
Wizard
editors,
that's
built
on
top
of
prose
mirror
tap
is
pretty
much
the
one
that
is,
you
know
by
far
the
the
most
popular
one,
the
race
on
doesn't
seem
to
be
maintained
at
all.
B
B
Another
thing
to
consider
is
slate
looks
like
it's
actually
in
beta,
so
I
don't
know
how
you
know
reliable
it
is
I
mean
we're
just
in
a
situation
where
you
know
we
have
to.
We
have
to
you
know,
move
forward
and
like
the
most
ideal
tool
doesn't
exist,
is
basically
kind
of
where
we're
at
so
I
definitely
understand
the
concerns
right
like
of
tiptap
and
it
being
especially
if
they're
going
to
a
v2.
I
share
that
same
concern.
I
think
we
all
do
it's
like
yeah.
B
D
To
take
a
shot
at
answering
john's
question,
so
if
we
did
go
with
chiptap
and
like
as
far
as
the
rewrite
and
typescript
that
seems
less
scary
to
me
than
like
they're
redesigning
their
api,
that
mostly
seems
like
they
just
want
to
clean
up
their
code,
have
type
safety
and
do
that.
I
didn't
see
what
their
roadmap
is.
D
We
should
look
closer,
but
if
it
means,
if
they're
not
necessarily
redesigning
the
api,
I'm
less
concerned
about
that,
but
even
if
they
do
the
fact
that
it's
rarely
decoupled
and
an
isolated
layer
and,
like
derek
said,
you
know
worst
case
down
the
road.
Maybe
we
say:
oh,
we
really
hate
tip
tap
2.0,
all
right,
we're
stuck
with
it.
We
have
to
fork
it
and
then
do
something
different.
D
The
fact
that
we
have
this
decoupled
approach
means
that,
okay,
we
we
need
to
shim
something
else
on
top
of
prose
mirror
whatever
that
is,
but
what
we've
done
in
tip
tap
is
still
going
to
work
for
the
time
being,
while
we
cross
that
bridge,
if
we
ever
have
to
come
to
it
down
the
road.
So
I'm
from
that
perspective
less
concerned
about
committing
to
tiptap,
if
it
does
what
we
want
right
now,
yeah
nicely.
C
For
me,
it's
just
about
you
know
whatever
option
we
go
with,
it
has
a
risk.
For
you
know
what
I'm
trying
to
calculate
in
my
mind
is
how
big
is
the
risk?
What
is
our
safety
net
look
like,
and
that
is
you
know,
that's
one
of
the
the
parts
we
need
to
evaluate
it's
not
a
deal
breaker
in
in
and
of
itself
in
you
know
in
total,
you
know
you
know.
Ultimately,
code
is
code
and
you
know
if
we
have
to.
C
We
can
write
our
own
code,
but
we
don't
want
to
because
we
want
to
leverage,
you
know
the
power
of
the
community.
You
know
the
40,
plus
people
contributing
to
the
project
is
exponentially
more
if
effective
than
the
four
or
five
of
us
that
work
on
it,
and
so
I
I
just
want
to
make
sure
that
you
know,
like
you
know,
it's
my
job
to
ask
the
the
risk
questions
and
because
you
know
committing
you
know
two
to
milestones
through
architecting
a
system.
It's
not
going
to
look
good.
C
If
you
know
in
two
milestones
after
that,
we
said
oops,
we
need
to
actually
we're
going
to
do
something
different
again,
and
so
we
need
to
with
a
fair,
fair
sense
of
of
confidence.
There's
no
guarantees
in
anything
but
the
fair
sense
of
confidence.
We
need
to
know
that
what
what
there
is
here
is
fundamentally
solid
enough
for
us
to
build
on
and
for
us
to
to
rely
on
for
for
foreseeable
times
under
doneness
in
future.
C
I
think
the
the
fact
that
that
is
the
only
pros
mirror
kind
of
like
base
view
exclusion
does
seem
to
have
high
usage.
I
mean
net
issue,
they
talk
about
200
000,
I
mean
this
is
not
a
year
ago,
always
two
hundred
plus
thousand
dollars
a
month
of
the
of
the
library,
so
it
definitely
seems
to
be
to
be
well
used.
There
is
an
active
community
that
we
can
see.
You
know
there's
this
pull
request,
there's
issues
in
this
conversation
on
those
issues
so
that
in
itself,
kind
of
like
mitigates
without
that
concern.
C
I
I
guess
that
it's
never
nice
when
you
don't
have
a
clear
alternative
to
to
be
able
to
go
to,
and
in
this
case
we
don't
seem
to
have
a
clear
alternative.
I
will.
I
will
highlight
that
another
gig
gitlab
team
member
previously
actually
worked
with
tap
and
try
to
make
it
work
as
part
of
the
editing,
experience
and
issues
for
for
the
editor,
and
they
got
closer.
Just
never
had
to
to
see
it
through.
C
B
A
Is
identifying
if
we
can
use
a
subset
of
pixel,
because
what
it
provides
is
a
custom
document
schema
that
works
well
with
the
visual
components
that
they
provide.
So
perhaps
an
option
is
like
just
adopting
those
special
components,
but
not
the
document
schema,
because
we
know
that
what
is
robust
and
is
stable
and
its
future
proof
is
pro
smithere,
not
thicker.
A
D
D
C
I
just
want
to
I
mean
I
don't
want
to
dismiss
any
options,
but
I'll
be
hard-pressed
to
be
cut
to
to
be
convinced
to
bring
in
iraq
based
on
our
ecosystem.
It's
from
a
maintainability
point
of
view.
It
just
doesn't
feel
right
to
introduce
another
and,
and
I'm
sure,
we'll
have
containers
as
well.
At
that
it's
just
another
thing.
We
need
to
learn.
D
B
Yeah
and
again
that
yeah
we're
on
the
same
page
again,
I
was
just
thinking
outside
the
box
right,
it's
like
what,
if
I
mean
that's
really
what
it
was
is
from
my
understanding.
It's
the
view,
flavored
version
of
slave,
which
is
and
again
I
know
very
little
about
it,
but
like
the
go-to,
the
go-to
wrapper
on
top
of
prosmer
for
react.
That's
basically
what
that
is
so
tip
tap
is
a
views.
Version
of
that.
C
C
B
B
And
right
now
it
sounds
like
prosemir
is
an
extremely
strong
base
to
enable
that
it
kind
of
sits
in
the
middle
in
a
way,
but
that
allows
us
to
choose
whatever
parser
we
want
and
then
whatever
editor
we
want
yeah.
I
guess
exactly
where
I'm
going
with
that
other
than
like
that's
the
main
win
of
this
entire
effort
as
far
as
I'm
concerned
and
then
downstream
further,
if
we
you
know,
say,
for
example,
today
we
had
to
make
a
decision
and
we
went
with
tip
tap.
B
The
sheer
fact
that
those
are
now
teased
apart
should
give
us
more
confidence
than
what
we
have
now
in
the
sense
that
we
can
now
swap
out,
not
one
big
piece,
but
just
the
editor
itself
again.
We
don't
want
to
do
that.
Ideally
have
the
the
winning
solution
right
now,
but
we
obviously
don't
so
it's
a
trade-off.
C
I
think
that
the
one
thing
that
we're
definitely
in
agreement
with
is
the
architectural
proposal
that
enrique
has.
I
think
the
four
of
us
have
commented
in
the
issue
and
on
this
hall
that
you
know
like
that.
I
think
is
definitely
the
right
time.
I
think
the
conversation
is
you
know,
is
it?
Is
it
remark
in
quill
or
is
it?
Is
it
pros,
mirror
and
mark
down
it?
And
that's
that's
where
we
we're
kind
of
like
not
a
hundred
percent
sure
and
I
think
to
answer
that
we
have
to
go
through
our.
You
know.
C
We
have
to
use
our
evaluation
criteria,
we
have
to
do
the
solid
we
have
to
evaluate.
I
personally
would
like
us
to
to
evaluate
at
least
two
opt-ins.
It's
it's
one
thing
for
us
to
evaluate
prose
marines
and
malcolm
x
against
our
criteria
and
and
say
yeah
broadly
it.
It
meets
the
criteria
we
can
make
it
work
and
so
on,
but
I
do
think
from
a
due
diligence
point
of
view.
C
We
have
to
at
least
have
a
an
alternative
that
we
also
evaluate
to
say
we
have
looked
at
this
because
maybe
we're
surprised
in
our
evaluation.
You
know
like
a
lot
of
the
the
things
that
not
one
single
validation
is
really
a
deal
breaker
except
for
license.
To
be
quite
honest,
that's
the
only
that's
the
only
kind
of
like
black
and
white
criteria.
C
I
think
your
your
your
rationale
behind
prosmer
and
martin,
like
I'm
looking
at
that,
and
I'm
almost
like,
I
always
want
to
say.
Yes,
that's
just
going
to
do
that,
but
I
I
want
us
to
to
just
you
know,
persevere
and
do
our
due
diligence
properly
and
make
sure
that,
even
if
we
do
make
a
mistake
with
our
choice,
you
know
like
when
we
make
a
decision
if
we
make
it
based
on
the.
C
If
we
make
the
right
decision
based
on
the
data
available,
it
was
still
the
right
decision
at
the
time
hindsight
was
20
20.
you
know
like,
but
when,
if
we
are
down
the,
if
we
do
go
down
the
line
and
we
and
we
realize
we
made
a
mistake
and
we
look
back
and
we
didn't
do
our
due
diligence-
that
is
not
right
and
so
I'd
rather
us
take
another
week
or
two
evaluate
two
options
and
make
make
our
case.
C
My
question,
then,
is:
what
is
the
the
best
use
of
our
time
right
now
together?
We're
we're
all
in
agreement
that
we
could
probably
give
another
20
30
minutes.
If
I
need
to,
is
it?
Is
it
about
looking
at
those
evaluation
criteria
and
assessing
the
pros
mirror
complex
stack?
Would
that
be
beneficial
to
you
in
the
uk.
A
That
has
a
markdown
that
I
interfaced
that
we
can
plug
with
remote.
I
just
haven't
read
about
it
like
extensively,
but
I
think
that
perhaps
the
next
step
is,
as
chad
said,
creating
that
spreadsheet,
with
a
lot
of
evaluation
criteria
and
feeling
feeling
down
with
ck8
or
angry
mark
or
other
other
type
of
combination.
C
D
A
I
think
that
we
have,
we
can
miss
a
mix
and
match.
So
perhaps
what
we
can
do
is
list
which
are
the
american
parties
that
we
have
available
mark
down.
It
remarked
which
are
the
visible
creators,
ck8
or
proof
meter
a3s,
and
then
we
can
distribute
the
work
among
ourselves
to
that
spike
and
see
how
we
can
mix
and
match
those
options.
D
Right
so
maybe
they're
they're
two
separate
comparison,
spreadsheets,
the
the
markdown
part
and
the
editor
part
and
as
an
experiment,
we
could
see
pick
the
best
one
of
each
of
those.
You
know,
maybe
there's
something
better
than
tip
tap
and
say:
well,
how
hard
is
it
to
make
the
best
one
work
with
rosemary?
B
I
think
that
makes
sense.
Obviously,
however,
we
choose
to
scope.
The
spikes
is
really
what
what
it
comes
down
to,
but
yeah,
I
think,
and
enrique
you
obviously
already
did
this.
I
have
not
so
I
just
don't
know
like
that.
That's
really
what
it's
gonna,
I
think
we're
gonna
learn
the
most
when
we
actually
try
to
implement
and
see
like
what
snags
do
we
hit?
How
smooth
is
this
that
type
of
thing
is?
Is
it
right.
C
I
want
to
propose
that
we
we
almost
create
like
a
test
criteria,
proof
of
concept
in
a
sense
of
here's,
a
here's,
a
here's,
a
a
source,
markdown
file,
and
it's
got
some.
You
know
like
standard
common
mark
stuff.
Maybe
it's
got
some
bad
syntax,
and
maybe
it's
got
some
erb
code
in
it
and
say,
and
then
we
we
evaluate
the
different
combinations
of
of
two
of
options.
We
have
you
know
with
tab
and
all
of
those
and
say
you
know,
and
let's,
let's
define
okay.
What
what
do
we
want
to
achieve?
C
You
know
so
create
a
proof
of
concept
that
and
render
this
properly
in
in
wizarding
mode
and
you're
like
or
maybe
at
least
doing
equivalence
of
what
we
currently
have
in
total
ui.
You
know,
identify
the
non-markdown
components
and
make
them
non-editable,
because
I
think
doing
that
will
will
a
allow
us
to
understand
how
powerful
and
flexible
the
the
architecture
is.
C
That
solution,
and
also
the
developer
experience,
because
I
think
we
shouldn't
we
never
actually
defined
that
as
a
criteria,
but
the
developer
experience
is
important
as
well
in
terms
of
how
easy
is
it
to
find
information
about
the
api
the
documentation
you're
like?
Do
you
actually?
Is
there
something
that's
obscure
within
the
the
code
that
isn't
documented
properly
that
that
you
needed
to
look
at
so
maybe.
D
C
Is
kind
of
like
our
our
pro
should
be
our
approach
with
this
is
first
first,
let's
identify
our
solution
options
you
know
like
so
so
that
that's
one
part
of
it,
the
second
and
then
our
proof
of
concept
phase
is
we've
done
these
solution
options.
We've
we've
done
a
a
rough
validation
on
them.
You
know,
and
I
and
I
think
our
we
should
go.
We
should
complete
the
validation
criteria
and
it
says
then,
based
on
that,
to
give
us
a
clear
indication
of
this
is
not
worth
doing
it.
You
know
like
ck.
C
Editor
is
a
great
editor,
but
I
have
some
concerns
about
how
flexible
it's
going
to
be
to
allow
us
to
do
what
we
want
to
do.
You
know
and
and
and
so
forth,
but
though
those
concerns
aren't
valid
until
we've
actually
done
an
evaluation
on
them.
So
maybe
the
first
step
is
okay:
let's,
let's
define
our
our
our
candidates
and
or
architecture
candidates.
D
D
B
D
C
C
B
B
A
C
B
C
C
C
B
C
C
C
D
A
C
Lie
with
you
in
retain
you're
gonna,
you
can.
You
can
get
the
input
from
all
the
team,
but
ultimately
you're
the
dri
on
this,
and
you
know
what
what
decision
you
make
needs
to
be
informed
and
will
support
support
you
as
a
team,
but
somebody
needs
to
make
the
final
decision
and,
and
that
lies
with
you
and
our.
C
Essentially,
for
making
that
final
decision
is
the
17th
of
october,
so
we've
got
it.
We've
got
33
days
or
32
days
to
to
make
that
decision,
and
so
I
think,
there's
quite
a
bit
of
work
in
this
and
we
should
try
and
and
get
as
much
as
done
as
possible.
Now
I'm
also
going
on
some
pto
soon.
So
I
I
want
you
to
make
sure
that
you
know
you
don't
just
take
this
all
on
yourself.