From: Carlos Maniero <carlos@maniero.me>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Carlos Maniero <carlos@maniero.me>
Subject: [PATCH olang 0/5] docs: some improvements on the website
Date: Sat, 7 Sep 2024 00:35:14 -0300 [thread overview]
Message-ID: <20240907033519.293370-1-carlos@maniero.me> (raw)
Apart of the first patch, all patches are independent (I believe). The
main point is to make the website even cleaner and simple. Almost like
accessing it from the w3m and other small adjustments.
Carlos Maniero (5):
docs: unify manual and site style
docs: include the manual link over the manual
docs: make the olang visuals a w3m like website
docs: prevents the menu items to break line
docs: home page: transform the unfinished software warn into a notice
docs/Makefile | 6 ++-
docs/index.md | 15 ++++---
docs/manual/Makefile | 2 +-
docs/manual/_header.html | 15 +++----
docs/{manual => }/style.css | 33 ++++++++++------
docs/template.html | 78 +++----------------------------------
6 files changed, 50 insertions(+), 99 deletions(-)
rename docs/{manual => }/style.css (77%)
base-commit: ffd6333175b2c49996731bcf0d224b4f9cac760c
--
2.34.1
next 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 Carlos Maniero [this message]
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 ` [PATCH olang 5/5] docs: home page: transform the unfinished software warn into a notice Carlos Maniero
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-1-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