many people say that R & D students should write documents in markdown, which is efficient, but as a front end, they have never found a use scenario for markdown? Please guide me, Daniel. Thank you.
many people say that R & D students should write documents in markdown, which is efficient, but as a front end, they have never found a use scenario for markdown? Please guide me, Daniel. Thank you.
thanks for the invitation. markdown is easy to learn.
I don't know what the scene you asked refers to. README.md on
gihtub .
for example, the input box for answering questions in codeshelper supports markdown . I write answers with markdown .
Nuggets, compendium, and other editors all support markdown syntax.
Markdown grammar description (simplified Chinese version)
you can also search some materials to learn, a little study can support many scenarios.
is to write a blog or document, similar to a text editor, except that there are some md rules to write down, whether you have learned them or not, to see if you have used them.
personally, I think it is a small skill that engineers need now, because it is not complicated to use; more importantly, it does improve the efficiency of writing documents a lot;
of course, markdown is much more efficient than word and looks more comfortable.
you can use
markdown is also very easy to learn. Most of the application scenarios are used to write blogs. As a developer, markdown is basically a necessary skill.
In the case of application scenarios, for example, some technical service companies may need to provide some external API documents, which can be written using markown, and then use webpack's markdown-loader to compile the .md files into chunk, that is, js code, so that you can write API documents without using html.
markdown syntax is very simple, you can learn ha, such as writing a blog, markdown, or github project readme is markdown grammar, the learning cost is very low, ha, not much content!
compared to html,css,js , markdown is a light drizzle.
find a document, write down the commonly used structures, and practice, like a title list picture link code block, half an hour is enough.
other things such as tables, the differences of each platform should be checked and remembered a few times.
Why bother with low learning costs and high benefits.
has nothing to do with front and rear
Markdown syntax is simple and many community editors support Git code hosting platforms, document management applications, blog systems, etc.
learn something very useful
for engineers, all the scenarios that need to use documents are the use of markdown, especially some self-use documents, using md files means that you do not need to open a separate software, just open it in the IDE/ editor. As for Word/PDF, is that the format for PM/ users / bosses?
in addition, the markdown format is easy to learn, while Word, open a software and wait more than ten seconds (the genuine Office2016 pre-installed in my notebook), and then have to figure out the format compatibility problems caused by copying and pasting online with WPS+ and the layout confusion caused by style sheet confusion. It's really much more troublesome than md.
this thing does not need to be specifically learned, just know the simple scene. Its main function is to record
which can be used to write readme or blog
you can use this thing does not need to be learned specially, just know the simple scene
same md code, task list, as follows: -sharp React-NewsWebsite website - [x] todo1 - [ ] todo2 - [x] todo3 Preview included with vscode, alt+shift+v, does not display correctly github: Why? Different compilers? So how do I display the effect...