Private and public, publish and publish state
Only pages which are not containing private material (i.e. are public) and which ready to publish (i.e. not a publish) (pdf)
March 5, 2019
Which web pages should be published
The publicly visible homepage should only include material which the author deems public and ready for publication. It must be possible to collect in the directories material which is in preparation and not yet ready for publication but also material which is of a private nature and not visible in the finished homepage.
Separate readiness for publication and visible to everybody
The web is in principle a medium where material is accessible to everybody - unless restricted. It must be possible to produce version of the homepage for public visibility and other versions which are restricted.
There are two reasons for excluding material from public visibility:
not yet fulfilling quality standards, e.g., spelling not checked, incomplete content, only a first idea sketched, etc.
private material which for should not be available to everybody or must not be included in a published version for, e.g., lack of copyright (i.e. material where somebody else has the copyright and is not public domain).
Coding in the
yaml
head of every blog page
In the head of every blog page two keywords are included:
visibility: which can have values
private
orpublic
.version: which can have values
publish
,draft
,idea
.
Current implementation (version 0.1.5.1 of SSG)
Only markdown files with public
and publish
are baked into the site. Two switches -d
and
-p
are included to include files which are not intended for
public view or not ready for publication to include such files in the
bake process. Be careful not to have the produced site served on a
publicly visible port!