<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Demo | Academic</title>
    <link>https://example.com/category/demo/</link>
      <atom:link href="https://example.com/category/demo/index.xml" rel="self" type="application/rss+xml" />
    <description>Demo</description>
    <generator>Wowchemy (https://wowchemy.com)</generator><language>en-us</language><lastBuildDate>Sat, 28 May 2022 00:00:00 +0000</lastBuildDate>
    <image>
      <url>https://example.com/media/icon_hu0b7a4cb9992c9ac0e91bd28ffd38dd00_9727_512x512_fill_lanczos_center_3.png</url>
      <title>Demo</title>
      <link>https://example.com/category/demo/</link>
    </image>
    
    <item>
      <title>About my previous week</title>
      <link>https://example.com/post/my-week04/</link>
      <pubDate>Sat, 28 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/my-week04/</guid>
      <description>&lt;h2 id=&#34;about-my-previous-week&#34;&gt;About My Previous Week&lt;/h2&gt;
&lt;p&gt;I spent my previous week doing labs for Operating Systems and stuudying for my English test. It was very hard. I hope I will keep doing well in studying.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Scientific Programming Languages</title>
      <link>https://example.com/post/post4/</link>
      <pubDate>Sat, 28 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/post4/</guid>
      <description>&lt;h1 id=&#34;fortran&#34;&gt;Fortran&lt;/h1&gt;
&lt;p&gt;Fortran is the language of the past in scientific computation, and one of the main languages of the present, as far as physics is concerned. Its main strengths at the moment are&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a huge body of well-debugged and working code available;&lt;/li&gt;
&lt;li&gt;a large base of experience residing in &amp;ldquo;older&amp;rdquo; physicists (pretty much all of us over the age of thirty?);&lt;/li&gt;
&lt;li&gt;ease of use.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The last point is perhaps the most important, as Fortran has a &amp;ldquo;model&amp;rdquo; of the computer which is simple enough that one does not have to be a professional (i.e., extensive training or self-education in computer science or programming) to produce a reasonable Fortran program.&lt;/p&gt;
&lt;p&gt;This is not to say that it is not possible to produce a bad Fortran program. It is quite easy, but that is true of pretty much every computer language to some degree.&lt;/p&gt;
&lt;p&gt;Fortran 90 extends fortran in several useful ways, and makes it a more modern programming language, while retaining full compatibility with Fortran-77 code. Two of the more interesting features are aggregrate data types (&amp;ldquo;structures&amp;rdquo;) and built-in operations on arrays and matrices. In my opinion, Fortran tends to lose big as projects get more complex. The support for reuse and encapsulation of code is fairly poor in Fortran, at least in Fortran-77. Fortran 90 has more support for this, but I have little experience with it. Also, most graphical-interface and visualization packages have no native Fortran support.&lt;/p&gt;
&lt;p&gt;Some Fortran 90 proponents would like to see some of the &amp;ldquo;dangerous&amp;rdquo; elements of Fortran-77 removed from the language. I think this is a bad idea. Go here to read why I think so.&lt;/p&gt;
&lt;h1 id=&#34;c-and-c&#34;&gt;C and C++&lt;/h1&gt;
&lt;p&gt;C is an interesting choice as a scientific language. It is extremely flexible and available on about every machine known to man. Also, one of the best C compilers (gcc) is available for free. Almost all visualization and user-interface packages support the C language. C is frequently taught as a first or second language in university computer-science departments.&lt;/p&gt;
&lt;p&gt;A long-standing gripe about C is that it produces slower code than does the equivalent Fortran. Nowadays, computer speeds are doubling every year or so, and C compilers don&amp;rsquo;t seem to be doing that bad compared to Fortran anymore (typical C code runs between 50 and 100% as fast as the equivalent Fortran, depending on the application). In light of this, I think it&amp;rsquo;s hard to discard C on the basis of the speed of the code it produces.&lt;/p&gt;
&lt;p&gt;Nevertheless, I don&amp;rsquo;t think it&amp;rsquo;s a good scientific programming language. The C language is fairly close to the hardware, and it is quite easy to make big mistakes in coding an application. These mistakes often don&amp;rsquo;t display themselves in small test cases, since they involve memory-management issues and the like. Also, programming large applications in C requires some degree of professionalism, meaning a fairly deep grasp of the language. As such, it is a bad language for mainstream scientific programming; typically only the creator of a program, or people with real expertise in computer programming, will be able to understand a large C application unless it is very carefully written.&lt;/p&gt;
&lt;p&gt;I believe these comments also apply to C++ coding. The concerns about readability and professionalism apply perhaps even more strongly here than for &amp;ldquo;just C&amp;rdquo;. C++ has the advantage of being the most-popular object-oriented language, but it is also recognized as being a fairly cryptic one. Again, a certain degree of professionalism is necessary to program a C++ application which is understandable to others. Packages which automatically generate C++ code from user-specified pseudocode help alleviate the problem, but then we are faced with asking all users to use the same C++ generator, which is another problem of the same magnitude.&lt;/p&gt;
&lt;p&gt;The above two are the &amp;ldquo;traditional&amp;rdquo; choices. I now turn to newer languages which are less well known in the scientific community.&lt;/p&gt;
&lt;h1 id=&#34;python&#34;&gt;Python&lt;/h1&gt;
&lt;p&gt;Python is an object-oriented, extensible, interpreted language. It runs on essentially all Unix systems, as well as on DOS/Windows platforms and on the Mac. It is free and comes with complete source code. It is very easy to begin using Python &amp;mdash; at a simple level, it resembles Basic and can be used interactively in the same way as Basic. However, it supports object methods and &amp;ldquo;scales&amp;rdquo; nicely. Scaling indicates the relative difficulty of writing small vs. large applications. The object facilities help and encourage one to write an application in small pieces. These small pieces can be put together to make the big program, and the small pieces can also be used in other applications.&lt;/p&gt;
&lt;p&gt;Another advantage of Python is its extensibility. One can write an object library in C, C++, or native Python, which can then either be dynamically or statically linked with the main Python system and used in Python programs. One can use this to make a programmable application, such as a data-plotting package. One would add a package to the interpreter which contained commands to set up your plots and to actually plot the data. This Python+graphics interpreter can be given a different name, such as &amp;ldquo;pygraph&amp;rdquo;, and invoked as a command. The interpreter will process the graphics commands and perform them. However, at the same time you can use any other valid Python command as a command to this graphics program! Thus one graphics input file for this program could first compute the result and then manipulate and plot it.&lt;/p&gt;
&lt;p&gt;The leap from this to having Python+package systems such as data-analysis programs, or experiment-control programs, is fairly obvious. This can also solve to some extent the above-mentioned dilemma about the use of C++. A professional programmer can produce a well-defined library package with a well-defined interface in C++, and this can be included into the Python programs for use. As Python is quite readable in much the same was as is Fortran, a &amp;ldquo;normal person&amp;rdquo; (i.e. someone who is not a professional programmer) can use this library in his programs. Both the professionals, who want the power and efficiency of C or C++, as well as the group who must use the result and be able to read and understand the program, can be happy.&lt;/p&gt;
&lt;p&gt;My experience with Python started when I used it simply as an interactive calculator application &amp;mdash; I had found the standard Unix calculator &amp;ldquo;bc&amp;rdquo; lacking. At some point, I programmed a four-vector object package in Python and used it to write some nuclear-reaction kinematics computations which I needed. I later in turn used both the four-vector and kinematics modules in a large application used to predict counting rates for a large nuclear-physics experiment. I have since then also written a multiparameter batch data-analysis facility in Python.&lt;/p&gt;
&lt;p&gt;Several graphical-interface tools exist for Python, and a graphical-visualization package is now in beta test. A Numerical Python extension (a C package as described above in the extensions section) also exists which has built-in support for whole-array and matrix operations (which run at the speed of compiled C code rather than at the speed of interpreted Python.)&lt;/p&gt;
&lt;p&gt;To see what Python can do with this numerical-computing package, check out this link. It will also give you a feel for what Python looks like, and allow you to assess its readability. Also check out the Python Tutorial on the Python Web Page link below (sublink &amp;ldquo;The Full Scoop on Python Documentation.&amp;rdquo;)&lt;/p&gt;
&lt;p&gt;An article on Numerical Programming in Python appears in the May/June 1996 issue of Computers in Physics. More Python information can be found on the newsgroup comp.lang.python, or on the Python Web Page. Of particular interest is the page on contributed Python software, which describes add-on packages available for Python. These are extensions in the vein mentioned above, which add new functionality to the core language.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>About my previous week</title>
      <link>https://example.com/post/my-week03/</link>
      <pubDate>Fri, 20 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/my-week03/</guid>
      <description>&lt;h2 id=&#34;about-my-previous-week&#34;&gt;About My Previous Week&lt;/h2&gt;
&lt;p&gt;I spent my previous week doing labs for Operating Systems and for Programming Technologies. It was very hard. I hope I will keep doing well in studying.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Оформление отчета</title>
      <link>https://example.com/post/post3/</link>
      <pubDate>Fri, 20 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/post3/</guid>
      <description>&lt;h2 id=&#34;требования&#34;&gt;Требования&lt;/h2&gt;
&lt;p&gt;К основным требованиям по оформлению отчета по практике по ГОСТу 2022 года относят:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Размер и тип шрифта: обычно это 14 или 12 кегль, тип шрифта Times New Roman, подчеркивание, использование жирного шрифта не рекомендуется&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Отступы страницы: оформление отчета по практике имеет свои требования ГОСТа, которые нужно обязательно учитывать при написании отчета.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Левый отступ – 3 см,
Правый  - 2 см,
Сверху и снизу – 2 см.
Абзацный отступ – 1,25 см.&lt;/p&gt;
&lt;ol start=&#34;3&#34;&gt;
&lt;li&gt;
&lt;p&gt;Объем текста: обычно объем отчета по практике составляет 25-30 листов, однако, в отдельных случаях по согласованию  с преподавателем.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Обязательные элементы: обязательным требованием оформления отчета является наличие в тексте сносок и цитат (внутритекстовых или постраничных), нумерации страниц, оформления заголовков.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h1 id=&#34;правильное-оформление&#34;&gt;Правильное оформление&lt;/h1&gt;
&lt;p&gt;Для того, чтобы разобраться, как правильно оформить отчет по практике по ГОСТу 2022 года, нужно напомнить, из каких элементов он состоит. Эти компоненты очень важны при написании, а значит нужно отнестись к ним очень основательно. Отсутствие даже одного элемента может нарушить всю целостность работы.&lt;/p&gt;
&lt;p&gt;Тут должны быть такие компоненты как: титульный лист, задание руководителя практики, план и дневник практики, отзыв или характеристика от руководителя практики введение, основное содержание, заключение, список литературы и приложения.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Титульный лист.&lt;/em&gt; Можно сказать, что это лицо вашей работы, титульник должен включать в себя информацию о  наименовании учреждения, виде практике, основные данные о практиканте и преподавателе.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Задание практики.&lt;/em&gt; Дается студенту преподавателем для того, чтобы он имел представление, в чем заключается его задача и какова главная цель прохождения практики.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;План и дневник практики.&lt;/em&gt; В план вносятся мероприятия, которые должны быть проведены во время практики. Дневник является настольной книгой практиканта, куда записываются все проведенные события, все полученные знания и опыт.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Отзыв(характеристика) на студента.&lt;/em&gt; Небольшой текст, написанный руководителем практики, который характеризует практиканта, описывает его личные качества,  профессиональные особенности, трудовые навыки.&lt;/p&gt;
&lt;p&gt;Введение отчета по практике – описывает основные цели, задачи прохождения практики, ее актуальность, выявляет проблему.&lt;/p&gt;
&lt;p&gt;Основная часть может быть только теоретической, если речь идет об учебной практике, или состоять из 2-х частей – теории и практической части (отчет по производственной практике).&lt;/p&gt;
&lt;p&gt;Заключение отчета по практике. Подводит итог всей работе, описывает практические результаты прохождения практики.&lt;/p&gt;
&lt;p&gt;Итак, мы разобрали в целом, как правильно оформить отчет по практике по ГОСТу 2022 года.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>About my previous week</title>
      <link>https://example.com/post/my-week02/</link>
      <pubDate>Thu, 12 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/my-week02/</guid>
      <description>&lt;h2 id=&#34;about-my-previous-week&#34;&gt;About My Previous Week&lt;/h2&gt;
&lt;p&gt;I spent my previous week doing labs for Operating Systems and for Programming Technologies.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Markdown</title>
      <link>https://example.com/post/markdown/</link>
      <pubDate>Thu, 12 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/markdown/</guid>
      <description>&lt;h2 id=&#34;markdown&#34;&gt;Markdown&lt;/h2&gt;
&lt;p&gt;Angle brackets&lt;/p&gt;
&lt;p&gt;If you use angle brackets in text in your file (for example, to denote a placeholder), you need to manually encode the angle brackets. Otherwise, Markdown thinks that they&amp;rsquo;re intended to be an HTML tag.&lt;/p&gt;
&lt;p&gt;For example, encode &lt;script name&gt; as &amp;lt;script name&amp;gt; or &amp;lt;script name&amp;gt;.&lt;/p&gt;
&lt;p&gt;Angle brackets don&amp;rsquo;t have to be escaped in text formatted as inline code or in code blocks.
Apostrophes and quotation marks&lt;/p&gt;
&lt;p&gt;If you copy from Word into a Markdown editor, the text might contain &amp;ldquo;smart&amp;rdquo; (curly) apostrophes or quotation marks. These need to be encoded or changed to basic apostrophes or quotation marks. Otherwise, you end up with things like this when the file is published: Itâ€™s&lt;/p&gt;
&lt;p&gt;Here are the encodings for the &amp;ldquo;smart&amp;rdquo; versions of these punctuation marks:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Left (opening) quotation mark: &amp;amp;#8220;
Right (closing) quotation mark: &amp;amp;#8221;
Right (closing) single quotation mark or apostrophe: &amp;amp;#8217;
Left (opening) single quotation mark (rarely used): &amp;amp;#8216;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Tip&lt;/p&gt;
&lt;p&gt;To avoid &amp;ldquo;smart&amp;rdquo; characters in your Markdown files, rely on the Docs Authoring Pack&amp;rsquo;s smart quote replacement feature. For more information, see smart quote replacement.
Blockquotes&lt;/p&gt;
&lt;p&gt;Blockquotes are created using the &amp;gt; character:
Markdown&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This is a blockquote. It is usually rendered indented and with a different background color.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The preceding example renders as follows:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;This is a blockquote. It is usually rendered indented and with a different background color.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Bold and italic text&lt;/p&gt;
&lt;p&gt;To format text as bold, enclose it in two asterisks:
Markdown&lt;/p&gt;
&lt;p&gt;This text is &lt;strong&gt;bold&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;To format text as italic, enclose it in a single asterisk:
Markdown&lt;/p&gt;
&lt;p&gt;This text is &lt;em&gt;italic&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;To format text as both bold and italic, enclose it in three asterisks:
Markdown&lt;/p&gt;
&lt;p&gt;This text is both &lt;em&gt;&lt;strong&gt;bold and italic&lt;/strong&gt;&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;For guidance on when to use bold and italic text, see text formatting guidelines.
Code snippets&lt;/p&gt;
&lt;p&gt;Docs Markdown supports the placement of code snippets both inline in a sentence and as a separate &amp;ldquo;fenced&amp;rdquo; block between sentences. For more information, see How to add code to docs.
Columns&lt;/p&gt;
&lt;p&gt;The columns Markdown extension gives Docs authors the ability to add column-based content layouts that are more flexible and powerful than basic Markdown tables, which are only suited for true tabular data. You can add up to four columns, and use the optional span attribute to merge two or more columns.&lt;/p&gt;
&lt;p&gt;While the columns extension still works, we no longer recommend it for creating custom layouts. We&amp;rsquo;ve found that many custom column layouts have accessibility issues or otherwise violate Docs style guidelines. Don&amp;rsquo;t create custom layouts. Use standard Docs features.&lt;/p&gt;
&lt;p&gt;The syntax for columns is as follows:
Markdown&lt;/p&gt;
&lt;p&gt;:::row:::
:::column span=&amp;quot;&amp;quot;:::
Content&amp;hellip;
:::column-end:::
:::column span=&amp;quot;&amp;quot;:::
More content&amp;hellip;
:::column-end:::
:::row-end:::&lt;/p&gt;
&lt;p&gt;Columns should only contain basic Markdown, including images. Headings, tables, tabs, and other complex structures shouldn&amp;rsquo;t be included. A row can&amp;rsquo;t have any content outside of column.&lt;/p&gt;
&lt;p&gt;For example, the following Markdown creates one column that spans two column widths, and one standard (no span) column:
Markdown&lt;/p&gt;
&lt;p&gt;:::row:::
:::column span=&amp;ldquo;2&amp;rdquo;:::
&lt;strong&gt;This is a 2-span column with lots of text.&lt;/strong&gt;&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;  Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec vestibulum mollis nunc
  ornare commodo. Nullam ac metus imperdiet, rutrum justo vel, vulputate leo. Donec
  rutrum non eros eget consectetur.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;:::column-end:::
:::column span=&amp;quot;&amp;quot;:::
&lt;strong&gt;This is a single-span column with an image in it.&lt;/strong&gt;&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;  ![Doc.U.Ment](media/markdown-reference/document.png)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;:::column-end:::
:::row-end:::&lt;/p&gt;
&lt;p&gt;This renders as follows:&lt;/p&gt;
&lt;p&gt;This is a 2-span column with lots of text.&lt;/p&gt;
&lt;p&gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec vestibulum mollis nunc ornare commodo. Nullam ac metus imperdiet, rutrum justo vel, vulputate leo. Donec rutrum non eros eget consectetur.&lt;/p&gt;
&lt;p&gt;Comments&lt;/p&gt;
&lt;p&gt;Docs supports HTML comments if you must comment out sections of your article:&lt;/p&gt;
&lt;!--- Here&#39;s my comment ---&gt;
&lt;p&gt;Warning&lt;/p&gt;
&lt;p&gt;Do not put private or sensitive information in HTML comments. Docs carries HTML comments through to the published HTML that goes public. While HTML comments are invisible to the reader&amp;rsquo;s eye, they are exposed in the HTML underneath.
Headings&lt;/p&gt;
&lt;p&gt;Docs supports six levels of Markdown headings:
Markdown&lt;/p&gt;
&lt;h1 id=&#34;this-is-a-first-level-heading-h1&#34;&gt;This is a first level heading (H1)&lt;/h1&gt;
&lt;h2 id=&#34;this-is-a-second-level-heading-h2&#34;&gt;This is a second level heading (H2)&lt;/h2&gt;
&lt;p&gt;&amp;hellip;&lt;/p&gt;
&lt;h6 id=&#34;this-is-a-sixth-level-heading-h6&#34;&gt;This is a sixth level heading (H6)&lt;/h6&gt;
&lt;pre&gt;&lt;code&gt;There must be a space between the last # and heading text.
Each Markdown file must have one and only one H1 heading.
The H1 heading must be the first content in the file after the YML metadata block.
H2 headings automatically appear in the right-hand navigating menu of the published file. Lower-level headings don&#39;t appear, so use H2s strategically to help readers navigate your content.
HTML headings, such as &amp;lt;h1&amp;gt;, aren&#39;t recommended, and in some cases will cause build warnings.
You can link to individual headings in a file via bookmark links.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;HTML&lt;/p&gt;
&lt;p&gt;Although Markdown supports inline HTML, HTML isn&amp;rsquo;t recommended for publishing to Docs, and except for a limited list of values will cause build errors or warnings.
Images&lt;/p&gt;
&lt;p&gt;The following file types are supported by default for images:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;.jpg
.png
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;To support other image types, such as .gif, you must add them as resources in docfx.json:
Markdown&lt;/p&gt;
&lt;p&gt;&amp;ldquo;resource&amp;rdquo;: [
{
&amp;ldquo;files&amp;rdquo; : [
&amp;ldquo;&lt;strong&gt;/*.png&amp;rdquo;,
&amp;ldquo;&lt;/strong&gt;/&lt;em&gt;.jpg,
&amp;ldquo;**/&lt;/em&gt;.gif&amp;rdquo;
],&lt;/p&gt;
&lt;p&gt;Standard conceptual images (default Markdown)&lt;/p&gt;
&lt;p&gt;The basic Markdown syntax to embed an image is:
Markdown&lt;/p&gt;
&lt;p&gt;















&lt;figure  &gt;
  &lt;div class=&#34;d-flex justify-content-center&#34;&gt;
    &lt;div class=&#34;w-100&#34; &gt;&lt;img src=&#34;folderPath&#34; alt=&#34;&amp;lt;alt text&amp;gt;&#34; loading=&#34;lazy&#34; data-zoomable /&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;Example:
















&lt;figure  &gt;
  &lt;div class=&#34;d-flex justify-content-center&#34;&gt;
    &lt;div class=&#34;w-100&#34; &gt;&lt;img src=&#34;../images/Introduction.png&#34; alt=&#34;alt text for image&#34; loading=&#34;lazy&#34; data-zoomable /&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;Where &lt;alt text&gt; is a brief description of the image and &lt;folder path&gt; is a relative path to the image. Alternate text is required for screen readers for the visually impaired. It&amp;rsquo;s also useful if there&amp;rsquo;s a site bug where the image can&amp;rsquo;t render.&lt;/p&gt;
&lt;p&gt;Underscores in alt text aren&amp;rsquo;t rendered properly unless you escape them by prefixing them with a backslash (_). However, don&amp;rsquo;t copy file names for use as alt text. For example, instead of this:
Markdown&lt;/p&gt;
&lt;p&gt;















&lt;figure  &gt;
  &lt;div class=&#34;d-flex justify-content-center&#34;&gt;
    &lt;div class=&#34;w-100&#34; &gt;&lt;img src=&#34;./media/bogusfilename/ADextension_2FA_Configure_Step4.PNG&#34; alt=&#34;ADextension_2FA_Configure_Step4&#34; loading=&#34;lazy&#34; data-zoomable /&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;Write this:
Markdown&lt;/p&gt;
&lt;p&gt;















&lt;figure  &gt;
  &lt;div class=&#34;d-flex justify-content-center&#34;&gt;
    &lt;div class=&#34;w-100&#34; &gt;&lt;img src=&#34;./media/bogusfilename/ADextension_2FA_Configure_Step4.PNG&#34; alt=&#34;Active Directory extension for two-factor authentication, step 4: Configure&#34; loading=&#34;lazy&#34; data-zoomable /&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;Standard conceptual images (Docs Markdown)&lt;/p&gt;
&lt;p&gt;The Docs custom :::image::: extension supports standard images, complex images, and icons.&lt;/p&gt;
&lt;p&gt;For standard images, the older Markdown syntax will still work, but the new extension is recommended because it supports more powerful functionality, such as specifying a localization scope that&amp;rsquo;s different from the parent topic. Other advanced functionality, such as selecting from the shared image gallery instead of specifying a local image, will be available in the future. The new syntax is as follows:
Markdown&lt;/p&gt;
&lt;p&gt;:::image type=&amp;ldquo;content&amp;rdquo; source=&amp;quot;&lt;folderPath&gt;&amp;rdquo; alt-text=&amp;quot;&lt;alt text&gt;&amp;quot;:::&lt;/p&gt;
&lt;p&gt;If type=&amp;ldquo;content&amp;rdquo; (the default), both source and alt-text are required.
Complex images with long descriptions&lt;/p&gt;
&lt;p&gt;You can also use this extension to add an image with a long description that is read by screen readers but not rendered visually on the published page. Long descriptions are an accessibility requirement for complex images, such as graphs. The syntax is the following:
Markdown&lt;/p&gt;
&lt;p&gt;:::image type=&amp;ldquo;complex&amp;rdquo; source=&amp;quot;&lt;folderPath&gt;&amp;quot; alt-text=&amp;quot;&lt;alt text&gt;&amp;quot;:::
&lt;long description here&gt;
:::image-end:::&lt;/p&gt;
&lt;p&gt;If type=&amp;ldquo;complex&amp;rdquo;, source, alt-text, a long description, and the :::image-end::: tag are all required.&lt;/p&gt;
&lt;p&gt;When your changes are in preview or published, you can check whether the long description exists by right-clicking on the image and selecting Inspect (when using Microsoft Edge browser, although other browsers have similar features). This action brings you to the image source in the HTML code, underneath which you&amp;rsquo;ll find a visually-hidden class. Expand the dropdown on this class, and you&amp;rsquo;ll find your long description.&lt;/p&gt;
&lt;p&gt;Automatic borders&lt;/p&gt;
&lt;p&gt;The :::image::: extension also supports the border property, which automatically adds a 1-pixel gray border around your image. The border property is true by default for content and complex images, so you&amp;rsquo;ll get the border automatically unless you explicitly add the property with a value of false. The border property is false by default for icon images.&lt;/p&gt;
&lt;p&gt;The border property is the recommended way to add a border. Don&amp;rsquo;t create your own borders manually.
Specifying loc-scope&lt;/p&gt;
&lt;p&gt;Sometimes the localization scope for an image is different from that of the article or module that contains it. This can cause a bad global experience: for example, if a screenshot of a product is accidentally localized into a language the product isn&amp;rsquo;t available in. To prevent this, you can specify the optional loc-scope attribute in images of types content and complex, and is required for screenshots that show a product with a different localization scope than the article or module that contains it.
Icons&lt;/p&gt;
&lt;p&gt;The image extension supports icons, which are decorative images and should not have alt text. The syntax for icons is:
Markdown&lt;/p&gt;
&lt;p&gt;:::image type=&amp;ldquo;icon&amp;rdquo; source=&amp;quot;&lt;folderPath&gt;&amp;quot;:::&lt;/p&gt;
&lt;p&gt;If type=&amp;ldquo;icon&amp;rdquo;, source should be specified but alt-text shouldn&amp;rsquo;t be.&lt;/p&gt;
&lt;p&gt;The border property is false by default for icons. If your decorative image requires the standard image border, explicitly add border=&amp;ldquo;true&amp;rdquo; to the :::image::: tag.
Included Markdown files&lt;/p&gt;
&lt;p&gt;Where markdown files need to be repeated in multiple articles, you can use an include file. The includes feature instructs Docs to replace the reference with the contents of the include file at build time. You can use includes in the following ways:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Inline: Reuse a common text snippet inline with within a sentence.
Block: Reuse an entire Markdown file as a block, nested within a section of an article.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;An inline or block include file is a Markdown (.md) file. It can contain any valid Markdown. Include files are typically located in a common includes subdirectory, in the root of the repository. When the article is published, the included file is seamlessly integrated into it.
Includes syntax&lt;/p&gt;
&lt;p&gt;Block include is on its own line:
Markdown&lt;/p&gt;
&lt;p&gt;[!INCLUDE &lt;a href=&#34;filepath&#34;&gt;&lt;title&gt;&lt;/a&gt;]&lt;/p&gt;
&lt;p&gt;Inline include is within a line:
Markdown&lt;/p&gt;
&lt;p&gt;Text before [!INCLUDE &lt;a href=&#34;filepath&#34;&gt;&lt;title&gt;&lt;/a&gt;] and after.&lt;/p&gt;
&lt;p&gt;Where &lt;title&gt; is the name of the file and &lt;filepath&gt; is the relative path to the file. INCLUDE must be capitalized and there must be a space before the &lt;title&gt;.&lt;/p&gt;
&lt;p&gt;Here are requirements and considerations for include files:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Use block includes for significant amounts of content--a paragraph or two, a shared procedure, or a shared section. Don&#39;t use them for anything smaller than a sentence.
Includes won&#39;t be rendered in the GitHub-rendered view of your article because they rely on Docs extensions. They&#39;ll be rendered only after publication.
Write all the text in an include file in complete sentences or phrases that don&#39;t depend on preceding or following text in the article that references the include. Ignoring this guidance creates an untranslatable string in the article.
Don&#39;t embed include files within other include files.
/Includes folders are excluded from build. Therefore, images stored in /includes folders and referenced in included files won&#39;t be displayed in published content. Store images in a /media folder outside the /includes folder.
As with regular articles, don&#39;t share media between include files. Use a separate file with a unique name for each include and article. Store the media file in the media folder that&#39;s associated with the include.
Don&#39;t use an include as the only content of an article. Includes are meant to be supplemental to the content in the rest of the article.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Indentation&lt;/p&gt;
&lt;p&gt;In Markdown, spaces before the first character of a line determine the line&amp;rsquo;s alignment relative to the preceding lines. Indentation especially influences numbered and bulleted lists to render multiple levels of nesting in a hierarchical or outline format.&lt;/p&gt;
&lt;p&gt;To indent text to align with a preceding paragraph or an item in a numbered or bulleted list, use spaces.&lt;/p&gt;
&lt;p&gt;The following two examples show how indented paragraphs render based on their relationship to other paragraphs.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;This is a numbered list example (one space after the period before the letter T).
This sentence is indented three spaces.
This code block is indented three spaces.&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;This is a bulleted list example (one space after the bullet before the letter T).
This sentence is indented two spaces.
&lt;blockquote&gt;
&lt;p&gt;[!TIP]
This tip is indented two spaces.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;This is a second-level bullet (indented two spaces, with one space after the bullet before the letter T).
This sentence is indented four spaces.
&lt;blockquote&gt;
&lt;p&gt;This quote block is indented four spaces.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The example above renders as:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;This is a numbered list example (one space after the period before the letter T).

This sentence is indented three spaces.

This code block is indented three spaces.

This is a bulleted list example (one space after the bullet before the letter T).

This sentence is indented two spaces.

Tip

This tip is indented two spaces.

    This is a second-level bullet (indented two spaces, with one space after the bullet before the letter T).

    This sentence is indented four spaces.

        This quote block is indented four spaces.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Links&lt;/p&gt;
&lt;p&gt;For information on syntax for links, see Use links in documentation.
Lists (Numbered, Bulleted, Checklist)
Numbered list&lt;/p&gt;
&lt;p&gt;To create a numbered list, you can use all 1s. The numbers are rendered in ascending order as a sequential list when published. For increased source readability, you can increment your lists manually.&lt;/p&gt;
&lt;p&gt;Don&amp;rsquo;t use letters in lists, including nested lists. They don&amp;rsquo;t render correctly when published to Docs. Nested lists using numbers will render as lowercase letters when published. For example:
Markdown&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;This is&lt;/li&gt;
&lt;li&gt;a parent numbered list
&lt;ol&gt;
&lt;li&gt;and this is&lt;/li&gt;
&lt;li&gt;a nested numbered list&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;(fin)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This renders as follows:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;This is
a parent numbered list
    and this is
    a nested numbered list
(fin)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Bulleted list&lt;/p&gt;
&lt;p&gt;To create a bulleted list, use - or * followed by a space at the beginning of each line:
Markdown&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;This is&lt;/li&gt;
&lt;li&gt;a parent bulleted list
&lt;ul&gt;
&lt;li&gt;and this is&lt;/li&gt;
&lt;li&gt;a nested bulleted list&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;All done!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This renders as follows:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;This is
a parent bulleted list
    and this is
    a nested bulleted list
All done!
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Whichever syntax you use, - or *, use it consistently within an article.
Checklist&lt;/p&gt;
&lt;p&gt;Checklists are available for use on Docs via a custom Markdown extension:
Markdown&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[!div class=&amp;ldquo;checklist&amp;rdquo;]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;List item 1&lt;/li&gt;
&lt;li&gt;List item 2&lt;/li&gt;
&lt;li&gt;List item 3&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;This example renders on Docs like this:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;List item 1
List item 2
List item 3
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Use checklists at the beginning or end of an article to summarize &amp;ldquo;What will you learn&amp;rdquo; or &amp;ldquo;What have you learned&amp;rdquo; content. Do not add random checklists throughout your articles.
Next step action&lt;/p&gt;
&lt;p&gt;You can use a custom extension to add a next step action button to Docs pages.&lt;/p&gt;
&lt;p&gt;The syntax is as follows:
markdown&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[!div class=&amp;ldquo;nextstepaction&amp;rdquo;]
[button text](link to topic)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;For example:
Markdown&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[!div class=&amp;ldquo;nextstepaction&amp;rdquo;]
&lt;a href=&#34;code-in-docs.md&#34;&gt;Learn about adding code to articles&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This renders as follows:&lt;/p&gt;
&lt;p&gt;You can use any supported link in a next step action, including a Markdown link to another web page. In most cases, the next action link will be a relative link to another file in the same docset.
Non-localized strings&lt;/p&gt;
&lt;p&gt;You can use the custom no-loc Markdown extension to identify strings of content that you would like the localization process to ignore.&lt;/p&gt;
&lt;p&gt;All strings called out will be case-sensitive; that is, the string must match exactly to be ignored for localization.&lt;/p&gt;
&lt;p&gt;To mark an individual string as non-localizable, use this syntax:
markdown&lt;/p&gt;
&lt;p&gt;:::no-loc text=&amp;ldquo;String&amp;rdquo;:::&lt;/p&gt;
&lt;p&gt;For example, in the following, only the single instance of Document will be ignored during the localization process:
Markdown&lt;/p&gt;
&lt;h1 id=&#34;heading-1-of-the-document&#34;&gt;Heading 1 of the Document&lt;/h1&gt;
&lt;p&gt;Markdown content within the :::no-loc text=&amp;ldquo;Document&amp;rdquo;:::.  The are multiple instances of Document, document, and documents.&lt;/p&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;Use \ to escape special characters:
markdown&lt;/p&gt;
&lt;p&gt;Lorem :::no-loc text=&amp;ldquo;Find a &amp;quot;Quotation&amp;quot;&amp;rdquo;::: Ipsum.&lt;/p&gt;
&lt;p&gt;You can also use metadata in the YAML header to mark all instances of a string within the current Markdown file as non-localizable:
yml&lt;/p&gt;
&lt;p&gt;author: cillroy
no-loc: [Global, Strings, to be, Ignored]&lt;/p&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;The no-loc metadata is not supported as global metadata in docfx.json file. The localization pipeline doesn&amp;rsquo;t read the docfx.json file, so the no-loc metadata must be added into each individual source file.&lt;/p&gt;
&lt;p&gt;In the following example, both in the metadata title and the Markdown header the word Document will be ignored during the localization process.&lt;/p&gt;
&lt;p&gt;In the metadata description and the Markdown main content the word document is localized, because it does not start with a capital D.
Markdown&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;no-loc-title-document&#34;&gt;title: Title of the Document
author: author-name
description: Description for the document
no-loc: [Title, Document]&lt;/h2&gt;
&lt;h1 id=&#34;heading-1-of-the-document-1&#34;&gt;Heading 1 of the Document&lt;/h1&gt;
&lt;p&gt;Markdown content within the document.&lt;/p&gt;
&lt;p&gt;Selectors&lt;/p&gt;
&lt;p&gt;Selectors are UI elements that let the user switch between multiple flavors of the same article. They are used in some doc sets to address differences in implementation across technologies or platforms. Selectors are typically most applicable to our mobile platform content for developers.&lt;/p&gt;
&lt;p&gt;Because the same selector Markdown goes in each article file that uses the selector, we recommend placing the selector for your article in an include file. Then you can reference that include file in all your article files that use the same selector.&lt;/p&gt;
&lt;p&gt;There are two types of selectors: a single selector and a multi-selector.
Single selector
Markdown&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[!div class=&amp;ldquo;op_single_selector&amp;rdquo;]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../articles/notification-hubs-windows-store-dotnet-get-started/&#34;&gt;Universal Windows&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../articles/notification-hubs-windows-phone-get-started/&#34;&gt;Windows Phone&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../articles/notification-hubs-ios-get-started/&#34;&gt;iOS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../articles/notification-hubs-android-get-started/&#34;&gt;Android&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../articles/notification-hubs-kindle-get-started/&#34;&gt;Kindle&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../articles/notification-hubs-baidu-get-started/&#34;&gt;Baidu&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../articles/partner-xamarin-notification-hubs-ios-get-started/&#34;&gt;Xamarin.iOS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../articles/partner-xamarin-notification-hubs-android-get-started/&#34;&gt;Xamarin.Android&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;&amp;hellip; will be rendered like this:
Multi-selector
Markdown&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[!div class=&amp;ldquo;op_multi_selector&amp;rdquo; title1=&amp;ldquo;Platform&amp;rdquo; title2=&amp;ldquo;Backend&amp;rdquo;]&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-dotnet-backend-ios-get-started-push.md&#34;&gt;(iOS | .NET)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-javascript-backend-ios-get-started-push.md&#34;&gt;(iOS | JavaScript)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-dotnet-backend-windows-universal-dotnet-get-started-push.md&#34;&gt;(Windows universal C# | .NET)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-javascript-backend-windows-universal-dotnet-get-started-push.md&#34;&gt;(Windows universal C# | Javascript)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-dotnet-backend-windows-phone-get-started-push.md&#34;&gt;(Windows Phone | .NET)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-javascript-backend-windows-phone-get-started-push.md&#34;&gt;(Windows Phone | Javascript)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-dotnet-backend-android-get-started-push.md&#34;&gt;(Android | .NET)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./mobile-services-javascript-backend-android-get-started-push.md&#34;&gt;(Android | Javascript)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./partner-xamarin-mobile-services-ios-get-started-push.md&#34;&gt;(Xamarin iOS | Javascript)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;./partner-xamarin-mobile-services-android-get-started-push.md&#34;&gt;(Xamarin Android | Javascript)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;&amp;hellip; will be rendered like this:
Platform
Backend
Subscript and superscript&lt;/p&gt;
&lt;p&gt;You should only use subscript or superscript when necessary for technical accuracy, such as when writing about mathematical formulas. Don&amp;rsquo;t use them for non-standard styles, such as footnotes.&lt;/p&gt;
&lt;p&gt;For both subscript and superscript, use HTML:
HTML&lt;/p&gt;
&lt;p&gt;Hello &lt;sub&gt;This is subscript!&lt;/sub&gt;&lt;/p&gt;
&lt;p&gt;This renders as follows:&lt;/p&gt;
&lt;p&gt;Hello This is subscript!
HTML&lt;/p&gt;
&lt;p&gt;Goodbye &lt;sup&gt;This is superscript!&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;This renders as follows:&lt;/p&gt;
&lt;p&gt;Goodbye This is superscript!
Tables&lt;/p&gt;
&lt;p&gt;The simplest way to create a table in Markdown is to use pipes and lines. To create a standard table with a header, follow the first line with dashed line:
Markdown&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;This is&lt;/th&gt;
&lt;th&gt;a simple&lt;/th&gt;
&lt;th&gt;table header&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;table&lt;/td&gt;
&lt;td&gt;data&lt;/td&gt;
&lt;td&gt;here&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;it doesn&amp;rsquo;t&lt;/td&gt;
&lt;td&gt;actually&lt;/td&gt;
&lt;td&gt;have to line up nicely!&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This renders as follows:
This is 	a simple 	table header
table 	data 	here
it doesn&amp;rsquo;t 	actually 	have to line up nicely!&lt;/p&gt;
&lt;p&gt;You can align the columns by using colons:
Markdown&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style=&#34;text-align:left&#34;&gt;Fun&lt;/th&gt;
&lt;th style=&#34;text-align:right&#34;&gt;With&lt;/th&gt;
&lt;th style=&#34;text-align:center&#34;&gt;Tables&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;left-aligned column&lt;/td&gt;
&lt;td style=&#34;text-align:right&#34;&gt;right-aligned column&lt;/td&gt;
&lt;td style=&#34;text-align:center&#34;&gt;centered column&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;$100&lt;/td&gt;
&lt;td style=&#34;text-align:right&#34;&gt;$100&lt;/td&gt;
&lt;td style=&#34;text-align:center&#34;&gt;$100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;$10&lt;/td&gt;
&lt;td style=&#34;text-align:right&#34;&gt;$10&lt;/td&gt;
&lt;td style=&#34;text-align:center&#34;&gt;$10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&#34;text-align:left&#34;&gt;$1&lt;/td&gt;
&lt;td style=&#34;text-align:right&#34;&gt;$1&lt;/td&gt;
&lt;td style=&#34;text-align:center&#34;&gt;$1&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Line breaks within words in any table cell&lt;/p&gt;
&lt;p&gt;Long words in a Markdown table might make the table expand to the right navigation and become unreadable. You can solve that by allowing Docs rendering to automatically insert line breaks within words when needed. Just wrap up the table with the custom class [!div class=&amp;ldquo;mx-tdBreakAll&amp;rdquo;].&lt;/p&gt;
&lt;p&gt;Here is a Markdown sample of a table with three rows that will be wrapped by a div with the class name mx-tdBreakAll.
Markdown&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[!div class=&amp;ldquo;mx-tdBreakAll&amp;rdquo;]&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;th&gt;Syntax&lt;/th&gt;
&lt;th&gt;Mandatory for silent installation?&lt;/th&gt;
&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Quiet&lt;/td&gt;
&lt;td&gt;/quiet&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Runs the installer, displaying no UI and no prompts.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;NoRestart&lt;/td&gt;
&lt;td&gt;/norestart&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Suppresses any attempts to restart. By default, the UI will prompt before restart.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Help&lt;/td&gt;
&lt;td&gt;/help&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Provides help and quick reference. Displays the correct use of the setup command, including a list of all options and behaviors.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/blockquote&gt;
&lt;p&gt;It will be rendered like this:
Name 	Syntax 	Mandatory for silent installation? 	Description
Quiet 	/quiet 	Yes 	Runs the installer, displaying no UI and no prompts.
NoRestart 	/norestart 	No 	Suppresses any attempts to restart. By default, the UI will prompt before restart.
Help 	/help 	No 	Provides help and quick reference. Displays the correct use of the setup command, including a list of all options and behaviors.
Line breaks within words in second column table cells&lt;/p&gt;
&lt;p&gt;You might want line breaks to be automatically inserted within words only in the second column of a table. To limit the breaks to the second column, apply the class mx-tdCol2BreakAll by using the div wrapper syntax as shown earlier.
Inconsistent column widths between tables&lt;/p&gt;
&lt;p&gt;You may notice that the column widths of the tables in your articles look odd or inconsistent. This behavior occurs because the length of text within the cells determines the layout of the table. Unfortunately, there&amp;rsquo;s no way to control how the tables render. This is a limitation of Markdown. Even though it would look nicer to have the width of table columns be consistent, this would have some disadvantages too:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Interlacing HTML code with Markdown makes topics more complicated and discourages community contributions.
A table that you make look good for a specific screen size may end up looking unreadable at different screen sizes as it preempts responsive rendering.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Data matrix tables&lt;/p&gt;
&lt;p&gt;A data matrix table has both a header and a weighted first column, creating a matrix with an empty cell in the top left. Docs has custom Markdown for data matrix tables:
Markdown&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Header 1&lt;/th&gt;
&lt;th&gt;Header 2&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;First column A&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Cell 1A&lt;/td&gt;
&lt;td&gt;Cell 2A&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;First column B&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Cell 1B&lt;/td&gt;
&lt;td&gt;Cell 2B&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;The example renders as:
Header 1 	Header 2
First column A 	Cell 1A 	Cell 2A
First column B 	Cell 1B 	Cell 2B&lt;/p&gt;
&lt;p&gt;Every entry in the first column must be styled as bold (&lt;strong&gt;bold&lt;/strong&gt;); otherwise the tables won&amp;rsquo;t be accessible for screen readers or valid for Docs.&lt;/p&gt;
&lt;p&gt;Tip&lt;/p&gt;
&lt;p&gt;The Docs Authoring Pack for VS Code includes a function to convert a regular Markdown table into a data matrix table. Just select the table, right-click, and select Convert to data matrix table.
HTML Tables&lt;/p&gt;
&lt;p&gt;HTML tables aren&amp;rsquo;t recommended for Docs. They aren&amp;rsquo;t human readable in the source - which is a key principle of Markdown.&lt;/p&gt;
&lt;p&gt;Have a great time using Markdown!&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Git Version Control</title>
      <link>https://example.com/post/post2/</link>
      <pubDate>Sat, 07 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/post2/</guid>
      <description>&lt;h2 id=&#34;about-version-control&#34;&gt;About Version Control&lt;/h2&gt;
&lt;p&gt;What is “version control”, and why should you care? Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. For the examples in this book, you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer.&lt;/p&gt;
&lt;p&gt;If you are a graphic or web designer and want to keep every version of an image or layout (which you would most certainly want to), a Version Control System (VCS) is a very wise thing to use. It allows you to revert selected files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more. Using a VCS also generally means that if you screw things up or lose files, you can easily recover. In addition, you get all this for very little overhead.&lt;/p&gt;
&lt;h1 id=&#34;local-version-control-systems&#34;&gt;Local Version Control Systems&lt;/h1&gt;
&lt;p&gt;Many people’s version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or copy over files you don’t mean to.&lt;/p&gt;
&lt;p&gt;To deal with this issue, programmers long ago developed local VCSs that had a simple database that kept all the changes to files under revision control.&lt;/p&gt;
&lt;p&gt;















&lt;figure  &gt;
  &lt;div class=&#34;d-flex justify-content-center&#34;&gt;
    &lt;div class=&#34;w-100&#34; &gt;&lt;img src=&#34;https://git-scm.com/book/en/v2/images/local.png&#34; alt=&#34;Local version control&#34; loading=&#34;lazy&#34; data-zoomable /&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;/figure&gt;
{ #fig:001 width=70% }&lt;/p&gt;
&lt;p&gt;One of the most popular VCS tools was a system called RCS, which is still distributed with many computers today. RCS works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all the patches.&lt;/p&gt;
&lt;h1 id=&#34;centralized-version-control-systems&#34;&gt;Centralized Version Control Systems&lt;/h1&gt;
&lt;p&gt;The next major issue that people encounter is that they need to collaborate with developers on other systems. To deal with this problem, Centralized Version Control Systems (CVCSs) were developed. These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients that check out files from that central place. For many years, this has been the standard for version control.&lt;/p&gt;
&lt;p&gt;















&lt;figure  &gt;
  &lt;div class=&#34;d-flex justify-content-center&#34;&gt;
    &lt;div class=&#34;w-100&#34; &gt;&lt;img src=&#34;https://git-scm.com/book/en/v2/images/centralized.png&#34; alt=&#34;Centralized version control&#34; loading=&#34;lazy&#34; data-zoomable /&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;/figure&gt;
{ #fig:002 width=70% }&lt;/p&gt;
&lt;p&gt;This setup offers many advantages, especially over local VCSs. For example, everyone knows to a certain degree what everyone else on the project is doing. Administrators have fine-grained control over who can do what, and it’s far easier to administer a CVCS than it is to deal with local databases on every client.&lt;/p&gt;
&lt;p&gt;However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything — the entire history of the project except whatever single snapshots people happen to have on their local machines. Local VCSs suffer from this same problem — whenever you have the entire history of the project in a single place, you risk losing everything.&lt;/p&gt;
&lt;h1 id=&#34;distributed-version-control-systems&#34;&gt;Distributed Version Control Systems&lt;/h1&gt;
&lt;p&gt;This is where Distributed Version Control Systems (DVCSs) step in. In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don’t just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history. Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it. Every clone is really a full backup of all the data.&lt;/p&gt;
&lt;p&gt;















&lt;figure  &gt;
  &lt;div class=&#34;d-flex justify-content-center&#34;&gt;
    &lt;div class=&#34;w-100&#34; &gt;&lt;img src=&#34;https://git-scm.com/book/en/v2/images/distributed.png&#34; alt=&#34;Distributed version control&#34; loading=&#34;lazy&#34; data-zoomable /&gt;&lt;/div&gt;
  &lt;/div&gt;&lt;/figure&gt;
{ #fig:002 width=70% }&lt;/p&gt;
&lt;p&gt;Furthermore, many of these systems deal pretty well with having several remote repositories they can work with, so you can collaborate with different groups of people in different ways simultaneously within the same project. This allows you to set up several types of workflows that aren’t possible in centralized systems, such as hierarchical models.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Welcome to my blog 👋</title>
      <link>https://example.com/post/getting-started/</link>
      <pubDate>Sat, 07 May 2022 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/getting-started/</guid>
      <description>&lt;h2 id=&#34;about-my-last-week&#34;&gt;About my last week&lt;/h2&gt;
&lt;p&gt;Hello and &lt;em&gt;welcome&lt;/em&gt; to my site! My life last week was just the same as the previous weeks which means I was studying a lot. I&amp;rsquo;ve spend a lot of time working on my &lt;strong&gt;labs for Operating systems&lt;/strong&gt;. I hope I will be able to study better and faster soon so I will have more time for the other subjects which are important too.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
