Skip to content

The front-end web application for the Community Ally suite of tools

License

Notifications You must be signed in to change notification settings

Ambesawi/HOA_CommunityAllyWebApp

 
 

Repository files navigation

Community Ally

Online tools that let offline groups accomplish greater things. Manage documents, payments, to-dos, calendars, committees, private communication, events, history, polls, maintenance, membership and more in a tool uniquely tailored for condos, HOAs, and neighborhoods. It's the perfect tool for these groups because it's built by board members that use it every day.

N|Logo

This is the code base for the front-end of the Community Ally web-based community management tool. Condo Ally, HOA Ally, Neighborhood Ally, and Block Club Ally use this code base. The back-end server code base is not yet open source.

Using Community Ally

If you're ready to improve your, or your client's, condo association, HOA, or neighborhood, go sign-up immediately at one of the afforementioned sites. It's free, instant, and simple. There's no need for you to build and host your own copy of the application unless you want to customize the site in a way beyond what is already offered.

Running Locally

To develop locally, you'll still need an active Community Ally site setup so you can make requests to the live server. If you haven't signed up for a Condo Ally or HOA Ally site yet, go ahead and do so now. It's instant and free. You're welcome to make a group specifically for development. If that's the case, please put the word "Dev" in your association name during sign-up.

  1. Clone the repo
  2. Run "npm install"
  3. Run "grunt serve"
  4. The site uses the subdomain to determine which group you're viewing. For example, https://123fake.condoally.com is for the 123 Fake St Condo Association and https://BrightElm.hoaally.org is for the Bright Elm HOA site. We need to override this logic while you're developing locally so you can specifiy which group to use while hosting off localhost. At the top of website\ngApp\ally-app.ts (Or ally-app.js if you haven't run 'grunt watch' yet), specify the origin of your Ally site in the OverrideBaseApiPath and OverrideOriginalUrl variables. Make sure you make this change while grunt is running so it recompiles with your updated values.

File Structure

If you want to jump right in to changing the main UI, look in the "website\ngApp\chtn\member" directory. By the way, CHTN stands for condo, HOA, townhome, neighborhood. Those UIs share pretty much the same experience, as opposed to the home and neighborhood watch UIs which is mostly separate code. Note in that "member" directory you should be able figure out which page is which by name. If you want to adjust one of the site admin pages, open the "CommunityAllyWebsite\ngApp\chtn\manager" directory.

The main app code is in "website\ngApp". Third-party libraries are in "website\js". The CSS is in the "website\assets\scss" directory, see style.scss for the breakdown.

Tech

Community Ally uses a number of amazing open source libraries:

Custom Development

We can setup, host, and modify custom sites for your community association. Simply contact us here on Github or reach out using the form at the bottom of our home page.

License

MIT

About

The front-end web application for the Community Ally suite of tools

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 59.6%
  • TypeScript 22.4%
  • HTML 14.4%
  • CSS 2.9%
  • Other 0.7%