¶ Navigating and contributing to the wiki
¶ Chalmers Aerospace Society for Advanced Rocketry
Welcome to the CAESAR wiki!
Hopefully this is one of the first documents that you read, which will provide you with the necessary information on how to navigate and/or contribute to the wiki page.
This wiki is for team members only. If you’d like to access it, follow the instructions below.
- Read this page first.
- Look through the wiki.js user guide.
- Create an account. You must create an account using your email adress from Chalmers or CAESAR. Contact the board or your team leader if you want to use a different email address.
- Creating an account does not automatically grant access. If you're part of the team, you'll get read and write permissions once a board member or team leader has added you to the appropriate group.
- When you think you have been approved, you need to log out and log in again.
¶ Building our knowledge base
The purpose of the CAESAR wiki is to aggregate information regarding rocketry. We thought that the best way to do this is to use a wiki format, where links, indexing and ease of editing are utilized to improve information sharing.
Seeing as we want the wiki to scale with the growth of CAESAR, following a standard on how to structure and organize contributions will be necessary. Here is a list on how this could be accomplished:
-
General: A flexible space for organizational material that doesn't naturally belong in the other folders. Even though it is labeled General, avoid cluttering it with too much information, or at least make sure to keep it tidy.
-
Projects: To organize all CAESAR-related technical, design, and research efforts into dedicated project folders. Each project has its own space. Some projects may extend across multiple academic years. By keeping them in a separate Projects folder, we ensure that all relevant files and documentation stay together and are not split between different yearly folders. This structure allows projects to evolve at their own pace, independent of changes in board members or organizational structure from year to year.
-
Resources: The idea behind having a resources folder is to collect information that will most likely remain static over time, or is independent of specific projects. This folder could contain topics such as:
- How to write a technical report
- How to get started with CAD
- How to manage a project
¶ Avoid duplicate content
Ensure that each topic in the wiki has a single authoritative page where it is documented in full. Do not duplicate the same content across multiple pages, as this leads to inconsistencies and maintenance issues. When a topic needs to be mentioned elsewhere, provide a brief reference or summary and link to the main page instead. This principle keeps the wiki consistent, maintainable, and reliable over time.
¶ Create and edit pages
You never need to create folders before adding new pages. Instead, pages are created directly at any path you choose, and the “folders” are handled automatically.
¶ Create a page
To create a page at /projects/phobos/propulsion, you don’t have to manually create the projects and phobos folders — these are inferred automatically.
¶ Create a landing page
For multi-level paths, it’s often useful to create a landing page at each virtual folder level.
For instance, if you have a page at /projects/phobos, you should also create a page at /projects. This ensures that when you click the projects breadcrumb link on /projects/phobos, you are taken to the /projects page.
¶ Site tree
The title of each level comes from its corresponding page. Creating the following pages:
-
/projectswith title Projects -
/projects/phoboswith title Phobos -
/projects/phobos/propulsionwith title Propulsion
will generate a site tree like this:
- Projects
- Phobos
- Propulsion
- Phobos
On the Propulsion page, the breadcrumb would look like:
/ projects / phobos / propulsion
with each link pointing to its respective page.
¶ How to write page paths
When creating or moving a page, it's important to follow a consistent and clear structure for the page path. This path determines both the URL and the page’s position in the site hierarchy.
- Use only letters, numbers and hyphens (-). Avoid using other special characters.
- Always use lowercase letters.
- Start with a letter.
- Use hyphens (-) to separate words.
- Choose terms that clearly indicate the content of the page.
¶ You should use tags
Tags group related pages in ways that are difficult to achieve using a traditional folder structure. They improve searchability by providing an effective mechanism for filtering pages. Unlike page titles, which should be fairly specific, tags are more general and can capture multiple aspects of a page’s content.
For example, if a page primarily concerns “propulsion” but also includes information about a parachute, it may be appropriate to also assign the tag “recovery” or “parachute”. To ensure consistency in tagging, we follow the same general principles used for naming pages.
- Use only letters, numbers and hyphens (-). Avoid using other special characters.
- Always use lowercase letters.
- Start with a letter.
- Use hyphens (-) to separate words.
- Choose tags that indicate the overall content of the page.
¶ Example: File tree
Here is an example on how the file tree could be structured:
C:.
├───general
│ └───the-board
│ └───history
│───projects
│ ├───phobos
│ │ ├───avionics
│ │ │ └───flight-computer
│ │ ├───euroc-2025
│ │ ├───euroc-2026
│ │ ├───ground-support
│ │ ├───pr
│ │ ├───propulsion
│ │ │ └───engine
│ │ ├───recovery
│ │ └───structures
│ │ └───frame
│ ├───pluto
│ │ ├───avionics
│ │ │ └───flight-computer
│ │ ├───euroc-2026
│ │ ├───ground-support
│ │ ├───pr
│ │ ├───propulsion
│ │ │ └───engine
│ │ ├───recovery
│ │ └───structures
│ │ └───frame
│ ├───rhea
│ │ ├───avionics
│ │ │ └───flight-computer
│ │ ├───euroc-2027
│ │ ├───ground-support
│ │ ├───pr
│ │ ├───propulsion
│ │ │ └───engine
│ │ ├───recovery
│ │ └───structures
│ │ └───frame
└───resources
├───how-tos
│ ├───chemistry
│ ├───engineering
│ │ ├───electrical
│ │ │ └───kicad
│ │ └───mechanical
│ │ └───cad
│ ├───math
│ ├───physics
│ │ └───simulate-cfd
│ └───programming
│ ├───cpp
│ └───git
└───university-resources
└───makerspace-tools