GithubHelp home page GithubHelp logo

rapidexpedition / theexpeditionarium Goto Github PK

View Code? Open in Web Editor NEW
3.0 2.0 0.0 58.46 MB

Ideas as technology.

Home Page: http://rapidexpedition.org

License: Creative Commons Attribution Share Alike 4.0 International

JavaScript 5.98% HTML 37.84% CSS 55.90% Ruby 0.28%
philosophy futurism resiliency

theexpeditionarium's Introduction

This work represents an attempt to establish and develop a set of philosophical principles collaboratively by employing appropriate technologies for ease of communication, iteration, and distribution.

Here, we will specifically survey the novel concept of Expeditionary Philosophy and, more specifically, the notion of Rapid Expedition, as attributive of a greater pre-existing cultural paradigm. Furthermore will we seek to hone the the concept with prejudice toward its value being universal and self-evident.

The goal of this is to establish a positive feedback loop toward the pioneering of a comprehensive and relevant philosophy and for the explicit benefit of the modern age--accomplishing this as much in practice as well as prescription.

As this work will remain open-source, its development will be public, and its contents available for copy and alteration.

How to Contribute

The simplest means of contribution would be to visit this document's home on gitbook and offer commentary inline in discussion.

Contributing more directly is somewhat advanced: It is necessary to first clone the repository in order to submit or edit articles here. It is recommended to do so in this manner:

git clone --recursive https://github.com/rapidExpedition/rapidExpedition.git

This work relies on git versioning, distribution, and collaboration as well as markdown syntax. The wiki itself is generated by GitBook, so it would behoove a contributor to peruse through its documentation.

It is also recommendable that one try git before diving in, but it is possible to edit any article directly through github without cloning or alternatively through GitBook's own editor; however, authorship is like any other craft and benefits from use of appropriate tools. For further reference see rapidExpedition.pub.

Why to Contribute

This work exists for the purpose of establishing permanent and permanently evolving guidelines for the essential tasks which befall a modern citizen of the global community. It is for the development of proficiency in those tasks as well as to explore and discover just what sort of tasks a productive and proficient life might entail. In short we are after a characterization of a complete and competent stewardship of life and civilization at large.

Written language is a well-established means of conveying ideas, and when ideas are shared and shaped collectively, they affect the development and history of the world at large. Thus, a concise and adaptive expression of ideas with substantial and universal utility could achieve a lasting and manageable legacy.

theexpeditionarium's People

Contributors

imdone-test avatar rmblrx avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

theexpeditionarium's Issues

explain the use of *xen-* versus *post-* or *neo-*, for instance, particularly as it derives from Nietzsche's conception of the Übermensch as a being not fully understandable or relatable (really, wholly alien) from the limits of a human perspective nor relating to a *human, all too human* perspective.


opened via imdone.io from a code comment on 550a0b9

TODO explain the use of xen- versus post- or neo-, for instance, particularly as it derives from Nietzsche's conception of the Übermensch as a being not fully understandable or relatable (really, wholly alien) from the limits of a human perspective nor relating to a human, all too human perspective. id:11


https://github.com/rapidExpedition/theExpeditionarium/blob/550a0b9fc5a22bd11e9d83b13cbf2c1a84170939/_includes/wayPoint/Xenanthropy.md#L13-L16

propose some initial content, such as a write-up on Militancy, in general, a manifest, some elaboration on the concept of the *Oligarch* (perhaps including its *catechism*)

-->


opened via imdone.io from a code comment on 550a0b9

TODO propose some initial content, such as a write-up on Militancy, in general, a manifest, some elaboration on the concept of the Oligarch (perhaps including its catechism) id:9


https://github.com/rapidExpedition/theExpeditionarium/blob/550a0b9fc5a22bd11e9d83b13cbf2c1a84170939/_includes/wayPoint/Weaponize.md#L28-L29

Footnotes not (or possibly no longer) working properly in wiki or code

As elaborated here, we're getting strange and inconsistent behavior with our footnote approach, even though it works as expected on the site, itself.

See this: https://github.com/rapidExpedition/wayPoint/wiki/pranaBindu

... compared to this: https://github.com/rapidExpedition/theExpeditionarium/blob/64b67542a68ca45383281e02f274d1af33d5da4e/wayPoint/pranaBindu/index.md

