►
Description
Discussion around how we might approach the design of an item for a hackathon coming up mid July.
A
A
When
I
first
saw
this,
I
was
thinking
about
how
how
the
content
editor
might
play
in
the
experience
of
editing.
So
my
my
assumption
of
this
issue
was
like
we
were
thinking
that
the
content
editor
would
come
to
like,
replace
and
or
add,
add
a
way
to
edit
issue
descriptions
using
the
content.
Editor
features
that
we've
implemented
and
the
same
thing
with
like
comments.
A
A
B
A
Cool
all
right,
so
this
is
like,
like
a
breakdown
of
kind
of
like
where
we're
at
where
we
might
go.
Who
knows,
but
at
the
moment
this
is
our
wiki
experience,
and
we
have
this
way
to
toggle
like
rich
text
or
edit
source,
and
it's
that's
the
thing
that
swaps
back
and
forth
between
content
editor
and
the
raw
markdown.
A
I
think
this
is
a
good
opportunity
to
kind
of
like
revisit
this
whole
thing
and
potentially
just
like
collaborate
on
this,
because
I
know
that
youtube
both
have
worked
on
the
content,
editor
extensively
and
very
familiar
with
the
ui
there,
so
you
might
have
some
ideas
of
how
to
implement
it
better
as
we
move
into
the
world
of
like
combining
it
so
that
it
works
in
here
like
how.
How
might
I
switch
from
this
view
to
the
content
editor
view.
A
B
B
C
A
B
A
And
then
I
was
just
exploring
this
without
something
that
I
mentioned
you
kind
of
brought
up
is
like
if
you
do
continue,
adding
stuff
to
the
tabs
that
this
and
this
toolbar
might
get
too
long,
and
potentially
we
may
need
to
like
truncate
this
into
a
drop
down.
This
is
like
a
recent
icon
that
was
added
it's
like
for
titles,
and
things
like
that
and.
B
A
If
we
need
that,
yes,
I
like
this
thinking
prevention
and,
let's,
let's
play
around
with
that,
because
what
I
mentioned
is
pointing
out
to
here
is
that
like?
Currently,
we
have
attach
a
file
in
here,
but
there
is
an
issue
out
there
that
suggests
hey.
Why
don't
we
move
this?
Attach
a
file
to
become
a
action
button
up
here
and
like
a
button
insert
diagram,
and
we
kind
of
visualize
this
here
where
this
is
like
attached,
file
or
image?
A
The
paper
clip
is
like
a
good
option
here
we
we
had
a
small
survey
and
people
said
yep.
If
attaching
files
or
images
this
paper
clip
would
be
fine,
but
recently
I
also
explored
some
other
ones.
That
kind
of
combine
concepts,
but
I
think
that's
a
finer
detail
that
we
can
result
look
into
later,
so
how
about
putting
a
preview
button
here?
A
A
C
A
C
A
C
B
B
C
C
A
We
don't
have
anything
at
the
bottom
at
the
moment,
our
world
kind
of
lives
in
like
the
toolbar
and
like
lots
of
actions
through
the
bubble
menu.
Should
we
have
like
a
footer
area
for
the
content
editor
I'm
just
thinking
out
loud
here
is
like.
Should
we
emulate
this
pattern
of
having
a
preview
and
stuff
like
that
for
the
content
editor,
or
should
we
not.
B
We
were
starting
to
implement
the
the
classic
mark
dominator
from
scratch.
Would
you
take,
would
you
make
the
decision
of
putting
like
actions
in
the
border?
Besides
the
beside
experience,
the
actions
in
the
toolbar,
or
would
you
just
like?
Will
you
make
the
decision
of
moving
the
the
attached
files
and
the
freebie
button
to
a
toolbar.
B
A
Yeah,
a
thought
has
come
up
in
the
past
with
like
inserting
items
that,
like
one
potential
approach,
would
be
having
formatting
tools
and
inserting
actions
kind
of
separate.
I
see
that
in
some
applications,
where
they
kind
of
separate
the
two,
whether
that's
the
right
way
or
not.
That's
that's
a
whole
another
ball
game,
but.
A
The
kind
of
concern
I
kind
of
have
with
like
preview
and
close
as
simple
as
it
is,
is
like
I
don't
know
what
happens
to
the
topic.
It
feels
strange
to
have
the
actions
still
available.
If
you
do
preview
do
preview
once
you've
done
the
preview,
then
it's
like
yeah.
You
can
surface
this,
but
it
feels
a
little
bit
strange
to
have
preview,
but
these
things
still
visible.
C
A
No,
no,
not
too
crazy,
because
one
one
thing
that
we
haven't
really
talked
about
too
much
is
like
the
full
screen
mode.
You
know
this
is
something
that
we're
going
to
talk
about
later
in
the
future,
but
yeah
side-by-side
view.
That's
when
you
have
the
real
estate
for
that
definitely
to
play
around
with
concepts
like
that.
A
A
A
B
A
B
That
I
I
think
like
first
I
I
don't
think
that
we
should
like
avoid
the
free
factoring
if
we
won't
like
to
to
implement
that
ideal
design.
But
what
I
think
is
like
we
have.
We
have
to
to
split
this
conversation
into
parts
like
what
do
we
want
to
achieve
in
the
in
the
context
of
the
hackathon,
and
what
do
we
want
to
achieve
long-term?
B
Because
if
we
are
like,
if
we
were
planning
dc
ford
as
a
water,
go
quarterly
ball
or
a
six-month
wall,
I
would
say:
yeah,
let's
go
for
it,
because
this
is
probably
the
best
way
of
doing
it
and
it's
cost
effective.
Based
on
on
the
time
that
we
have.
But
if
we
think
about
these
designs
in
the
context
of
a
single
week
swarm
between
everyone
in
the
team,
where
only
two
engineers
are
actually
familiarized
with
the
code
base
and
the
continuator,
what
do
we
want
to
achieve?
B
A
B
C
Yeah,
the
idea
of
hackathon
is
mostly
that
you
are
free
to
do
whatever
you
want
kind
of
without
any
constraints.
So
you
don't
really
have
to
depend
on
the
design
or
even
like
you.
You
should
be
able
to
do
things
that
are
not
conventionally
okay
to
do
or
it
can
be
a
bad
code
which
doesn't
really
go
well
in
master.
So
you
can.
You
should
be
able
to
do
things
like
that.
A
Okay,
silly
question:
on
my
side:
the
code
that
we
come
up
with
during
the
hackathon
would
that
be
something
that
would
be
releasable
behind
a
feature
flag
or
something
like
that
like
would
it
would
that
be
a
end
result,
or
is
there
more
like
a
proof
of
concept
that
we
would
end
that
like?
Where
is
the
line
like
what?
What
is
what
is
done
for
a
hackathon
from
the
engineering
side.
B
B
A
All
right,
so
that's
that's
my
takeaway
from
here
is
that
I'll
come
up
and
mock
up
a
few
rough
ideas
for
for
this,
and
then
we
can
use
that
during
the
week
of
the
hackathon
to
discuss-
or
if
you
have
time
next
week,
to
give
any
feedback
on
it.
We
can
discuss
it
asynchronously
next
week
and
then,
when
we
jump
into
the
hackathon,
hopefully
yeah
we're
kind
of
like
aligned
prior
to
jumping
into
it,
sounds
good.