Skip to content

Commit 2635aa1

Browse files
jeromehardawayjeromehardaway
committed
Deployed 143581a with MkDocs version: 1.6.1
1 parent b17d505 commit 2635aa1

File tree

2 files changed

+42
-17
lines changed

2 files changed

+42
-17
lines changed

‎index.html‎

Lines changed: 41 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,13 @@
4343
<ul class="current">
4444
<li class="toctree-l1 current"><a class="reference internal current" href="#">Home</a>
4545
<ul class="current">
46-
<li class="toctree-l2"><a class="reference internal" href="#commands">Commands</a>
46+
<li class="toctree-l2"><a class="reference internal" href="#why-have-sops">Why Have SOPs</a>
4747
</li>
48-
<li class="toctree-l2"><a class="reference internal" href="#project-layout">Project layout</a>
48+
<li class="toctree-l2"><a class="reference internal" href="#collection-i-core-fundamentals">Collection I: Core Fundamentals</a>
49+
<ul>
50+
<li class="toctree-l3"><a class="reference internal" href="#core-training-modules">Core Training Modules</a>
51+
</li>
52+
</ul>
4953
</li>
5054
</ul>
5155
</li>
@@ -73,21 +77,42 @@
7377
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
7478
<div class="section" itemprop="articleBody">
7579

76-
<h1 id="welcome-to-mkdocs">Welcome to MkDocs</h1>
77-
<p>For full documentation visit <a href="https://www.mkdocs.org">mkdocs.org</a>.</p>
78-
<h2 id="commands">Commands</h2>
80+
<h1 id="vets-who-code-engineering-standard-operating-procedures-sops">Vets Who Code Engineering Standard Operating Procedures (SOPs)</h1>
81+
<p>A veteran transitioning into software engineering through Vets Who Code...</p>
82+
<ul>
83+
<li>Has responsibilities to their unit – mentor, coach, and lead.</li>
84+
<li>Knows their <strong>SOPs</strong>. Follows their SOPs. Improves their SOPs if they are inefficient. If they find better SOPs, they incorporate them. If somebody could use their SOPs, they share them.</li>
85+
<li>Leads by example. Models the behaviors we desire both interpersonally and technically.</li>
86+
<li>Strives to understand how their work fits into a broader context and ensures mission success.</li>
87+
</ul>
88+
<p>These are our Standard Operating Procedures for Software Engineering Core Fundamentals. All contributions are welcome! Please feel free to submit a pull request to get involved.</p>
89+
<h2 id="why-have-sops">Why Have SOPs</h2>
7990
<ul>
80-
<li><code>mkdocs new [dir-name]</code> - Create a new project.</li>
81-
<li><code>mkdocs serve</code> - Start the live-reloading docs server.</li>
82-
<li><code>mkdocs build</code> - Build the documentation site.</li>
83-
<li><code>mkdocs -h</code> - Print help message and exit.</li>
91+
<li>To increase overall efficiency for the entire Vets Who Code community.</li>
92+
<li>To reduce the number of errors and avoid common pitfalls in the transition of becoming software engineers.</li>
93+
<li>To strive to be better engineers and learn from shared experiences so we can flatten each others growth curve.</li>
94+
<li>To establish a consistent, high-quality approach to software development tasks.</li>
8495
</ul>
85-
<h2 id="project-layout">Project layout</h2>
86-
<pre><code>mkdocs.yml # The configuration file.
87-
docs/
88-
index.md # The documentation homepage.
89-
... # Other markdown pages, images and other files.
90-
</code></pre>
96+
<p>If you do nothing else, follow the Engineering Fundamentals Checklist! (Link to be added)</p>
97+
<h2 id="collection-i-core-fundamentals">Collection I: Core Fundamentals</h2>
98+
<p>This collection of units and modules covers essential topics for software development. It equips you with the necessary skills and knowledge to build a strong foundation in coding, applicable across various programming domains. We're starting with the most fundamental modules, with more to come as we build out our curriculum.</p>
99+
<h3 id="core-training-modules">Core Training Modules</h3>
100+
<ol>
101+
<li><a href="command-line-bash/intro.md">Command Center: Mastering Command Line and Bash</a></li>
102+
<li>Master your primary interface for commanding computer operations</li>
103+
<li>Learn to navigate file systems, manipulate data, and automate tasks efficiently</li>
104+
<li>Understand the power of text-based computer interaction</li>
105+
<li>
106+
<p>Harness the full potential of Bash scripting for task automation and system management</p>
107+
</li>
108+
<li>
109+
<p><a href="git-github/intro.md">Mission Control: Git and GitHub</a></p>
110+
</li>
111+
<li>Understand version control concepts and their importance in modern software development</li>
112+
<li>Learn to track changes, collaborate with others, and manage your codebase effectively</li>
113+
<li>Master the art of branching, merging, and resolving conflicts</li>
114+
<li>Utilize GitHub for project management, collaboration, and showcasing your work</li>
115+
</ol>
91116

92117
</div>
93118
</div><footer>
@@ -131,5 +156,5 @@ <h2 id="project-layout">Project layout</h2>
131156

