
Building Griffin Arts Council Online on a Small Nonprofit Budget
How I helped a new local arts council get set up as an organization and launch two Jekyll sites for public information, events, donations, and brand files.
A new community organization needs a way to explain what it does, share upcoming events, and make it easy for people to get involved. And it has to do all that without taking on a big technology bill before it has any regular income.
That's where the Griffin Arts Council website started. The organization was brand new, so there was no old site to update or move. It needed a mobile-friendly public presence that made sense to people, plus simple tools for sharing information and accepting support. I serve on the board, I've contributed financially, and I helped with both the organizational setup and the technology.
We ended up with two connected sites: griffinarts.org, the council's public website, and assets.griffinarts.org, a public library of approved brand files and guidance. Both run on Jekyll and GitHub Pages. That setup keeps the sites simple to run, and it gave the council good ways to reach people from day one.
Set up the organization first
A website can explain an organization. It can't create the legal and financial structure behind it. Alongside the web work, I filed the state paperwork to form the corporation, set up bank accounts, arranged payment processing, and set up the donation platform on Givebutter. I also submitted the IRS Form 1023-EZ application for federal tax-exempt status. As I write this, the application is still pending.
I want to be careful about how we describe that. Submitting an application isn't the same as getting approved. When the IRS makes a decision, the council should update its public language, and anything we tell donors should match where the organization actually stands.
For a startup nonprofit, keeping these jobs apart makes the web project a lot easier to handle. The site explains things and points people to the right next step. Banking, legal filings, and payment processing stay in the systems built for them.
A public front door that works on phones
The main site gives Griffin Arts Council a place to describe its work, introduce its board, publish news, and share ways to take part. It adapts to phone screens as well as bigger displays, since someone checking an event or a donation link might well be on a phone and not sitting at a computer.


I wasn't trying to turn every visitor into a supporter. I wanted the next thing a person needs to be easy to find. Now, when someone asks what the council does, who's involved, or how to take part, there's one address to send them to.
A startup website should answer the next question. Future features can wait.
The events list tells people what's next
One of the most basic reasons to have a website is to tell people what's happening next. Each listing in the events section has a title, date, time, and location, plus an optional cost and ticket link. Labels can mark the format, like a workshop, art show, or fundraiser. A short list of upcoming events can show up on the home page, too.
It's a small feature with one job. A resident, artist, or partner can check what's coming up without hunting for a social media post. And when the council announces an event somewhere else, it has one place to point people.
An event listing does its job when people can see when it is, where to go, and what to do next.
Each event is its own content file instead of something hand-built into the page layout. That keeps the event details apart from the design. A new listing follows the same structure as the ones before it, and the site sorts and displays them, so nobody has to rearrange a page by hand every time the calendar changes.
Give people clear ways to support the work
The site splits out the different ways to get involved. A business can read about sponsorship. An individual can look at membership options or find the patron directory. Community partners have a directory of their own. The donation page embeds a Givebutter giving form, and the membership page links to the council's membership campaign.
Since we use a dedicated fundraising service, the council doesn't have to build a payment system into its website. The site lays out the choices and sends each visitor to the right Givebutter form. Payment processing and campaign settings live with Givebutter, not in custom code on the site.
Let a payment provider handle payments. Keep the website focused on information and clear next steps.
That also means the cost isn't automatically zero. Givebutter's pricing describes optional donor tips and payment-processing fees, and what a nonprofit pays depends on its settings and whether donors cover the fees. Check the current pricing and campaign settings before you estimate how much a donation will net [1].
The site also has a contact form run through Formspree and a Givebutter signup widget. Every outside service comes with its own account, limits, privacy terms, and possible costs. If you're a small organization, list those services and read the terms before you depend on them. Handing a feature off to another service cuts down on custom development, but you still need to know who handles the data and what happens if a free tier changes.
A separate library for official brand files
The second site, assets.griffinarts.org, solves a different problem. A lot of organizations share logos by forwarding an old email or asking someone to dig a file off a personal computer. A public asset library gives board members, designers, printers, partners, and volunteers one place to find the approved files.
The library catalogs the council's horizontal, stacked, and G-logo configurations, in color and grayscale versions and in formats for digital and print. It also publishes logo guidance and a web color palette. The site uses the Just the Docs theme, which comes with the kind of navigation and search a reference library needs.

The asset files live apart from the main website's content. That way the library works on its own, and people get a stable link to the right logo or guidance. Every new file needs a matching catalog entry, so nobody has to guess a filename to find it.
Why Jekyll and static pages fit this work
Both sites use Jekyll, a static site generator. Put simply, Jekyll takes content, configuration, templates, and styles and turns them into ordinary HTML, CSS, and other files for a web server to deliver. The published pages don't need a running application server or a database for each visit [2] [3].
That tradeoff works for these sites. Their main jobs are publishing information, showing events and directories, and linking to outside services. Jekyll can build those pages from Markdown, HTML, and YAML source files. The council can add or change content without paying someone to develop a custom content-management application. There's also documentation to help a future contributor preview the project and follow its publishing process.

