diff options
| -rw-r--r-- | css/base.css | 21 | ||||
| -rw-r--r-- | index.html | 21 |
2 files changed, 42 insertions, 0 deletions
diff --git a/css/base.css b/css/base.css index 9acdaed..0a41b18 100644 --- a/css/base.css +++ b/css/base.css @@ -57,10 +57,14 @@ body { h1, h2, h3 { + /* Put some spacing with the things prior to this header. */ + padding-top: 1em; + /* Bring the headers closer to the text under them, this is a * complementary command with the margin-top in `p` tag styling */ padding-bottom: 0; margin-bottom: 0; + /* Set line-height for headers to prevent overlap when browser is * forced to wrap the words. */ line-height: 1; @@ -73,14 +77,23 @@ p { margin-top: 5px; } +ul, +ol { + /* Put some spacing with the things prior to this header. */ + padding-top: 0; + margin-top: 0; +} + /* Wrap the entire content of the page in this `div` - the navigation * bar is an exception, because of its fixed position. */ #container { /* Prevent additional horizontal spacing in smaller screens */ width: 100%; + /* Center the whole page into a narrow column. Keeps the webpage stylish * and easy to look at in the widest screens. */ max-width: 960px; + /* The container should always have a margin-top high enough to * prevent content overlapping with the navigation bar */ margin: 45px auto 0; @@ -91,6 +104,7 @@ p { /* Make sure `left`, `right`, and `width` values add up to 100% to * help keep the navigation bar in center for big screens */ margin: 0 auto; + /* Make the content a block to to put it in the center of the page */ display: block; } @@ -153,6 +167,7 @@ li > code { /* Stick to the top */ position: fixed; top: 0; + /* Make sure `left`, `right`, and `width` values add up to 100% to * help keep the navigation bar in center for big screens */ margin: 0 auto; @@ -161,8 +176,10 @@ li > code { width: 99%; max-width: 960px; /* same as the `#container` max-width */ margin: 0 auto; + /* Prevent sharp edges on the top navigation bar */ border-radius: 0 0 5px 5px; + /* Keep link texts center-aligned */ text-align: center; background: #030504; @@ -250,6 +267,7 @@ a:hover { * screens as specified at the end of this CSS file */ .banner div { display: inline-block; + /* Keep headers aligned in the middle next to Maneage logo */ vertical-align: middle; text-align: left; @@ -270,6 +288,7 @@ a:hover { min-height: 170px; max-width: 220px; max-height: 220px; + /* Keep headers aligned in the middle next to Maneage logo */ vertical-align: middle; } @@ -314,8 +333,10 @@ footer[role=contentinfo] { margin: 0 auto; max-width: 960px; /* same as the `#container` max-width */ padding: 5px 15px; + /* Prevent sharp edges on the bottom navigation bar */ border-radius: 5px 5px 0 0; + /* Keep link texts center-aligned */ text-align: left; font-size: small; @@ -107,9 +107,30 @@ git checkout -b main <span class="comment"># Make n </p> <p>See the <a href="https://gitlab.com/maneage/project/-/blob/maneage/README-hacking.md#customization-checklist">Customization Checklist</a> in the cloned <code>README-hacking.md</code> file for the next steps to start customizing Maneage for your project. </p> + <h3>Messaging rooms for direct contact</h3> + <p>Maneage uses the <a href="https://en.wikipedia.org/wiki/Matrix_(protocol)">Matrix protocol</a> for fast, robust and free communication between the developers and users. + The top-level Maneage "Space" (which collects the Maneage-related rooms) is available at <code>maneage:matrix.org</code>. The available list of rooms are:</p> + <ul> + <li><code>#maneage-general:matrix.org</code>: The best place for new "Maneagers".</li> + <li><code>#maneage-make:matrix.org</code>: Discussions specific to <a href="https://en.wikipedia.org/wiki/Make_(software)">GNU Make</a> within Maneage (Make is the core workflow manager in Maneage).</li> + <li><code>#maneage-latex:matrix.org</code>: Discussions specific to <a href="https://en.wikipedia.org/wiki/LaTeX">LaTeX</a> within Maneage (LaTeX is the type-setting system to produce the final report/PDF).</li> + <li><code>#maneage-dev:matrix.org</code>: Development discussions in Maneage (on the core infrastructure; maybe too technical for early Maneagers).</li> + </ul> + <i>How can I access Matrix-based messaging rooms?</i> There are <a href="https://matrix.org/clients/">many clients</a> for the Matrix protocol for web-based, smartphone or Desktop (GUI or command-line). + One suggested client can be <a href="https://element.io/get-started">Element</a>, which has both a web-based interface (only requiring a modern browser), a GUI desktop application, or smartphone apps. + If you just want to see the message rooms above (without logging-in), you can take the steps below. + Later, you can register a Matrix protocol account for yourself using the "Create Account" button the first item below. + <ol> + <li>Go to Element's <a href="https://element.io/get-started">Get started</a> page.</li> + <li>Click on the <b>Launch Element Web</b> button, then the <b>Explore rooms</b> button.</li> + <li>In the search box, put the identifier of the room (for example <code>#maneage-general:matrix.org</code>).</li> + <li>In the search results, click on "preview" infront of your desired room, to see the latest discussions in the room.</li> + </ol> +<!-- <h3>Submitting bugs and suggesting new features</h3> <p>Development discussions (like list of existing <a href="https://savannah.nongnu.org/bugs/?group=reproduce">bugs</a> and <a href="https://savannah.nongnu.org/task/?group=reproduce">tasks</a>) are currently maintained in <a href="https://savannah.nongnu.org/projects/reproduce/">GNU Savannah</a>. You can <a href="https://savannah.nongnu.org/account/register.php">register in GNU Savannah</a> to <a href="https://savannah.nongnu.org/bugs/?func=additem&group=reproduce">submit a bug</a> or <a href="https://savannah.nongnu.org/task/?func=additem&group=reproduce">submit a task</a>, or comment on an existing bug or task. If you want to submit a general issue without registering on Savannah, you can <a href="https://savannah.nongnu.org/support/?func=additem&group=reproduce">submit an item</a>.</p> +--> <h3>Merge/Pull requests</h3> <p>As you continue customizing Maneage for your own project, you will notice generic improvements that can be useful for other projects too. In such cases, please send us those changes to implement in the core Maneage branch and let them propagate to all projects using it. |