The goal

[angular-ui]

The goal

[ProLoser]

This was supposed to be a bower module that contains something like the doc
generator code you have been building that we could inject into each
project. It wasn't solidified if this was the direction we were going to go
in though, and we were also considering having a project that we would
inject other projects into to serve their demos.

This is NOT the bower version of each project.
On May 5, 2013 2:53 PM, "Douglas Duteil" [email protected] wrote:

Hi

What's the goal of this repo ?

The description says :

Helper component for building your angular modules as bower components

But don't see any relation with Bower here...
I mean for me a good repo for bower is a repo with only built files like
bower-angular https://github.com/angular/bower-angular.
So no docs, non travis, etc...

I get it wrong ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

[douglasduteil]

Okay...
So can I transform it into a repository that will be a submodule in each project to power them doc ?

[ProLoser]

You can change this into whatever you see fit. It was an early (unused) prototype.

[ProLoser]

My intention is that this project can be used to standardize the docs across all angular-ui projects. Whatever way you think would best achieve that is up to you.

[douglasduteil]

Alright thanks.

[ProLoser]

Also, feel free to rename this project to suite your needs or to something that you find more applicable.

[ProLoser]

@douglasduteil sorry, I just wanted to clarify. This project should essentially be the equivalent to your ui-utils/out folder. I would like to reuse as much of that code as possible. It would even be interesting if we could create some sort of grunt task SPECIFICALLY for performing actions to another (gh-pages) branch, that anyone who uses grunt could leverage (theoretically).

[douglasduteil]

Almost there !

Here is a fast explication of what I did

I still have a strange bug on first run. The loading stops along the way...

I tested it on the ft-doc-t0 branch of my Ace repo (result) and my CodeMirrorr repo (result)

What you think?

PS : I still feel like it's using a sledge-hammer to crack a nut...
Apart ui-utils there aren't that much doc to make a site...

[ProLoser]

I sort of agree that it's a lot. But if we can get it to be leveraged across all projects (most importantly, add Travis deployment automation!) it will be well worth it.

[douglasduteil]

Agreed.
Le 10 mai 2013 20:35, "Dean Sofer" [email protected] a écrit :

I sort of agree that it's a lot. But if we can get it to be leveraged
across all projects (most importantly, add Travis deployment automation!)
it will be well worth it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-17737014
.