|
1 | | -### Outliners everywhere! |
2 | | - |
3 | | -I've long felt that every operating system and web browser should have a great outliner baked-in. |
4 | | - |
5 | | -If you were going to try to do that today, you'd release it under the GPL written in JavaScript. |
6 | | - |
7 | | -That's exactly what Concord is. |
8 | | - |
9 | | -<i><a href="http://scripting.com/2013/09/16/concordOurGplOutliner">Dave Winer</a>, 9/16/13.</i> |
10 | | - |
11 | | - |
12 | | - |
13 | | -### Concord is an outliner |
14 | | - |
15 | | -<a href="http://docs.fargo.io/outlinerHowto">An outliner</a> is a text editor that organizes information in a hierarchy, allowing users to control the level of detail and to reorganize according to structure. Your notes can have full detail, yet be organized so a casual reader can get a quick overview. Outlining is a great way for teams to organize work. |
16 | | - |
17 | | - |
18 | | - |
19 | | -### Written in JavaScript |
20 | | - |
21 | | -It's a jQuery plug-in that implements a full-featured outliner that you can drop into other applications with a minimum of work. |
22 | | - |
23 | | - |
24 | | - |
25 | | -### It's the core of Fargo |
26 | | - |
27 | | -<a href="http://fargo.io/">Fargo</a> is our browser-based outliner that hooks into Dropbox. |
28 | | - |
29 | | -Concord is the outlining engine in Fargo. |
30 | | - |
31 | | - |
32 | | - |
33 | | -### GPL-licensed |
34 | | - |
35 | | -<a href="https://github.com/scripting/concord">Concord</a> is licensed under the GPL because outliners are an incredibly useful way to edit structured information. We want Concord to be able to fill every conceivable need for outlining technology. |
36 | | - |
37 | | -Ideas include file systems, mailboxes, chatrooms, databases, documents, presentations, product plans, code, libraries, laws, systems of laws, contracts, rules, guidelines, principles, docs, manifestos, journals, blogs, etc. |
38 | | - |
39 | | -Here's an important 11-minute <a href="http://scripting.com/2013/09/17/importantPodcastAboutConcordGpl">podcast</a> about Concord and the GPL. |
40 | | - |
41 | | - |
42 | | - |
43 | | -### Example 0: The bare minimum |
44 | | - |
45 | | -This <a href="https://github.com/scripting/concord/blob/master/example0/index.html">example</a> has the bare minimum to add an outliner to an existing app. |
46 | | - |
47 | | -This saves developers the trouble of having to factor it out of Example 1, below. |
48 | | - |
49 | | -You can try it out <a href="http://static.smallpicture.com/concord/example0/index.html">here</a>. |
50 | | - |
51 | | - |
52 | | - |
53 | | -### Example 1: Hello Outliner |
54 | | - |
55 | | -This <a href="https://github.com/scripting/concord/tree/master/example1/index.html">example</a> is a functional outliner, with most of the capabilities of the Little Outliner app and the same basic approach. You edit a single outline, saved in local storage, so it's there when you come back to it, but only on that machine. |
56 | | - |
57 | | -It has a simple menubar, with menus containing Outliner commands, links to OPML documents you can view and edit, and links to docs. |
58 | | - |
59 | | -You can try it out <a href="http://static.smallpicture.com/concord/example1/index.html">here</a>. |
60 | | - |
61 | | - |
62 | | - |
63 | | -### Example 2: Small Picture Reader |
64 | | - |
65 | | -We've released the <a href="https://github.com/scripting/concord/blob/master/example2/index.html">source</a> for <a href="http://docs.fargo.io/fargo/reader">Small Picture Reader</a> under the GPL as part of the Concord release. |
66 | | - |
67 | | -This app provides a way to read any OPML file even if you aren't using an outliner. |
68 | | - |
69 | | -There's a command in Fargo that creates a link between the document you're editing and a reader version. |
70 | | - |
71 | | -If you want to run the app, <a href="http://static.smallpicture.com/concord/example2/index.html">click here</a>. |
72 | | - |
73 | | - |
74 | | - |
75 | | -### Inaugural blog post |
76 | | - |
77 | | -<a href="http://scripting.com/2013/09/16/concordOurGplOutliner">Here's the post</a> I ran on Scripting News when Concord was publicly announced. It includes a link to a podcast. |
78 | | - |
79 | | - |
80 | | - |
81 | | -### Worknotes |
82 | | - |
83 | | -I keep a log of work I do on Concord, in an <a href="https://raw.github.com/scripting/concord/master/opml/worknotes.opml">outline</a> of course. |
84 | | - |
85 | | -There's a <a href="https://github.com/scripting/concord/blob/master/worknotes.md">markdown rendering</a> of the worknotes file. |
86 | | - |
87 | | - |
88 | | - |
89 | | -### Community |
90 | | - |
91 | | -We have a <a href="https://groups.google.com/forum/?fromgroups#!forum/smallpicture-concord">Google Group mail list</a> for technical support. |
92 | | - |
93 | | - |
94 | | - |
| 1 | +# Concord |
| 2 | + |
| 3 | +Concord is a JavaScript outliner written by Kyle Shank in 2013, maintained by Dave Winer since, GPL-licensed. |
| 4 | + |
| 5 | +The user interface is keystroke and mouse-compatible with the Living Videotext outliners, ThinkTank, Ready and MORE, and the outliner built into UserLand Frontier and Radio UserLand. |
| 6 | + |
| 7 | +There's a new release in February 2020, the first since 2013. |
| 8 | + |
| 9 | +Concord is the core component of <a href="http://littleoutliner.com/">Little Outliner</a> and numerous other of Dave's projects. |
| 10 | + |
| 11 | +Concord's native file format is <a href="http://dev.opml.org/">OPML</a>. |
| 12 | + |
| 13 | +### What's new? |
| 14 | + |
| 15 | +You can see the work notes <a href="https://github.com/scripting/concord/blob/master/worknotes.md">here</a>. |
| 16 | + |
| 17 | +I've been adding features carefully and slowly over the years. The best way to see them is to review the history in GitHub. |
| 18 | + |
| 19 | +The biggest change is that Concord is now managed using the same code editing and deploying tools I use for all my other <a href="https://github.com/scripting?tab=repositories">projects</a>, so it will be easier to publicly release new versions. |
| 20 | + |
| 21 | +### Concord is an outliner |
| 22 | + |
| 23 | +<a href="http://outlinerhowto.opml.org/">An outliner</a> is a text editor that organizes information in a hierarchy, allowing users to control the level of detail and to reorganize according to structure. Your notes can have full detail, yet be organized so a casual reader can get a quick overview. Outlining is a great way for teams to organize work. |
| 24 | + |
| 25 | +### Written in JavaScript |
| 26 | + |
| 27 | +It's a jQuery plug-in that implements a full-featured outliner that you can drop into other applications with a minimum of work. |
| 28 | + |
| 29 | +### GPL-licensed |
| 30 | + |
| 31 | +<a href="https://github.com/scripting/concord">Concord</a> is licensed under the GPL because outliners are an incredibly useful way to edit structured information. We want Concord to be able to fill every conceivable need for outlining technology. |
| 32 | + |
| 33 | +Ideas include file systems, mailboxes, chatrooms, databases, documents, presentations, product plans, code, libraries, laws, systems of laws, contracts, rules, guidelines, principles, docs, manifestos, journals, blogs, etc. |
| 34 | + |
| 35 | +Here's an important 11-minute <a href="http://scripting.com/2013/09/17/importantPodcastAboutConcordGpl">podcast</a> about Concord and the GPL. |
| 36 | + |
| 37 | +### Example 0: The bare minimum |
| 38 | + |
| 39 | +This <a href="https://github.com/scripting/concord/blob/master/example0/index.html">example</a> has the bare minimum to add an outliner to an existing app. |
| 40 | + |
| 41 | +This saves developers the trouble of having to factor it out of Example 1, below. |
| 42 | + |
| 43 | +You can try it out <a href="http://scripting.com/code/concord/repo/example0/">here</a>. |
| 44 | + |
| 45 | +### Example 1: Hello Outliner |
| 46 | + |
| 47 | +This <a href="https://github.com/scripting/concord/tree/master/example1/index.html">example</a> is a functional outliner, with most of the capabilities of the Little Outliner app and the same basic approach. You edit a single outline, saved in local storage, so it's there when you come back to it, but only on that machine. |
| 48 | + |
| 49 | +It has a simple menubar, with menus containing Outliner commands, links to OPML documents you can view and edit, and links to docs. |
| 50 | + |
| 51 | +You can try it out <a href="http://scripting.com/code/concord/repo/example1/">here</a>. |
| 52 | + |
| 53 | +### Example 2: Small Picture Reader |
| 54 | + |
| 55 | +We've released the <a href="https://github.com/scripting/concord/blob/master/example2/index.html">source</a> for <a href="http://docs.fargo.io/fargo/reader">Small Picture Reader</a> under the GPL as part of the Concord release. |
| 56 | + |
| 57 | +This app provides a way to read any OPML file even if you aren't using an outliner. |
| 58 | + |
| 59 | +There's a command in Little Outliner that creates a link between the document you're editing and a reader version. |
| 60 | + |
| 61 | +If you want to run the app, <a href="http://scripting.com/code/concord/repo/example2/">click here</a>. |
| 62 | + |
| 63 | +### The previous version |
| 64 | + |
| 65 | +Here's a <a href="http://scripting.com/2020/02/13/concord-master.zip">snapshot</a> of this repo before integrating the new stuff. |
| 66 | + |
| 67 | +Here's the <a href="https://github.com/scripting/concord/blob/master/archive/readme2013.md">previous readme</a>. |
| 68 | + |
| 69 | +### Support |
| 70 | + |
| 71 | +If you have a question, comment, or bug to report, please post an <a href="https://github.com/scripting/concord/issues">issue</a> here. |
| 72 | + |
| 73 | +I do not take pull requests, it's best to describe the problem or feature you want to add, as an issue, and let's talk about the best way to do it. Writing the code is never the biggest part of a change or addition. |
| 74 | + |
0 commit comments