Deploy preview for PR 84 🛫

Author: mingness

pr-preview/pr-84/develop.html

@@ -560,41 +560,21 @@ <h2 id="configuring-the-gradle-build-file">Configuring the Gradle build file</h2
 contributed library Processing, after being installed. Please look at our
 <a href="troubleshooting.html">troubleshooting guide</a> if you suspect this is the case.</p>
 </li>
-<li>
-<p><strong>Define the <code>version</code> of your library in <code>build.gradle.kts</code>.</strong> This value will also be
-    included in the release artifact <code>library.properties</code>. The version of your library usually 
-    follows semantic versioning (semver), which uses three numbers separated by dots: 
-    "MAJOR.MINOR.PATCH" (e.g., "1.0.0"). </p>
-<ul>
-<li>MAJOR: Increases when you make incompatible changes.</li>
-<li>MINOR: Increases when you add new features that are backward-compatible.</li>
-<li>PATCH: Increases when you make backward-compatible bug fixes.</li>
-</ul>
-<p>You will update these numbers as you release new versions of your library.</p>
-</li>
 </ol>
-<div class="admonition note">
-<p class="admonition-title">Note</p>
-<p>If you <a href="https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository">release your library on Github</a>,
-the prettyVersion field in your release artifacts will reflect your release tag instead of the <code>version</code> defined in <code>build.gradle.kts</code>, as a helpful automation.</p>
-</div>
 <h2 id="creating-examples">Creating examples</h2>
 <p>Examples help users understand your library’s functionality, it is recommended that you include several clear and well-commented samples sketches in the <code>examples</code> folder.</p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>The example sketch included in this template outputs the image shown on the home page.</p>
 </div>
 <h2 id="creating-the-release-artifacts">Creating the release artifacts</h2>
-<p>If you've already gone through the <a href="getting-started.html#first-steps">Getting started</a> guide, you will have
-already run Gradle tasks, and edited the <code>release.properties</code> file.</p>
 <ol>
-<li>Fill in the file <code>release.properties</code> with information for your library. This information will be
-    used by Gradle to create the <code>library.properties</code> file, which is one of the required release 
-    artifacts, used by the website and Contribution Manager to describe your library. In the file itself,
-    There are comments to guide you. To create just the <code>library.properties</code> file without building the
+<li>Fill in the file <code>release.properties</code> with information for your library. In the file itself,
+    There are comments to guide you. This information will be used by Gradle to create the 
+    <code>library.properties</code> file, which is one of the required release artifacts, used by the website 
+    and Contribution Manager to describe your library. To create just the <code>library.properties</code> file without building the
     library, toggle <code>Tasks</code> &gt; <code>processing</code> and double click <code>writeLibraryProperties</code>. This task will
-    copy all the values in <code>release.properties</code>, and also include the <code>version</code> in your <code>build.gradle.kts</code>
-    file as <code>prettyVersion</code>.</li>
+    copy all the values in <code>release.properties</code>.</li>
 <li><strong>To build the library and create the release artifacts, run the Gradle task <code>buildReleaseArtifacts</code>.</strong>
     This task will create a <code>release</code> folder with needed artifacts. To do this, go to the Gradle menu 
     (elephant), toggle <code>Tasks</code> &gt; <code>processing</code> and double click <code>buildReleaseArtifacts</code>. This task 
@@ -612,6 +592,12 @@ <h2 id="creating-the-release-artifacts">Creating the release artifacts</h2>
     <code>deployToProcessingSketchbook</code>, which will create the release artifacts, and copy them into the 
     sketchbook folder.</li>
 </ol>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+</div>
+<p>If you <a href="https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository">release your library on Github</a>,
+your release tag will be used for the value of the <code>prettyVersion</code> field, overwriting the value for <code>prettyVersion</code> 
+defined in <code>release.properties</code>, as a helpful automation.</p>
 <h2 id="additional-documentation">Additional Documentation</h2>
 <p>See the following guides for more details:</p>
 <ul>

pr-preview/pr-84/release.html

@@ -545,7 +545,7 @@ <h2 id="releasing-on-github">Releasing on Github</h2>
 <div class="admonition important">
 <p class="admonition-title">Important</p>
 <p>The release tag created on Github will be propagated to the release artifacts.
-Specifically the tag, without the leading <code>v</code>, will be used for the <code>prettyVersion</code> in the txt file and <code>library.properties</code> file in the zip. This overwrites the value input for <code>version</code> in the <code>build.gradle.kts</code> file.</p>
+Specifically the tag, without the leading <code>v</code>, will be used for the <code>prettyVersion</code> in the txt file and <code>library.properties</code> file in the zip. This overwrites the value input for <code>prettyVersion</code> in the <code>release.properties</code> file.</p>
 </div>
 <div class="admonition note">
 <p class="admonition-title">Note</p>