Merge pull request #1 from UNFDanmark/main

[Added] Placeholder project

wiki/Writerside/c.list

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE categories
+        SYSTEM "https://resources.jetbrains.com/writerside/1.0/categories.dtd">
+<categories>
+    <category id="wrs" name="Writerside documentation" order="1"/>
+</categories>

wiki/Writerside/cfg/buildprofiles.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE buildprofiles SYSTEM "https://resources.jetbrains.com/writerside/1.0/build-profiles.dtd">
+<buildprofiles xsi:noNamespaceSchemaLocation="https://resources.jetbrains.com/writerside/1.0/build-profiles.xsd"
+               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+
+    <variables></variables>
+    <build-profile instance="in">
+        <variables>
+            <noindex-content>true</noindex-content>
+        </variables>
+    </build-profile>
+
+</buildprofiles>

wiki/Writerside/cfg/glossary.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE terms SYSTEM "https://resources.jetbrains.com/writerside/1.0/glossary.dtd">
+<terms>
+    <term name="foo">
+        Description of what "foo" is.
+    </term>
+</terms>

wiki/Writerside/in.tree

@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE instance-profile
+        SYSTEM "https://resources.jetbrains.com/writerside/1.0/product-profile.dtd">
+
+<instance-profile id="in"
+                 name="GDC Wiki"
+                 start-page="roles.md">
+
+    <toc-element topic="roles.md">
+        <toc-element topic="Empty-MD-Topic.md">
+            <toc-element topic="Unity-project.md"/>
+            <toc-element topic="Git-setup.md"/>
+            <toc-element topic="Install-Script.md"/>
+            <toc-element topic="Bloker-webside-lokalt.md"/>
+        </toc-element>
+    </toc-element>
+</instance-profile>

wiki/Writerside/topics/Bloker-webside-lokalt.md

@@ -0,0 +1,3 @@
+# Bloker webside lokalt
+
+Start typing here...

wiki/Writerside/topics/Empty-MD-Topic.md

