-
Don't you think it would be clearer/cleaner to have the coffee source in src/ and the compiled JavaScript in lib/? It seems like a standard convention to have the runtime code in lib/.
I've even see…
-
Think about a better organization of CSS and HTML for each template. We need to have a single CSS and a single HTML for every template. Only the default one is loaded. When setting a new template we n…
-
The site folders and files and are well organized for coherency and ease of navigation and are labeled consistency with little to no confusion. Having said that consider using a project folder for you…
-
I was thinking about the organization of the project and I think it would be better if it followed the pattern some other projects have established when they have a large plugin architecture. Rather t…
trans updated
13 years ago
-
This could be the sensible way to address #12 and some of the use cases for #35:
- Allow a user to create an Organization.
- The Organization gets its own detail page, title, description, badge set,…
-
Great job keeping both the css and HTML neat and organized using comments and indentation. run through your HTML and make sure your indentation is consistent. everything that is nested to the same lev…
-
Organization basically have specific category like
- Healthcare
- Education
- Programming Tools
- ...
But it doesn't explicitly mentioned in the org details.
We can actually categorize it by…
-
For a CDS service provider, it is necessary to know which organization (or client) and potentially sub-organization is requesting the service. For example, it may be that a given client purchased only…
-
First - Nice project! was considering something similar.
I've built a and used a few ECS's. I was wondering why you explicitly declare the systems on an entity? Why didn't you declare components …
-
The number of branches has grown, and many of them are likely no longer needed. Unnecessary branches should be removed, after checking for possible work.
Known needed branches are:
* master
* per…