Added first batch of changes.

Author: lvicoun

articles/journalctl.asm.xml

@@ -137,10 +137,12 @@ You must have &sudo; privileges.
 </variablelist>
 </abstract>
 </merge>
-<module renderas="section" resourceref="_journal-about-journald"/>
+<module renderas="section" resourceref="_journal-about-journald">
+  <module renderas="section" resourceref="_journald-configure"/>
+  </module>
 <module renderas="section" resourceref="_journald-filter-journals"/>
 <module renderas="section" resourceref="_journalctl-usage"/>
-<module renderas="section" resourceref="_journald-configure"/>
+
 <module renderas="section" resourceref="_systemd-journald-troubleshooting"/>
 <module resourceref="_legal"/>
 <module resourceref="_gfdl">

concepts/journal-about-journald.xml

@@ -16,11 +16,22 @@
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xmlns:trans="http://docbook.org/ns/transclusion">
   <info>
-    <title>About journald</title>
+    <title>About <literal>journald</literal></title>
     <meta name="maintainer" content="[email protected]" its:translate="no"/>
     <abstract>
       <para>
-        <command>systemd</command> uses <command>journald</command> as its logging system. The <command>systemd-journald</command> service is enabled by default.</para>
+        <command>journald</command> is a &systemd; service responsible for collecting, indexing, and storing log data. The collected events include  kernel messages, initrd (initial RAM disk) messages,
+        service startup/shutdown, application events, and authentication and session data.
+      </para>
+    </abstract>   
+  </info>
+  <para>
+    On &productname; the <literal>systemd-journald</literal> service is enabled and started by
+    default. The service logs the data into the journal described in <xref linkend="journal-what-it-is"./>
+    </para>
+        
+        
+        as its logging system. The <command>systemd-journald</command> service is enabled by default.</para>
     <para>All system events are written to the journal, a system service managed by <command>systemd-journald</command> service. This allows you to search and manage all system logs. It collects and stores logging data by maintaining structured indexed journals based on logging information received from the kernel, user processes, standard input, and system service errors. The journal records nearly every type of event generated on the system, including kernel messages, initrd (initial RAM disk) messages, service startup/shutdown, application events, and authentication and session data. Journal allows centralization and unification of logs from all sources, and it records events in structured manner which in turn helps identifying errors and in crash recovery.</para>
    <para><command>journalctl</command> is the command-line tool to view and analyze the logs from the <command>systemd-journald</command> service.</para></abstract>
 

concepts/journal-structure.xml

@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- This file originates from the project https://github.com/openSUSE/doc-kit -->
+<!-- This file can be edited downstream. -->
+<!DOCTYPE topic
+[
+  <!ENTITY % entities SYSTEM "../common/generic-entities.ent">
+    %entities;
+]>
+<!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> -->
+<!-- point back to this document with a similar comment added to your legacy doc piece -->
+<!-- refer to README.md for file and id naming conventions -->
+<!-- metadata is dealt with on the assembly level -->
+<topic xml:id="journal-what-it-is"
+ role="concept" xml:lang="en"
+ xmlns="http://docbook.org/ns/docbook" version="5.2"
+ xmlns:its="http://www.w3.org/2005/11/its"
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:trans="http://docbook.org/ns/transclusion">
+  <info>
+    <title>About journal</title><!-- can be changed via merge in the assembly -->
+    <!--add author's email address-->
+    <meta name="maintainer" content="[email protected]" its:translate="no"/>
+    <abstract><!-- can be changed via merge in the assembly -->
+      <para>
+       Journal is a  centralization and unification of logs from all sources, and it stores events in structured manner which in turn helps identifying errors and in crash recovery.
+      </para>
+    </abstract>
+  </info>
+  <section xml:id="journal-what-it-is-location">
+    <title>Where can I find the journal?</title>
+    <para>
+      By default, <literal>journald</literal> stores the collected data in the volatile memory in
+      <filename>/run/log/journal</filename>, so after reboot the data is lost.
+    </para>
+  </section>
+  <section xml:id="journal-what-it-is-structure">
+    <title>The structure of the journal</title>
+    <para>
+      A paragraph of text, answering the question above and explaining the
+      mechanism behind foo bar.
+    </para>
+    
+  </section>
+</topic>