From c3a19eb2087679bb536a476a5d4ae607c12fdd28 Mon Sep 17 00:00:00 2001 From: Bryan Ashby Date: Sun, 12 Jul 2020 13:58:46 -0600 Subject: [PATCH] Slight doc update on message conf/areas --- docs/messageareas/configuring-a-message-area.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/messageareas/configuring-a-message-area.md b/docs/messageareas/configuring-a-message-area.md index 011e9497..444cb091 100644 --- a/docs/messageareas/configuring-a-message-area.md +++ b/docs/messageareas/configuring-a-message-area.md @@ -1,15 +1,17 @@ --- layout: page -title: Configuring a Message Area +title: Message Base --- -## Message Conferences -**Message Conferences** and **Areas** allow for grouping of message base topics. +## General Information +In ENiGMA½, a message base is divided into two logical grouping components: **Message Conferences** and **Areas**. Message conferences are top level containers while areas are for a specific topic. Messages are always stored internally with a area tag. ## Conferences Message Conferences are the top level container for *1:n* Message *Areas* via the `messageConferences` block in `config.hjson`. A common setup may include a local conference and one or more conferences each dedicated to a particular message network such as fsxNet, ArakNet, etc. Each conference is represented by a entry under `messageConferences`. Each entries top level key is it's *conference tag*. +:information_source: It is **highly** recommended to use snake_case style message *conference tags* and *area tags*! + | Config Item | Required | Description | |-------------|----------|-------------| | `name` | :+1: | Friendly conference name |