create legacy content based on last publish commit a8e9533

rjournal · Jun 22, 2022 · c7f909b · c7f909b
commit c7f909b
Show file tree

Hide file tree

Showing 2,034 changed files with 341,992 additions and 0 deletions.
diff --git a/.htaccess b/.htaccess
@@ -0,0 +1,2 @@
+Redirect 301 /current.html /index.html
+Redirect 301 /2009-1/ /archive/2009-1/
diff --git a/.nojekyll b/.nojekyll
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1 @@
+The contents of this website are Copyright, The R Foundation, while articles are copyright to their authors. All website content is licensed under the Creative Commons Attribution 4.0 International license.
diff --git a/README.md b/README.md
@@ -0,0 +1,53 @@
+# R Journal website
+
+The R journal website is published using [github pages](http://pages.github.com/). This makes it easier to manage the articles in git, and the website automatically updated when the git repo is pushed to github.
+
+## Deployment
+
+The `master` branch is the sandbox. It is automatically served at https://rjournal.github.io/ as GitHub pages, and an update is triggered at every push so the site can be previewed prior to merging with the `deploy` branch.
+
+The official website `https://journal.r-project.org/` is synchronised (cron job) by the Vienna team from the `deploy` branch of this repository, which is in turn generated by a GitHub Action from the `published` branch on push. Therefore one can consider the `master` branch as development and merging it into `published` starts the deployment to the official site.
+
+In addition to the `master` branch the deployment the action also copies the contents from the `_web` folder in the `dev` branch into the `dev` folder of the deployment. It is currently used to test the development version of the R Journal website so that both branches are deployed.
+
+## Templates
+
+The overall layout for the site can be found in `layouts/defaults.html`.  The template is written using [liquid](https://github.com/Shopify/liquid/wiki/Liquid-for-Designers), a simple templating system.
+
+## Building the site locally
+
+You'll need to install the jekyll ruby gem:
+
+```
+gem install jekyll
+```
+
+Then run the following command in the web site directory to preview the website http://localhost:4000
+
+```
+jekyll serve --watch
+```
+
+*If you run into problems serving locally to check changes, you may need to*
+
+- if you get a versioning issue with i18n try ```bundle exec jekyll serve --watch```
+
+or install particular versions with
+
+```gem install i18n --version 0.9.5```
+
+```gem install coderay```
+
+## Publishing new articles
+
+Modify `_config.yml`
+
+__Note__: `_config.yml` is only parsed once when you start jekyll, it's not automatically updated like when you modify html files. This means that whenever you add new articles you'll need to stop and restart jekyll to see the changes.
+
+## Publishing a new issue
+
+* In `_config.yml` move current `accepted` issue to correct name and add additional metadata. Delete all pdfs in `archive/accepted`
+
+* Create `archive/issue`, copy in `index.html` and `references.bib`
+
+* In `_layouts/default.html`, change the path to the current issue
diff --git a/RLogo.png b/RLogo.png
diff --git a/Rlogo.svg b/Rlogo.svg
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		Redirect 301 /current.html /index.html
		Redirect 301 /2009-1/ /archive/2009-1/
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		The contents of this website are Copyright, The R Foundation, while articles are copyright to their authors. All website content is licensed under the Creative Commons Attribution 4.0 International license.