►
From YouTube: UX Showcase: Create: Editor Snippets with multiple files
A
We
work
mostly
on
the
web
id
and
snippets
a
little
bit
less
on
live
preview.
We
did
just
recently
take
over
a
bs
code
extension
called
git
lab
workflow
that
we
plan
on
doing
some
enhancements
in
the
near
future
for
today
we're
going
to
focus
on
snippets.
So
what
are
snippets?
Snippets
are
really
just
small
bits
of
code
that
are
reusable
and
shareable.
Some
use
cases
might
be
reusing
code
among
several
projects,
documentation
for
scripts
and
functions
or
instructions
for
using
the
main
project.
A
This
really
limited
the
potential
of
snippets
users
wanted
to
collaborate
star
fork
version,
all
the
all
the
real
benefits
of
git
that
we
get
everywhere
else
in
the
product
really
wanted
to
apply
those
to
snippets
themselves.
So
the
lack
of
version
control
made
it
hard
to
know
what
the
latest
version
was
or
what
changes
had
happened.
A
A
So
now
all
snippets
are
version
controlled
each
commit
each
time
you
edit
one,
it
creates
a
commit.
You
can
also
pull
snip
it
down
and
edit
it
locally
and
then
push
your
changes
back
up
just
like
any
other
git
repository,
but
there
wasn't
actually
a
lot
of
changes
to
the
ui.
At
this
point,
this
clone
button
that
I'm
highlighting
here
actually
was
the
only
change
that
would
let
a
user
know
that
any
change
that
really
even
occurred.
So
a
lot
of
work
went
into
this
button.
A
So
that's
why
I'm
highlighting
it
here,
but
with
this
button
you
were
able
to
see
the
clone
options,
and-
and
this
is
what
allowed
a
user
to
know-
how
to
pull
their
pull
the
snippets
down
and
make
like
local
edits,
but
obviously
we
weren't
doing
this
just
to
get
to
this
point.
We
were
really
setting
ourselves
up
for
the
future.
So,
let's
take
a
look
a
little
bit
further
ahead
of
where
we
actually
are
right
now
and
what
we're
working
on
today.
A
So
the
next
big
block
of
work-
that's
actually
already
in
progress,
is
snippets
with
multiple
files,
so
oftentimes
to
encompass
an
idea
of
code
or
a
block
of
code.
You
need
more
than
one
files.
Single
file
is
a
little
bit
limiting.
Also
in
the
customer
use
case
that
I'm
highlighting
here,
it's
a
package.json.
Another
example
might
be
html
with
css,
but
oftentimes
today
you
need.
A
So,
as
I
mentioned,
work
is
already
underway
for
this
we're
targeting
13.5
from
when
we
think
this
might
be
completed.
But
I'm
really
excited
about
this.
This
unlocks
a
lot
of
possibilities,
and
this
is
something
users
have
been
asking
for
for
a
while.
So
this
should
be
good
for
snippets
and
and
really
opens
up
a
lot
of
doors
possibilities
of
things
we
might
be
able
to
do
in
the
future.
A
So
after
multi-file
snippets.
The
next
thing
we're
going
to
tackle
is
revisions
so,
with
snippets
now
being
git
based
inversion
controlled
you
kind
of
get
all
the
benefits
that
come
with
that
and
and
one
of
the
big
ones
is
revisions
and
being
able
to
see
the
history
and
the
changes
that
were
associated
with
that.
So
we
will
be
introducing
a
revisions,
tab
that
lets
c,
see
users
see
who
made
what
changes
to
what
files
and
when
kind
of
get
all
the
benefits
of
git.
I
won't
go
too
deep
into
that.
A
I
think
working
at
get
lab.
We
we
understand
the
benefits
of
gate
and
and
being
able
to
see
revisions
and
history
and
all
that
good
stuff.
But
what
I
think
it
adds
in
terms
of
snippets
is
is
additional
confidence
and
accountability,
and
I
feel,
like
users,
will
be
a
lot
more
likely
to
share
and
reuse
code
if
they
have
kind
of
an
audit
trail
of
of
where
that
code's
at
and
how
it
got
there.
A
A
So,
when
you're
inside
of
a
project,
only
the
original
author
of
snippets
can
make
changes
to
the
snippet.
This
has
been
a
source
of
confusions
to
members
of
the
project,
as
they
might
have
permissions
to
add
other
type
of
content,
but
but
not
snippets.
So
what
we're
going
to
do
is
basically
bring
that
that
permission
model
back
into
line
with
with
that
of
the
snippets.
A
But
what
I
think
is
next
is
is
how
do
we
use
them
or
how,
more
importantly,
how
do
users
use
them?
What
can
we
do
with
snippets
that
that
might
let
users
get
more
use
out
of
them?
You
know
right
now.
They
can
embed
them
and
share
them,
but
there
are
other
use
cases
that
might
be
out
there
that
allow
more
integrated
kind
of
sharing
experiences
within
the
gitlab
platform
kind
of
planning
in
the
idea
that
gitlab
is
is
the
one
tool
for
your
devops
platform.
A
A
So
this
is
a
very
blue
sky
idea
at
this
point,
but
we
have
opened
up
an
issue
to
evaluate
the
viability
of
this
both
with
engineers
and
then
as
a
business
standpoint,
and
I've
linked
that
issue
here
to
go
even
more
blue
sky.
With
this
idea,
general
blocks
of
code
are
interesting,
but
for
gitlab
specific
things
like
the
get
lab,
yaml
file
and
and
jobs
and
templates,
and
things
like
that.
A
At
this
point,
another
idea,
like
I
mentioned
at
the
beginning
of
the
video
we
have
recently
taken
over
vs
code
extension,
called
git
lab
workflow
and
in
that
extension,
you're
actually
able
to
create
snippets
with
it,
but
you're
not
allowed
to
consume
them
or
basically,
the
the
downstream
version
of
it
doesn't
exist
so
very
similar
to
the
web.
Id
having
your
snippets
in
the
place
that
you,
edit
code,
makes
a
lot
of
sense.
A
So
that's
a
couple
of
things
we're
looking
at
but,
like
I
said
I
feel
like
now
that
we've
laid
the
foundation
with
with
with
version
control
and
multi-files
and
and
being
able
to
see
your
revisions
happy
to
hear
any
other
ideas
and
and
see
where
we
can
take
snippets
into
the
future
and
last,
but
probably
most
important.
We
do
have
an
issue
open
to
change
the
icon
for
snippets,
so
the
current
icon
is
a
pair
of
scissors
and
we're
looking
to
move
to
something
that
is
maybe
a
little
bit
more
code
related.
A
So
jeremy
has
put
together
a
number
of
fantastic
options
for
us
that
we
are
currently
considering,
and
since
this
is
on
the
navigation
bar,
it's
basically
present
on
every
page
in
git
lab,
so
we'd
love
everybody's
opinion
on
it
feedback
is,
is
certainly
welcome
and
feel
free
to
reach
out
in
the
issue,
and
I
think
that's
all
I
had
to
cover
today
thanks
for
taking
the
time
to
listen
to
me
and
please
reach
out
with
any
questions
or
feedback.
Thank.