add RStudio tips

Author: jyoti-bhogal

blogs/posts/rstudio_and positron_ide_tips.qmd

@@ -8,7 +8,20 @@ RStudio and Positron are IDEs useful for running R programmign language code. In
 
 # RStudio IDE tips
 
-* For a new code, use New Project and then create the necesssary files (.R, .Rmd, .qmd, etc.) inside the New Project. This helps is keeping the r environment including the dependencies spearate for separate projects.
-* Tip 2
-* Tip 3
-* Tip 4
+* **New Project for a new analysis**: For a new code, use New Project and then create the necesssary files (.R, .Rmd, .qmd, etc.) inside the New Project. This helps is keeping the r environment including the dependencies spearate for separate projects.
+* **Adopt a consistent folder structure**: Organise your project directory with subfolders for clarity, such as `data/` (with `raw/` and `processed/` subdirectories), `scripts/`, and `output/` (for figures and reports).
+* **Create dynamic reports rather than static**: One can use R markdown or a quarto file to create a dynamic output document, slides, or website. This allows you to integrate code and narrative text, making it easier to update and reproduce your analysis.
+* **Integrate Version Control using Git or GitHub**: RStudio has a built in **Terminal** as well as **Git** pane to help you manage version control. This allows you to track code or text changes, collaborate with others on shared and/or open source projects, and maintain a history of your project.
+* **Spell Check feature**: Use the spell check feature from `Edit -> Check Spelling...` to ensure your code comments and documentation are free from typos. 
+* **History**: Go through the `History` tab to review previously run commands. You can easily re-run or copy commands from your history to save time.
+* **Environment**: Use this section to have a cursory look at the active variables and a glimpse of the values stored in them.
+* **Four panels in RStudio**: Familiarise yourself with the four-panel layout of RStudio (Source, Console, Environment/History, Files/Plots/Packages/Help). This layout helps you efficiently manage your coding, output, and resources.
+* **Running code in chunks**: In R markdown and quarto files, use the features to run selected lines, current chunk, next chunk, all the chunks, all the chunks above, and all the chunks below to efficiently test and run your code. 
+
+# Positron IDE tips
+
+* **Tip 1**:
+* **Tip 2**:
+* **Tip 3**:
+* **Tip 4**:
+* **Tip 5**:

docs/blogs/index.html

@@ -240,7 +240,7 @@ <h5 class="no-anchor card-title listing-title">
 </div>
 </div></a>
 </div>
-<div class="g-col-1" data-index="1" data-categories="UlN0dWRpbyUyQ1Bvc2l0cm9uJTJDQmVnaW5uZXI=" data-listing-file-modified-sort="1763617819691" data-listing-reading-time-sort="1" data-listing-word-count-sort="73">
+<div class="g-col-1" data-index="1" data-categories="UlN0dWRpbyUyQ1Bvc2l0cm9uJTJDQmVnaW5uZXI=" data-listing-file-modified-sort="1763625394036" data-listing-reading-time-sort="2" data-listing-word-count-sort="344">
 <a href="../blogs/posts/rstudio_and positron_ide_tips.html" class="quarto-grid-link">
 <div class="quarto-grid-item card h-100 card-left">
 <div class="listing-item-img-placeholder card-img-top" style="height: 150px;">&nbsp;</div>

docs/blogs/posts/rstudio_and positron_ide_tips.html

@@ -137,6 +137,7 @@ <h2 id="toc-title">On this page</h2>
 
   <ul>
   <li><a href="#rstudio-ide-tips" id="toc-rstudio-ide-tips" class="nav-link active" data-scroll-target="#rstudio-ide-tips">RStudio IDE tips</a></li>
+  <li><a href="#positron-ide-tips" id="toc-positron-ide-tips" class="nav-link" data-scroll-target="#positron-ide-tips">Positron IDE tips</a></li>
   </ul>
 </nav>
     </div>
@@ -177,10 +178,25 @@ <h1 class="title">RStudio and Positron IDE Tips to Make Your Workflows Efficient
 <section id="rstudio-ide-tips" class="level1">
 <h1>RStudio IDE tips</h1>
 <ul>
