can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml
can reuse content by using include files, allowing for consistent
naming across several diagrams. The include files can be standalone
PlantUML too. Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
<pre>
@startuml