Feedback please - what should the new documentation platform be called?
Jonathan Hung
jhung at ocadu.ca
Fri Jul 24 13:28:51 EDT 2015
Yes that is the workflow we would follow Anastasia.
The step where you fork https://github.com/fluid-project/docs-template can
be skipped and you can clone it directly. I'd still recommend forking since
it mitigates any accidental commits or gh-pages deployments if a person did
not have their repositories configured properly (docpad gh-pages plugin
just deploys to origin by default).
- Jon.
On Fri, Jul 24, 2015 at 12:24 PM, Cheetham, Anastasia <acheetham at ocadu.ca>
wrote:
>
> On Jul 24, 2015, at 11:50 AM, Jonathan Hung <jhung at ocadu.ca> wrote:
>
> This make sense Anastasia?
>
>
> I think so. I’ve filled this in using some more specific examples, based
> on my general workflow with IDRC projects. Let me know if I’m understanding
> correctly:
>
>
> 1. Create a new repository on github. i.e. docs-video-player
>
> So I would do this in fluid-project, to create
> https://github.com/fluid-project/docs-video-player. It would be empty, to
> start. I would probably also fork this to my own repository, i.e.
> https://github.com/acheetham/docs-video-player, since that’s usually how
> I start to work with a fluid-project repository.
>
>
> 1.
> 2. Fork docs-template so now you have docs-template and
> docs-video-player on github.
>
> So I would fork https://github.com/fluid-project/docs-template into
> https://github.com/acheetham/docs-template
>
>
> 1.
> 2. Clone docs-template locally into the directory you will be working
> from i.e. clone into ./docs-video-player
>
> I would clone https://github.com/acheetham/docs-template into
> docs-video-player on my laptop.
>
> Question: Could I skip step 2, and just clone
> https://github.com/fluid-project/docs-template directly?
>
>
> 1.
> 2. From within docs-video-player rename origin to something else. i.e.
> git remote rename origin docs-template
>
> Ok
>
>
> 1.
> 2. Add the new remote you want to push to as the new origin i.e. git
> remote add origin https://www.github.com/~acheetham/docs-video-player/
>
> Gotcha. I’d also set https://github.com/fluid-project/docs-video-player
> as my *upstream*.
>
>
> 1.
> 2. Now grab your node dependencies, make your changes, add content,
> styling etc.
>
> 3. When ready commit your changes to your repository
>
> I would push my branches to my origin (
> https://github.com/acheetham/docs-video-player) and issue pull requests
> against https://github.com/fluid-project/docs-video-player.
>
> Sound right? reasonable?
>
> --
> Anastasia Cheetham – acheetham at ocadu.ca
> Inclusive Design Research Centre
> Inclusive Design Institute
> OCAD University
>
>
--
*JONATHAN HUNG*
INCLUSIVE DESIGNER, IDRC
*T:* 416 977 6000 x3951
*F:* 416 977 9844
*E:* jhung at ocadu.ca
*OCAD UNIVERSITY*
Inclusive Design Research Centre
205 Richmond Street W, Toronto, ON, M5V 1V3
www.ocadu.ca
www.idrc.ocad.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20150724/e3950233/attachment.html>
More information about the fluid-work
mailing list