... compared to this: https://www.rapidexpedition.org/waypoint/pranabindu/

figure out how establish a conditional in which goToGitHub and goToProse direct to the appropriate wiki repo for transcluded articles instead of the page *stubs* in theExpeditionarium repo

Issue created with imdone.io


TODO: figure out how establish a conditional in which goToGitHub and goToProse direct to the appropriate wiki repo for transcluded articles instead of the page stubs in theExpeditionarium repo +wikiTransclusion +enhancement id:29
public\js\all.js:66

@imdone Issue Creator. The developer's task board. imdone.io

explain the proposed method of developing/exploring Xenanthropy by means of a single collaborative and iterative document which might ultimately be published in any number of ways (on [gitbook](https://www.gitbook.com/book/rapidexpedition/xenanthropy/), to start with, but otherwise developed [here](https://github.com/rapidExpedition/Xenanthropy)), but also explain the idea that behind the document will be a more rapidly iterative wiki for that document to reference or otherwise draw off of.


opened via imdone.io from a code comment on 6fe05241 by RMBLRX

TODO explain the proposed method of developing/exploring Xenanthropy by means of a single collaborative and iterative document which might ultimately be published in any number of ways (on gitbook, to start with, but otherwise developed here), but also explain the idea that behind the document will be a more rapidly iterative wiki for that document to reference or otherwise draw off of. id:12


https://github.com/rapidExpedition/theExpeditionarium/blob/550a0b9fc5a22bd11e9d83b13cbf2c1a84170939/_includes/wayPoint/Xenanthropy.md#L14-L16

really need this page to explain [IMDONE](https://imdone.io/) implementation as well as wiki contribution (which will be distinct from general site contribution, as I want to direct people to edit the wiki itself, rather than its subtree manifestation on the site; and I believe that's doable through the prose and octicon JS) -->

Issue created with imdone.io


TODO: really need this page to explain IMDONE implementation as well as wiki contribution (which will be distinct from general site contribution, as I want to direct people to edit the wiki itself, rather than its subtree manifestation on the site; and I believe that's doable through the prose and octicon JS) +wikiTransclusion +feature --> id:3
siteWiki\contributionGuidelines.md:10

@imdone Issue Creator. The developer's task board. imdone.io

include a link that allows for the creation of a new page under the empty directory that returns a 404, and also include an explanation with a link to the contribution guidelines


opened via imdone.io from a code comment on 550a0b9

TODO include a link that allows for the creation of a new page under the empty directory that returns a 404, and also include an explanation with a link to the contribution guidelines id:5 +feature gh:7


<!-- #TODO: include a link that allows for the creation of a new page under the empty directory that returns a 404, and also include an explanation with a link to the contribution guidelines id:5 +feature gh:7
-->

this project might have some things to learn from [LightPaper](http://lightpaper.42squares.in/), particularly its [use of notes](http://blog.42squares.in/2015/12/21/introducing-lightpaper-mini/) (though that functionality might be better relegated to something more like a combination of [imdone](https://imdone.io/) and [CriticMarkup](http://criticmarkup.com/))


opened via imdone.io from a code comment on 550a0b9

IDEA this project might have some things to learn from LightPaper, particularly its use of notes (though that functionality might be better relegated to something more like a combination of imdone and CriticMarkup) id:15


https://github.com/rapidExpedition/theExpeditionarium/blob/550a0b9fc5a22bd11e9d83b13cbf2c1a84170939/_includes/wayPoint/rapiDex.md#L62-L67

really need this page to explain [IMDONE](https://imdone.io/) implementation as well as wiki contribution (which will be distinct from general site contribution, as I want to direct people to edit the wiki itself, rather than its subtree manifestation on the site; and I believe that's doable through the prose and octicon JS)

Issue created with imdone.io


TODO: really need this page to explain IMDONE implementation as well as wiki contribution (which will be distinct from general site contribution, as I want to direct people to edit the wiki itself, rather than its subtree manifestation on the site; and I believe that's doable through the prose and octicon JS) +wikiTransclusion +feature id:4
siteWiki\contributionGuidelines.md:10

@imdone Issue Creator. The developer's task board. imdone.io

explain our [hexadecimal](https://en.wikipedia.org/wiki/Hexadecimal) numbering system for [reference links](http://spec.commonmark.org/0.28/#reference-link) and [footnotes](https://stackoverflow.com/a/32119820/8304877)

consider using [CriticMarkup](http://criticmarkup.com/), but probably only if we can figure out how to configure Jekyll to hide that markup when it builds. It would be useful if [Prose](http://prose.io) or Atom (Atom does have [*some*](https://atom.io/themes/pen-paper-coffee-syntax) [support](https://github.com/shd101wyy/markdown-preview-enhanced/issues/591#issuecomment-326782396)) recognized CriticMarkup, as well, but we'll just have to make do and perhaps [roll our own solution](https://www.rapidexpedition.org/waypoint/rapidex/) in regard to that


opened via imdone.io from a code comment on 550a0b9

IDEA consider using CriticMarkup, but probably only if we can figure out how to configure Jekyll to hide that markup when it builds. It would be useful if Prose or Atom (Atom does have some support) recognized CriticMarkup, as well, but we'll just have to make do and perhaps roll our own solution in regard to that id:16


https://github.com/rapidExpedition/theExpeditionarium/blob/550a0b9fc5a22bd11e9d83b13cbf2c1a84170939/_includes/siteWiki/contributionGuidelines.md#L67-L72

try defining the root depth by way of categories (wayPoint having "../../", for instance, perhaps defined in [config](/_config.yml), and having categories of *wiki* and *rapidExpedition* and *topLevel* and so on) instead of explicitly denoting the root depth in each file


opened via imdone.io from a code comment on 550a0b9

TODO try defining the root depth by way of categories (wayPoint having "../../", for instance, perhaps defined in config, and having categories of wiki and rapidExpedition and topLevel and so on) instead of explicitly denoting the root depth in each file +relativization id:10


#TODO: try defining the root depth by way of categories (wayPoint having "../../", for instance, perhaps defined in [config](/_config.yml), and having categories of *wiki* and *rapidExpedition* and *topLevel* and so on) instead of explicitly denoting the root depth in each file +relativization id:10
-->
{% capture root %}{% if page.root %}{{ page.root }}{% elsif post.root %}{{ post.root }}{% else %}{{ default.root }}{% endif %}{% endcapture %}
<link rel="stylesheet" href="{{ root }}{{ "public/css/poole.css" | relative_url }}">
<link rel="stylesheet" href="{{ root }}{{ "public/css/syntax.css" | relative_url }}">

figure out a way to include an edit icon next to the headings of ancillary content ("Elaboration" and "Articulations", for instance) since it is not contained in the main wiki article and has no path for editing directly from the website. This may not be so vital to the completion the first round of adaptations for the project.


opened via imdone.io from a code comment on 6fe05241 by RMBLRX

TODO figure out a way to include an edit icon next to the headings of ancillary content ("Elaboration" and "Articulations", for instance) since it is not contained in the main wiki article and has no path for editing directly from the website. This may not be so vital to the completion the first round of adaptations for the project. +wikiTransclusion id:18


# TODO: figure out a way to include an edit icon next to the headings of ancillary content ("Elaboration" and "Articulations", for instance) since it is not contained in the main wiki article and has no path for editing directly from the website. This may not be so vital to the completion the first round of adaptations for the project. +wikiTransclusion
-->

really need this page to explain [IMDONE](https://imdone.io/) implementation as well as wiki contribution (which will be distinct from general site contribution, as I want to direct people to edit the wiki itself, rather than its subtree manifestation on the site; and I believe that's doable through the prose and octicon JS)


opened via imdone.io from a code comment on 550a0b9

DONE really need this page to explain IMDONE implementation as well as wiki contribution (which will be distinct from general site contribution, as I want to direct people to edit the wiki itself, rather than its subtree manifestation on the site; and I believe that's doable through the prose and octicon JS) +wikiTransclusion +feature id:4 gh:6


https://github.com/rapidExpedition/theExpeditionarium/blob/550a0b9fc5a22bd11e9d83b13cbf2c1a84170939/_includes/siteWiki/contributionGuidelines.md#L64-L69

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.