config for -> docs.snigdhaos.org

This commit is contained in:
2024-03-26 07:03:07 +05:30
parent 4747f56e4c
commit 9a38556af2
195 changed files with 1766 additions and 1301 deletions

14
build/blog/archive.html Normal file

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View File

@@ -1,99 +1,59 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>https://docs.snigdhaos.org/documentation/blog</id>
<id>https://docs.snigdhaos.org/blog</id>
<title>SNIGDHA OS - DOCS Blog</title>
<updated>2021-08-26T00:00:00.000Z</updated>
<updated>2024-03-25T02:20:39.000Z</updated>
<generator>https://github.com/jpmonette/feed</generator>
<link rel="alternate" href="https://docs.snigdhaos.org/documentation/blog"/>
<link rel="alternate" href="https://docs.snigdhaos.org/blog"/>
<subtitle>SNIGDHA OS - DOCS Blog</subtitle>
<icon>https://docs.snigdhaos.org/documentation/img/favicon.ico</icon>
<icon>https://docs.snigdhaos.org/img/favicon.ico</icon>
<entry>
<title type="html"><![CDATA[Welcome]]></title>
<id>https://docs.snigdhaos.org/documentation/blog/welcome</id>
<link href="https://docs.snigdhaos.org/documentation/blog/welcome"/>
<updated>2021-08-26T00:00:00.000Z</updated>
<summary type="html"><![CDATA[Docusaurus blogging features are powered by the blog plugin.]]></summary>
<content type="html"><![CDATA[<p><a href="https://docusaurus.io/docs/blog" target="_blank" rel="noopener noreferrer">Docusaurus blogging features</a> are powered by the <a href="https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog" target="_blank" rel="noopener noreferrer">blog plugin</a>.</p>
<p>Simply add Markdown files (or folders) to the <code>blog</code> directory.</p>
<p>Regular blog authors can be added to <code>authors.yml</code>.</p>
<p>The blog post date can be extracted from filenames, such as:</p>
<title type="html"><![CDATA[Write Effective Bug Report]]></title>
<id>https://docs.snigdhaos.org/blog/effective_bug_report</id>
<link href="https://docs.snigdhaos.org/blog/effective_bug_report"/>
<updated>2024-03-25T02:20:39.000Z</updated>
<summary type="html"><![CDATA[Writing an effective bug report is crucial for helping developers understand, reproduce, and ultimately fix the issue. Here's a step-by-step guide on how to write an effective bug report:]]></summary>
<content type="html"><![CDATA[<p>Writing an effective bug report is crucial for helping developers understand, reproduce, and ultimately fix the issue. Here's a step-by-step guide on how to write an effective bug report:</p>
<ol>
<li>
<p><strong>Title</strong>: Provide a concise and descriptive title that summarizes the issue. It should give a clear indication of what the problem is without being too lengthy. For example, "Error message appears when trying to log in."</p>
</li>
<li>
<p><strong>Description</strong>:</p>
<ul>
<li><code>2019-05-30-welcome.md</code></li>
<li><code>2019-05-30-welcome/index.md</code></li>
<li><strong>Overview</strong>: Begin with a brief overview of the problem, including what you were trying to do and what went wrong.</li>
<li><strong>Steps to Reproduce</strong>: List the specific steps or actions taken that lead to the issue. Provide enough detail so that others can follow the same steps and encounter the same problem.</li>
<li><strong>Expected Behavior</strong>: Describe what you expected to happen after performing the steps mentioned above.</li>
<li><strong>Actual Behavior</strong>: Describe what actually happened or what you observed that indicates the presence of a bug. Include any error messages, unexpected behavior, or deviations from the expected outcome.</li>
<li><strong>Frequency</strong>: Indicate whether the issue occurs consistently or intermittently. If intermittent, specify any patterns or conditions that seem to trigger the problem.</li>
<li><strong>Environment</strong>: Mention the operating system, browser/version, device, or any other relevant environment details where the issue occurred.</li>
<li><strong>Screenshots/Attachments</strong>: If applicable, include screenshots, logs, error messages, or any other relevant files that can help illustrate or reproduce the problem.</li>
</ul>
<p>A blog post folder can be convenient to co-locate blog post images:</p>
<p><img decoding="async" loading="lazy" alt="Docusaurus Plushie" src="https://docs.snigdhaos.org/documentation/assets/images/docusaurus-plushie-banner-a60f7593abca1e3eef26a9afa244e4fb.jpeg" width="1500" height="500" class="img_ev3q"></p>
<p>The blog supports tags as well!</p>
<p><strong>And if you don't want a blog</strong>: just delete this directory, and use <code>blog: false</code> in your Docusaurus config.</p>]]></content>
</li>
<li>
<p><strong>Impact</strong>: Explain the impact of the bug on the user experience, system functionality, or any other relevant aspect. Include information about any workarounds or mitigations you've discovered.</p>
</li>
<li>
<p><strong>Additional Information</strong>:</p>
<ul>
<li><strong>Related Issues</strong>: If you suspect the bug may be related to other issues or if you've found similar reports, mention them and provide links if possible.</li>
<li><strong>Priority/Severity</strong>: Optionally, suggest a priority or severity level for the bug based on its impact and urgency.</li>
<li><strong>Timeframe</strong>: If applicable, specify any deadlines or time constraints that may affect the resolution of the issue.</li>
<li><strong>Contact Information</strong>: Provide your contact information (email, username, etc.) in case developers need clarification or further details.</li>
</ul>
</li>
<li>
<p><strong>Submission</strong>: Submit the bug report through the designated bug tracking system, issue tracker, or communication channel used by the development team. Follow any specific guidelines or templates provided by the project.</p>
</li>
<li>
<p><strong>Follow-up</strong>: Be prepared to respond to any follow-up questions or requests for clarification from developers. Provide additional information as needed to help troubleshoot and resolve the issue.</p>
</li>
</ol>
<p>By following these steps and providing detailed, organized information, you can help developers diagnose and address the bug more effectively, ultimately leading to quicker resolution and improved software quality.</p>]]></content>
<author>
<name>Sébastien Lorber</name>
<uri>https://sebastienlorber.com</uri>
<name>Eshan Roy</name>
<uri>https://eshan.snigdhaos.org</uri>
</author>
<author>
<name>Yangshun Tay</name>
<uri>https://github.com/yangshun</uri>
</author>
<category label="facebook" term="facebook"/>
<category label="hello" term="hello"/>
<category label="docusaurus" term="docusaurus"/>
</entry>
<entry>
<title type="html"><![CDATA[MDX Blog Post]]></title>
<id>https://docs.snigdhaos.org/documentation/blog/mdx-blog-post</id>
<link href="https://docs.snigdhaos.org/documentation/blog/mdx-blog-post"/>
<updated>2021-08-01T00:00:00.000Z</updated>
<summary type="html"><![CDATA[Blog posts support Docusaurus Markdown features, such as MDX.]]></summary>
<content type="html"><![CDATA[<p>Blog posts support <a href="https://docusaurus.io/docs/markdown-features" target="_blank" rel="noopener noreferrer">Docusaurus Markdown features</a>, such as <a href="https://mdxjs.com/" target="_blank" rel="noopener noreferrer">MDX</a>.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>tip</div><div class="admonitionContent_BuS1"><p>Use the power of React to create interactive blog posts.</p><div class="language-js codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-js codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token operator" style="color:#393A34">&lt;</span><span class="token plain">button onClick</span><span class="token operator" style="color:#393A34">=</span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">alert</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'button clicked!'</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">}</span><span class="token operator" style="color:#393A34">&gt;</span><span class="token maybe-class-name">Click</span><span class="token plain"> me</span><span class="token operator" style="color:#393A34">!</span><span class="token operator" style="color:#393A34">&lt;</span><span class="token operator" style="color:#393A34">/</span><span class="token plain">button</span><span class="token operator" style="color:#393A34">&gt;</span><br></span></code></pre><div class="buttonGroup__atx"><button type="button" aria-label="Copy code to clipboard" title="Copy" class="clean-btn"><span class="copyButtonIcons_eSgA" aria-hidden="true"><svg viewBox="0 0 24 24" class="copyButtonIcon_y97N"><path fill="currentColor" d="M19,21H8V7H19M19,5H8A2,2 0 0,0 6,7V21A2,2 0 0,0 8,23H19A2,2 0 0,0 21,21V7A2,2 0 0,0 19,5M16,1H4A2,2 0 0,0 2,3V17H4V3H16V1Z"></path></svg><svg viewBox="0 0 24 24" class="copyButtonSuccessIcon_LjdS"><path fill="currentColor" d="M21,7L9,19L3.5,13.5L4.91,12.09L9,16.17L19.59,5.59L21,7Z"></path></svg></span></button></div></div></div><button>Click me!</button></div></div>]]></content>
<author>
<name>Sébastien Lorber</name>
<uri>https://sebastienlorber.com</uri>
</author>
<category label="docusaurus" term="docusaurus"/>
</entry>
<entry>
<title type="html"><![CDATA[Long Blog Post]]></title>
<id>https://docs.snigdhaos.org/documentation/blog/long-blog-post</id>
<link href="https://docs.snigdhaos.org/documentation/blog/long-blog-post"/>
<updated>2019-05-29T00:00:00.000Z</updated>
<summary type="html"><![CDATA[This is the summary of a very long blog post,]]></summary>
<content type="html"><![CDATA[<p>This is the summary of a very long blog post,</p>
<p>Use a <code>&lt;!--</code> <code>truncate</code> <code>--&gt;</code> comment to limit blog post size in the list view.</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>]]></content>
<author>
<name>Endilie Yacop Sucipto</name>
<uri>https://github.com/endiliey</uri>
</author>
<category label="hello" term="hello"/>
<category label="docusaurus" term="docusaurus"/>
</entry>
<entry>
<title type="html"><![CDATA[First Blog Post]]></title>
<id>https://docs.snigdhaos.org/documentation/blog/first-blog-post</id>
<link href="https://docs.snigdhaos.org/documentation/blog/first-blog-post"/>
<updated>2019-05-28T00:00:00.000Z</updated>
<summary type="html"><![CDATA[Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet]]></summary>
<content type="html"><![CDATA[<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>]]></content>
<author>
<name>Gao Wei</name>
<uri>https://github.com/wgao19</uri>
</author>
<category label="hola" term="hola"/>
<category label="docusaurus" term="docusaurus"/>
<category label="bug" term="bug"/>
</entry>
</feed>

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View File

@@ -2,80 +2,56 @@
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>SNIGDHA OS - DOCS Blog</title>
<link>https://docs.snigdhaos.org/documentation/blog</link>
<link>https://docs.snigdhaos.org/blog</link>
<description>SNIGDHA OS - DOCS Blog</description>
<lastBuildDate>Thu, 26 Aug 2021 00:00:00 GMT</lastBuildDate>
<lastBuildDate>Mon, 25 Mar 2024 02:20:39 GMT</lastBuildDate>
<docs>https://validator.w3.org/feed/docs/rss2.html</docs>
<generator>https://github.com/jpmonette/feed</generator>
<language>en</language>
<item>
<title><![CDATA[Welcome]]></title>
<link>https://docs.snigdhaos.org/documentation/blog/welcome</link>
<guid>https://docs.snigdhaos.org/documentation/blog/welcome</guid>
<pubDate>Thu, 26 Aug 2021 00:00:00 GMT</pubDate>
<description><![CDATA[Docusaurus blogging features are powered by the blog plugin.]]></description>
<content:encoded><![CDATA[<p><a href="https://docusaurus.io/docs/blog" target="_blank" rel="noopener noreferrer">Docusaurus blogging features</a> are powered by the <a href="https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog" target="_blank" rel="noopener noreferrer">blog plugin</a>.</p>
<p>Simply add Markdown files (or folders) to the <code>blog</code> directory.</p>
<p>Regular blog authors can be added to <code>authors.yml</code>.</p>
<p>The blog post date can be extracted from filenames, such as:</p>
<title><![CDATA[Write Effective Bug Report]]></title>
<link>https://docs.snigdhaos.org/blog/effective_bug_report</link>
<guid>https://docs.snigdhaos.org/blog/effective_bug_report</guid>
<pubDate>Mon, 25 Mar 2024 02:20:39 GMT</pubDate>
<description><![CDATA[Writing an effective bug report is crucial for helping developers understand, reproduce, and ultimately fix the issue. Here's a step-by-step guide on how to write an effective bug report:]]></description>
<content:encoded><![CDATA[<p>Writing an effective bug report is crucial for helping developers understand, reproduce, and ultimately fix the issue. Here's a step-by-step guide on how to write an effective bug report:</p>
<ol>
<li>
<p><strong>Title</strong>: Provide a concise and descriptive title that summarizes the issue. It should give a clear indication of what the problem is without being too lengthy. For example, "Error message appears when trying to log in."</p>
</li>
<li>
<p><strong>Description</strong>:</p>
<ul>
<li><code>2019-05-30-welcome.md</code></li>
<li><code>2019-05-30-welcome/index.md</code></li>
<li><strong>Overview</strong>: Begin with a brief overview of the problem, including what you were trying to do and what went wrong.</li>
<li><strong>Steps to Reproduce</strong>: List the specific steps or actions taken that lead to the issue. Provide enough detail so that others can follow the same steps and encounter the same problem.</li>
<li><strong>Expected Behavior</strong>: Describe what you expected to happen after performing the steps mentioned above.</li>
<li><strong>Actual Behavior</strong>: Describe what actually happened or what you observed that indicates the presence of a bug. Include any error messages, unexpected behavior, or deviations from the expected outcome.</li>
<li><strong>Frequency</strong>: Indicate whether the issue occurs consistently or intermittently. If intermittent, specify any patterns or conditions that seem to trigger the problem.</li>
<li><strong>Environment</strong>: Mention the operating system, browser/version, device, or any other relevant environment details where the issue occurred.</li>
<li><strong>Screenshots/Attachments</strong>: If applicable, include screenshots, logs, error messages, or any other relevant files that can help illustrate or reproduce the problem.</li>
</ul>
<p>A blog post folder can be convenient to co-locate blog post images:</p>
<p><img decoding="async" loading="lazy" alt="Docusaurus Plushie" src="https://docs.snigdhaos.org/documentation/assets/images/docusaurus-plushie-banner-a60f7593abca1e3eef26a9afa244e4fb.jpeg" width="1500" height="500" class="img_ev3q"></p>
<p>The blog supports tags as well!</p>
<p><strong>And if you don't want a blog</strong>: just delete this directory, and use <code>blog: false</code> in your Docusaurus config.</p>]]></content:encoded>
<category>facebook</category>
<category>hello</category>
<category>docusaurus</category>
</item>
<item>
<title><![CDATA[MDX Blog Post]]></title>
<link>https://docs.snigdhaos.org/documentation/blog/mdx-blog-post</link>
<guid>https://docs.snigdhaos.org/documentation/blog/mdx-blog-post</guid>
<pubDate>Sun, 01 Aug 2021 00:00:00 GMT</pubDate>
<description><![CDATA[Blog posts support Docusaurus Markdown features, such as MDX.]]></description>
<content:encoded><![CDATA[<p>Blog posts support <a href="https://docusaurus.io/docs/markdown-features" target="_blank" rel="noopener noreferrer">Docusaurus Markdown features</a>, such as <a href="https://mdxjs.com/" target="_blank" rel="noopener noreferrer">MDX</a>.</p>
<div class="theme-admonition theme-admonition-tip admonition_xJq3 alert alert--success"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>tip</div><div class="admonitionContent_BuS1"><p>Use the power of React to create interactive blog posts.</p><div class="language-js codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-js codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token operator" style="color:#393A34">&lt;</span><span class="token plain">button onClick</span><span class="token operator" style="color:#393A34">=</span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">alert</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'button clicked!'</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">}</span><span class="token operator" style="color:#393A34">&gt;</span><span class="token maybe-class-name">Click</span><span class="token plain"> me</span><span class="token operator" style="color:#393A34">!</span><span class="token operator" style="color:#393A34">&lt;</span><span class="token operator" style="color:#393A34">/</span><span class="token plain">button</span><span class="token operator" style="color:#393A34">&gt;</span><br></span></code></pre><div class="buttonGroup__atx"><button type="button" aria-label="Copy code to clipboard" title="Copy" class="clean-btn"><span class="copyButtonIcons_eSgA" aria-hidden="true"><svg viewBox="0 0 24 24" class="copyButtonIcon_y97N"><path fill="currentColor" d="M19,21H8V7H19M19,5H8A2,2 0 0,0 6,7V21A2,2 0 0,0 8,23H19A2,2 0 0,0 21,21V7A2,2 0 0,0 19,5M16,1H4A2,2 0 0,0 2,3V17H4V3H16V1Z"></path></svg><svg viewBox="0 0 24 24" class="copyButtonSuccessIcon_LjdS"><path fill="currentColor" d="M21,7L9,19L3.5,13.5L4.91,12.09L9,16.17L19.59,5.59L21,7Z"></path></svg></span></button></div></div></div><button>Click me!</button></div></div>]]></content:encoded>
<category>docusaurus</category>
</item>
<item>
<title><![CDATA[Long Blog Post]]></title>
<link>https://docs.snigdhaos.org/documentation/blog/long-blog-post</link>
<guid>https://docs.snigdhaos.org/documentation/blog/long-blog-post</guid>
<pubDate>Wed, 29 May 2019 00:00:00 GMT</pubDate>
<description><![CDATA[This is the summary of a very long blog post,]]></description>
<content:encoded><![CDATA[<p>This is the summary of a very long blog post,</p>
<p>Use a <code>&lt;!--</code> <code>truncate</code> <code>--&gt;</code> comment to limit blog post size in the list view.</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>]]></content:encoded>
<category>hello</category>
<category>docusaurus</category>
</item>
<item>
<title><![CDATA[First Blog Post]]></title>
<link>https://docs.snigdhaos.org/documentation/blog/first-blog-post</link>
<guid>https://docs.snigdhaos.org/documentation/blog/first-blog-post</guid>
<pubDate>Tue, 28 May 2019 00:00:00 GMT</pubDate>
<description><![CDATA[Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet]]></description>
<content:encoded><![CDATA[<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet</p>]]></content:encoded>
<category>hola</category>
<category>docusaurus</category>
</li>
<li>
<p><strong>Impact</strong>: Explain the impact of the bug on the user experience, system functionality, or any other relevant aspect. Include information about any workarounds or mitigations you've discovered.</p>
</li>
<li>
<p><strong>Additional Information</strong>:</p>
<ul>
<li><strong>Related Issues</strong>: If you suspect the bug may be related to other issues or if you've found similar reports, mention them and provide links if possible.</li>
<li><strong>Priority/Severity</strong>: Optionally, suggest a priority or severity level for the bug based on its impact and urgency.</li>
<li><strong>Timeframe</strong>: If applicable, specify any deadlines or time constraints that may affect the resolution of the issue.</li>
<li><strong>Contact Information</strong>: Provide your contact information (email, username, etc.) in case developers need clarification or further details.</li>
</ul>
</li>
<li>
<p><strong>Submission</strong>: Submit the bug report through the designated bug tracking system, issue tracker, or communication channel used by the development team. Follow any specific guidelines or templates provided by the project.</p>
</li>
<li>
<p><strong>Follow-up</strong>: Be prepared to respond to any follow-up questions or requests for clarification from developers. Provide additional information as needed to help troubleshoot and resolve the issue.</p>
</li>
</ol>
<p>By following these steps and providing detailed, organized information, you can help developers diagnose and address the bug more effectively, ultimately leading to quicker resolution and improved software quality.</p>]]></content:encoded>
<category>bug</category>
</item>
</channel>
</rss>

14
build/blog/tags.html Normal file

File diff suppressed because one or more lines are too long

50
build/blog/tags/bug.html Normal file

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long