「[Early Preview] New React Documentation by rachelnabors · Pull Request #3965 · reactjs/reactjs.org · GitHub」

Since announcing the start of the new React documentation effort, we’ve been busy writing the content and building a custom website designed around the learning experience. We are now ready to share this early preview of what we’ve created so far to get your feedback. This early preview is deployed at beta.reactjs.org and is in active development. Please leave any feedback in #3308. TLDR Visit the early preview of the new React Docs at beta.reactjs.org to find:  All new learning materials featuring Hooks Interactive examples and challenges “Code diagrams” that visually dissect how Hooks work Illustrations and diagrams that explain how React works New site designed around learning experience  You may encounter some broken links—pardon our dust! Some content is yet to be released! What's in the beta The beta has two major sections:  Learn React—a comprehensive, step-by-step guide to React. This section is roughly 70% complete. This content is stable and unlikely to change much beyond a few edits and fixes. Some content is still being written (notably, guides for effects, performance optimizations, and React DevTools). API Reference—detailed explanations of each API This section currently only has a few pages, so there is a lot left to write here! Have a look at the useState page to get a sense of what’s coming.  The landing page is a temporary stub and will be replaced closer to the end of the project. Similarly, the Home tab is a bit empty now—we intend to port over more things from the existing site, like Blog, after most of the remaining work is done. Known issues  No tutorials. We need to complete explanations for all core concepts and APIs before we can add tutorials. (This could be really cool to work on with the community at a later date! But not today!) Performance. When we say “beta,” we mean the site as well as the content! We still have some perf optimizations to make like code splitting at a later stage. Accessibility. While we have been mindful of accessibility during production, we’re waiting until the site is close to getting out of beta to run a comprehensive accessibility audit.  What’s next We will make an official post on the blog and put up a banner on the existing site to let visitors know where to find the new docs sometime after gathering feedback from this soft launch. Once we achieve content parity with the old site, we’ll be ready to switch over to this one and keep the old one archived at a subdomain. We'll figure out which pages to redirect to which site at that stage—for now it's too early to discuss a plan. We intend to document all the stable React APIs before we switch over. That includes classes—however, they will be described on a separate page, while most of the docs will use Hooks. Please note that:  We are not ready to kick off any official translation efforts at this time because the content is still in a state of flux. To keep the tone cohesive, we are writing the primary new content ourselves. While offers to write are much appreciated, we must regretfully decline for now!  You can help!  Read and share the docs with friends, colleagues, family! Report bugs! If you see one, please don’t hesitate to leave a comment here or send a fix to the beta folder in the main branch with the [Beta] tag in the title. Tell us what you think!  Where to leave feedback?  Leave your general feedback in a comment in #3308 or using this handy survey. Leave feedback as you read using the feedback button on the site  High-level feedback is more useful than e.g. typos since we'll be doing more editing passes on all the content (bug fixes for typos much appreciated!). We'd particularly appreciate feedback on how to organize the content (see #3965 (comment)). Special thanks Getting to this stage required a lot of effort from different people, whom we would like to thank and acknowledge. This includes:  Rachel Nabors: editing, writing, illustrating Dan Abramov: writing, curriculum design Sylwia Vargas: example code Dan Lebowitz: design Razvan Gradinar: design Maggie Appleton: diagram system (not integrated yet) Jared Palmer: site development ThisDotLabs (Dane Grant, Dustin Goodman): site development CodeSandbox (Ives van Hoorne, Alex Moldovan, Jasper De Moor, Danilo Woznica): sandbox integration Rick Hanlon: site development  We'd also like to thank countless alpha testers and community members who gave us feedback along the way. Your support and encouragement meant the world to us over this longhaul project!

