Verbatim (code) blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Indented code blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Fenced code blocks . . . . . . . . . . . . . . . . . . . . 154 Running pandoc as a web server 155 Running pandoc as a Lua interpreter 157 A note on security 159 Authors 161 vi Synopsis pandoc [options] [input-file]… (TikiWiki markup) • twiki (TWiki markup) • typst (typst) • vimwiki (Vimwiki) • the path of a custom Lua reader, see Custom readers and writers below Extensions can be individually enabled or disabled by

引发哪些问题？作为站在隧道⼝的⼈类，其实是猜不透的。 2. 中国开源崛起以及开源世界分裂的趋势 随着越来越多中国开源项⽬的影响⼒不断增加、⽊兰协议的推出、开放原⼦基⾦会的成⽴， Gitee 的超⾼速增⻓，CODE China 的新发布，我们已经可以确信，2020 年是中国开源的崛 起之年。接下来阅读报告的朋友们，应该会看到很多确切的证据。 但是，另⼀个值得注意的现象，也可以从下⾯的数据⾥看出来。在 GitHub 跑出来的，是⼀项开发者必备的重要基础技能。 6.2 在线⽂档协作编辑⼯具 在线⽂档编辑⼯具中，⽯墨⽂档是⽬前中国开源社区经常使⽤的⼯具，wiki 也依然是⾮常多参 与者使⽤的协作⼯具。 6.3 编辑器 VS Code 今年仍然是最受欢迎的编辑器，紧随其后的是 vim 以及 notepad++。 6.4 版本控制⼯具 毫⽆疑问的是，Git ⼀枝独秀，具有绝对性优势。SVN、TFS、CVS ⽬前仍有不少参与 Gitlab。 【专家点评】 蒋涛：随着开源规模和商业化的快速发展，开源平台作为开源项目和开发者生态的重要基础及 支撑体系，未来将承载更多的服务和应用场景，也将发展出各自特色。2020 年新发布的 CODE China，作为独立第三方开源平台，将重点围绕 AIOT，为更多开源项目和开发者提供 运营支持和生态服务。 6.9 技术论坛 知乎和 CSDN ⽬前是最受参与者们⻘睐的两个技术论坛，其次则是

要性，更多开源贡献者投入到了文档撰写中。  Similar to last year, participation in open source continues to be primarily in the form of code and documentation, with communities and projects realizing the importance of documentation and 43%还未参与工作的学生群体占比最大，这证实了近两年我国开源文化 推广成果，能反映出开源项目的推广已下沉影响到学生群体。不论是 gitee 开源暑期活 动、中科院开源软件点亮计划以及 Google summer of code 等这些来自各个组织公司的 项目都培养了下一代参与开源贡献习惯，了解了开源文化精神和开源协作的共创模式，为 我们更好的推进开源发展能做出巨大贡献，未来可期。 Guo Yue: The most summer (Gitee), Open Source Software Lighting Program (Chinese Academy of Sciences), and Summer of Code (Google), have cultivated the habit of contributing to open source participation of the next generation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . main/groovy/ - A collection of scripts written in Groovy └── main/java/ - java source code └── test/groovy/ - A collection of scripts written in Groovy └── test/java/ - java as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

Contents: 1. Minimum viable documentation 2. Update docs with code 3. Delete dead documentation 4. Documentation is the story of your code Minimum viable documentation A small set of fresh and accurate guidelines. • Delete cruft frequently and in small batches. Update docs with code Change your documentation in the same CL as the code change. This keeps your docs fresh, and is also a good place to explain despair in engineers and laziness in team leads. They set a precedent for leaving behind messes in a code base. If your home is clean, most guests will be clean without being asked. Just like any big cleaning

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.6. Code Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . main reason for this choice is 1. all "autocompletion" mechanism and javadoc reading when writing code; 2. having a full IT language. Obviously, usage of java should be very simple for all non IT people test boundary is very clear. A Unit Test is not build to be used by a scenario test, so, if part of code could be used by Scenario Test, dedicated method should be created for that. All methods, like simple