-<li>For a new code, use New Project and then create the necesssary files (.R, .Rmd, .qmd, etc.) inside the New Project. This helps is keeping the r environment including the dependencies spearate for separate projects.</li>
-<li>Tip 2</li>
-<li>Tip 3</li>
-<li>Tip 4</li>
+<li><strong>New Project for a new analysis</strong>: For a new code, use New Project and then create the necesssary files (.R, .Rmd, .qmd, etc.) inside the New Project. This helps is keeping the r environment including the dependencies spearate for separate projects.</li>
+<li><strong>Adopt a consistent folder structure</strong>: Organise your project directory with subfolders for clarity, such as <code>data/</code> (with <code>raw/</code> and <code>processed/</code> subdirectories), <code>scripts/</code>, and <code>output/</code> (for figures and reports).</li>
+<li><strong>Create dynamic reports rather than static</strong>: One can use R markdown or a quarto file to create a dynamic output document, slides, or website. This allows you to integrate code and narrative text, making it easier to update and reproduce your analysis.</li>
+<li><strong>Integrate Version Control using Git or GitHub</strong>: RStudio has a built in <strong>Terminal</strong> as well as <strong>Git</strong> pane to help you manage version control. This allows you to track code or text changes, collaborate with others on shared and/or open source projects, and maintain a history of your project.</li>
+<li><strong>Spell Check feature</strong>: Use the spell check feature from <code>Edit -&gt; Check Spelling...</code> to ensure your code comments and documentation are free from typos.</li>
+<li><strong>History</strong>: Go through the <code>History</code> tab to review previously run commands. You can easily re-run or copy commands from your history to save time.</li>
+<li><strong>Environment</strong>: Use this section to have a cursory look at the active variables and a glimpse of the values stored in them.</li>
+<li><strong>Four panels in RStudio</strong>: Familiarise yourself with the four-panel layout of RStudio (Source, Console, Environment/History, Files/Plots/Packages/Help). This layout helps you efficiently manage your coding, output, and resources.</li>
+<li><strong>Running code in chunks</strong>: In R markdown and quarto files, use the features to run selected lines, current chunk, next chunk, all the chunks, all the chunks above, and all the chunks below to efficiently test and run your code.</li>
+</ul>
+</section>
+<section id="positron-ide-tips" class="level1">
+<h1>Positron IDE tips</h1>
+<ul>
+<li><strong>Tip 1</strong>:</li>
+<li><strong>Tip 2</strong>:</li>
+<li><strong>Tip 3</strong>:</li>
+<li><strong>Tip 4</strong>:</li>
+<li><strong>Tip 5</strong>:</li>
 </ul>
 
 

docs/search.json

@@ -116,6 +116,6 @@
     "href": "blogs/posts/rstudio_and positron_ide_tips.html",
     "title": "RStudio and Positron IDE Tips to Make Your Workflows Efficient!",
     "section": "",
-    "text": "RStudio and Positron are IDEs useful for running R programmign language code. In this blog, we will explore some tips and tricks to make your workflow more efficient while using these IDEs.\n\nRStudio IDE tips\n\nFor a new code, use New Project and then create the necesssary files (.R, .Rmd, .qmd, etc.) inside the New Project. This helps is keeping the r environment including the dependencies spearate for separate projects.\nTip 2\nTip 3\nTip 4"
+    "text": "RStudio and Positron are IDEs useful for running R programmign language code. In this blog, we will explore some tips and tricks to make your workflow more efficient while using these IDEs.\n\nRStudio IDE tips\n\nNew Project for a new analysis: For a new code, use New Project and then create the necesssary files (.R, .Rmd, .qmd, etc.) inside the New Project. This helps is keeping the r environment including the dependencies spearate for separate projects.\nAdopt a consistent folder structure: Organise your project directory with subfolders for clarity, such as data/ (with raw/ and processed/ subdirectories), scripts/, and output/ (for figures and reports).\nCreate dynamic reports rather than static: One can use R markdown or a quarto file to create a dynamic output document, slides, or website. This allows you to integrate code and narrative text, making it easier to update and reproduce your analysis.\nIntegrate Version Control using Git or GitHub: RStudio has a built in Terminal as well as Git pane to help you manage version control. This allows you to track code or text changes, collaborate with others on shared and/or open source projects, and maintain a history of your project.\nSpell Check feature: Use the spell check feature from Edit -> Check Spelling... to ensure your code comments and documentation are free from typos.\nHistory: Go through the History tab to review previously run commands. You can easily re-run or copy commands from your history to save time.\nEnvironment: Use this section to have a cursory look at the active variables and a glimpse of the values stored in them.\nFour panels in RStudio: Familiarise yourself with the four-panel layout of RStudio (Source, Console, Environment/History, Files/Plots/Packages/Help). This layout helps you efficiently manage your coding, output, and resources.\nRunning code in chunks: In R markdown and quarto files, use the features to run selected lines, current chunk, next chunk, all the chunks, all the chunks above, and all the chunks below to efficiently test and run your code.\n\n\n\nPositron IDE tips\n\nTip 1:\nTip 2:\nTip 3:\nTip 4:\nTip 5:"
   }
 ]