@@ -0,0 +1,103 @@
+# Teknisk Ansvarlig
+## Opgaver før Campen
+
+1. **Aftal lån/leje af computere**
+    - Samarbejd med koordinator
+    - Kontakt Aage (AAU kontakt) i god tid
+2. **Udstyr til faggrupperne**
+    - Aftal hvem der står for udstyr (recorders, headphones, usbstik, mus og tastatur)
+3. **Tjek af computere**
+    - 2D: Åbne Krita, teste pen
+    - 3D: Specificerede testopgaver
+    - Lyd: Specificerede testopgaver
+    - Programmering: Unity projekt åbner, Rider fungerer
+4. **Forberedelse af software**
+    - Custom Windows ISO eller script til download af programmer
+    - Installerede programmer aftales med faglig ansvarlig
+    - URP templated Unity projekt med ren asset folder
+    - Test push på deltager computere
+5. **Opsætning af Git**
+    - Forbered git oplæg
+    - Opsæt git repositories (brug GDC-Teknisk konto)
+    - Navngivningsmønster: GDC202Y-GRN (e.g. GDC2023-GR1)
+    - Programmering: GDC202Y-TeachingProgramming, GDC202Y-TeachingProgrammingTraining
+6. **Internet adgang**
+    - Aftal internet adgang på campen
+7. **Dokumentation**
+    - Dokumenter problemløsning for campen
+    - Research automatiske reminders i Google Chats
+8. **Git Oplæg**
+    - Team opdelt git oplæg
+    - Undersøg restriktioner af download på deltagernes computer
+
+## Opgaver under Campen
+
+1. **Opsætning af computere**
+    - Opsætning og test af software og udstyr
+    - Git oplæg
+2. **Support**
+    - Hjælp med git problemer
+    - Dokumenter problemløsning
+    - Løbende tjek for push og builds
+3. **Eksport dag**
+    - Sørg for 1366x768 spil opløsning
+    - Sørg for eksport af spil (description.txt, icon.png)
+    - Sørg for at build version 1 fungerer
+    - Løbende afsluttende run for ekstra ændringer
+    - Skærmopløsning skal passe
+    - Web-upload af spil: tal med SDO og DKA
+
+## Opgaver efter Campen
+
+1. **Aflevering af udstyr**
+    - Aflever lånte/lejede computere
+2. **Opdatering og Dokumentation**
+    - Opdater rolleguide
+    - Dokumenter problemløsning
+
+## Git Oplæg
+
+- Undgå tekniske detaljer om metafiler og merge errors
+- Forklar hvad merge errors er og hvordan man identificerer dem
+- Vigtighed af kommunikation og pull før arbejde
+
+## Eksempler på Teknisk Problemer Under Campen
+
+- Flere arbejder på samme fil
+- Unity crashes: find backup scener
+
+## Programmer og Drivers Installeret i 2024
+
+- Unity Hub, Unity LTS
+- Git, Github CLI, Github Desktop
+- Jetbrains Rider, Krita, Piskel
+- Wacom Drivers (Wacom Intuos Draw)
+- Blender, Ableton Live 11, Audible, Asio4all
+- Google Chrome
+
+## Install Script
+
+- PowerShell: [GDC-Scripts](https://github.com/UNFDanmark/GDC-Scripts)
+
+## Tilføjelser
+
+1. **Gitignore**
+    - Placering: /git-root/TheUnityProject/.gitignore
+2. **Ableton Licenser**
+    - Brugerspecifikke, én gang per computer, test med VM
+3. **Aage (AAU Kontakt)**
+    - Kontakt Aage i god tid ved lån af computere
+4. **URP Graphics in Unity**
+    - Placeholder
+5. **Commit Reminders**
+    - Windows commit reminders hver time (hvis muligt)
+6. **Custom ISO**
+    - Optimalt med en custom ISO med alle programmer og opsætning
+7. **Text Mesh Pro Import**
+    - Placeholder
+8. **External Tool Rider**
+    - Unity's external tool sat til Rider på alle computere
+9. **Git Hook Reminder**
+    - Reminder til arrangør ved merge error
+10. **Gitforedrag**
+- Forklar commit, pull, push

wiki/Writerside/topics/Git-setup.md

@@ -0,0 +1,3 @@
+# Git setup
+
+Start typing here...

wiki/Writerside/topics/Install-Script.md

@@ -0,0 +1,3 @@
+# Install Script
+
+Start typing here...

wiki/Writerside/topics/Unity-project.md

@@ -0,0 +1,3 @@
+# Unity project
+
+Start typing here...

wiki/Writerside/topics/roles.md

@@ -0,0 +1,79 @@
+# Arrangør roller
+
+<!--Writerside adds this topic when you create a new documentation project.
+You can use it as a sandbox to play with Writerside features, and remove it from the TOC when you don't need it anymore.-->
+
+## Add new topics
+You can create empty topics, or choose a template for different types of content that contains some boilerplate structure to help you get started:
+
+![Create new topic options](new_topic_options.png){ width=290 }{border-effect=line}
+
+## Write content
+%product% supports two types of markup: Markdown and XML.
+When you create a new help article, you can choose between two topic types, but this doesn't mean you have to stick to a single format.
+You can author content in Markdown and extend it with semantic attributes or inject entire XML elements.
+
+## Inject XML
+For example, this is how you inject a procedure:
+
+<procedure title="Inject a procedure" id="inject-a-procedure">
+    <step>
+        <p>Start typing and select a procedure type from the completion suggestions:</p>
+        <img src="completion_procedure.png" alt="completion suggestions for procedure" border-effect="line"/>
+    </step>
+    <step>
+        <p>Press <shortcut>Tab</shortcut> or <shortcut>Enter</shortcut> to insert the markup.</p>
+    </step>
+</procedure>
+
+## Add interactive elements
+
+### Tabs
+To add switchable content, you can make use of tabs (inject them by starting to type `tab` on a new line):
+
+<tabs>
+    <tab title="Markdown">
+        <code-block lang="plain text">![Alt Text](new_topic_options.png){ width=450 }</code-block>
+    </tab>
+    <tab title="Semantic markup">
+        <code-block lang="xml">
+            <![CDATA[<img src="new_topic_options.png" alt="Alt text" width="450px"/>]]></code-block>
+    </tab>
+</tabs>
+
+### Collapsible blocks
+Apart from injecting entire XML elements, you can use attributes to configure the behavior of certain elements.
+For example, you can collapse a chapter that contains non-essential information:
+
+#### Supplementary info {collapsible="true"}
+Content under a collapsible header will be collapsed by default,
+but you can modify the behavior by adding the following attribute:
+`default-state="expanded"`
+
+### Convert selection to XML
+If you need to extend an element with more functions, you can convert selected content from Markdown to semantic markup.
+For example, if you want to merge cells in a table, it's much easier to convert it to XML than do this in Markdown.
+Position the caret anywhere in the table and press <shortcut>Alt+Enter</shortcut>:
+
+<img src="convert_table_to_xml.png" alt="Convert table to XML" width="706" border-effect="line"/>
+
+## Feedback and support
+Please report any issues, usability improvements, or feature requests to our
+<a href="https://youtrack.jetbrains.com/newIssue?project=WRS">YouTrack project</a>
+(you will need to register).
+
+You are welcome to join our
+<a href="https://jb.gg/WRS_Slack">public Slack workspace</a>.
+Before you do, please read our [Code of conduct](https://plugins.jetbrains.com/plugin/20158-writerside/docs/writerside-code-of-conduct.html).
+We assume that you’ve read and acknowledged it before joining.
+
+You can also always email us at [[email protected]](mailto:[email protected]).
+
+<seealso>
+    <category ref="wrs">
+        <a href="https://plugins.jetbrains.com/plugin/20158-writerside/docs/markup-reference.html">Markup reference</a>
+        <a href="https://plugins.jetbrains.com/plugin/20158-writerside/docs/manage-table-of-contents.html">Reorder topics in the TOC</a>
+        <a href="https://plugins.jetbrains.com/plugin/20158-writerside/docs/local-build.html">Build and publish</a>
+        <a href="https://plugins.jetbrains.com/plugin/20158-writerside/docs/configure-search.html">Configure Search</a>
+    </category>
+</seealso>

wiki/Writerside/v.list

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE vars SYSTEM "https://resources.jetbrains.com/writerside/1.0/vars.dtd">
+<vars>
+    <var name="product" value="Writerside"/>
+</vars>

wiki/Writerside/writerside.cfg

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE ihp SYSTEM "https://resources.jetbrains.com/writerside/1.0/ihp.dtd">
+
+<ihp version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+     xsi:noNamespaceSchemaLocation="https://resources.jetbrains.com/writerside/1.0/writerside-cfg.xsd">
+    <topics dir="topics"/>
+    <images dir="images" web-path="images"/>
+    <categories src="c.list"/>
+    <vars src="v.list"/>
+    <instance src="in.tree"/>
+</ihp>