You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dynamo offers a vast number of features out of the box and also maintains an extensive package library, to which the community can contribute, that can significantly extend Dynamo's capability.
164
+
This documentation describes how a user can publish a package from Dynamo.
165
+
</p>
166
+
<p>
167
+
The menu option to publish a package can be found at: "Packages > Publish New Package...".
168
+
Clicking this menu item will open a dialog box that will ask for all the information related to the package the user wants to publish.
169
+
</p>
170
+
<h4>Package Name:</h4>
171
+
<p>
172
+
Name of the package you want to publish. This will appear in the library and on the package manager website.
173
+
</p>
174
+
<p>
175
+
<b>Description:</b><br/>
176
+
The description is a great place to add more details about your package, including listing any exceptions and pre-requisites.
177
+
It can also be used to educate users on what the package does and how it can be utilised into their workspaces.
178
+
</p>
179
+
<p>
180
+
<b>Version:</b><br/>
181
+
The version field is split into three sections, major, minor and build, which allows you as a package author to upload new versions of your
182
+
package that follow versioning semantics - Users may want to publish more versions for their packages with new and improved features,
183
+
polish some corners which were left out in the first version, or fix a bug.
184
+
</p>
185
+
<p>
186
+
<b>Group:</b><br/>
187
+
This field can be used to specify a group that a package belongs to such as the company/organization.
188
+
</p>
189
+
<p>
190
+
<b>External Dependency (optional):</b><br/>
191
+
Your package may depend on a host or its API as Dynamo can be integrated with a bunch of different optional
192
+
hosts such as Revit or Civil 3D, so this field can be used to specify which other host(s) your package depends upon.
193
+
</p>
194
+
<p>
195
+
<b>Keywords (optional):</b><br/>
196
+
Some keywords that can be used as tags related to your package. For e.g Generative Design, ML etc.
197
+
</p>
198
+
<p>
199
+
<b>Website (optional):</b><br/>
200
+
Website that may provide the user with more info regarding the package or the organization/author.
201
+
</p>
202
+
<p>
203
+
<b>Repository URL (optional):</b><br/>
204
+
A link to package's repository that can help users to view or contribute to the package development.
205
+
</p>
206
+
<p>
207
+
<b>License (optional):</b><br/>
208
+
A license under which the package is released. Default license : MIT.
209
+
</p>
210
+
<p>
211
+
<b>Package Contents (optional):</b><br/>
212
+
This section includes the right sidebar of the dialog box.
213
+
</p>
214
+
<p>
215
+
<b>Add File:</b><br/>
216
+
Select and add all the files that are related to your package; generally the bin folder, binaries and dependencies are added.
217
+
</p>
218
+
<p>
219
+
<b>Select Node Libraries:</b><br/>
220
+
Select the node libraries/DLLs from the list of added files.
221
+
</p>
222
+
<p>
223
+
After filling in all the required details user can publish the package locally or online.
224
+
When publishing locally the package will be published in the local root directory,
225
+
whereas while publishing online the package will be uploaded to the package manager.
0 commit comments