A static site isn't the answer to every web problem. On its own, it doesn't give you a private member portal, a custom donation database, or server-side application logic. If the council needs those later, it can use a service built for them or add a separate application. Keeping the public information site simple means we're not building and maintaining features the organization doesn't need yet.
How the sites reach their custom domains
GitHub Actions builds the Jekyll source, and then GitHub Pages publishes the generated files. GitHub supports custom Actions workflows that build a static site and deploy the resulting artifact [4]. The two repositories have separate jobs. The GAC site builds from its source repository, and the asset library deploys from its own repository.
The main GAC site uses a production branch and a required build check. Changes come in through a pull request, the check confirms the production site can build, and the approved version gets deployed to griffinarts.org. There's a staging workflow too, but staging publishing is paused as I write this. The asset library is simpler. A change to its main branch starts a build and deploys the reference site to assets.griffinarts.org.

GitHub Pages supports custom domains, but someone still has to manage the domain registration and DNS. GitHub can set up HTTPS once a domain is configured correctly [5]. So even when the hosting platform charges nothing extra, the domain name is still a separate renewal cost.
What “low cost” really means
Jekyll itself is open-source software, and GitHub Pages can keep the hosting bill very small for a public site that's mostly content. The exact cost depends on how the repository and account are set up, though. GitHub Free includes Pages for public repositories. The GAC source repository is private, so whether it qualifies for hosting, and what any account plan costs, have to be looked at separately. Don't assume a private source repository gets the same no-cost deal as a public one [6].
If you're another small nonprofit thinking about this approach, a public source repository can keep the software and Pages hosting cost at zero under GitHub Free, as long as you're comfortable making the source public. That doesn't make every part of the project free. Budget for:
- domain registration and renewal;
- any GitHub plan or Actions usage beyond the included allowance;
- payment-processing fees or other fundraising-service costs;
- optional fees for contact forms, email, analytics, or other outside services; and
- the time someone needs to write, review, update, and maintain the content.
GitHub documents size, bandwidth, and other usage limits for Pages. It also says the service isn't meant to be free hosting for an online business or a site built mainly to facilitate commercial transactions [7]. The GAC site is an informational nonprofit site, and Givebutter handles donations, so there's no custom payment code. Every organization should check the current terms and limits against its own use.
I wouldn't tell anyone “a nonprofit website costs nothing.” What I would say is that a small organization can publish a good informational site without buying a server or paying for a custom application. It just has to keep the feature set to what it needs, check whether its repository qualifies, and plan for domains and third-party services.
Check whether the site is doing its job
A new website doesn't need years of analytics to prove itself. Early on, the real test is whether it helps someone get a task done every time: find the next event, figure out how to take part, make a donation, or download the right logo. Those are service checks. They don't show that the site changed attendance or had a measurable effect on the community.
A small nonprofit can look at a few simple signals every month or quarter:
- Event information: Check that upcoming listings show the right date, time, location, cost, and ticket link. Ask event partners whether they can quickly find the details they need to share.
- Ways to participate: Test the membership, donation, contact, and signup paths on a phone. Make sure each button goes to the right form and that a visitor can tell what happens next.
- Fundraising handoff: Compare the donation and membership links on the site with the active Givebutter campaigns. Where campaign reporting allows, look at completed transactions separately from page visits or button clicks.
- Brand materials: Ask a board member or partner to find the right logo for a specific use. If they can't tell which file to download, fix the catalog or the usage notes.
- Content maintenance: Look over key pages for outdated dates, contact details, or descriptions. Write down who owns each update so the information doesn't depend on one person remembering every change.
You don't need a fancy measurement system for any of this. A shared checklist, a quick conversation with event organizers, and the reports the donation platform already gives you may be enough to catch broken links or confusing instructions. If the organization uses web analytics, stick to a few questions that could lead to a change, like whether people reach the event page or click through to a campaign. Don't collect personal information you don't need.
Keep activity and outcomes separate. Page views and link clicks show whether people used a path. They don't prove the website is why someone attended, donated, or got involved. As programs grow, the council can compare site activity with event registrations, donations, or participant feedback, using clear date ranges and definitions. For now, what we have is a working, maintainable way to publish information and connect people to the next step.
Measure whether the path works before claiming it changed the outcome.
Where I'd start if you're another small nonprofit
If you're starting a similar organization on a tight budget, begin with what people need to know most: what the organization does, who's responsible for it, what's happening next, and how to take part or give. Pick a setup that fits those needs. Don't pay to build a custom system before you know you need one.
Use static hosting for public information that doesn't change too fast. Leave payments and other sensitive workflows to services built to handle them. Put approved brand files somewhere people can find them. Write down how updates work so the site doesn't depend on one developer forever. And check the real costs, account requirements, service terms, and renewal dates before you call the plan free.
Griffin Arts Council now has a public home at griffinarts.org and a brand library at assets.griffinarts.org. That gives a brand-new organization a place to share information while it builds its programs, relationships, and operating capacity.
- Givebutter. (2026). Givebutter Pricing. Givebutter. https://givebutter.com/pricing
- GitHub. (2026). Setting Up a GitHub Pages Site with Jekyll. GitHub. https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll
- GitHub. (2026). What Is GitHub Pages?. GitHub. https://docs.github.com/en/pages/getting-started-with-github-pages/what-is-github-pages
- GitHub. (2026). Using Custom Workflows with GitHub Pages. GitHub. https://docs.github.com/en/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages
- GitHub. (2026). Configuring a Custom Domain for Your GitHub Pages Site. GitHub. https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site
- GitHub. (2026). GitHub’s Plans. GitHub. https://docs.github.com/en/get-started/learning-about-github/githubs-plans
- GitHub. (2026). GitHub Pages Limits. GitHub. https://docs.github.com/en/pages/getting-started-with-github-pages/github-pages-limits
