►
From YouTube: Static Site Editor - WYSIWYG 13.0
Description
Walkthrough of the small step for WYSIWYG markdown editor for the static site editor.
Also included in this video is some future concepts
A
This
is
walkthrough
of
what
I'm
proposing
for
the
next
generation
in
the
markdown
editor.
So
at
the
moment
for
the
12:10,
we
have
a
text
area
and
that
shows
up
and
the
markdown
content
for
a
page
to
be
headed
for
the
$13
most
were
planning
to
do
as
a
team
is
replacing
that
text
area
with
Atos
UI
editor,
so
we
zoom
in
a
little
bit
into
this.
We
can
see
that
replacing
the
text
area
with
toast
UI
editor.
A
If
we
can
get
that
what-you-see-is-what-you-get
part
to
show
up
prior
to
the
markdown,
then
that
kind
of
takes
us
into
the
direction
of
editing
real
content
as
soon
as
possible.
One
caveat
to
this
is
that
you
know
what
you
see
is
what
you
get
scenario
I'm,
not
a
hundred
percent
sure
what
we
would
do
with
the
title
and
layout
aspect.
A
So
this
part
of
the
markdown
file
that
specifies
more
the
settings
part
of
what
the
page,
that's
something
that
I'm
100%
sure
how
that
would
render,
and
what
you
see
is
what
you
get
part
and
one
proposal.
There
is
not
to
show
it
at
all,
as
MBC
changed
with,
where
we're
introducing
the
toast
UI
editor.
A
Moving
on
from
that,
one
of
the
things
that
I
kind
of
a
small
issue
with
is
kind
of
this
acronym,
what
you
see
is
what
you
get
I
am
not
hundred
percent
sure,
that's
universally
known,
as
what-you-see-is-what-you-get
editor,
so
I
proposed
simplify
that
to
a
term
called
edit
and
markdown,
where
it's
the
same
text
editor
that
we
had
previously.
The
toggling
between
the
two
will
render
the
page
either
as
marked
down
as
markdown
or
rendered
aged
rendered
content.
A
A
When
it
comes
time
to
saving
okay,
if
we
iterate
more
on
this,
the
next
step
of
this
is
kind
of
looking
at
like
the
whole
page
structure,
because
what
we
have
now
is
like
the
toggling
between
the
views
and
then
the
submit
changes
down
here
and
then
the
scroll
part
is
just
this
page
here.
What
I'm
trying
to
get
us
to
in
this
note
is
like
a
whole
page,
immersive,
editing
experience,
so
one
step
towards
that
is
to
have
the
text
area
to
be
the
area
that
you're
allowed
to
scroll.
A
So
here
we
moved
buttons
to
the
tops,
and
now
you,
the
markdown
page,
is
the
content
Scrolls
completely,
and
this
part
here
Scrolls,
but
so
has
these
two
things
at
the
bottom
that
kind
of
get
in
the
way.
The
reason
this
is
at
the
bottom
and
not
at
the
top,
is
that
if
you
toggle
between
edit
and
markdown
and
your
page
won't
jump
a
lot
and
that's
kind
of
the
goal
there,
where
this
stays
and
then
the
toolbar
here
kind
of
stays.
A
Is
to
introduce
a
side
panel
where
we
could
stash
some
of
those
things,
and
this
is
probably
future
future
generations,
where
stash
all
those
things
into
your
Settings
panel
and
that
goes
inside,
so
that
just
gives
us
room
for
the
title
and
the
content
of
the
page,
and
this
is
an
example
of
like
blue
sky
thinking,
I
think
here,
where
we
removed
the
chrome
of
the
toast
UI
editor
and
have
field
here
called
title.
And
if
we
look
at
some
of
the
toolbars
settings,
it
can
be
split
between
text,
formatting
and
objects
to
insert.
A
A
This
is
where
you
could
insert
like
this:
a
line,
break
tables,
images
or
inline
code,
so
that's
kind
of
separating
and
making
the
functionality
a
bit
more
focused
around
what
users
can
do
here,
and
you
know
once
again:
it's
like
the
panel
that
hides
other
things
like
their
layouts
with
the
table
of
contents.
There
might
be
other
layouts
that
we
could
choose
from
and
by.
A
We
can
change
it
from
here
or
there
could
be
other
attributes
in
the
future
that
we
could
add
to
this
panel
and
switching
to
markdown
returns
us
back
to
this
page
that
we
talked
about
previously
and
we
seen
so
it's
actually
something
that
can
that
doesn't
need
to
change
over
time.
He
just
evolves
in
the
parent
layout
page.
A
This
layout
also
works.
If
we
start
thinking
about.
If
we
want
to
introduce
breadcrumbs
to
these
pages
and
potentially,
if
we
do
introduce
breadcrumbs,
we
don't
need
that
return
to
site
and
just
have
more
focus
buttons
up
here
around
controlling
the
state
of
changes,
whether
we
want
to
discard
or
submit
them
rather
than
having
buttons,
I,
say:
I
submit
or
navigate
back
to
page.