public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Carlos Maniero <carlos@maniero.me>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Carlos Maniero <carlos@maniero.me>
Subject: [PATCH olang 5/5] docs: home page: transform the unfinished software warn into a notice
Date: Sat,  7 Sep 2024 00:35:19 -0300	[thread overview]
Message-ID: <20240907033519.293370-6-carlos@maniero.me> (raw)
In-Reply-To: <20240907033519.293370-1-carlos@maniero.me>

No fool would try to use olang at the current stage. IMO, This
uppercased warning was catching the readers eyes and would distract them
to understand what olang is.

Signed-off-by: Carlos Maniero <carlos@maniero.me>
---
 docs/index.md | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/docs/index.md b/docs/index.md
index 82c4ef3..13aab32 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -1,7 +1,5 @@
 % Introduction
 
-**[WARNING] THIS SOFTWARE IS UNFINISHED AND NOT PRODUCTION READY**
-
 The O language is a system programming language crafted to be remarkably simple
 and flexible. It stands not as a replacement for C, but rather as a
 complementary counterpart, as both can coexist within the same source code. O
@@ -10,6 +8,13 @@ almost predictable machine code.
 
 olang is a deterministic system language that follows tree principles:
 
-- **fights complexity** by providing a simple syntax with a low level of abstraction.
-- **doesn't babysit programmers**, it gives you the freedom of shooting your own foot.
-- **aims easy maintainability** by providing a syntax with a low refactoring overhead.
+- **fights complexity** by providing a simple syntax with a low level of
+  abstraction.
+- **doesn't babysit programmers**, it gives you the freedom of shooting your
+  own foot.
+- **aims easy maintainability** by providing a syntax with a low refactoring
+  overhead.
+
+## Notice
+
+This software is unfinished and not production ready.
-- 
2.34.1


  parent reply	other threads:[~2024-09-07  3:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07  3:35 [PATCH olang 0/5] docs: some improvements on the website Carlos Maniero
2024-09-07  3:35 ` [PATCH olang 1/5] docs: unify manual and site style Carlos Maniero
2024-09-07  3:35 ` [PATCH olang 2/5] docs: include the manual link over the manual Carlos Maniero
2024-09-07  3:35 ` [PATCH olang 3/5] docs: make the olang visuals a w3m like website Carlos Maniero
2024-09-07  3:35 ` [PATCH olang 4/5] docs: prevents the menu items to break line Carlos Maniero
2024-09-07  3:35 ` Carlos Maniero [this message]
2024-09-07 10:38 ` [PATCH olang 0/5] docs: some improvements on the website Johnny Richard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240907033519.293370-6-carlos@maniero.me \
    --to=carlos@maniero.me \
    --cc=~johnnyrichard/olang-devel@lists.sr.ht \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.johnnyrichard.com/olang.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox