src/README.md - brief intro for this folder

README.md

@@ -0,0 +1,52 @@
+# WhenWe
+
+Whenwe is dead. Long love Whenwe?
+
+A "when-we" is a nostagic reminisce. This is an archive of when-wes, currently.
+
+However, it may grow into a database of mini-biographies. Time will tell...
+
+## Structure
+
+- `src/` - the website content and templates
+- `bin/` - helper scripts
+
+Everything in the top directory are configs and documentation, like this.
+
+## Requirements
+
+The site is built using Eleventy. We assume you have Git, NodeJS and NPM installed.
+
+## Installation for development or deployment
+
+    git clone $whenwe_repo_url
+	cd whenwe
+	npm install
+	
+## Development
+
+    npm run server
+
+Now you should be able to visit the development site in your browser at http://localhost:8080
+
+If you edit the content in src/ - it should rebuild the site. Your browser should refresh automatically, but if not, refresh it manually.
+
+See [./src/README.md](./src/README.md) for more information.
+
+## Deployment
+
+Currently the destination is configured in package.json, as part of the definition of the `deploy` run-script.  To change the destination, change that.
+
+`rsync` is used for deploying the site. Therefore you need to have that installed and on the path.
+
+You will need `ssh` access to the destination.  Setting that up is outside the scope of this document, but if you have your own web space, you will probably know about this already, and if not, you will need the assistance of someone who does. For setting up your ssh client, it depends on your OS - there are guides online.
+
+But given that, the deploy process goes like this:
+
+    npm run build
+    npm run deploy
+
+## Issues and questions
+
+These can be submitted via the issue tracker attached to this repository.  You may need to create an account.
+

src/README.md

@@ -0,0 +1,16 @@
+# Source code
+
+This is the source code for WhenWe2.
+
+## Structre
+
+- `_articles/` - articles go here, in files with a .md suffix. The are essentially yaml files, with a leading `---`, then two sections, delimited with another `---`. The first section is the "front matter" - essentially a list of name/value pairs (or more generally, a datastructure - as in any YAML document items can be lists, directories, and so on, possibnly nested). The second section is markdown, which is essentially text, formatted according to certain conventions, and optionally containing HTML mark-up and template directives. See the Eleventy documentation for details of this.
+- `assets/` - this is copied verbatim to the destination site. It contains stylesheets and javascript, for the most part.
+- `_data/` - currently just contains a definition of the default layout to use on web pages.
+- `_images/` - images used in the site, liked to via articles. Copied verbatim to the site, but as the directory `images/`
+- `_includes/` - templates and template fragments, which define the layouts used to build the site HTML.
+- `_pages/` - non-article web pages.
+- `_people/` - descriptions of people.
+- `index.html` - the site's front page template.
+
+

src/_config.yml

@@ -1,27 +0,0 @@
----
-#remote_theme: wu-lee/jekyll-theme-monos
-title: When We
-description: When we 2
-unpublished: false
-collections:
-  articles:
-    output: true
-  people:
-    output: true
-defaults:
-  - scope:
-      path: ''
-      type: 'articles'
-    values:
-      layout: 'article'
-  - scope:
-      path: ''
-      type: 'people'
-    values:
-      layout: 'people'
-plugins:
-  - jekyll-remote-theme
-  - jekyll-feed
-feed:
-  collections:
-    - articles