Progress reports are Giving Jar’s way of celebrating success, reflecting on failure (and what was learned from it), giving thanks, and taking a peek at what’s up and coming. Hopefully you will find these progress reports informative. If you have feedback to offer, send it along!
Since this is the first progress report, it’s not so much an update as it is a baseline from which all other progress reports can be measured. The next one will be much shorter!
Here are the major wins in this progress report:
- The landing page was launched.
- The Giving Jar blog is available for consumption.
- A weekly newsletter is in production.
- Curated news with positive messages are shared daily.
- The filing cabinet is open for all to peruse.
- All browser-visible content has been open sourced.
If you don’t want to know about the details of these wins, feel free to skip to Failure.
The biggest news of the first progress report is that the landing page is live! Go there to learn all about Giving Jar and sign up for the newsletter.
Giving Jar Blog
Writing is the earliest way that Giving Jar can help people discover charities and learn about the Giving Jar platform. The charity spotlights and progress reports are two such examples.
All written content will be published to the Giving Jar blog. If the content is more technical in nature, you’ll find the details on the Technical Rex blog. Until Giving Jar gets its own development blog, those technical articles will just be linked to from here.
If you prefer to get your news in one place, there are Atom feeds for both blogs.
At the time of this writing, there is a sign up form on the Giving Jar landing page. Subscribe if you want to discover more about nonprofits, charitable giving, and Giving Jar.
The newsletter will be sent weekly and will contain one of the following:
- Charity Spotlights. These charity interviews will help nonprofits get the word out about their mission and explore valuable information about how they operate, the challenges they face, and how donors can help.
- Progress Reports. This is what you’re reading now. These reports are how Giving Jar keep interested readers up to date.
This idea was a last-minute addition to the rollout of the landing page. If you follow Giving Jar on social media then you will see daily items from the news about charities and donations.
These shared links exist to inform and inspire. Each one is hand-picked because of the positive message or information it provides about the nonprofit space. They are not ads and Giving Jar does not make money from them whatsoever.
Open Filing Cabinet
Right now there are two files available:
Open Source Content
Along the same vein as the open filing cabinet, all web content for Giving Jar is being open sourced. The following repositories are available for perusal:
Feel free to fork and use these resources, but please abide by the license assigned to each repository. If there is no license file, then the content of the repository should not be used without explicit permission from Giving Jar.
There are almost always setbacks when working on a project of any size. Here are the lessons learned from the last round of setbacks:
- Tasks should be small and specific.
- Expect technical difficulties.
Here are the stories behind those takeaways. If you don’t want the details, jump ahead to the Thanks.
Tasks Should Be Small and Specific.
The first handful of tasks for Giving Jar were very high-level:
- Create landing page.
- Create blog.
- Create newsletter.
The reason these tasks should have been smaller is a matter of prioritization. Here’s a real example: hours of time went into picking a color scheme for the site. After the photos were taken, though, it was obvious what the color scheme should be.
Expect Technical Difficulties.
Technical difficulties will happen. When they do, it’s important to be able to quickly adapt your plan accordingly.
Setting up email for
givingjar.org went poorly because server issues were causing 2-5 hour delays in email delivery. If you are working on a remote system and run into issues, bring up their status page. It might save you hours if you quickly discover the issue is on their side.
Bonus Takeaway: If you offer a service to others, be very forthcoming on your website and social media when issues crop up!
Acquiring an SSL certificate was also quite the rollercoaster ride. The gist of the lesson learned here is to hold off on purchasing software until you need it. Giving Jar doesn’t need an SSL certificate right now, but when it does, Let’s Encrypt will be the first stop.
The landing page wouldn’t look nearly as good if it weren’t for photographic prowess of Ian Kast. Same goes for Dean Attali, creator of the Beautiful Jekyll theme that the Giving Jar blog is based on.
A tip of the hat to everyone who helped by giving feedback during the development process as well (Chris, Sam, Rich, Kevin, and everyone in the Lansing Codes Slack team). Never underestimate the value of someone who is willing to critique your work.
Finally, thanks to everyone following Giving Jar:
- 12 mailing list members
- 7 Twitter followers
- 19 Facebook page likes
The first charity spotlight will be published next week! Giving Jar is on the lookout for charities to interview, too. If you know a charity that might be interested, send an email, tweet, or write on Facebook.
A meeting needs to be scheduled with an accountant. There are lots of financial considerations to be made for a startup as it rolls into the new year.
It doesn’t sound like much, but with Christmas falling at the end of the next week, it’ll be enough!
“Sensitive” information is anything that could be used in malicious ways against Giving Jar or its employees (social security numbers, usernames/passwords, etc.). ↩