Since announcing the start of the new React documentation effort, we’ve been busy writing the content and building a custom website designed around the learning experience. We are now ready to share this early preview of what we’ve created so far to get your feedback. This early preview is deployed at beta.reactjs.org and is in active development. Please leave any feedback in #3308. TLDR Visit the early preview of the new React Docs at beta.reactjs.org to find: All new learning materials featuring Hooks Interactive examples and challenges “Code diagrams” that visually dissect how Hooks work Illustrations and diagrams that explain how React works New site designed around learning experience You may encounter some broken links—pardon our dust! Some content is yet to be released! What's in the beta The beta has two major sections: Learn React—a comprehensive, step-by-step guide to React. This section is roughly 70% complete. This content is stable and unlikely to change much beyond a few edits and fixes. Some content is still being written (notably, guides for effects, performance optimizations, and React DevTools). API Reference—detailed explanations of each API This section currently only has a few pages, so there is a lot left to write here! Have a look at the useState page to get a sense of what’s coming. The landing page is a temporary stub and will be replaced closer to the end of the project. Similarly, the Home tab is a bit empty now—we intend to port over more things from the existing site, like Blog, after most of the remaining work is done. Known issues No tutorials. We need to complete explanations for all core concepts and APIs before we can add tutorials. (This could be really cool to work on with the community at a later date! But not today!) Performance. When we say “beta,” we mean the site as well as the content! We still have some perf optimizations to make like code splitting at a later stage. Accessibility. While we have been mindful of accessibility during production, we’re waiting until the site is close to getting out of beta to run a comprehensive accessibility audit. What’s next We will make an official post on the blog and put up a banner on the existing site to let visitors know where to find the new docs sometime after gathering feedback from this soft launch. Once we achieve content parity with the old site, we’ll be ready to switch over to this one and keep the old one archived at a subdomain. We'll figure out which pages to redirect to which site at that stage—for now it's too early to discuss a plan. We intend to document all the stable React APIs before we switch over. That includes classes—however, they will be described on a separate page, while most of the docs will use Hooks. Please note that: We are not ready to kick off any official translation efforts at this time because the content is still in a state of flux. To keep the tone cohesive, we are writing the primary new content ourselves. While offers to write are much appreciated, we must regretfully decline for now! You can help! Read and share the docs with friends, colleagues, family! Report bugs! If you see one, please don’t hesitate to leave a comment here or send a fix to the beta folder in the main branch with the [Beta] tag in the title. Tell us what you think! Where to leave feedback? Leave your general feedback in a comment in #3308 or using this handy survey. Leave feedback as you read using the feedback button on the site High-level feedback is more useful than e.g. typos since we'll be doing more editing passes on all the content (bug fixes for typos much appreciated!). We'd particularly appreciate feedback on how to organize the content (see #3965 (comment)). Special thanks Getting to this stage required a lot of effort from different people, whom we would like to thank and acknowledge. This includes: Rachel Nabors: editing, writing, illustrating Dan Abramov: writing, curriculum design Sylwia Vargas: example code Dan Lebowitz: design Razvan Gradinar: design Maggie Appleton: diagram system (not integrated yet) Jared Palmer: site development ThisDotLabs (Dane Grant, Dustin Goodman): site development CodeSandbox (Ives van Hoorne, Alex Moldovan, Jasper De Moor, Danilo Woznica): sandbox integration Rick Hanlon: site development We'd also like to thank countless alpha testers and community members who gave us feedback along the way. Your support and encouragement meant the world to us over this longhaul project!

github.com

Webページ

コンテンツ文字数:0 文字

見出し数(H2/H3タグ):0 個

閲覧数:90 件

2021-11-01 08:09:23

オリジナルページを開く

タグ一覧
Early
Preview
New
React
Documentation
by
rachelnabors
Pull
Request
3965
reactjs
org
GitHubSince
announcing
the
start
of
new
documentation
effort
we’ve
been
busy
writing
content
and
building
custom
website
designed
around
learning
experience
We
are
now
ready
to
share
this
early
preview
what
created
so
far
get
your
feedback
This
is
deployed
at
beta
in
active
development
Please
leave
any
3308
TLDR
Visit
Docs
find
All
materials
featuring
Hooks
Interactive
examples
challenges
Code
diagrams
that
visually
dissect
how
work
Illustrations
explain
works
site
You
may
encounter
some
broken
links
pardon
our
dust
Some
yet
be
released
What
39
The
has
two
major
sections
Learn
comprehensive
step-by-step
guide
section
roughly
70
complete
stable
unlikely
change
much
beyond
few
edits
fixes
still
being
written
notably
guides
for
effects
performance
optimizations
DevTools
API
Reference
detailed
explanations
each
currently
only
pages
there
lot
left
write
here
Have
look
useState
page
sense
what’s
coming
landing
temporary
stub
will
replaced
closer
end
project
Similarly
Home
tab
bit
empty
we
intend
port
over
more
things
from
existing
like
Blog
after
most
remaining
done
Known
issues
No
tutorials
need
all
core
concepts
APIs
before
can
add
could
really
cool
on
with
community
later
date
But
not
today
Performance
When
say
mean
as
well
have
perf
make
code
splitting
stage
Accessibility
While
mindful
accessibility
during
production
we’re
waiting
until
close
getting
out
run
audit
What’s
next
an
official
post
blog
put
up
banner
let
visitors
know
where
docs
sometime
gathering
soft
launch
Once
achieve
parity
old
we’ll
switch
one
keep
archived
subdomain
ll
figure
which
redirect
it
too
discuss
plan
document
That
includes
classes
however
they
described
separate
while
use
note
kick
off
translation
efforts
time
because
state
flux
To
tone
cohesive
primary
ourselves
offers
appreciated
must
regretfully
decline
help
Read
friends
colleagues
family
Report
bugs
If
you
see
please
don’t
hesitate
comment
or
send
fix
folder
main
branch
Beta
tag
title
Tell
us
think
Where
Leave
general
using
handy
survey
read
button
High-level
useful
than
typos
since
doing
editing
passes
bug
particularly
appreciate
organize
Special
thanks
Getting
required
different
people
whom
would
thank
acknowledge
Rachel
Nabors
illustrating
Dan
Abramov
curriculum
design
Sylwia
Vargas
example
Lebowitz
Razvan
Gradinar
Maggie
Appleton
diagram
system
integrated
Jared
Palmer
ThisDotLabs
Dane
Grant
Dustin
Goodman
CodeSandbox
Ives
van
Hoorne
Alex
Moldovan
Jasper
De
Moor
Danilo
Woznica
sandbox
integration
Rick
Hanlon
also
countless
alpha
testers
members
who
gave
along
way
Your
support
encouragement
meant
world
longhaul
Conversation
What's