Commit cf4334bc authored by Erik Huelsmann's avatar Erik Huelsmann
Browse files

Merge branch 'master' into 'master'

Added support for .lisp files in content/;  Added more instructions in README.md.

See merge request clo/cl-site!53
parents 089d3e20 c55e4fdb
......@@ -8,3 +8,6 @@ auto-save-list
# Output files
output/
system-index.txt
content/newsbox.html
content/about.html
*.dx64fsl
......@@ -24,7 +24,14 @@ the `index.html` page - defining the site's front page
- is located in `content/` as well as any images that
are included on the front page but not included on any
template content. Referred content, such as stylesheets,
scripts and images are located in `content/static/*`.
scripts and images are located in `content/static/*`
The `content/` directory can contain both `html` files and `lisp`
files. `html` files are processed with the template stuff directly
into the `output/` directory. `lisp` files are expected to have a call
to `cl-site:add-content` as their toplevel form, which takes arguments
of `:headers-plist` and `html-string`. See `content/about.lisp` for a
reference example.
If a file by the same name is stored in both
`layout/static/` and `content/static/`, then the one
......@@ -35,6 +42,11 @@ in `layout/static/` takes precedence.
* CL-MUSTACHE for HTML templating
* CL-YAML for YAML "header" parsing
* CLOSER-MOP (because...?)
* CL-WHO for LHTML processing
* MARKDOWN.CL for Markdown processing
(these are all called out in the cl-site.asd file and will be fetched
automatically by Quicklisp)
## Execution
......@@ -52,12 +64,33 @@ Among them:
### From Lisp ###
Load with this command:
(The following assumes you have a reasonably recent Quicklisp loaded)
Either (in one fell swoop):
(load ".../cl-site/build.lisp") ;; replace with your actual path to cl-site/
Or (step by step):
First, make sure your `cl-site/` directory (the directory containing
this file) is pushed onto `ql:*local-project-directories*` or you have
this directory moved or linked under your `quicklisp/local-projects/`
directory (see `build.lisp` for example of how to push onto
`ql:*local-project-directories*`).
Then, load the system with this command:
(ql:quickload :cl-site)
To generate the site:
(cl-site::make-site)
(cl-site:make-site)
The output files will be generated in the `output/` directory.
To clean any old files from output/ directory:
(cl-site:make-clean)
(push (uiop:getcwd) quicklisp:*local-project-directories*)
(in-package :cl-user)
(push (make-pathname :defaults *load-truename* :name nil :type nil)
quicklisp:*local-project-directories*)
(ql:quickload :cl-site)
(cl-site::make-site (merge-pathnames "output/" (uiop:getcwd)))
(cl-site::make-site)
......@@ -8,9 +8,7 @@
:author "C. Yang & Common-Lisp.Net maintainers"
:licence "TBD"
:description "Static site generator for common-lisp.net, written in CL"
:depends-on (:cl-mustache :plump :markdown.cl :closer-mop :cl-yaml)
:depends-on (:cl-mustache :plump :markdown.cl :closer-mop :cl-who :cl-yaml)
:components ((:module source
:pathname ""
:serial t
......@@ -19,6 +17,7 @@
(:file "helpers")
(:file "process")
(:file "main")))
(:module package
:pathname ""
:components ((:file "package"))))
......
title: Common-Lisp.net | About
---
<h1><i class="far fa-question-circle"></i>&nbsp;About Common-Lisp.net</h1>
<p> Common-Lisp.net provides hosting for projects and user groups
related to the programming language Common Lisp.
</p>
<p>The site is run under the governance of the <a
href="http://www.cl-foundation.org/">Common Lisp Foundation</a> and
maintained mostly by a committee of volunteers. <a
href="/contribute">Please consider donating</a>.</p>
<p>Its source is hosted
on <a href="https://gitlab.common-lisp.net/clo/cl-site">gitlab.common-lisp.net</a>.
</p>
<p>If you want to request a project, <a href="/project-intro">read
this document</a>.</p>
<p>If you have questions, suggestions or comments about this site or
you simply wish to reach the current maintainers, <a
href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel">email
this mailinglist</a>.</p>
<p>The documentation, procedures, feature requests etc are located in
our Trac instance: <a href="http://trac.common-lisp.net/clo">clo's
Trac</a>.</p>
<h2>Maintainance</h2>
<p>Since many years <a href="/">Common-Lisp.net</a> has been run
by a number of volunteers.</p>
<h3>Currently active maintainers</h3>
<ul>
<li>Mark Evenson</li>
<li>Erik Huelsmann</li>
<li>Mariano Montone</li>
</ul>
<h3>Previous maintainers</h3>
<ul>
<li>Erik Enge</li>
<li>Drew Crampsie</li>
<li>Hans H&uuml;bner</li>
<li>Cheryl Yang</li>
<li>Mario S. Mommer</li>
</ul>
(in-package :cl-site-content)
(add-content
:headers-plist (list :|title| "Common-Lisp.net | About")
:html-string
(with-cl-who-string (:indent t)
(:h1 ((:i :class "far fa-question-circle")) " About Common-Lisp.net")
(wmd "
Common-Lisp.net provides hosting for projects and user groups related to the programming language Common Lisp.
The site is run under the governance of the [Common Lisp
Foundation](http://www.cl-foundation.org) and maintained mostly by a
committee of volunteers. [Please consider donating](/contribute).
Its source is hosted on
[gitlab.common-lisp.net](https://gitlab.common-lisp.net/clo/cl-site).
If you want to request a project, read [this
document](/project-intro).
If you have questions, suggestions or comments about this site or you
simply wish to reach the current maintainers, email [this mailing
list](http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel).
The documentation, procedures, feature requests etc are located in our
Trac instance: [clo's Trac](http://trac.common-lisp.net/clo).")
(:h2 "Maintainance")
(wmd "
Since many years [Common-Lisp.net](/) has been run by a number of
volunteers.")
(:h3 "Currently active maintainers")
(wmd "
* Mark Evenson
* Erik Huelsmann
* Mariano Montone")
(:h3 "Previous maintainers")
(wmd "
* Erik Enge
* Drew Crampsie
* Hans H&uuml;bner
* Cheryl Yang
* Mario S. Mommer")))
placeholder until we support detecting *.md files as page sources.
\ No newline at end of file
<div id="bodyText"><a class="btn btn-secondary float-right" href="https://gitlab.common-lisp.net/clo/cl-site/edit/master/content/news.md"><i class="far fa-edit"></i>&nbsp;Edit this page</a><h1>Latest Common-Lisp.net news</h1>
<h3>2018-10-12 <em>Intent to remove unused projects</em></h3>
<p>
As per <a href="https://mailman.common-lisp.net/pipermail/clo-devel/2018-October/001253.html">the announcement</a>,
the site admins plan to remove the following list of projects which have been determined to neither
have a project page nor a code repository. Please contact the site admins before October 26, 2018 to
cancel project cleanup in case your project is wrongfully listed.
</p>
<ul>
<li>
arxana
</li>
<li>
asdf-install
</li>
<li>
asdf-packaging
</li>
<li>
boston-lisp
</li>
<li>
chemboy
</li>
<li>
cl-amqp
</li>
<li>
cl-buchberger
</li>
<li>
cl-cactus-kev
</li>
<li>
cl-captcha
</li>
<li>
cl-clickatell
</li>
<li>
cl-gdbm
</li>
<li>
cl-gtk2
</li>
<li>
clint
</li>
<li>
cl-lazy-list
</li>
<li>
cl-lexer
</li>
<li>
cl-match
</li>
<li>
cl-ode
</li>
<li>
clotnet
</li>
<li>
cl-peg
</li>
<li>
cl-player
</li>
<li>
cl-rundown
</li>
<li>
cltl3
</li>
<li>
cl-yacc-ebnf
</li>
<li>
decl
</li>
<li>
defmud
</li>
<li>
docutrack
</li>
<li>
innen
</li>
<li>
israel-lisp
</li>
<li>
jess-parse
</li>
<li>
lisp-interface-library
</li>
<li>
mk-defsystem
</li>
<li>
movies
</li>
<li>
objective-cl
</li>
<li>
phorplay
</li>
<li>
same
</li>
<li>
sqlisp
</li>
<li>
tioga
</li>
<li>
trivial-features
</li>
<li>
trivial-shell
</li>
<li>
ucs-sort
</li>
<li>
umpa-lumpa
</li>
<li>
xml-psychiatrist
</li>
</ul>
<h3>2018-10-12</h3>
<p>
Today I found some time to enable GitLab's 'reply by e-mail' functionality.
</p>
<p>
When you receive a notification e-mail from our GitLab instance, you can now send a reply to that notification. If the notification was from an issue being updated, then your reply will update the issue with a follow-up commont.
</p>
<h3>2018-10-10</h3>
<p>
A new version of Common-Lisp.net has been launched!
</p>
<p>
Among other things, the new site features:
</p>
<ul>
<li>
A site generator implemented in Common Lisp.
</li>
<li>
A gitlab pipeline for automatic deployment.
</li>
<li>
A new responsive design based on Bootstrap and new content.
</li>
</ul>
<h3>2018-10-06</h3>
<p>
As per <a href="https://mailman.common-lisp.net/pipermail/clo-devel/2018-August/001221.html">the announcement in August</a>,
the list of users with O/S level access has been cleaned up: those accounts which haven't been accessed since
2013 (and for which the owner didn't object to removal), have been removed. Home directories will be destructed
to comply with GDPR regulations.
</p>
<p>
If you once had an account and you need your access restored, please contact our admins.
</p>
<h3>2018-02-17</h3>
<p>
The Darcs (a distributed version control system before Git) repositories listed in our darcsweb instance
have been converted to <a href="https://gitlab.common-lisp.net/">our GitLab instance</a>. All use of Darcs on our site
has been marked deprecated for a long time and we're happy to have found a way forward, keeping the
repository content available to more modern VCSes.
</p>
<h3>2017-07-15</h3>
<p>
Our server was upgraded to Stretch as part of the regular life cycle management. See <a href="https://mailman.common-lisp.net/pipermail/clo-devel/2017-July/001166.html">our announcement</a>.
</p>
<h3>2015-05-25</h3>
<p>
Today the system has been declared "CVS clean"! All remnants of CVS have been removed.
</p>
<h3>2015-05-23</h3>
<p>
On Friday, the system had performance problems due to slow I/O. Checking the S.M.A.R.T. parameters of the disks didn't show anything unusual. Today, the disk system reports running in degraded mode, so we ordered the failing disk to be replaced, causing only minor downtime. The disk array has been rebuilt and it's smooth sailing from here again!
</p>
<h3>2015-05-22</h3>
<p>
GitLab upgraded to <a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/v7.11.1/CHANGELOG">GitLab 7.11.1.</a>
</p>
<h3>2015-05-15</h3>
<p>
Proposed approach for <a href="https://mailman-test.common-lisp.net/pipermail/clo-devel/2015-May/001051.html">Darcs repository migration</a> sent out.
</p>
<h3>2015-05-12</h3>
<p>
The final batch of CVS projects has been migrated. None of the projects opted to move to Subversion, so all of them were migrated to Git+GitLab:
</p>
<ul>
<li>
gamelib
</li>
<li>
ganelon
</li>
<li>
geometry
</li>
<li>
ginseng
</li>
<li>
glouton
</li>
<li>
gsharp
</li>
<li>
gtk-cffi
</li>
<li>
html-template
</li>
<li>
hyperdoc
</li>
<li>
hyperspec-lookup
</li>
<li>
ieeefp-tests
</li>
<li>
imago
</li>
<li>
iso8601-date
</li>
<li>
jnil
</li>
<li>
lambda-gtk
</li>
<li>
lgtk
</li>
<li>
lispfaq
</li>
<li>
lispy
</li>
<li>
lmud
</li>
<li>
log4cl
</li>
<li>
mcclim
</li>
<li>
meta-cvs
</li>
<li>
misc-extensions
</li>
<li>
morphologie
</li>
<li>
movitz
</li>
<li>
nio
</li>
<li>
noctool
</li>
<li>
pal
</li>
<li>
pg
</li>
<li>
phemlock
</li>
<li>
plain-odbc
</li>
<li>
rfc2388
</li>
<li>
rfc2822
</li>
<li>
rjain-utils
</li>
<li>
rucksack
</li>
<li>
sapaclisp
</li>
<li>
sb-simd
</li>
<li>
snmp1
</li>
<li>
spray
</li>
<li>
stamp
</li>
<li>
s-xml
</li>
<li>
s-xml-rpc
</li>
<li>
trivial-freeimage
</li>
<li>
unetwork
</li>
<li>
zip
</li>
<li>
zlib
</li>
</ul>
<p>
Now that the CVS repositories have been migrated, we'll move to clean up the cvs services from the underlying box and preparations will start to migrate the Darcs repositories on the system. For progress on the Darcs repository migration, watch the <a href="https://mailman.common-lisp.net/listinfo/clo-devel">clo-devel mailing list</a>.
</p>
<h3>2015-05-03</h3>
<p>
The next batch of CVS projects has been migrated. None of the projects opted to move to Subversion, so all of them were migrated to Git+GitLab:
</p>
<ul>
<li>
cl-magick
</li>
<li>
cl-menusystem
</li>
<li>
cl-mp3-parse
</li>
<li>
closure
</li>
<li>
clouchdb
</li>
<li>
cl-plus-ssl
</li>
<li>
cl-ppcre
</li>
<li>
cl-prevalence
</li>
<li>
cl-rope
</li>
<li>
cl-sbml
</li>
<li>
cl-screen
</li>
<li>
cl-selenium
</li>
<li>
cl-semantic
</li>
<li>
cl-smogames
</li>
<li>
cl-smtp
</li>
<li>
cl-snmp
</li>
<li>
cl-soap
</li>
<li>
cl-store
</li>
<li>
cl-syslog
</li>
<li>