From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Websites with drupal and php
Date: Sat, 28 Dec 2024 12:25:48 +0000 [thread overview]
Message-ID: <bWVM_Jug_UGolVjZXLDzr1Q7auo4c0qXUKyiPkU09XyufgVatLCmQ8KMsuRzl_zFwIQnXMQU-bhOxk76Wmdi0zutJTId2Nrf0F9wcstkwlk=@protonmail.com> (raw)
In-Reply-To: <Z26FcC5GX2vqiqM_@lco2>
Sent with Proton Mail secure email.
On Friday, December 27th, 2024 at 10:46 PM, Jean Louis <bugs@gnu.support> wrote:
> * Heime via Users list for the GNU Emacs text editor help-gnu-emacs@gnu.org [2024-12-21 00:00]:
>
> > Have got a work assignment for a website where they are currently
> > using wordpress. Been thinking about drupal with php. What is the
> > Gnu Project current advice for good websites?
>
>
> My personal advice is using GNU Emacs.
>
> Not PHP.
>
> Not Drupal.
>
> Not WordPress.
>
> GNU Emacs 😎
>
> First I was using straight HTML, then asciidoc and SGML back in time,
> simple files and generation of connected website, later somewhere
> 2000-2004 I was using M4 macro processor, which I find very hand for
> HTML pages.
>
> PHP started as a scripting language in 1995, PHP or "Personal Home
> Page" made out of Perl programming language. Later it changed to its
> own programming language.
>
> I find all HTML programming unreliable for any future-proof.
>
> If I would use Common Lisp, I guess it would stay functional even
> after 10 or 30 years. Emacs Lisp is pretty stable over the time,
> though too many changes are coming and it cannot really stand the test
> of the future, to remain stable over time.
>
> m4 as macro processor stays the same! Whatever websites I made with it
> in 2004 they are same now in 2024, imagine!
>
> I would just include files, navigation, footers:
>
> m4_include(basics.m4)
>
> All the templates can be switched easily.
>
> I did not even write HTML, I have used m4 macros for that.
>
> Like this:
> m4_define(`H1',`<h1>$1</h1>')
>
>
> There are many Emacs tools to make website pages. You could use Org
> for example, it generates good pages!
>
> fniessen/org-html-themes: Transform your Org mode files into stunning HTML documents in minutes with our Org mode HTML theme. Elevate your productivity and impress your readers! #orgmode #html #theme #productivity #design
> https://github.com/fniessen/org-html-themes?tab=readme-ov-file
>
> then you could just write Org and export to HTML, job done!
>
> BREAK -- look at this guy:
>
> Emacs Boost Training
> https://emacsboost.com/en/
>
> Org-THTML: An HTML template system for org-mode
> https://juanjose.garciaripoll.com/blog/org-mode-html-templates/index.html
>
> Org Themes collection
> https://olmon.gitlab.io/org-themes/
>
> look there, so many nice templates!
>
> Is that something you can use?
What does the Gnu Project and FSF use for their website?
> I don't use them, I use Org and then convert it to HTML and then use
> ANY HTML template. Nobody even knows it was written in Org
> mode. Though that is not my markup statistics, for website I use
> mostly Markdown. I was one among first on Internet to use Markdown,
> this is because at the time I was heavy user of Asciidoc and m4.
>
> As Website Revision System programmer I have been using many tools,
> that is why it is simple to me to provide mind map on how to proceed:
>
> Think this way:
>
> - you need HTML template; find one;
>
> - you need various pages, you can simply write files;
>
> - all pages must be somehow connected to each other, that means there
> must be navigation for each page;
>
> - make Emacs Lisp to generate all pages by using template and by
> inserting navigation;
>
> Rely on yourself, not on others.
>
> I have used a single Perl program for that, now I am using 🐃 Emacs.
>
> I write a page, press a key, and it gets published.
>
> Doing things my own way always passes the test over time.
>
> Doing the exercise yourself will help you in future.
>
> Basic HTML template is here:
>
> <!DOCTYPE html>
>
> <html lang="⟦ languages_extension ⟧">
>
> <head>
>
> <meta charset="utf-8">
>
> <title>⟦ (xml-escape wrs::title) ⟧</title>
>
> </head>
>
> <body>
>
> ⟦ rcd::text ⟧
> ⟦ after_content ⟧
> ⟦ inquiry ⟧
> </body>
>
> </html>
>
>
> I am using the
>
> RCD Template Interpolation System for Emacs:
> https://hyperscope.link/3/7/1/3/3/RCD-Template-Interpolation-System-for-Emacs.html
>
> As that way I can interpoloate those things like ⟦ languages_extension ⟧
> or ⟦ after_content ⟧ by using variables.
>
> I can insert navigation. It works well for me, I receive leads and
> clients all the time.
>
> --
> Jean Louis
prev parent reply other threads:[~2024-12-28 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 20:58 Websites with drupal and php Heime via Users list for the GNU Emacs text editor
2024-12-27 10:46 ` Jean Louis
2024-12-28 12:25 ` Heime via Users list for the GNU Emacs text editor [this message]
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='bWVM_Jug_UGolVjZXLDzr1Q7auo4c0qXUKyiPkU09XyufgVatLCmQ8KMsuRzl_zFwIQnXMQU-bhOxk76Wmdi0zutJTId2Nrf0F9wcstkwlk=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=bugs@gnu.support \
--cc=heimeborgia@protonmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.