utopia-project 0.35.0 → 0.35.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ce836aa13bef0faf0023d66ba3c5fcb0dca6447e872df581110221fe38ba5991
-  data.tar.gz: 191dba3b66205f9bf29b4095d53681a70c1a9db1d00698ebacc0a38878306295
+  metadata.gz: cfd904d0661eca52af7af1d7c16cc1e39fc9664dcc6d1b263693a779d7777a06
+  data.tar.gz: f0ab7c6d9c241794d58de46dfaa6db3d0dd44888aebeac0211dcf8e96b7b15c0
 SHA512:
-  metadata.gz: 89c0377b952cd09fafb222248c25bb4d4e16a3a068ce40099c0106bd3ef623321fc5bbedb24e226e24d3ed2aaad13137f4d5d69093ea5520906b93cbd320e43a
-  data.tar.gz: fa29db6a3865b528aeef22bd187db14c9cd737efcd6f8fc202d47857e4b4d3454e19794937e40c1d4ec410010007e3bb2fe9a72c89eafe0da602fe382d63c144
+  metadata.gz: 22229199613c3b999385d16b9ba274e6453929a36b86e832f4699f096dceeeec6b0e6d9201e0a5e2c870fed38ea6f44c76cba5b84c21a7ac16dd0f9b8ce7e186
+  data.tar.gz: a46c96093621d0e759dffd4ee838aaffdb7ba1beb6477ced3fdc00b358fc094f6aa5cd235ee27741147c789bf2b0f2eeec7c4d424477549e11488bd87bffd3be

data/context/documentation-guidelines.md

@@ -0,0 +1,105 @@
+# Documentation Guides
+
+This guide explains how to create and maintain documentation for your project using `utopia-project`.
+
+## Overview
+
+There are two main aspects to consider when creating documentation with `utopia-project`:
+
+1. **Source Code Documentation**: This involves adding documentation directly within your code using special tags.
+2. **Examples & Guides**: This includes creating separate example files and guides to help users understand how to use your project.
+
+### Source Code Documentation
+
+Source code documentation is included adjacent to the code it describes, using special tags to provide structured information. This allows for easy generation of documentation from the source code itself. The `utopia-project` documentation generator uses the `decode` gem (which is documented elsewhere).
+
+However, in short:
+
+- Documentation is expected to be in markdown format.
+- You may embed links to definitions using `{MyClass}` or `{my_method}`.
+- You can use tags:
+  - `@parameters name [Type] Description.`
+  - `@yields {|argument| ...} If a block is given.`
+  - `@returns [Type] Description.`
+- Classes and Modules should typically be described as "Represents a ..." where it makes sense to do so.
+
+In addition, for complex classes that require extra documentation, e.g. `my_class.rb` can have an adjacent `my_class.md` which should have the title `# MyClass` and can include additional details, examples, and usage guidelines.
+
+### Examples & Guides
+
+In addition to source code documentation, it's helpful to provide separate examples and guides to demonstrate how to use your project. This can include:
+
+- Code snippets that illustrate common use cases.
+- Step-by-step tutorials for more complex scenarios.
+
+By providing both inline documentation and separate guides, you can help users understand your project more easily and encourage adoption.
+
+These resources are located in the `guides/` directory of your project, and have the following format:
+
+```
+guides/
+├── links.yaml
+├── documentation-guidelines/
+│   └── readme.md
+├── documentation-guides/
+│   └── readme.md
+├── getting-started/
+│   └── readme.md
+└── github-pages-integration/
+    └── readme.md
+```
+
+The `links.yaml` file comes from the `utopia` framework, and is used to define metadata and ordering of the guides, e.g.
+
+```yaml
+# guides/links.yaml
+getting-started:
+  order: 1
+github-pages-integration:
+  order: 2
+documentation-guides:
+  order: 3
+```
+
+Every guide should start with a brief overview, explaining its purpose and what the user can expect to learn: "This guide explains how to use x to do y." – it should be short and to the point, as it's used as the description of the guide on other pages that link to it.
+
+#### "Getting Started" Guide
+
+Every project should have a "Getting Started" guide that provides an introduction to the project, including the following sections:
+
+~~~markdown
+# Getting Started
+
+This guide explains how to get started with `$project`.
+
+## Installation
+
+Add the gem to your project:
+
+```bash
+$ bundle add $project
+```
+
+## Core Concepts
+
+`$project` has several core concepts:
+
+- A {ruby MyProject::MyClass} which represents the main entry point for using the project.
+
+## Usage
+
+Brief explaination about usage.
+
+### Specific Scenario
+
+More detailed explanation about usage in a specific scenario.
+
+```ruby
+# some example code
+```
+~~~
+
+In the above example:
+
+- "Core Concepts" is optional and should be included if it helps to clarify the usage and structure of the project.
+- "Specific Scenario" only makes sense if there are more than one scenario that is typical.

