chore: import blog (#1469)

Last big item missing from #1184.

CONTRIBUTING.md

@@ -0,0 +1,14 @@
+# Contributing to JabRef's blog
+
+You want to write a blog entry? Great!
+
+Just create a file in `content/blog`.
+Be sure that
+
+- the suffix of the file (e.g., `JabRef3-3`) matches the entry `id` in the header and
+- you quote the values in the header.
+  Then, create a pull request.
+
+All your contribution is licensed as <a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="CC-BY-4.0" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a>.
+
+For more information, see the [CONTRIBUTING.md of our help page](https://github.com/JabRef/help.jabref.org/blob/gh-pages/CONTRIBUTING.md#contributing-to-the-jabref-help).

README.md

@@ -1,6 +1,7 @@
 # JabRefOnline
 
 This repository contains the source of the [JabRef homepage](https://www.jabref.org/).
+It contains also the [JabRef blog](https://blog.jabref.org/). Feel free to send blog entries.
 
 ## Servers
 

content/blog/2016-01-26-welcome.md

@@ -0,0 +1,17 @@
+---
+title: Welcome to the JabRef blog
+id: welcome
+bg: jabref-font
+color: white
+author: '[JabRef Developers](https://github.com/orgs/JabRef/teams/developers)'
+---
+
+This is the blog website of JabRef.
+Any developer or user can write and publish blog posts on this website.
+To do so you need to go to <https://github.com/JabRef/www.jabref.org> and fork the repository.
+Then you create a new branch on your fork with the name of the subject you want to write about.
+Write your blog post in a markdown file.
+Prefix the file name with the date of your blog post and place it in the `_posts` folder.
+Add your changes to your git index, commit, and push your changes.
+Finally open a pull request and wait for feedback.
+Once your changes are merged your blog post will be on top of this site.

content/blog/2016-01-27-JabCon.md

@@ -0,0 +1,8 @@
+---
+title: Survey and JabCon
+id: survey-jabcon
+author: '[JabRef Developers](https://github.com/orgs/JabRef/teams/developers)'
+---
+
+- The results of the survey are available at [https://www.jabref.org/surveys/2015/](https://www.jabref.org/surveys/2015/)
+- [JabCon](https://jabcon.jabref.org/) is over and we are working on releasing a new version containing the results of our hacking sessions

content/blog/2016-04-08-FasterJabRef.md

@@ -0,0 +1,28 @@
+---
+title: A faster JabRef is coming!
+id: faster-jabref
+bg: jabref-font
+color: white
+author: '[mlep](https://github.com/mlep)'
+---
+
+Some users reported JabRef was slow on large databases (thank you for the feedback!).
+This was especially the case for three operations:
+
+- loading a database
+- saving a database
+- searching through a database.
+
+During a search, the user interface could become very unresponsive, which is indeed quite annoying...
+Well, this time will be over soon: [Simon Harrer](https://github.com/simonharrer) has recently contributed [code making search much faster](https://github.com/JabRef/jabref/pull/1100).
+
+[By integrating the Java Microbenchmarking framework](https://github.com/JabRef/jabref/pull/1103),
+[Tobias Diez](https://github.com/tobiasdiez) was able to benchmark JabRef and reveal interesting insights about the performance of JabRef:
+Preliminary tests have been carried out on a database with 100000 entries (is it big enough for you?).
+They show that **JabRef is now 10 times faster at searching**: it takes only one second to search through 60000 entries!
+
+You can [give it a try](http://builds.jabref.org/master/)
+(_This is a development version: Be carefully, and back up your data first!)_.
+[Your comments are welcomed](https://github.com/JabRef/jabref/pull/1100)!
+
+_Stay tuned: [work is under way to speed up the opening of large databases](https://github.com/JabRef/jabref/issues/1094)._

content/blog/2016-04-19-JabRef3-3.md

@@ -0,0 +1,33 @@
+---
+title: Release of JabRef 3.3
+id: JabRef3-3
+author: '[JabRef Developers](https://github.com/orgs/JabRef/teams/developers)'
+---
+
+We are pleased to announce the release of JabRef version 3.3!
+
+Since April 17, 2016, JabRef 3.3 can be downloaded from [FossHub](http://www.fosshub.com/JabRef.html), the official JabRef download site.
+
+This release contains new and improved features such as:
+
+- online help at [help.jabref.org](https://help.jabref.org). Changes can be proposed easily via <https://github.com/JabRef/help.jabref.org>.
+- file-based BibTeX and BibLaTeX modes
+- save actions: automatically format your entries on save
+- quicker addition of papers having a DOI
+  - Add a new entry
+  - Add the title in the title field
+  - Go to the "General" tab, click into the DOI field (workaround for [#1234](https://github.com/JabRef/jabref/issues/1234)) and click "Lookup DOI"
+  - Click on "Get BibTeX data from DOI"
+- faster search
+- improved import from ArXiv and Ovid
+- better integration of OpenOffice/LibreOffice style files
+- improved support on Mac OS X
+- translation into Swedish
+
+It also includes about 40 bug fixes and the removal of a few features (mostly outdated).
+Details are listed on [GitHub](https://github.com/JabRef/jabref/blob/v3.3/CHANGELOG.md).
+
+For questions about the functioning, and for congratulation messages, please, use [our discussion forum](http://discourse.jabref.org/).
+For bugs and improvements, open an issue on [GitHub](https://github.com/JabRef/jabref/issues).
+
+_**You like it? Foster JabRef development with [Code](https://github.com/JabRef/jabref/blob/master/CONTRIBUTING.md) or [Money](https://github.com/JabRef/jabref/wiki/Donations).**_

content/blog/2016-04-25-WinEdtBothDirections.md

@@ -0,0 +1,23 @@
+---
+title: 'JabRef & WinEdt: two-way communications'
+id: JabRefWinEdt
+bg: jabref-font
+color: white
+author: '[JabRef Maintainers](https://github.com/JabRef/jabref/blob/main/MAINTAINERS)'
+---
+
+For a longtime, a single click on a toolbar button has allowed JabRef to insert citations in [WinEdt](http://www.winedt.com).
+
+![image: From JabRef to WinEdt](/img/blog/JabRef-WinEdt.png)
+From JabRef to WinEdt.
+
+WinEdt is a powerful and versatile all-purpose text editor for Windows with a strong predisposition towards the creation and compilation of LaTeX documents.
+
+Up to now, communication was only one-way: from JabRef to WinEdt.
+This time is over: since April 2, 2016, WinEdt can also communicate with Jabref!
+
+Thanks to [a package contributed by Karl Koeller](http://www.winedt.org/config/menus/JabRef.html),
+JabRef can be launched from within WinEdt.
+
+![image: From WinEdt to JabRef](/img/blog/WinEdt-JabRef.png)
+From WinEdt to JabRef.

content/blog/2016-06-02-JabRef3-4.md

@@ -0,0 +1,31 @@
+---
+title: Release of JabRef 3.4
+id: JabRef3-4
+author: '[JabRef Developers](https://github.com/orgs/JabRef/teams/developers)'
+---
+
+We are pleased to announce the release of JabRef version 3.4!
+
+The new version can be downloaded as of now from [FossHub](http://www.fosshub.com/JabRef.html), the official JabRef download site.
+
+The main focus of this release is improving the grouping functionality of JabRef with various bug fixes and new features:
+
+- Group information is now directly stored in the BibEntry - and no longer at the end of the `bib` file
+- Group view is immediately updated after adding an entry to a group
+- Dragging an entry to a group preserves scrolling
+- Entries retain their groupmembership when undoing their cut/deletion
+- The group tree now uses the whole available space in the left sidebar
+
+Some other selected new features and improvements are:
+
+- You can directly paste a DOI into the main table and JabRef tries to create the matching entry
+  - _Did you know: This also works with complete BibTeX entries you have in your clipboard!_
+- The merge entries dialog now shows all text and colored differences between the fields
+- Added support for several Biblatex-fields through drop-down lists with valid alternatives
+- DOI and normal web links are now distinguished with different icons in the main table
+
+JabRef 3.4 also includes more than 30 bug fixes and the removal of a few features (mostly outdated).
+Details are listed on [GitHub](https://github.com/JabRef/jabref/blob/v3.4/CHANGELOG.md).
+
+For questions about the functioning, please use [our discussion forum](http://discourse.jabref.org/)..
+In case you have trouble, report bugs and suggestions for improvements on [GitHub](https://github.com/JabRef/jabref/issues).

content/blog/2016-06-27-JabRefForum.md

@@ -0,0 +1,33 @@
+---
+title: New User Forum
+id: JabRefForum
+author: '[JabRef Developers](https://github.com/orgs/JabRef/teams/developers)'
+bg: jabref-font
+color: white
+---
+
+In cooperation with [discourse.org](http://www.discourse.org) a new forum for JabRef has just been opened!
+
+You can find it by now in the top navigation bar on JabRef.org or directly here: [http://discourse.jabref.org](http://discourse.jabref.org)
+
+The main reasons for introducing the forum are:
+
+- Foster the communication between the large user base and the developers of JabRef, creation of an active _"JabRef community"_
+- Provide an easier to use, searchable, more modern way to give feedback and request help
+- Provide a better place for feature and enhancement discussions by a [dedicated category for such topics](http://discourse.jabref.org/c/features)
+- Reduce the number of created issues at the GitHub tracker - only real bugs and work-in-progress feature requests should be handled there
+
+We hope you'll like the new forum as much as we do and join us at [http://discourse.jabref.org](http://discourse.jabref.org) to contribute with your knowledge!
+
+### Discontinued support at the mailing list
+
+During the last years we started to move away from sourceforge.net (for various reasons): The source code and issues are now managed at [GitHub](https://github.com/JabRef/jabref), downloads are handled by [FossHub](http://www.fosshub.com/JabRef.html) and we are using our own domain JabRef.org for hosting the website and this blog.
+
+However, there is still a mailing list left on sourceforge: [https://lists.sourceforge.net/lists/listinfo/jabref-users](https://lists.sourceforge.net/lists/listinfo/jabref-users)
+
+With the new forum we now provide an easy to use platform to ask questions (and hopefully to get answers) from the JabRef community.
+Thus, we decided to officially discontinue the support on the mailing list. We'll leave the list open for some time - but the official communication channels for the future will be the [GitHub issue tracker](https://github.com/JabRef/jabref/issues) (for bugs) and the [discourse forum](http://discourse.jabref.org) (for all other questions, feature requests and feedback).
+
+For those of you who like to stick with a mailing-list like behavior we provide you [a guide on how to use the discourse forum just like a mailing list](http://discourse.jabref.org/t/quick-start-guide-for-former-mailing-list-users/31).
+
+_Thanks again to [discourse.org](http://www.discourse.org) for the great software and especially for providing us free hosting!_

content/blog/2016-07-14-JabRef3-5.md

@@ -0,0 +1,24 @@
+---
+title: Release of JabRef 3.5
+id: JabRef3-5
+author: '[JabRef Maintainers](https://github.com/JabRef/jabref/blob/main/MAINTAINERS)'
+---
+
+We just released a new version of JabRef!
+
+The new version 3.5 can be downloaded as of now from [FossHub](http://www.fosshub.com/JabRef.html), the official JabRef download site.
+
+JabRef 3.5 mainly concentrates on fixing some bugs. The most serious one was a broken installer for Mac OS X in version 3.4 which inhibited the correct start of JabRef.
+Apart from that again some bugs in the grouping feature have been fixed.
+
+But we also introduced some new features:
+
+- The import dialogs can now filter by file extension (e.g., displaying only \*.bib files)
+- The discussion forum can be opened directly from the "Help" menu
+- If a **crossref** to another entry is set (using the BibTeX-key) clicking on the button "select" directly opens the referenced entry
+- Last but not least: As we are releasing more often than before, we introduced a "Check for updates" functionality. You'll be informed if a new version of JabRef is available for download. This check is performed automatically on startup or can be triggered manually in the "Help" menu.
+
+An overview on all new features and fixes can be found on [GitHub](https://github.com/JabRef/jabref/blob/v3.5/CHANGELOG.md).
+
+For questions about the functioning or suggestions for improvements please use [the discussion forum](http://discourse.jabref.org).
+In case you have trouble, report bugs on [GitHub](https://github.com/JabRef/jabref/issues).

content/blog/2016-08-09-Polls.md

@@ -0,0 +1,20 @@
+---
+title: Vote for the features you like!
+id: PollsAugust2016
+author: '[JabRef Maintainers](https://github.com/JabRef/jabref/blob/main/MAINTAINERS)'
+bg: jabref-font
+color: white
+---
+
+By voting in the forum's polls, JabRef will better suits your needs.
+It is fast and simple.
+
+Currently, you can **make your voice heard** about:
+
+- [Seamless crossreferencing](http://discourse.jabref.org/t/seamless-crossreferencing/100)
+- [Duplicated entries: which comparison mode do you use?](http://discourse.jabref.org/t/duplicated-entries-which-comparison-mode-do-you-use/114)
+- [Improved duplicate key resolving](http://discourse.jabref.org/t/improved-duplicate-key-resolving/50)
+- [Get information about researchers from social websites](http://discourse.jabref.org/t/get-information-about-researchers-from-social-websites/66/1)
+- [Add system specific notifications](http://discourse.jabref.org/t/add-system-specific-notifications/102)
+- [Show warnings of integrity checker directly in entry editor](http://discourse.jabref.org/t/show-warnings-of-integrity-checker-directly-in-entry-editor/106)
+- [Introduce formatter to truncate the target filename for automatic rename of attached files](http://discourse.jabref.org/t/introduce-formatter-to-truncate-the-target-filename-for-automatic-rename-of-attached-files/63)

content/blog/2016-08-15-HotkeyRevision.md

@@ -0,0 +1,35 @@
+---
+title: Revised Hotkey System
+id: HotkeyRevisionAugust2016
+author: '[JabRef StuPro](https://github.com/orgs/JabRef/teams/stupro)'
+---
+
+In the next release of JabRef a revised hotkey system is introduced. The two goals of this revision is to improve maneuverability through the keyboard and streamlining hotkeys. Sometimes, related hotkeys (like the ones covering the side panes) were scattered across the keyboard, so we grouped them together. You might be wondering what has changed, so have a look at them:
+
+| Keys - new                                         | Keys - old                                         | Function                               |
+| -------------------------------------------------- | -------------------------------------------------- | -------------------------------------- |
+| <kbd>F7</kbd>                                      | <kbd>alt</kbd> + <kbd>F</kbd>                      | Automatically set file links           |
+| <kbd>F8</kbd>                                      | <kbd>ctrl</kbd> + <kbd>shift</kbd> + <kbd>F7</kbd> | Cleanup entries                        |
+| <kbd>alt</kbd> + <kbd>1</kbd>                      | <kbd>ctrl</kbd> + <kbd>shift</kbd> + <kbd>E</kbd>  | Focus entry table                      |
+| <kbd>alt</kbd> + <kbd>2</kbd>                      | <kbd>ctrl</kbd> + <kbd>F9</kbd>                    | Toggle entry/preview editor            |
+| <kbd>alt</kbd> + <kbd>3</kbd>                      | <kbd>ctrl</kbd> + <kbd>shift</kbd> + <kbd>G</kbd>  | Toggle groups                          |
+| <kbd>alt</kbd> + <kbd>4</kbd>                      | <kbd>F5</kbd>                                      | web search                             |
+| <kbd>alt</kbd> + <kbd>0</kbd>                      | -                                                  | Open Openoffice/LibreOffice connection |
+| <kbd>ctrl</kbd> + <kbd>shift</kbd> + <kbd>F7</kbd> | <kbd>ctrl</kbd> + <kbd>F4</kbd>                    | Synchronize file links                 |
+| <kbd>ctrl</kbd> + <kbd>shift</kbd> + <kbd>R</kbd>  | -                                                  | Technical report                       |
+| -                                                  | <kbd>alt</kbd> + <kbd>P</kbd>                      | Print entry preview                    |
+| -                                                  | <kbd>ctrl</kbd> + <kbd>alt</kbd> + <kbd>T</kbd>    | Hide/show toolbar                      |
+| -                                                  | <kbd>ctrl</kbd> + <kbd>p</kbd>                     | Edit preamble                          |
+
+- Improve group pane maneuverability by making groups selectable by arrow keys
+- Improve main table maneuverability by making <kbd>tab</kbd> jump to the next entry instead of the next cell, <kbd>shift</kbd> + <kbd>tab</kbd> selects the previous entry.
+- We moved related functions together. <kbd>F7</kbd> is now affiliated with file links, hence we changed key bindings if they contained "<kbd>F7</kbd>" but weren't related to file links.
+- We moved all side panes together by changing them to <kbd>ALT</kbd>+<kbd>0</kbd> to <kbd>ALT</kbd>+<kbd>4</kbd>. By doing so we hope to improve the accessibility, because now one doesn't have to remember all kinds of key combinations for side panes, only which number stands for your desired pane. One side note: Open OpenOffice/LibreOffice connection was added to this family due to being a side pane.
+- The new hotkey for "New technical report" was requested by some users that use it frequently, so we added a key binding.
+- We removed the hotkey for "Hide/show toolbar" and "Edit preamble" due to the assumption that is used by a too small groups of users.
+- We removed the hotkey for "Print entry preview" due to some conflicts with others and the fact that this function wasn't really used that often by users. The function itself is not gone: It existed in the right click menu of the preview panel and now is also available at the right click menu.
+- We resized the "change key bindings" dialog due to being too small for some descriptions.
+
+If you would like to try the new system, you can try it out at [https://builds.jabref.org/master/](https://builds.jabref.org/master/).
+
+For questions about the functioning or suggestions for improvements, please use the [discussion forum](http://discourse.jabref.org/). In case you have trouble, report bugs on [GitHub](https://github.com/JabRef/jabref/issues).