update howto to reflect new document types and structure

Author: Benedikt Hegner

howto.md

@@ -4,76 +4,72 @@ author: Torre Wenaus
 layout: default
 ---
 
-## About the newsletter site
+## About the HSF website
 
-This site is maintained by the [HSF github repository people](https://github.com/orgs/HEP-SF/people). If you're interested to become one contact the HSF startup team or any team member. It was set up by Torre Wenaus.
+This site is maintained by the [HSF github repository people](https://github.com/orgs/HEP-SF/people). If you're interested to become one contact the HSF startup team or any team member. It was set up by Torre Wenaus and Benedikt Hegner.
 
 ## Implementation
 
-This HSF newsletter website is implemented using [github's Pages service](https://pages.github.com/) which makes it easy to create a website associated with a github account or project. [Pages uses Jekyll](https://help.github.com/articles/using-jekyll-with-pages/), a tool to automatically build a website from source files (which are kept in github). It supports structured sites like blogs in a simple but powerful way. We all like to work in code editors; this lets you write content in a friendly editor using the easy [markdown syntax](http://daringfireball.net/projects/markdown/syntax) (which is used by github itself).
+This website is implemented using [github's Pages service](https://pages.github.com/) which makes it easy to create a website associated with a github account or project. [Pages uses Jekyll](https://help.github.com/articles/using-jekyll-with-pages/), a tool to automatically build a website from source files (which are kept in github). It supports structured sites like blogs in a simple but powerful way. We all like to work in code editors; this lets you write content in a friendly editor using the easy [markdown syntax](http://daringfireball.net/projects/markdown/syntax) (which is used by github itself).
 
-## How to post
+## How to add and edit information
 
-To create a post you add a file in the [github repository of posting sources](https://github.com/HEP-SF/hep-sf.github.io/tree/master/_posts), so you need to be an [HSF github repository](https://github.com/HEP-SF) user. Talk to any member of the startup team.
+To create or edit files you have to use the [github repository of the HSF website](https://github.com/HEP-SF/hep-sf.github.io/), so you need to be an [HSF github repository](https://github.com/HEP-SF) user. Talk to any member of the startup team.
 
-If you wish (and it is recommended) you can easily set up a local instance of the newsletter site in order to preview submissions. See the [documentation on installing and running Jekyll](https://help.github.com/articles/using-jekyll-with-pages/). The newsletter uses user pages, ie use the master branch.
+If you wish (and it is recommended) you can easily set up a local instance of the newsletter site in order to preview submissions. See the [documentation on installing and running Jekyll](https://help.github.com/articles/using-jekyll-with-pages/). The website uses user pages, ie use the master branch.
 
-### Sharing and testing drafts
-If you want to store a draft of a post, you can put it into the `_drafts/` folder. Adding `--drafts` to the command line of jekyll allows you to render them locally. Once happy, `git mv` it into the `_posts/` directory and publish to the official repository.
-
-## What to post
-
-Here's a template. This snippet covers the entire content of what should be in the post file. Note that the first lines enclosed by three dashes must be the first lines in the file. The format is markdown, see references below.
+If you only do simple operations like the ones mentioned below, the GitHub interface itself gives you all options to add and edit such files in the browser.
 
-The file must be added to the [_posts directory](https://github.com/HEP-SF/hep-sf.github.io/tree/master/_posts) following the name convention `yyyy-mm-dd-title-goes-here.md`.
+### Adding to the newsletter
 
-        ---
-        title: HEP Software Foundation news, May 1 2015 (required)
-        project: Project name if the post is about a particular project (optional)
-        tags: tags for software category, etc. (optional)
-        author: you (optional)
-        ---
+Add a new file in `workinggroups/_posts` and follow the front-matter of the
+other files in there. The list of news will be updated automatically.
 
-        HEP Software Foundation news this week: (include the sections for which you're giving updates)
+### Adding a working group
 
-        ## Packaging
-        
-        ## Software projects
+Add a new file in `workinggroups/_posts` and follow the front-matter of the
+other files in there. The navigation bar will be updated automatically.
 
-        ## Training
+### Adding an event
 
-        ## Development tools
+Add a new file in `events/_posts` and follow the front-matter of the other files
+in there. The events page will be updated automatically. Please don't forget
+adding a startdate. Only this allows a proper ordering
 
-        ## Knowledge base
+### Adding a job opening
 
-        ## Technical notes
+Add a new file in `jobs/_posts` and follow the front-matter of the other files
+in there. It is important to fill the field `open: true`. This field allows to
+only show positions that aren't filled yet.
 
-        ## Forum news
 
-        ## Licenses
-
-        ## Recent meetings
+### Sharing and testing drafts
+You can either use the github approach of forking a repository, do your changes there and make a pull request. Or if you want to store the draft into the main repository directly, you can put it into the `_drafts/` folder. Adding `--drafts` to the command line of jekyll allows you to render them locally. Once happy, `git mv` it into the `_posts/` directory and publish to the official repository.
 
-        ## Coming events
-        
-        You can also have subsections
+## Technical details
 
-        ### Subsection
+### Page templates
 
-        (you get the idea). You can include a link [here](http://path), use
+As of writing, this website contains the following page templates:
 
-        * bulleted
-            * nested
-        * lists
+ * default - every page inherits from this
+ * event
+ * job_summary
+ * job
+ * newsletter
+ * page
+ * plain
 
-        and refer to `inline code` and
+### Menu bar and automatization
+The menu bar is defined in `default.html`, from which all page layouts inherit.
+The layout is hard-coded except for the addition of working groups. A new post
+in the `workinggroups/_posts` directory automatically adds the group to the drop
+down menu `Working Groups`.
 
-                include
-                large
-                code
-                blocks.
+### Side bar and automatization
+The side bar contains two dynamic blocks - *upcoming events* and *current job
+openings*. Both are filled with *liquid* snippets defined in `_includes`.
 
-        See the markdown doc for more. 
 
 
 ## Useful references