emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Bastien Guerry <bzg@gnu.org>
Cc: Ihor Radchenko <yantar92@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] worg-setup.org is outdated
Date: Tue, 14 Jun 2022 08:32:06 +1000	[thread overview]
Message-ID: <87czfcupve.fsf@gmail.com> (raw)
In-Reply-To: <87y1y0od9e.fsf@gnu.org>


Bastien Guerry <bzg@gnu.org> writes:

> Hi Ihor,
>
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> Sorry. worg-setup.org is outdated. Bastien, could you update it?
>
> Done, thanks for the heads up.

Thanks Bastien, that will help!

Just a couple of questions regarding all of this (really just
background and to anyone who may have the knowledge, not just Bastien)

Is there any reason we don't use a CSS framework, like bulma or
tailwind to manage the CSS? I know that using JS can be an issue, but
what about a CSS only framework with an MIT license? This would make it
*much* easier to have a site which is both responsive and looks good on
different sized displays, is accessibility compliant, works well across
different browsers and is easier to maintain while still avoiding
inclusion of JS (Ironically, I know JS a lot better than CSS!). 

I'm going to see if I can get a local copy of worg running so that I
have an environment to work with. However, one thing which occurs to me
is that it might be quite nice if we also had a dev site in addition to
the prod site. It should be possible to setujp something with CI such
that you could deploy to a 'dev' url on orgmode.org rather than the
production one. This would make testing of patches etc much easier. It
would also mean I could do the work I'm looking at, deploy to dev site,
ask for feedback on the list, review and later deploy to prod site
without affecting the prod site until we are ready. To do this, it would
be necessary to have Bastien (or someone with the necessary access)
assistance to modify server configurations (like web server config). 

Finally, Bastien and others who may have worked on worg previously, if
yuou have any notes or points which you think it would help for me to
know, please feel free to send them through directly. While I've done a
bit of HTML and CSS in the past, I've only ever used org mode for very
simple/minor HTML output and usually for my own personal consumption.
I've never taken advantage of the publishing side of org. 


  reply	other threads:[~2022-06-13 23:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 21:51 [accessibility] worg obscures text Samuel Wales
2022-06-12 19:35 ` Rudolf Adamkovič
2022-06-13  0:22 ` Tim Cross
2022-06-13  0:34   ` Ihor Radchenko
2022-06-13  2:16     ` Tim Cross
2022-06-13  5:30       ` [BUG] worg-setup.org is outdated (was: [accessibility] worg obscures text) Ihor Radchenko
2022-06-13  5:44         ` Tim Cross
2022-06-13  6:14           ` Timothy
2022-06-13 14:21           ` [BUG] worg-setup.org is outdated Bastien Guerry
2022-06-13 14:21         ` Bastien Guerry
2022-06-13 22:32           ` Tim Cross [this message]
2022-06-14  0:57             ` Ihor Radchenko
2022-06-14  1:08               ` Tim Cross
2022-06-14  1:37                 ` Ihor Radchenko
2022-06-14  1:51                   ` Tim Cross
2022-06-14  2:18                     ` Ihor Radchenko
2022-06-14  2:46                       ` Tim Cross
2022-06-14  2:59                         ` Ihor Radchenko
2023-01-02 10:40                 ` Ihor Radchenko
2023-01-02 20:03                   ` Tim Cross
2023-01-03 11:01                     ` Ihor Radchenko
2023-01-04 10:21                     ` [TASK] Enhance Worg HTML styling (was: [BUG] worg-setup.org is outdated) Bastien Guerry
2023-01-04 10:50                       ` Alain.Cochard
2023-01-04 22:43                         ` Tim Cross
2023-01-05 14:07                           ` Alain.Cochard
2023-01-05 15:41                             ` Tim Cross
2023-01-05 20:18                               ` [TASK] Enhance Worg HTML styling Leo Butler
2023-01-06  1:23                                 ` Tim Cross
2022-06-13  5:37       ` [accessibility] worg obscures text Max Nikulin
2022-06-16  3:22 ` Tim Cross
2022-06-16 23:30   ` Samuel Wales

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87czfcupve.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).