A simple logging system, created as a proof-of-concept. Fully standards compliant and
accessible, it is designed to quickly set up a functional and structured site to conveniently
track related and unrelated items.
Installation starts with filling in the root and path, as well as the author's name and
e-mail address, a picture and description in the /admin/config.php file. The information
is stored in a php array.
Use .htaccess or similar to secure the /admin/ directory.
The entry form lives at /admin/enter.php. Choose an input language, decide whether to draft
or publish and if this is a post or a feature article with an associated html file.
Liquid. Styleswitching to either light or distinctive dark red scheme.
Every entry is assigned a unique id.
Entries are saved as xml-data, in one single xml-file;
CON: constrained by size of file,
PRO: easy search and manipulation, dynamic sort, no static html-pages necessary.
Every entry with <status>published</status> is automatically indexed in a standard rdf 1.0
file, available for syndication.
Outline Processor Markup Language
Parsing OPML-files, shown on the front page as a definition list.
Substring in title, body, keywordsÉ
Related entries are shown with individual articles.
BLOG SOFTWARE CHART
URL of the home page for the software
Sample install: http://alexanderbecker.net/lightningnotes/
Current version number of the software in production
As of 2004-06-14 | 2011-11-25: 0.1
License requirements for the installation of the software
GPL, see below
Languages supported by the administration interface of the system
System's administrative interface localized based on individual user settings?
Maximum number of weblogs (channel of postings) that the system can manage through a single
installed administrative interface
Minimum requirements of the server on which the software is to be installed
Primary source of drawn data for the transmission of site pages
XML-Data-File -- When the site is served to requesting browsers, the data for the page is
pulled from a flat file and inserted into a template for delivery.
Methods for ordering the display of posts on the site
descending -- Posts can be ordered in descending chronological order, with the newest
at the top
Category -- Posts can be ordered by the category in which they appear.
Allows posts to be classified by categories: the system allows posts to be classified by
multiple categories -- A post can be assigned to any number of categories.
Allows subcategories to be created in a hierarchy
Allows keywords to be associated by a post author to each post, and also allows the system
to return posts that are related by these keywords via a keyword search
Default Post Fields
TITLE, BODY, EXTENDED BODY, KEYWORDS, EXCERPT
Textile -- The system accepts post data from a <textarea> and processes it through
Textile. There may be scripted controls that automatically apply Textile markup.
HTML -- plain entry
Supports submitting unpublished drafts of posts
Versions of RSS the system produces for syndication
RSS 1.0 (RDF)
PHP File -- The templates are stored as PHP files and are executed. The code built into
the template files inserts post data for display.
PHP functions -- The template contains actual PHP functions that execute to insert post
data at that point.
Single user -- There is only one user account that can log in to the software control
Simple -- The system includes some amount of pre-defined user profile information that
can be edited by the user
Incorporates a method by which users can change between styles of display of the site.
This may be by CSS or by template selection.
OPML -- the system can maintain a list of links to external sites
Lightning Notes version 0.1
Copyright 2003 - 2011
by Alexander Becker email@example.com
This program is licensed under the GPL http://www.gnu.org/copyleft/gpl.html
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.