132157
<!--
133158
MkDocs version : 1.6.1
134-
Build Date UTC : 2024-10-11 23:19:29.993733+00:00
159+
Build Date UTC : 2024-10-11 23:36:50.898903+00:00
135160
-->

‎search/search_index.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Welcome to MkDocs For full documentation visit mkdocs.org . Commands mkdocs new [dir-name] - Create a new project. mkdocs serve - Start the live-reloading docs server. mkdocs build - Build the documentation site. mkdocs -h - Print help message and exit. Project layout mkdocs.yml # The configuration file. docs/ index.md # The documentation homepage. ... # Other markdown pages, images and other files.","title":"Home"},{"location":"#welcome-to-mkdocs","text":"For full documentation visit mkdocs.org .","title":"Welcome to MkDocs"},{"location":"#commands","text":"mkdocs new [dir-name] - Create a new project. mkdocs serve - Start the live-reloading docs server. mkdocs build - Build the documentation site. mkdocs -h - Print help message and exit.","title":"Commands"},{"location":"#project-layout","text":"mkdocs.yml # The configuration file. docs/ index.md # The documentation homepage. ... # Other markdown pages, images and other files.","title":"Project layout"}]}
1+
{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Vets Who Code Engineering Standard Operating Procedures (SOPs) A veteran transitioning into software engineering through Vets Who Code... Has responsibilities to their unit \u2013 mentor, coach, and lead. Knows their SOPs . Follows their SOPs. Improves their SOPs if they are inefficient. If they find better SOPs, they incorporate them. If somebody could use their SOPs, they share them. Leads by example. Models the behaviors we desire both interpersonally and technically. Strives to understand how their work fits into a broader context and ensures mission success. These are our Standard Operating Procedures for Software Engineering Core Fundamentals. All contributions are welcome! Please feel free to submit a pull request to get involved. Why Have SOPs To increase overall efficiency for the entire Vets Who Code community. To reduce the number of errors and avoid common pitfalls in the transition of becoming software engineers. To strive to be better engineers and learn from shared experiences so we can flatten each others growth curve. To establish a consistent, high-quality approach to software development tasks. If you do nothing else, follow the Engineering Fundamentals Checklist! (Link to be added) Collection I: Core Fundamentals This collection of units and modules covers essential topics for software development. It equips you with the necessary skills and knowledge to build a strong foundation in coding, applicable across various programming domains. We're starting with the most fundamental modules, with more to come as we build out our curriculum. Core Training Modules Command Center: Mastering Command Line and Bash Master your primary interface for commanding computer operations Learn to navigate file systems, manipulate data, and automate tasks efficiently Understand the power of text-based computer interaction Harness the full potential of Bash scripting for task automation and system management Mission Control: Git and GitHub Understand version control concepts and their importance in modern software development Learn to track changes, collaborate with others, and manage your codebase effectively Master the art of branching, merging, and resolving conflicts Utilize GitHub for project management, collaboration, and showcasing your work","title":"Home"},{"location":"#vets-who-code-engineering-standard-operating-procedures-sops","text":"A veteran transitioning into software engineering through Vets Who Code... Has responsibilities to their unit \u2013 mentor, coach, and lead. Knows their SOPs . Follows their SOPs. Improves their SOPs if they are inefficient. If they find better SOPs, they incorporate them. If somebody could use their SOPs, they share them. Leads by example. Models the behaviors we desire both interpersonally and technically. Strives to understand how their work fits into a broader context and ensures mission success. These are our Standard Operating Procedures for Software Engineering Core Fundamentals. All contributions are welcome! Please feel free to submit a pull request to get involved.","title":"Vets Who Code Engineering Standard Operating Procedures (SOPs)"},{"location":"#why-have-sops","text":"To increase overall efficiency for the entire Vets Who Code community. To reduce the number of errors and avoid common pitfalls in the transition of becoming software engineers. To strive to be better engineers and learn from shared experiences so we can flatten each others growth curve. To establish a consistent, high-quality approach to software development tasks. If you do nothing else, follow the Engineering Fundamentals Checklist! (Link to be added)","title":"Why Have SOPs"},{"location":"#collection-i-core-fundamentals","text":"This collection of units and modules covers essential topics for software development. It equips you with the necessary skills and knowledge to build a strong foundation in coding, applicable across various programming domains. We're starting with the most fundamental modules, with more to come as we build out our curriculum.","title":"Collection I: Core Fundamentals"},{"location":"#core-training-modules","text":"Command Center: Mastering Command Line and Bash Master your primary interface for commanding computer operations Learn to navigate file systems, manipulate data, and automate tasks efficiently Understand the power of text-based computer interaction Harness the full potential of Bash scripting for task automation and system management Mission Control: Git and GitHub Understand version control concepts and their importance in modern software development Learn to track changes, collaborate with others, and manage your codebase effectively Master the art of branching, merging, and resolving conflicts Utilize GitHub for project management, collaboration, and showcasing your work","title":"Core Training Modules"}]}

0 commit comments

Comments
 (0)