Developer-oriented introduction to Infusion core concepts (for 2.0 version)
Tony Atkins
tony at raisingthefloor.org
Tue Jan 17 10:14:35 UTC 2017
Sorry, left out a step!
1.
git clone https://github.com/waharnum/infusion-docs.git
infusion-docs.waharnum
2.
cd infusion-docs.waharnum/
3.
git checkout FLUID-6112
4.
yarn install (or npm install)
5.
yarn run docpad (or npm run docpad)
6.
Open the following URL in your browser: http://127.0.0.1:9778/
infusion/development/to-do/DeveloperIntroductionToInfusionFramework.html
<http://127.0.0.1:9778/infusion/development/to-do/DeveloperIntroductionToInfusionFramework.html>
Cheers,
Tony
On Tue, Jan 17, 2017 at 10:41 AM, Tony Atkins <tony at raisingthefloor.org>
wrote:
> Hi, All:
>
> I will leave feedback on the PR, but just to comment, the use of markdown
> within HTML breaks things on GitHub. For example, the links on GitHub do
> not look as they do within docpad. To view the content in the way it would
> be displayed in our documentation:
>
> 1.
>
> git clone https://github.com/waharnum/infusion-docs.git
> infusion-docs.waharnum
> 2.
>
> cd infusion-docs.waharnum/
> 3.
>
> yarn install
> 4.
>
> yarn run docpad
> 5.
>
> Open the following URL in your browser: http://127.0.0.1:9778/
> infusion/development/to-do/DeveloperIntroductionToInfusio
> nFramework.html
> <http://127.0.0.1:9778/infusion/development/to-do/DeveloperIntroductionToInfusionFramework.html>
>
> Cheers,
>
>
> Tony
>
> On Tue, Jan 17, 2017 at 12:07 AM, Harnum, Alan <aharnum at ocadu.ca> wrote:
>
>> Hello everyone,
>>
>> I've written some documentation intended to help developers orient
>> themselves to Infusion's core concepts, in the style of the (pre-1.4 page)
>> at https://wiki.fluidproject.org/display/docs/Developer+Intr
>> oduction+to+Infusion+Framework
>>
>> There is a pull request open for it at https://github.com/fluid-pr
>> oject/infusion-docs/pull/114 for comments; the document itself is
>> viewable in my fork at https://github.com/waharnum
>> /infusion-docs/blob/FLUID-6112/src/documents/to-do/Devel
>> operIntroductionToInfusionFramework.md
>>
>> In particular, each concept is introduced through code samples that have
>> live versions on CodePen.
>>
>> I would describe this as a "surface level how" to what I think are the
>> most important parts of the core framework to get a handle on for a
>> developer new to it, with some amount of why. In some ways I am writing to
>> my self of a year and a half ago, who would probably have appreciated this
>> document (the self of the current day found writing it solidified his own
>> sense of understanding of the framework, to the extent his understanding
>> can be claimed to have a solid nature).
>>
>> I would appreciate the thoughts of the community.
>>
>> *ALAN HARNUM*
>> SENIOR INCLUSIVE DEVELOPER
>> INCLUSIVE DESIGN RESEARCH CENTRE, OCAD UNIVERSITY
>>
>> *E *aharnum at ocadu.ca <//aharnum at ocadu.ca>
>>
>> *OCAD UNIVERSITY*
>> 100 McCaul Street, Toronto, Canada, M5T 1W1
>> www.ocadu.ca <http://ocadu.ca/>
>>
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
>> To unsubscribe, change settings or access archives,
>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170117/29bf984c/attachment.html>
More information about the fluid-work
mailing list