Project

confluence

0.0
No commit activity in last 3 years
No release in over 3 years
confluencefoxnewsnetwork/confluenceHomepageDocumentationSource CodeBug TrackerWiki
One of the biggest problems facing any ruby (possibly rails) based web dev is the extreme lack of modularization of actual web components. Sure there are plenty of great modularized tools from rails to sprockets to whatever outthere that will help you get build a cool web app, but there is very little in terms of convention to help you build a cool web kit that can be reused anywhere else. Confluence is designed and used (by me) to build highly modular web assets like navigation bars, footers, map views, user profile tabs, etc. so that I never have to build the same again across different application.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
30,807
Stars
0
Forks
0
Watchers
3
 Releases
Current version
1.0.3
Total releases
9
First release
2013-02-14
Latest release
2013-02-20
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2013-02-17
Reverse Dependencies
0

 Dependencies

Development

haml
>= 0
jeweler
~> 1.8.4
rails
>= 0
rspec
>= 0
rspec-rails
>= 0

Runtime

activesupport
>= 0
bundler
>= 0
git
>= 0
rake
>= 0
rdoc
>= 0
rspec
>= 0
simplecov
>= 0
thor
>= 0
 Project Readme

confluence

In terms of diction, confluence refers to the merging of streams into a grand river. This embodies the objective of the confluence project. Consider any given ruby-based web application; after a certain point, all the assets, logic, stylesheets, etc. all become deeply intertwined with the given project. Modularity, portability, and agility are all out the window.

Some may argue this is a consequence of the "real world" where "scalability" necessarily implies that the code must be a clusterfuck. I humbly beg to differ. Thus confluence, the project you have at hand might be grand and momentus like the Amazon River, but, you should still build it from trickles, streams, and tributaries and, only in the end, do you confluent them together to form the raging rivers of life.

== Contributing to confluence

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
  • Fork the project.
  • Start a feature/bugfix branch.
  • Commit and push until you are happy with your contribution.
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

== Copyright

Copyright (c) 2013 Thomas Chen. See LICENSE.txt for further details.