This repository has been archived by the owner on May 16, 2019. It is now read-only.
/
README.txt
53 lines (36 loc) · 2.04 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
=== Persistent Forking (WordPress plugin) ===
Contributors: UUDigitalHumanitiesLab
Tags: forking, forks, posts
Requires at least: 4.0
Tested up to: 4.3
License: MIT
License URI: http://opensource.org/licenses/MIT
Enable contributors to create permanent forks of existing posts.
Visualise the family of any fork.
== Description ==
Persistent Forking allows contributors of your site to create
permanent "forks" of existing posts. Every fork is a full-fledged
post in its own right and can be published as such. This
distinguishes Persistent Forking from the *Post Forking* plugin,
where forks are a collaborative tool in order to arrive at a single
definitive version. The parent-child relationships between posts are
tracked and it is possible to visualise the entire family tree of a
post.
== Installation ==
Just copy the plugin to your wp-content/plugins directory, then
enable the plugin in your admin panel.
== Screenshots ==
1. Forking controls are added to the top of every post. This is only visible for members of your site who can create posts.
2. When you click the "Fork" control, a new post is created and you are redirected to the editing form. The direct parent and the family are displayed in a metabox (red circle). The title of the parent post is copied with "[fork]" in front. As you can see, post contents are not copied over to the fork.
3. When you click the "Show family" control, all parent-child relations within the family are displayed in a tree diagram. You can click on a node to go to the corresponding post.
== Support ==
Please report any issue that you find while using the plugin at our
GitHub repository:
https://github.com/UUDigitalHumanitieslab/persistent-forking/issues
The first priority of the Digital Humanities Lab is to service
requests from Humanities researchers at Utrecht University. However,
the plugin is open source with a liberal license, so anyone can
provide a patch if we don't follow up on your issue.
If you are interested in (Digital) Humanities, please have a look at
our website:
http://digitalhumanities.wp.hum.uu.nl