data/lib/utopia/project/version.rb

@@ -5,6 +5,6 @@
 
 module Utopia
 	module Project
-		VERSION = "0.35.0"
+		VERSION = "0.35.1"
 	end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: utopia-project
 version: !ruby/object:Gem::Version
-  version: 0.35.0
+  version: 0.35.1
 platform: ruby
 authors:
 - Samuel Williams
@@ -132,7 +132,7 @@ files:
 - bake/utopia/project.rb
 - bake/utopia/project/agent/context.rb
 - bake/utopia/project/readme/update.rb
-- context/documentation-formatting.md
+- context/documentation-guidelines.md
 - context/getting-started.md
 - context/github-pages-integration.md
 - context/index.yaml

metadata.gz.sig

@@ -1,3 +1,2 @@
--�m�����ϬI�\6.=���%2���Q���U�C_�4^����$����q�������7�X�FR'�PR�j�I��wN��
-�-Dc��K�?m+�<�,�c"	��́���0OR2���Q=E,/Z���I0���2�'�Kޠs��A�a4�1�+��
-ܑ��#t�[Ҭ����Y!v����+)��n⾒�~��K�h1V(�@�:
��*r쟮<C��'�,�V�e��
+��c�U��߈^������5'
+N�L� ;+�`�	9��^\��r���}zhKY�
͓�-gЃWL�䥕z�Ss�]$r�hG&${]�]��蘒~�g�J0����^ҏ�{����"
�Qx�N-�}=Wc��C����yܧb<W-�Q҇}���,l���[�H�6�[UN�x5���#h�|#a"�Fm<�t���3���+��P6ƫ	Xb�*#�ݺ؀{Ȭ�*�

data/context/documentation-formatting.md

@@ -1,67 +0,0 @@
-# Documentation Formatting
-
-This guide explains the conventions used by `utopia-project` when generating documentation for your project.
-
-## Source Code Documentation
-
-Source code documentation is expected to be in markdown format. This is different from the canonical `RDoc` format used by Ruby. However, using markdown is a good format for standardised documentation across a range of different languages.
-
-### Tags
-
-#### `@parameter`
-
-The `@parameter` tag is used to describe the parameters of a method:
-
-~~~ ruby
-# @parameter x [Integer] The x co-ordinate.
-# @parameter y [Integer] The y co-ordinate.
-def move(x, y)
-	# ...
-end
-~~~
-
-#### `@returns`
-
-The `@returns` tag is used to describe the return type of the definition:
-
-~~~ ruby
-# @returns [Integer] The result of the computation.
-def fib(n)
-	# ...
-end
-~~~
-
-### References
-
-It is possible to insert references in your documentation using curly brackets. In the following example `{Input}` will be expanded relative to the usage, to some symbol named `Input`.
-
-~~~ ruby
-# Frobulates the input, see {Input} for more details.
-def frobulate(input)
-	# ... left to the imagination ...
-end
-~~~
-
-## Examples & Guides
-
-Examples provide structured information to help users understand your project and are located in the `examples/` directory. One sub-directory per example.
-
-### `readme.md`
-
-If an example has a `readme.md` file, it is used as the main source of documentation.
-
-### Source Files
-
-All other source files are listed on the example page. Top level comments with trailing code (segments) are used to help guide the user through the example.
-
-## Diagrams
-
-You can add diagrams formatted using `mermaid.js`.
-
-``` mermaid
-	graph LR;
-			A-->B;
-			A-->C;
-			B-->D;
-			C-->D;
-```