This site is an independent resident-built resource. It is not affiliated with the City of Trussville, the Cahaba Homestead Heritage Foundation, or any political organization. It exists to put scattered information — city documents, the proposed ordinance, the survey, both sides of the debate — in one place so residents can read for themselves.
A neighborhood is not a museum.
It's the people who live in it.
The City of Trussville is considering a new ordinance that would single out the Cahaba Project — and only the Cahaba Project — for binding architectural design review of every home renovation, addition, and rebuild. Before the City Council votes, every household here deserves the facts. Both sides. Read for yourself. Then make up your own mind.
Our goal is to educate our community and bring neighbors together — not to divide them. We believe informed residents make better decisions for the place they call home.
The information about this proposal is scattered — city documents, the heritage foundation's website, Facebook posts, council minutes, and a confusing survey. This site puts it all in one place — both sides, with sources — so every household can read for themselves and decide.
Compiled by a Cahaba Project homeowner and reviewed by neighbors before it went live — so every fact gets checked and one person's bias stays out of it. Not the City. Not the Heritage Foundation. Not a political group. Just neighbors trying to make a confusing situation easier to understand.
This site is long on purpose — the facts about this proposal have been scattered, and we gathered them in one place and checked each one. But if you only have a minute, here is the heart of it:
We've worked to be fair to both sides — the preservation case is presented here too. Because the decision rests with the Council and not with residents, the most important thing you can do is get informed and speak up before the vote.
A neighbor asked a fair question: if a story is going to be told, tell the whole story. So here it is, from the iron furnace to today — as plainly as we can tell it, without leaving out the parts that don’t fit an argument. Read it start to finish and one thing becomes clear: Cahaba has never stood still.
Warren Truss built a grist mill on the Cahaba River in the 1820s, and the settlement that became Trussville grew up around it. For decades this exact ground was industrial: a blast furnace operated near today’s Cahaba Elementary, and when it was dismantled it left a mountain of slag behind. The idle site even served for a time as “Jefferson County Camp No. 3,” a prison camp. In 1935 the property was sold to a federal housing effort — and the land’s next life began.
As one of Franklin Roosevelt’s New Deal communities, the federal Resettlement Administration (folded into the Farm Security Administration in 1937) built a planned village here for working families who commuted into Birmingham. Built in plain sight of the old slag pile, it was first nicknamed “Slagheap Village,” then renamed for the river: Cahaba. In all, 287 dwellings — 243 single-family homes and 44 duplexes — rose between 1936 and 1938, along with streets, sidewalks, parks, and the stone gateway and gazebo, at a total cost of $2,661,981.26.
At first, no one here owned their home. Approved families rented from the government for $14 to $23 a month. That changed after the war: in 1946–47 the government offered residents the first chance to buy, and families purchased their homes for roughly $4,400 to $9,000 each. The parks and water system were handed to the town, the deeds were transferred by 1948, and in 1947 Cahaba Village and Old Trussville voted to incorporate together as the City of Trussville. The day the families got their deeds, Cahaba stopped being a federal “project” and became an ordinary neighborhood of owners — free, like any owners, to make their own choices.
For half a century, Cahaba did what neighborhoods do. Homes changed hands and changed shape — porches enclosed, kitchens modernized, rooms and carports added, a few homes rebuilt — as one generation handed the place to the next. Trussville grew up around it; when interstates 59 and 459 were completed in the 1980s, the city roughly tripled in size. Through all of it, with no binding design rules of any kind, Cahaba kept its character not because change was forbidden, but because neighbors made their changes carefully. The fullest record of these years lives with the people who were here — see the “Read more” note below.
As the neighborhood neared seventy, the City created a Design Review Committee to look over plans for new construction, demolition, and major remodels in the Project. From the start its role was purely advisory — neighbors went through review, but nothing was binding. Then on March 29, 2006, Cahaba Homestead Village was added to the National Register of Historic Places, recognized as the largest and most intact Great Depression–era planned community in Alabama. The honor put a name to what residents already felt. On its own, it set no rules over what a private owner could build.
For its first seven decades the neighborhood barely changed: by the time it reached the National Register in 2006, only about 14 of the original 287 homes had been lost — under 5 percent — to fire, severe weather, age, and the occasional demolition. After 2006 the pace of teardowns picked up, and by the mid-2010s a cluster of original cottages had been replaced with much larger homes — enough that the neighborhood found itself debating its future for the first time. In February 2017 the City Council passed a 90-day moratorium on demolitions while it studied guidelines; it expired that June with no new rules. A neighborhood survey that summer found most respondents open to some kind of standards — but far from unanimous, and homeowners were genuinely split. A preservation ordinance was floated in 2018 and set aside. Good neighbors simply did not agree on the answer — and still don’t. The disagreement isn’t new, and it was never really about the facts. It was about subjective, personal opinion — just as it still is today.
In 2021, residents founded the Cahaba Homestead Heritage Foundation — a volunteer 501(c)(3) — to document and celebrate the Project’s history. That August, more than fifty neighbors filled a City Council workshop to hear its first presentation. The city said it hoped to find a “happy medium.”
The Foundation launched its annual Heritage Days in 2023 and its “Cahaba 100” improvements ahead of the community’s centennial in the 2030s: rebuilt stone gateways dedicated in January 2024, four 1930s streetlamps relit in October 2024 for the first time in fifty years, the gazebo restored, a daffodil trail planted. All of it done by choice, by neighbors, with no one compelled. It was also in early 2024 that a new proposal began to take shape — to replace the neighborhood’s zoning with a binding historic overlay. That’s where today’s story picks up, in the timeline just below.
Read the whole timeline and one thing stands out: Cahaba has never stood still. It began as rental housing the families didn’t own, became a neighborhood of homeowners free to make their own choices, and has been reshaped — added onto, modernized, rebuilt, replanted — by three generations of the people who actually lived here. The continuity Cahaba is loved for was never the absence of change. It was neighbors changing the place carefully, together, on their own terms.
That’s why the choice in front of us isn’t really a question of facts. Everyone agrees the history matters. Everyone can read the same dates. Where neighbors differ is on something facts can’t settle — how much each family should be free to write the next chapter of their own home, and how much should be decided for everyone at once. That’s a question of values, memory, and feeling, and good neighbors looking at the identical timeline will honestly land in different places. No ordinance, and no website, can make that disagreement disappear.
Our view is simple: a question this personal belongs to the people who live here — settled neighbor to neighbor, not handed down from City Hall. Respect the past. Let the people who call Cahaba home choose its future.
Read more — the fuller story is kept by the neighbors who lived it.
For resident histories and the deepest account of the decades this timeline can only sketch, see Gary Lloyd’s history of the Project, The Model City, and the Cahaba Homestead Heritage Foundation ↗. Vintage 1937–1940 photographs of nearly every street are preserved in the Birmingham Public Library Archives.
A proposed "Cahaba Homestead Village Historic Overlay District" would replace the existing R-CP zoning with binding design review of construction, renovation, and demolition. The draft ordinance is public. The public hearing already happened in April. The City Council vote still lies ahead — coming in months, not years.
The City established the Design Review Committee for the Cahaba Project. From the outset, the Committee's role has been advisory: every owner planning new construction, demolition, or major renovation must go through Design Review, but the recommendations are not legally binding. The City has no authority to mandate aesthetic compliance on private property without a binding overlay ordinance. For twenty years, this advisory framework has been the entire system — and it has worked, imperfectly but transparently. The current proposal would convert that advisory system into a binding one for the first time.
The Cahaba Homestead Heritage Foundation presented a draft overlay concept to the Planning & Zoning Commission. The Commission supported the concept but rejected the proposed $10,000 demolition fee. The subcommittee that drafted it included now-Mayor Ben Short.
P&Z Chairman Darrell Skipper formally updated the Commission on his efforts to amend the Zoning Ordinance by "replacing the R-CP district with a Cahaba Project overlay district."
Written hearing notices were mailed to Cahaba Project residents along with a QR-code survey from the Mayor's office. The survey is the one whose design we examine in detail below.
The public hearing took place. Residents spoke on both sides. The Commission has since made modifications based on the hearing — including allowing stone as an accent material rather than banning it entirely.
The Planning Commission's recommendation has not yet been voted. When it is, the matter goes to the five-member Trussville City Council — the people who will decide. They have said they want to hear from the community before they vote. This is the moment that matters.
The draft is public. We read all 15 pages. Here's what the proposed Cahaba Homestead Village Historic Overlay District would mandate for homes inside our neighborhood. Quotes are from the draft ordinance, marked "DRAFT" in red.
A common misunderstanding: the ordinance does not ban demolition. You can still tear down. The catch is what comes after. Once you do, your replacement home must conform to a specific list of design requirements — chosen by the Design Review Board, not you.
Before the City will issue a demolition permit, you must submit the full plans for the home you intend to build in its place. The Design Review Board reviews and approves those plans first. If they say no to your design, you can't demolish.
Two stories maximum. Gable or hip roof only. Roof pitch must be between 8:12 and 10:12. Front roof ridge must run parallel to the street. Windows taller than wide, no arches facing the street. Garage hidden behind the house. These are not suggestions — they are mandates.
Every roof visible from the street “shall be covered with metal shingles or material that has the appearance of metal shingles.” Cedar shake, asphalt, slate, and standing seam — not permitted on the front. Yet the City's own Cahaba Project neighborhood logo features a gazebo with cedar shake shingles, and the City's newly built pickleball and tennis restrooms at the Mall wear a green standing seam roof — neither of which would meet the standard the ordinance would set for residents.
Wood, fiber-cement, and brick are permitted as primary materials. Stone is allowed only as an “accent.” A stone-front home — a common Trussville style — is not permitted. The ordinance does not define what percentage qualifies as an “accent,” leaving the call to the Board.
Even though some of these are used widely in Trussville's newer neighborhoods, they are prohibited in the Cahaba Project. So is board-and-batten siding — a style that has been used in the neighborhood for years.
If your plans don't match the Board's interpretation of “compatible,” the Board can deny your application. You can resubmit. You can appeal — but only to the same City Council that adopted the rules. There is no circuit-court review built in.
The proposed ordinance bans the very roofing material the Cahaba Project's own iconic gazebo wears at the neighborhood entrance — cedar shake shingles. The same shape used in the neighborhood's emblematic structure would not be permitted on a homeowner's new build under the proposed rules. The City's newly built pickleball and tennis restrooms at the Mall make the same point from the other direction — they wear a green standing seam roof, a material the ordinance would not allow on a resident's street-facing roof. That is a fair question to ask: why is the standard for our homes stricter than the standard the City applies to its own buildings?
The Cahaba Project gazebo, featured on the cover of the City's own Cahaba Project Construction Guidelines (2023).
If a tornado, fire, or fallen tree damages your home more than 50% of replacement value, you cannot rebuild what you had. You must build to the new ordinance. Your insurance pays for what you had; the City says no.
Section VI.C exempts "residential structures constructed after the Cahaba Project was transferred to the City of Trussville" from the design standards for all repairs and remodels. The new million-dollar homes already built don't have to follow these rules. Only the original 1938 cottages do.
The Design Review Board has 7 members. Only ONE is required to have "a background in either architecture or construction." Zero are required to live in the Cahaba Project. The people deciding what your home can look like don't have to live next to it.
If the Design Review Board denies your plans, your appeal goes back to the same council that passed the rules — not to a circuit court (the safeguard the state historic-preservation statute provides). That's an unusual structure for binding aesthetic regulation.
The full ordinance is available on the City of Trussville's website. We encourage every household to read it for themselves before forming an opinion.
Here's every major provision of the draft ordinance, with the exact proposed language, what's already on the books today, and a neighbor's note. Tap any rule to expand it. You'll quickly see that a large share of the ordinance restates existing law — and that a smaller, identifiable set of provisions are the genuinely new restrictions worth focused attention.
One structural point first: the proposal is actually two coordinated ordinances — a Cahaba Overlay District Ordinance (what land use is allowed, which repeals and replaces current R-CP §30) and a separate Design Review Ordinance (how projects get reviewed, which creates the binding Design Review Board). The provisions below are drawn from both.
The proposed text restates a rule that already exists. Adopting it changes nothing.
This rule exists today as guidance only. The ordinance would make it enforceable.
This rule has no parallel in current Trussville code. It would be a new requirement.
An existing rule is being changed, narrowed, or expanded.
The exact current language couldn't be confirmed online. Needs city verification.
What the ordinance says it's trying to do, and what's allowed to exist in the district.
The Cahaba Project is a historically significant area of the city in which certain protections are desired… The Cahaba Homestead Village Historic Overlay District is established to address the mixed land uses within the survey of Cahaba… and to maintain the historical integrity of the district.
The current R-CP Section 30.1 uses nearly identical language: "This mixed use development… was established in the late 1930s. The Cahaba Project district is established to address the mixed land uses within the survey of Cahaba, as recorded in Map Book 29, Pages 30, 31, and 32 and to maintain the historical integrity of the district."
The stated purpose is admirable, and it's the same purpose the current code already articulates. The question is not whether to maintain the district's integrity — that's already settled — but whether binding aesthetic mandates achieve that goal better than the advisory framework we have now.
Detached single-family residences; Duplexes (North Mall, South Mall, and West Mall only); Multiplexes (corner of North Mall and Parkway Drive and corner of South Mall and Parkway Drive only); Park/public buildings (as allowed under the federal land grant documents); customary accessory structures and buildings; public utility service. Special-exception uses (by permit from the Board of Zoning Adjustment): home occupation (per Article VIII §5.0) and public utility facility.
Confirmed against the City's adopted Zoning Ordinance. The current §30.1 intent paragraph describes the district as "single family homes, duplexes, and triplexes, as well as parks, schools, and public buildings." The current §30.2 permitted-use list reads: detached single-family residences; duplexes (North, South, and West Mall only); multiplexes (the two named Mall/Parkway corners only); park/public buildings; customary accessory structures; and public utility service. So West Mall for duplexes, the two multiplex corners, and "public utility service" are already in current code — not new. The draft's changes are narrower than they look: it drops the word "triplexes" from the narrative, and it no longer lists day-care and family-care homes, which current §30.3 allows as special-exception uses by permit.
This is not a density change. No new commercial use or higher-density development is being introduced — the mixed-use character matches what the neighborhood has today. Two things are worth a clarifying question to the City: (1) the current §30.1 narrative lists "triplexes" and "schools" that the draft's wording drops, and (2) the draft no longer lists day-care and family-care homes as special-exception uses, which current §30.3 permits by special exception. Residents should ask the City to confirm nothing is quietly gained or lost in the translation.
No lots in this district shall be further subdivided into new building lots. However, a resurvey may be approved subject to all required setbacks of the district and approval by the planning and zoning board.
Confirmed against the City's adopted Zoning Ordinance: this prohibition exists today as current R-CP §30.6(C) — "No lots in this district shall be further subdivided into new building lots. However, a resurvey may be approved subject to all required set backs of the district and approval by the Planning and Zoning Board." (The same §30.6 already requires plans to be reviewed by the Cahaba Project Advisory Committee, and §30.6(D) requires any residence that is removed or substantially damaged to be replaced with an architecturally compatible structure.) It protects against carving original lots into smaller parcels for infill. The posted draft's own enacting clause states it will "Repeal Appendix A, Article VI, Section 30 of the Code of Ordinances and Replace it" — so the entire current R-CP section is repealed, not amended. We checked the full draft text: the words “subdivided” and “resurvey” appear nowhere in it. The draft mentions subdivision only once — in the part that says the new Design Review Board “shall not consider nor exercise any control over” the City’s subdivision regulations. So the overlay drops the district’s own absolute ban on splitting original lots (and the resurvey-with-Planning-and-Zoning-Board path that went with it) and simply leaves subdivision to the City’s general subdivision rules — which contain no Cahaba-specific prohibition. A long-standing, district-specific protection would be dropped, not carried forward — the opposite of a new protection. (A final adopted version could restore it; residents should press the City on whether the overlay still bars subdividing original lots.)
Subdivision has been prohibited the entire time the district has existed. If the new ordinance quietly drops that clause, it would weaken a protection, not add one — the opposite of the ordinance's stated purpose. Worth asking the City directly: does the new overlay still prohibit subdividing original lots?
How big homes can be, where they can sit on the lot, and how far from the property line.
Single-family residential: minimum lot 20,000 sq ft, minimum dwelling 895 sq ft. Duplex: minimum lot 15,000 sq ft per unit, minimum dwelling 1,150 sq ft per unit. Multiplex: minimum lot 15,000 sq ft per unit, minimum dwelling 750 sq ft per unit.
Confirmed against the City's adopted Zoning Ordinance, §30.4 "Dimensional Requirements." The current R-CP table already requires Single-Family — 20,000 sq ft lot, 895 sq ft minimum dwelling; Duplex — 15,000 sq ft lot and 1,150 sq ft per unit; Multiplex — 15,000 sq ft lot and 750 sq ft per unit. These are the exact same figures as the draft — the City's own statement that there is "no change to lot size and minimum square footage" checks out. This is restated, not new.
The City is correct that nothing changed here: a 20,000-square-foot minimum lot — nearly half an acre — already applies, and so do the minimum heated-dwelling sizes. Verified line by line against the current §30.4 table, these are not the figures to worry about. If you want to focus your attention, the genuinely new restrictions are elsewhere — start with the height caps below.
Principal structures — Front Yard: 40 feet. Rear Yard: 40 feet. Side Yard: 15 feet. Corner lots shall observe front-yard setbacks on all sides abutting streets. Accessory structures — Rear: 10 feet. Side: 8 feet.
Confirmed against the City's adopted Zoning Ordinance, §30.4. The current R-CP setbacks are already 40 ft front, 40 ft rear, and 15 ft side for principal structures, and 10 ft rear and 8 ft side for accessory structures — with corner lots observing front-yard setbacks on all sides abutting streets or rights-of-way. These are identical to the draft. This is restated, not new. The City already enforces them through the Engineering and Inspections Department before any building permit is issued. See the setback diagram ↓
Setbacks are not new. The City already enforces them. Plans that violate setbacks don't get permits today — and won't tomorrow, ordinance or no ordinance.
The height for any residential or accessory structure shall not exceed 23 feet for 1 story structures and 32 feet for 2 story structures, measured from first-floor elevation to the ridge of the main roof or the tallest portion of the roof structure. No structure shall exceed 2 stories above grade. The height of residential structures surrounding the Mall shall not exceed the height of the original structure.
Confirmed against the City's adopted Zoning Ordinance: the current R-CP §30.4 "Dimensional Requirements" table sets lot size, dwelling size, and setbacks but contains no height limit and no maximum-stories rule. (Article VII §4.0 ties building height to "the heights specified in the district requirements" — and the R-CP district specifies none.) So the draft's caps — 23 ft for a 1-story, 32 ft for a 2-story, a 2-story maximum, and the Mall-adjacent "no taller than the original structure" rule — are genuinely new for this district, not a restatement.
Because today's R-CP code sets no height ceiling at all, the 23/32-foot caps and the 2-story maximum are a real new limit — modest, and arguably reasonable for a neighborhood of one- and two-story cottages, but new, and residents should see it as such. The Mall-adjacent piece — homes surrounding the Mall capped at their original height — is meant to protect Mall sightlines. Fair to ask: does "original structure" mean the cottage that stood there in 1938, or the structure currently standing today? The draft doesn't define which, and the difference is significant for any owner planning to rebuild.
Maximum 2 stories.
Today’s R-CP zoning (§30.4) sets no height or story limit at all — only lot size, dwelling square footage, and yard setbacks. None of Trussville’s single-family districts (R-1 through R-6 or R-CP) cap stories; only multi-family and commercial districts do. So a hard two-story maximum is a new rule the overlay would add — even though it happens to match how the neighborhood already looks.
Worth knowing this is consistent with what the neighborhood looks like today. No 3-story homes have been built since the district was established.
What roof shapes, pitches, and materials are mandated under the proposed ordinance.
The roof shape shall be gable or hip. The front roof ridge shall be parallel to the street in front of the house. The totality of street-facing gables shall not exceed 50% of the length of the roof.
The current Cahaba Project Construction Guidelines (advisory, 2023) state: "Houses shall use common roof forms and materials found in the historic district and shall include gable or hipped roofs and eve details appropriate to the building style. Avoid complex and unbalanced roof forms as well as flat or boxy roofs for the main part of the house." The Guidelines also note this "does not apply to carports, sheds, or other auxiliary structures." This guidance exists today — it's just not enforceable.
This converts existing guidance into a binding rule. Worth asking: how often, in 88 years, has anyone built a flat-roofed home in Cahaba? If the answer is "never," the question becomes whether a binding rule is solving a real problem or a hypothetical one.
The main roof pitch shall be within an 8:12 to 10:12 slope. Ancillary roofs, such as porch roofs, may be as low as 1:12 but shall not exceed the pitch of the main roof.
The current advisory Guidelines say: "Most roof pitches in the historic Cahaba Project homes are 10:12. Some accessory roofs over porches, etc. may be less." The Guidelines describe what's common — they do not mandate a specific pitch range. The 8:12-to-10:12 mandate on the main roof is new and binding.
To be fair to the draft, it does allow porch and ancillary roofs to go as low as 1:12 — so the rule isn't as rigid as a single number. But the main roof is locked to 8:12–10:12 with no stated variance path. A homeowner who wants a slightly steeper or shallower main-roof pitch, even for a fully compatible design, would have to seek relief. The current advisory document only describes 10:12 as "typical"; the ordinance turns a description into a binding band.
All roofs visible from the street facing side of the structure shall be covered with metal shingles or material that has the appearance of metal shingles. Standing seam metal roofing may be used for low-pitch porch roofs or for roofs not visible from the street facing side of the primary structure. Screw-down metal roofing is not permitted except on accessory structures. Corner lots shall use metal shingles for all roofs visible from any street.
The current advisory Guidelines say: "The original Cahaba Project homes were built with metal shingles. All roofs visible from the street shall be covered with metal shingle or material that has the appearance of metal shingles… Corner lots should use metal shingles for all roofs visible from any street." The same language — but currently a recommendation, not enforceable.
We're thankful the rule lets homeowners use "material that has the appearance of metal shingles" — that gives manufacturers some flexibility. But there are two real concerns worth raising about this provision.
1. The contradiction with the City's own buildings. The Cahaba Project's own iconic gazebo at the neighborhood entrance — featured on the cover of the City's own Construction Guidelines — has what appear to be cedar shake shingles, which would not be permitted on a homeowner's new build under this rule. And the City's newly built pickleball and tennis restrooms at the Mall wear a green standing seam roof — another material the ordinance would not allow on a resident's street-facing roof. If cedar shake is right for the City's own landmark and standing seam is right for its own new construction, why is neither acceptable on a homeowner's roof?
2. The material-availability and research-gap problem. The original 1938 Cahaba Project roofs were silver-finish metal shingles with a wood grain design pressed in. The ordinance language is meant to honor that. But the roofing contractors the City has been steering homeowners toward primarily stock pressed-wood-grain metal shingles in every color but not silver metal to match the original shingles. When homeowners have asked whether truly period-appropriate silver-finish shingles exist, they have at times been told the answer is no. That is not accurate.
One concrete, verifiable example: The Aluminum Shingle Company (Perma Lock), based in Kaysville, Utah, has been manufacturing aluminum shingles since 1948. They produce a plain silver-finish, wood-grain pressed aluminum shingle that matches the original 1938 Cahaba Project shingle as closely as any product commercially available in 2026. The company is a Metal Roofing Alliance member, the product is made from 95% recycled aluminum, and it carries a lifetime warranty. The silver wood-grain option does not appear on the company's website — homeowners interested in it have to call directly at 877-319-7999 (or email info@aluminumshingle.com) to request pricing, photos, and physical samples. That is part of why local roofers either don't know about it or don't present it as an option.
To be clear: this site does not advocate for one shingle brand over another. Homeowners should have the widest practical range of options — cedar shake, standing seam, asphalt, aluminum shingles in a variety of finishes. The narrower and more important point is this: if the City is going to mandate roofing materials in the name of historical accuracy, the City should have done the basic research to know which materials actually achieve it — and should not have steered homeowners toward visually inaccurate options while letting them believe historically accurate alternatives do not exist. That is a research gap. It connects directly to the concerns raised in Questions Worth Asking, Q2 about who drafted this and what they knew.
What homes can be built out of — and what's prohibited.
All portions of the house shall have siding that is between 6 and 9 inches in exposure. Acceptable siding materials include wood or cement fiber board in plank or shake shingle, and brick; all brick shall be modular or queen size. Stone shall be allowed as an accent material but not as a primary material.
The current advisory Guidelines list "wood (plank or shingle), hardy board (shake or shingle), or brick" as acceptable, and place stone in the "discouraged" category alongside vinyl, stucco, exposed concrete block, and T-1-11. The original draft of the proposed ordinance fully prohibited stone. After the April 13, 2026 public hearing, the Commission modified it to allow stone as an accent material.
We're thankful the Commission listened and added stone back as an accent material after the hearing — that responsiveness deserves recognition. But the next question is fair: should the ordinance limit how much stone a homeowner can use? The proposed rule never defines what percentage of a façade qualifies as "accent" versus "primary." That call gets left to the Design Review Board to interpret case-by-case. A homeowner planning a stone-front home — a common Trussville style — has no clear standard to design to.
There is also a consistency question worth raising. Stone is already woven through this neighborhood and the City's own work — the original stone entry walls and gateways, the stone piers beneath the gazebo on the City's own Cahaba Project logo, and homes built here over the years — and the City is using stone as a primary material on the new municipal construction going up nearby. If stone is the right material for the City's own landmarks and buildings, used as a primary material rather than an accent, it is fair to ask why a homeowner may use it only sparingly.
Non-conforming siding materials, including vinyl, aluminum, stucco, board & batten, exposed concrete block, and plywood or oriented strand board, are not permitted.
The current advisory Guidelines "discourage" vinyl, stucco, stone, exposed concrete block, and T-1-11. They are not currently banned. The proposed ordinance makes them binding prohibitions and adds aluminum, board-and-batten, plywood, and OSB.
Two questions worth raising. First: board-and-batten siding has been used in the neighborhood for years on accessory structures and some additions — banning it outright affects homeowners who already have it. Second: the cost difference between fiber-cement plank ($) and the banned materials ($$) is real. Forcing higher-cost materials on every renovation raises the cost of preservation. Is the goal preservation, or is it preservation only by homeowners who can afford the premium materials?
Foundation material and the height of the exposed area between the ground and the bottom of the walls should be consistent with other historic buildings in a neighborhood. Exposure of one to three feet is generally consistent with most historical houses.
This language comes from the current advisory Construction Guidelines (Section D.4). We checked it against the binding draft ordinance: the draft's design standards (Section VI.B) do not include a foundation-height provision. So this would remain advisory guidance, not an enforceable rule.
We're including this only to be complete and accurate. Some summaries circulating online treat every line of the advisory Guidelines as if it were part of the ordinance. It isn't. The binding draft is narrower than the full Construction Guidelines — and residents should evaluate the ordinance on what it actually says, not on guidance that never became law.
Mandates on the visual rhythm of the home's street-facing elevation.
No arched windows or doors shall be on street facing elevations. Windowpanes shall be taller than they are wide.
The binding draft (Section VI.B.f) contains only the two sentences above. The more specific "2-to-1 height-to-width ratio" and "single-hung, six-over-six muntin" details that circulate online are from the current advisory Guidelines (Section C.1), not the ordinance. The draft's actual rule is the simpler "no arches, panes taller than wide."
The draft's window rule is narrower than the advisory guidance — worth knowing if you've seen the stricter 2:1 figure quoted. Still, "panes taller than wide, no arches on the street side" becomes a binding mandate. A homeowner who wants a transom over the front door (often wider than tall) or a picture window facing the street would need relief from the Board.
No horizontal sash, casement, or awning-type windows should be placed on the fronts of buildings.
This is from the current advisory Guidelines (Section C.3). It is not in the binding draft ordinance's design standards. The draft's only window rule is "no arches on the street side, panes taller than wide." This window-style restriction would remain advisory, not enforceable.
Included for accuracy. If you've seen this listed as part of "the ordinance," it isn't — it lives in the non-binding Guidelines. The binding draft is narrower.
Front and/or street facing doors should be single entry doors. Double doors are acceptable on rear portions of the house but discouraged for sides of the house commonly visible from the street.
From the current advisory Guidelines (Section C.5). It does not appear in the binding draft ordinance. This door-style preference would remain advisory, not an enforceable rule.
Another item that belongs to the advisory Guidelines, not the ordinance. We flag the distinction because the ordinance should be judged on what it actually binds — and "discouraged" is advisory-toned wording that wouldn't carry binding force here in any case.
What goes behind the house, and what shows from the street.
Attached garages shall be situated behind the house so that they are not visible from the street facing elevation of the primary structure. Accessory structures shall be in compliance with Article VII, Section 6.
The current advisory Guidelines (Sections E.1 and E.5–E.6) carry the same intent: "Attached garages are acceptable but should be situated behind the house so that they are not visible from the front of the house." Advisory today; the draft makes the attached-garage placement binding. (The "detached garages to scale" and "garage no taller than the house" lines that circulate are advisory only — they are not in the binding draft.)
Worth walking the neighborhood with this rule in mind. Several of the most recently rebuilt homes — and remodeled original Cahaba Project homes — have attached or detached garages clearly visible from the street: the garage door faces the driveway, which faces the street. Under the proposed ordinance, those homes would not be allowed to be built the way they were built. Combined with the Section VI.C exemption, the situation becomes especially odd: the recent rebuilds with visible garages would be exempt from having to comply, while any future homeowner would be required to hide their garage entirely from street view. The rule would enforce a standard the most recent construction in the neighborhood has already moved away from. And remember — design review here has been advisory, not binding — so these garages did not go up because the City judged them acceptable; they went up because the City had no authority over a home’s appearance. A fair question: if so many recent new builds and remodels across the neighborhood already place the garage in plain view, why should the next homeowner’s garage be treated as a problem? Garages are simply used differently today than when these homes were built in 1938 — and a rule that forces them out of sight works against how families actually live now.
Solar panels, skylights, and other external utility systems should be installed to the rear or side of a building where they will not be visible from the street. Solar panels/skylights shall be installed flat and not alter the slope of the roof.
Verbatim from current advisory Guidelines, Section F. Same wording, would become binding.
Federal and state law preempts most local restrictions on solar panel placement (Alabama Code §35-9A allows homeowners to install solar). The City should consult its legal department on whether this provision is enforceable. As written, it could expose the City to litigation from any homeowner who needs south-facing solar on a street-facing slope.
What happens when a homeowner wants to tear down — and what happens if disaster does it for them.
In the case of the proposed Demolition of a building in the Cahaba Homestead Village Historic Overlay District, the DRB shall consider… Building plans of any replacement structure to be constructed on the subject property after the demolition of the current structure.
Currently, Trussville issues demolition permits under its building code (Chapter 14, Buildings & Building Regulations), which requires utility disconnection and proof of proper septic abandonment or sewer capping before demolition begins — and that's it. There is no requirement to submit or get pre-approval of replacement plans before demolition. This requirement is entirely new.
This is the heart of the ordinance's practical effect, and it is worth stating plainly. Today, a homeowner with a demolition permit can tear down and then build a replacement of their own choosing, as long as it meets the existing setback, height, and building-code rules. Under the proposed ordinance, that sequence reverses: before the City will issue a demolition permit, you must first submit the full plans for the home you intend to build in its place, and the Design Review Board must approve that design. In plain terms — if these ordinances pass, an appointed board, not the homeowner, would dictate the design of your rebuild, and your right to demolish your own home would hinge on the Board approving the replacement first. If the Board rejects your design, you cannot demolish at all. That is a significant shift in how the process works, and every homeowner deserves to understand it clearly — not have it buried in technical language.
Should such nonconformity be destroyed by any means to an extent of more than 50 percent of replacement cost at the time of destruction, it shall not be reconstructed except in conformity with the provisions of this ordinance.
Trussville already has this exact rule citywide: Appendix A, Article III, Section 2.4: "A non-conforming building or structure which has been damaged by fire or other causes to the extent of more than 50 percent of its current replacement value at the time of such damage shall not be rebuilt or restored, except in conformity with the provisions of this Ordinance." The overlay restates the citywide rule — it doesn't invent it.
Important context that's often missed: the 50% rule is not new. It applies to every nonconforming building in Trussville today. What changes is the standard a Cahaba Project home would have to be rebuilt to. Today, that standard is the current R-CP rules. Tomorrow, it would be the new overlay's binding design mandates. So while the 50% threshold isn't new, what's required at that threshold changes substantially.
In plain language — can you rebuild what you have? Think of every home as either “conforming” (it already meets the overlay’s design rules: roof shape, materials, garage placement, and so on) or “nonconforming” (it does not — for example, an original cottage remodeled with modern materials, or a home with a street-facing garage). If a nonconforming home is destroyed by more than half — fire, storm, a fallen tree — this rule says you cannot simply rebuild the same home you had. The replacement must meet whatever design rules are in force at that time. Today that means the current R-CP requirements; under the overlay it would mean the new binding design standards. So if your home does not match the overlay’s design rules and it is more than 50% destroyed, you generally could not rebuild exactly what you had — the new home would have to comply.
One genuinely open question worth pinning down: the draft also exempts homes built after the Cahaba Project was transferred to the City (Section VI.C) from the design standards for repairs and remodels — but it does not spell out how that exemption applies to a full rebuild after a disaster. If this could affect you, ask the City directly, in writing: “If my home is destroyed by fire or storm, may I rebuild it exactly as it stands today, or will I be required to meet the new overlay design standards?” Every homeowner deserves a clear answer before the vote.
Residential structures constructed after the Cahaba Project was transferred to the City of Trussville shall be exempt from Section VI (B) for all repair and remodeling projects.
This exemption has no parallel in current code. Most historic preservation ordinances do the opposite: they exempt or ease rules for original contributing historic resources, and apply stricter standards to non-historic infill. This proposal inverts that approach.
This is the most consequential provision in the entire ordinance and the one most worth pressing the council on. It means two homeowners on the same street face two completely different rulebooks based solely on when their house was built. The owner of an original 1938 cottage has to meet every design mandate on every repair. The owner of a 2015 new build right next door does not. That's the opposite of how preservation ordinances are normally written — and it's the strongest legal vulnerability in the draft.
Is this the same as the 50% rebuild rule described above? No — they are two separate rules, and it is the combination that matters. The 50% rule governs when you are forced to build to the new design standards (if your home is more than half destroyed, you must). This exemption governs which homes have to follow those design standards in the first place (homes built after the City took over the Project do not). Stack them together and the effect lands hardest on an original cottage: it must meet the design mandates on every repair and remodel, and — because it does not qualify for this exemption — it would have to be rebuilt to those same mandates if it is ever more than 50% destroyed. The newer home next door carries neither burden for its repairs and remodels. In short, the houses the ordinance says it most wants to protect end up under the strictest rules, while the newest, least-historic houses get the lightest.
Who decides — and how they're chosen.
The DRB shall be composed of seven (7) members, each residing within the corporate limits of the City of Trussville. Four are nominated by the Mayor and approved by the City Council; one is appointed by the Mayor alone; one is appointed by the City Council alone; and one is a member of the Planning & Zoning board. At least one of the four members selected by the Mayor and the Council shall have a background in either architecture or construction. Members serve staggered three-year terms. A quorum is four voting members. The Chief Building Official serves ex officio, with no vote.
Trussville already has a Design Review Committee that reviews plans in its commercial, industrial, institutional, and historical districts in an advisory/recommending capacity. The proposed ordinance repeals and recreates that body as the binding "Design Review Board" and extends its authority over Cahaba Project homes. (Confirm the current committee's exact membership and enabling ordinance with the City Clerk before citing names publicly.)
Two specifics deserve scrutiny. First: of the seven members deciding what homes can look like, only one is required to have any background in architecture or construction. Second: not one member is required to live in the Cahaba Project. Members must live somewhere in Trussville — but the people deciding what a Cahaba homeowner's house may look like don't have to live anywhere near it. A simple amendment — requiring at least two resident members from the district and more members with relevant professional credentials — would substantially strengthen the board's legitimacy and its decisions' durability. And a fair question to put to the City now, before this board is even created: who has already been approached about serving on it, and what professional or preservation credentials would those members bring? Residents are entitled to know who will hold this authority over their homes — and what qualifies them — before the vote, not after.
An Applicant aggrieved by a decision of the DRB may, within fifteen (15) days, appeal the decision of the DRB to the City Council. On appeal, the DRB's determination is treated only as a recommendation; the City Council affirms or overturns it by resolution. Separately, if the DRB fails to act on an application within thirty (30) days of submission, the application is deemed approved.
Under Alabama's standard Historic Preservation statute (Code §11-68), appeals from an architectural review board go to Circuit Court — independent judicial review. The draft instead routes appeals back to the same City Council that adopts the rules. That is a structural difference from how binding historic-preservation boards typically work in Alabama. (The 30-day auto-approval is a genuine homeowner protection: if the board sits on an application, it can't stall a project indefinitely.)
If the DRB rules against a homeowner, the appeal goes to the council that wrote the rules — not to a neutral court — and the homeowner has only 15 days to file it. That isn't how Birmingham, Mobile, or most Alabama cities structure binding design review. A simple amendment routing appeals to the Circuit Court of Jefferson County (the state-statute default) would give residents a fair, independent review and give the City an extra layer of legal protection. The 30-day "deemed approved" clause is worth keeping — it's one of the few provisions that protects the applicant rather than the board.
Who and what the ordinance actually reaches — and what it leaves out.
Applicants must submit plans for construction, renovation, or demolition for projects in the District. "Major Renovation" means a renovation of 50% or more of a structure; "Minor Renovation" means anything that is not a Major Renovation or Demolition. The DRB reviews all of them before any permit is issued.
Today, routine repairs and minor exterior work in the Cahaba Project don't go before a binding review board — the current Cahaba Project advisory committee only makes recommendations to Engineering & Inspections. Under the draft, even a Minor Renovation visible from the street would require a DRB application before a permit could issue.
This is the provision most likely to surprise homeowners. The public conversation has focused on teardowns and new builds — but the draft's review net is far wider. Replacing street-facing windows, re-siding, changing a porch, altering a roofline: if it's a "Minor Renovation" the Board reviews it first. Applications must be filed at least 14 days before a meeting, with a fee set by the Council. Worth asking the City to spell out, in plain terms, exactly which everyday projects will and won't require an application.
This Ordinance shall not apply to any action by the City brought under Chapter 38 … any City owned property, any property owned by a public utility, any property owned by the state of Alabama, any property owned by Jefferson County or St. Clair County, or any property owned by the federal government. (Section X)
Separately, residential structures built after the Cahaba Project was transferred to the City are also exempt from the design standards for repairs and remodels (Section VI.C).
There is no equivalent exemption today because there is no binding overlay today. These carve-outs are created by the new ordinance.
The most visible maintenance concerns in the district — the City's own Public Works yard and unscreened construction storage, in plain view of the park and the walking trail — sit on City property, which this ordinance exempts. So does every newer home, under Section VI.C. The neighborhood's own public buildings get the same pass: Cahaba Elementary School — the historic Hewitt building, which sits inside the district — would not be held to the standards homeowners must meet. The ordinance asks original-cottage owners to meet strict standards on every project while exempting the government writing the rules and the newest houses on the block. If the goal is the district's appearance, a fair question is why the exemptions run in that direction.
Reading the ordinance carefully, the conversation isn't really about whether to have rules — most of the rules already exist in some form, and a few items people attribute to "the ordinance" aren't actually in the binding draft at all. The real conversation is about (a) whether advisory guidance should become binding, (b) whether the genuinely new restrictions are warranted, and (c) whether the structural pieces — the demolition pre-approval process, the broad Minor-Renovation review net, the Section VI.C exemption for newer homes, the Section X exemption for City and government property, the DRB's composition, the appeals path, and the quiet removal of the current no-subdivision protection — are designed correctly. Those are the questions worth bringing to the council.
You won't find one-sided argument here. Below are the strongest cases on both sides, as fairly as we can state them. Real preservation advocates and real growth advocates are good neighbors with real reasons. The disagreement is honest — and worth hearing fully.
Hear this case from its advocates: Cahaba Homestead Heritage Foundation ↗
Both sides love this neighborhood. The real question is not whether we care — it's who decides, on what evidence, and on what basis.
Numbers and quotes — sourced where we can, estimated honestly where we can't. The point isn't to win an argument. It's to give every household here the same starting information.
The Cahaba Project was added to the National Register of Historic Places in 2006. That listing is honorary — it's recognition of historic significance, but it does not, by itself, restrict what a property owner can do with their home. Federal designation gives Cahaba prestige; it does not give the City new powers over individual homes. The proposed overlay is what would create binding local restrictions for the first time.
Before any home gets built in Cahaba today, Trussville's Engineering and Inspections Department verifies setback (the minimum distance a building must sit from the property line — Cahaba's are 40 feet front, 40 feet rear, 15 feet side, with corner lots observing front-yard setbacks on all street-facing sides) and height rules. Plans that break these rules don't get permits. Construction that violates them gets stopped by the inspector mid-build.
A setback is the minimum open distance a building must sit back from your property line. You still own that land — but a structure generally can't be built in it.
On a corner lot, every side that faces a street uses the larger front-yard setback — so a corner lot can have two front setbacks.
Detached garages and sheds get smaller setbacks — 10 ft at the rear and 8 ft on the side — so they can sit closer to the lot line than the main house.
Illustrative public-education diagram — not to scale and not an official survey. Verify exact setbacks, easements, and right-of-way with the City of Trussville before building.
A note on what the eye actually sees. Setbacks are minimums — a home must sit at least 40 feet back from the front line, but it can sit farther, and many of the original cottages do. Most people cannot judge by eye whether a house is 40 feet back or 65; what they can notice is when one house sits forward of its neighbors. So when a newer home is built right at the 40-foot minimum between two original homes that happen to sit 60 or 65 feet back, it can look as though it is too close to the street — even though it follows the setback rules exactly. That impression is about alignment, not a violation: the home is fully legal, and the block still reads with reasonable flow and curb appeal. It is one more case where a home can look “off” to the eye while breaking no rule at all. And at that point the difference is a matter of subjective, individual taste — not a break in policy, and not something a building rule can fairly settle for everyone.
The new ordinance would add aesthetic mandates — roof shape, roof material, siding material, window proportions — on top of what is already enforced. The honest question for the council is whether the additional layer is warranted, not whether nothing exists today.
Roughly 50 yards from the back fence of multiple Cahaba Project homes — with the city-built walking trail running between them — sits the Trussville Public Works facility. Industrial metal building. Chain-link fence largely unscreened. A fleet of school buses parked behind the fence and visible from the community park. Concrete drainage pipes dumped in the woods nearby. It has looked like a construction zone for years.
The overlay would force private homeowners to meet detailed design standards. The City's own industrial facility — visible from a children's park, on land inside the Cahaba Project — would not. Screening a chain-link fence with an evergreen hedge runs roughly $15–$45 per linear foot. Before holding residents to binding design standards on their own homes, the City could meet that same standard on its own land — screening this fence and clearing the debris.
Photos taken from the Cahaba Project community park and walking trail · Spring 2025
A common worry is that without binding rules, someone will place a mobile home or metal barndominium on a Cahaba lot. In 88 years, that has never happened. Here's why:
The economics of the neighborhood make that outcome very unlikely. Buying a home here and clearing the lot to rebuild is a major investment, and people who invest at that level build accordingly. Placing a mobile home or metal barndominium on land worth $300,000 to $400,000 simply makes no financial sense — the value lies in constructing something substantial and lasting. In practice, the new homes going up in Cahaba are predominantly large, custom homes built by families who intend to live here, not by speculators or industrial users.
Could someone, in theory, build a boxy ultra-modern home that doesn't fit the neighborhood? Yes. In nearly nine decades, no one has. The cost of the land, prevailing neighborhood norms, and the existing (non-binding) Design Review Committee already steer builders toward designs that fit — and the track record bears that out.
Alabama assesses owner-occupied homes as Class III property at 10% of fair market value. Trussville's combined millage is 62.1 mills (state, county, school, and municipal levies combined). Recent sales of original Cahaba cottages cluster around $300,000. Large new custom homes in 35173 reach $600,000–$1,000,000.
That difference matters. Here's the annual property tax math:
Multiply across the rebuilds we'll see over the next decade and the City is looking at tens of thousands of additional dollars per year in recurring property tax revenue. That's funding for schools, roads, parks, and public safety — the things that make Trussville a great place to live. An overly restrictive overlay risks discouraging the very reinvestment that strengthens the tax base.
Many original Cahaba homes have not been substantially updated in decades. When a new owner buys one and decides to renovate seriously rather than rebuild, the honest budget tends to include all of the following:
Add it all up and a thorough renovation easily reaches $250,000–$400,000 on a home that, when complete, still has the original square footage and room layout. The same money will build a new home, to 2026 IRC standards, that uses 40–60% less energy per square foot, performs dramatically better in severe weather, has safer wiring and plumbing, accommodates a modern family's needs, and will last another 80 years.
That isn't disrespect for the past — it's construction reality. Some original homes are in good enough condition to renovate economically. Many are not. The preservation conversation should acknowledge this honestly. Homeowners who want to preserve their cottage should be supported and even financially helped through tax credits or grants. Homeowners who inherit or purchase a home requiring $300,000+ of deferred maintenance shouldn't be compelled into the more expensive path by ordinance.
Trussville already has ordinances on the books that the City does not consistently enforce. The most visible example comes straight from the Zoning Ordinance (Article IX, §3.2(E), "Parking Prohibitions"): "no boats, trailers, commercial vehicles, recreational vehicles, campers and/or similar equipment … shall be kept within a residential district unless such vehicle is parked behind the front building line." Yet trailers and campers regularly sit in front yards along Cahaba streets, sometimes year-round. The City has every authority to address this today. It chooses not to.
The honest question to the council is this: if existing rules go unenforced, what makes anyone confident new aesthetic rules — far more complex, far more subjective — will be enforced fairly and consistently? Before adding layers, enforce what already exists.
The City sells permits for door-to-door solicitation in Cahaba. In 2026, virtually no one shops via door-to-door sales — U.S. e-commerce now runs roughly $1.2 trillion a year — about 16% of all U.S. retail (U.S. Census Bureau). Meanwhile, the U.S. Supreme Court has recognized that "burglars frequently pose as canvassers" to scope out homes (Martin v. Struthers, quoted in Watchtower v. Stratton, 2002). Recent cases nationwide confirm the pattern: armed home invasions and burglaries staged by people posing as door-to-door salespeople.
The City cannot ban canvassing outright — the First Amendment protects it. But it can adopt a binding "Do Not Knock" registry that legitimate solicitors must honor, require background checks and photo ID badges, and restrict to narrow daytime hours. This is what other cities do. It's a safety improvement the council could pass this month — with bipartisan support and zero design-review committees.
The biggest complaint heard at the April 13 public hearing was not about roofs, windows, or siding. It was about size. Multiple speakers said the recently built homes are "dwarfing" the original 1938 cottages and breaking the visual rhythm of the streetscape. That concern is sincerely felt, and we do not dismiss it — but it is worth examining closely rather than accepting at face value, because the wrong diagnosis leads to the wrong policy response.
The original New Deal designers of the Cahaba Project were genuine forward thinkers. They platted this neighborhood with lot sizes generous enough that, even at full buildout with every house built right to the setback lines, homes still have meaningful breathing room. The 40-foot front and rear, 15-foot side configuration produces a streetscape that doesn't feel crowded — a quality most modern subdivisions cannot replicate. Trussville inherited a piece of design wisdom from 1938 that deserves to be honored. Tightening the setbacks is not the answer.
It comes from the size contrast between the original cottages and the new builds. The original 1938 cottages were roughly 1,000–1,300 square feet. Many of today's new homes are 3,000–5,000+ square feet — making the new homes 2 to 4 times the floor area of the originals, or roughly 35–60% larger in footprint depending on the lot. Even when both homes sit politely inside the same setback lines, the larger home reads visually as "bigger" because it is bigger. That contrast — not setback violations, not bad design — is what creates the impression people describe at the hearings.
It is also worth being clear that home size is not unlimited here. Two rules set the ceiling: the setbacks (illustrated in the setback diagram above) fix how much of the lot a building can cover, and the proposed two-story / 32-foot height cap fixes how tall it can be. Together with the size of the lot itself, they define the largest home that can physically be built — the “building envelope.” This hard ceiling is actually something the overlay would add: today’s R-CP sets no height or story limit at all, so the two-story cap is what makes a maximum size definable in the first place.
In plain terms for homeowners: picture leaving a 40-foot strip open across the front and back of your lot, plus a 15-foot strip down each side — whatever rectangle remains in the middle is where your home can sit, up to two floors. The bigger the lot, the bigger that rectangle, and the bigger the home the rules allow: a roughly 0.75-acre lot can legally hold a larger home than a 0.55-acre lot, even though both give up the same setback strips. To estimate your own lot’s ceiling, subtract 30 feet from its width and 80 feet from its depth, multiply the two, then double the result for the two-story cap — a theoretical maximum that lands far above the 3,000–5,000-square-foot homes actually being built. The takeaway: a home’s scale is already governed by your lot plus the height cap, not left wide open — which is exactly why the neighborhood’s generous original lots can hold homes so much larger than the 1938 cottages beside them.
The new homes being built in the Cahaba Project are, on the whole, beautifully designed. They flow, they have genuine curb appeal, and many would not look out of place in a design magazine — much as the lovingly restored original Cahaba Project homes do. They are not monstrosities in any aesthetic sense; they are simply larger than the cottages they sit beside. “Bigger” and “ugly” are not the same thing, and the public conversation has at times conflated the two.
The newer homes do use different materials, different colors, and slightly less boxy shapes than the 1938 originals — but a change in aesthetic is not a decline in it. No single design pleases every taste, and in a neighborhood with this much history, change is often met with hesitation simply because it is unfamiliar. Unfamiliar, however, is not the same as unattractive, and “different” is not the same as harmful to the neighborhood’s character. Whether a house is “beautiful” or “ugly” is an inherently subjective judgment, and debating the ordinance in those terms leads nowhere. The honest, useful approach is to separate the facts from matters of personal taste, and to weigh those facts rather than the adjectives no one will ever fully agree on.
If the Council's real goal is to address the size contrast, the policy tools for that look completely different from what's being proposed — direct floor-area caps, floor-area ratios, or tighter lot-coverage limits. None of those are in the draft ordinance — and, to be clear, none of them are what we are calling for, either. What's in the draft regulates aesthetics — roof shape, roof material, siding, window proportions, garage placement. A home built to comply with every aesthetic mandate in the ordinance can still be the maximum possible size that fits within the existing envelope.
That distinction matters: if "too big" is the real problem, the ordinance does not fix it. If "wrong style" is the problem, the ordinance does address that. These are two different conversations that have been conflated — and the Council should be clear about which one this ordinance is actually for.
There is one more wrinkle, and it cuts against the ordinance’s own goal. To its credit, the draft says it “shall not impose any architectural style, traditional or modern, as a condition precedent to approval” — no one is required to copy the 1938 cottages. But by mandating the cottages’ building blocks — the roof shape and a narrow pitch band, metal-shingle roofing, a short list of siding materials, specific window proportions — the ordinance steers every new home toward the cottage look while doing nothing about size.
That is the tension. A 1938 cottage was designed as a whole: its roof pitch, sight lines, materials, and window and door proportions were all chosen so that a small home reads as balanced and graceful. Those cues do not automatically scale up. Take a home the ordinance still allows to be built large — out to the setbacks, up to two stories — and require it to wear cottage-scale rooflines, materials, and window proportions, and you do not get a cottage; you get a much larger house wearing details borrowed from a much smaller one. Today’s new homes generally look good precisely because their designers were free to choose proportions and materials suited to a larger home — force a cottage palette onto that footprint and the result can read as forced and mismatched, less “in character,” not more. Regulating the surface details while leaving size untouched risks working against the very design quality the ordinance is meant to protect.
To be clear, this is not an argument for the City to cap home size. Larger homes are a natural result of today’s construction costs, modern family needs, and the kind of investment that lifts property values for the whole neighborhood — that is a benefit, not a problem to be zoned away. The point is aimed squarely at the concern preservation-minded neighbors raised at the hearing: this ordinance does not shrink the larger homes they are worried about, and by requiring cottage-scale detailing on homes that will naturally be built larger, it could deepen the very “out of character” feeling it was meant to cure. If the goal is to protect the neighborhood’s charm, mandating small-cottage detailing on large homes is as likely to work against that charm as to preserve it.
At the April 13 public hearing, several distinct voices came forward. Each of them deserves to be heard fairly. Here is what was said, and how a reasonable resident might respond to each.
Multiple residents stood up and described feeling visually overwhelmed by the largest of the recent new builds. That reaction is sincere and deserves a respectful hearing — but it is only part of the picture: a neighborhood is the people in it, not a postcard to be frozen in 1938. Families in 2026 do not live the way families did in the New Deal era, and the original footprints were never large enough for how households live today — homes have to be able to evolve and grow, as explained in detail in the Growth-With-Respect case. Their concern about scale is honest, and it deserves an honest policy response — which, as Fact ix above shows, the current ordinance is not. A narrow, size-focused rule would look completely different from this broad design ordinance. And a larger home is not, in itself, a problem to be fixed — it is usually a family choosing to invest here. And to the extent visual scale and street rhythm are a genuine concern, the front- and side-yard setbacks the City already enforces keep new homes on the established street line and off their neighbors — protecting the block's rhythm and curb appeal far more directly than any design rule. This ordinance isn't about the size of homes at all; it governs appearance and materials, so it simply isn't the tool to address a scale concern.
Some speakers have lived in the Cahaba Project since the 1950s and spoke movingly about wanting the neighborhood to look the way it did when they were young. That feeling deserves real respect. The longtime families who stayed, raised children here, and kept the neighborhood's heart beating for three generations are part of what makes the Cahaba Project one of the most distinctive places in Alabama. We are deeply thankful they have stayed.
The honest reality is that 2026 cannot perfectly recreate the snapshot of 1955. Families today often live differently and need more room than the original footprints offered, and building materials and methods have naturally evolved — but evolved is not the same as inferior. A new home can echo the neighborhood’s historic character in its rooflines, proportions, and materials, and be built with craftsmanship and quality every bit as high as the originals — only safer, more efficient, and to modern code. What cannot be brought back is an original 1938 home once it is gone; what takes its place, though, can be both thoroughly modern and genuinely beautiful. But the love of the place behind that feeling is real, and any good ordinance has to honor it without pretending it can freeze time. And here is the part that is within reach: while no rule can return the streetscape to exactly the way it looked in 1955, the neighborhood can absolutely recover the way it once felt — neighbors who know one another, look out for one another, and treat each other with genuine warmth and respect. That old-time sense of community cannot be mandated by an ordinance or erased by a teardown; it is something residents choose to live out, and reviving it would do more to preserve the true spirit of the Cahaba Project than any design standard ever could.
More than one speaker suggested that residents wanting larger or modern homes should leave the Cahaba Project and "move to Mountain Brook" — a reference to the wealthy Birmingham suburb. That comment, said in frustration at a public hearing, is worth naming directly: it is unhelpful, it is dismissive, and it works against the very preservation cause the speakers care about.
The families building new homes in Cahaba pay two to three times the property tax of the cottages they replace. They chose to raise their children in Trussville over hundreds of other options. Many of them grew up here themselves. They are exactly the families this city says it wants. Telling them they don't belong is not a policy position; it is a tone problem that makes the substantive conversation about scale and character harder to have for everyone.
A small number of speakers expressed the position that when an original cottage must be rebuilt, the replacement should reuse the salvaged components of the original home — saved roof shingles, original floors, original doors, even original doorknobs. The position is sincere and reflects genuine love for the neighborhood.
It is also unworkable as a binding ordinance standard. Insurance adjusters cannot value salvaged 80-year-old hardware. Modern building code cannot certify reused 1938 wiring or pipe. Builders cannot warrant the structural performance of repurposed 1938 floor joists. Lenders cannot underwrite a home built to that standard. And a homeowner whose home was destroyed by fire or storm should not have to litigate the salvageability of every doorknob with a Design Review Board to be allowed to rebuild on their own lot. The right tool for this view is encouragement and incentive (see A Better Path Forward), not mandate.
A frequent preservationist argument runs like this: instead of tearing down an original cottage to build a larger home, simply preserve the original house and add the additional square footage as a rear or side addition. Keep the original façade. Live in a larger home. Everyone wins. The argument is not wrong in principle. A small percentage of homeowners have pulled this off beautifully, where lot shape, lot size, and the homeowner's specific needs aligned with what an addition could provide. Those owners deserve genuine recognition for their work — and exactly the kind of incentive program described in A Better Path Forward below.
But for most homeowners, the "just add on" approach has real downsides that deserve honest acknowledgment:
None of this is meant to dismiss the add-on approach. For the right homeowner, on the right lot, with the right needs, it can be a genuinely beautiful path — and one this site enthusiastically respects. That is precisely why it should be a rewarded option, not a mandated one. The City's job is to make the add-on path attractive enough that more homeowners choose it voluntarily — not to forbid the alternative for everyone else.
Some context worth understanding, because it shapes what kind of fix the neighborhood actually needs:
Honest reading of the facts: a binding aesthetic overlay aimed at every single homeowner is a very wide net for what is, in real numbers, a narrow problem. A more surgical approach — make the existing advisory standards more attractive to follow through incentives; address specific problem-property cases through existing nuisance ordinances; reward owners who genuinely preserve original homes (see A Better Path Forward) — would address the actual concerns without sweeping every renovating family into the same regulatory framework.
The overlay itself solves a problem that isn't a crisis. By the City's own record, more than 90% of the original homes still stand after nearly 90 years; most losses came over decades from fire, weather, and age, not recent teardowns; and as original-cottage prices climb past $300,000–$500,000, buying one simply to demolish and rebuild is already becoming uneconomical.
Some perspective the current debate has been missing. Here is what the public record shows about how much the Cahaba Project has actually changed since 1938:
Two honest things follow from those numbers:
One: by any reasonable historic-preservation standard, an 8–9% loss rate over nearly nine decades is remarkable preservation, not a crisis. Many New Deal-era resettlement communities have not survived at all; most have lost far more. The Cahaba Project remains one of the most intact such villages in the South. The 287 figure is still the right way to describe this neighborhood, and the streetscape that makes it special is still very much here.
Two: the recent pace has picked up — an estimated six to nine homes over the past three to five years, faster than the long-run trend — and some residents understandably want a thoughtful response to that. But "thoughtful response" does not have to mean "binding aesthetic ordinance applied to every household in the district." Surgical, targeted approaches — the kind described in A Better Path Forward — can address the pace without imposing a permission process on every homeowner.
One last honest observation worth making. Of the 273 homes standing in 2006, only 264 were counted as "contributing" to the National Register nomination — meaning 9 of them, about 3.3%, had already been altered enough to lose historic-integrity status. Twenty years later, that percentage is almost certainly higher. The deeper reality is that nearly every home in the Cahaba Project has been modified for modern life: central air, modern wiring, updated kitchens, replacement windows, new bathrooms, additions, garages, fences. The "1938 original" that many preservation arguments invoke largely does not exist anymore in pure form. Most of what is being preserved — and is worth preserving — is the exterior character and the streetscape. Both deserve honest discussion when policy uses the word "original."
Two related claims worth examining honestly, because both have been used in the public conversation about this ordinance.
First, the property-value argument. Preservation advocates have cited research suggesting that historic designation can raise property values in historic districts. That research exists, and is often true in the contexts where it has been studied. But it is worth asking whether it actually applies here.
The Cahaba Project has been on the National Register of Historic Places since 2006. Honorary designation has been in place for twenty years. The dramatic property-value acceleration most residents have observed is recent — concentrated in roughly the past five to ten years. That timing does not line up with the 2006 designation. It lines up with a much broader transformation of Trussville:
Cahaba Project property values are rising because the location is exceptional — walkable to amenities, in a strong school zone, in a city that is visibly investing in itself. Historic character contributes to that appeal. But the dominant driver is location and amenities, not the regulatory framework around historic preservation. That distinction matters when policy is being justified by appeal to property-value research that was conducted in very different contexts.
Second — the related point about who is actually buying. When buyers do purchase original cottages, the most common pattern is actually a positive one for the neighborhood. Young families specifically seek out the original homes. They often prefer the unrenovated ones because the price is more accessible, and because the buyer plans to either substantially renovate or rebuild a home they intend to live in long-term and raise children in. They are choosing this neighborhood deliberately. They are not flipping for profit; they are committing to the place.
Whether a young family ends up doing a major renovation or a full rebuild, the underlying outcome is the same: a household choosing to invest in Cahaba long-term. That is exactly the kind of household every neighborhood says it wants. The conversation about new-construction aesthetics is downstream of this more fundamental win.
Worth raising directly. If the goal of the proposed ordinance is to preserve the historic character of the Cahaba Project, the rule does only one side of that job. It mandates strict aesthetic compliance on any homeowner who chooses to build new, rebuild after a fire or storm, or substantially renovate. It does not — and largely could not — require existing original-style homes to be maintained to a historic standard.
Anyone who walks the neighborhood today can see this for themselves. Many original 1938-style homes are in poor repair: peeling paint, rusting metal shingles, rotting wood window frames, weathered siding, sagging porches, neglected landscaping. The historic character those homes contribute to the streetscape is being degraded by neglect, not by replacement. The proposed ordinance does nothing about that. It regulates the visible-new while ignoring the visible-deteriorating.
If the honest question is "what most damages the historic character of the Cahaba Project today," neglect is a serious answer. A binding aesthetic ordinance on new construction does not address neglect. Incentives for preservation — the kind described in A Better Path Forward — actually do. Owners get rewarded for maintaining and restoring, not punished for adding a screened porch.
There is also a deeper principle worth naming. Once a city establishes that it can mandate aesthetic choices on private residential property — color, material, window style, roof line — there is no clean stopping point. Today it might be roofing materials and street-facing windows. The same logic could later extend to paint color, landscaping, porch furniture, holiday decorations, and any number of other personal choices. Government control over personal property does not tend to shrink once it has been established. It tends to expand. An inch of authority granted today is the foundation for a mile of authority claimed tomorrow.
Property rights are not absolute — there are legitimate restrictions a city can impose for genuine health, safety, and nuisance reasons. But the further restrictions reach into the aesthetic and personal, the more they conflict with what most American homeowners — across political lines — would consider basic ownership. That is a serious question worth weighing carefully before the precedent is set, not after.
The overlay is offered in the name of protecting the neighborhood — and, as the City frames it, the value of residents' homes. Fair enough. So it's worth asking what the City already owns and is already responsible for. Walk the Cahaba Project and you'll find public sidewalks — maintained by the City, not by homeowners — that have been left to deteriorate: concrete slabs heaved and split by tree roots, joints lifted inches out of alignment, crumbling edges. These are genuine trip hazards for children, older neighbors, and anyone pushing a stroller.
This isn't an aesthetic complaint. Uneven, displaced sidewalks are a recognized health-and-safety and accessibility (ADA) issue, and they sit squarely inside the City's existing duties — no new ordinance required. Repairing them protects residents in a concrete, immediate way that an aesthetic design-review board never will.
The honest question is one of priorities. Before holding homeowners to binding new standards on their own property, a City might first meet its own basic obligations in the same neighborhood: repair the hazardous sidewalks, screen the Public Works yard, and act on the maintenance-and-incentives approach in A Better Path Forward. Each delivers real benefit to Cahaba today — without reaching into anyone's property rights.
Heaved, root-lifted public sidewalk slabs in the Cahaba Project — trip hazards the City is responsible for maintaining.
The Mayor's office sent a QR-code survey to Cahaba Project residents. We read every question. The mailer is fair-toned, the topics are reasonable, and the two-adults-per-household limit is sensible. But the way several key questions are structured means the data will skew toward the answer the city wants — regardless of what residents actually think.
Mayor Short's letter is professional and acknowledges "both sides." Public hearing date listed. Two-adults-per-household limit. This part is done well. The problem is not the cover letter — it's what's inside the form.
The central question asks what reflects your view, with four choices: preservation, flexibility, "a balance," or "Other." There is no option to say leave the current rules as they are. The American Association for Public Opinion Research’s question-wording standards say a survey’s response options should include every reasonable choice — including neutral ones — and should not present only one side. Leaving out “keep things as they are” is exactly what those standards caution against.
"If demolition is allowed, should rebuilt homes meet some architectural design standards?" Who answers no to "some" standards? The word "some" makes it nearly impossible to say no. A yes is then counted as support for the binding design overlay — even though the question itself never mentions binding regulation.
Two questions sit back to back. One asks how important it is to preserve the architectural character of the neighborhood. The next asks how important it is to maintain “maximum” flexibility for property owners. Preservation is put in plain, sympathetic terms; property rights are framed as wanting the maximum — the most extreme version. A neutral survey would have asked about “property owners’ flexibility,” not “maximum flexibility.” One word tilts the comparison before anyone marks an answer.
One version of the “which design elements should standards apply to?” question lists building height, setbacks, roof style, exterior materials, porch design, and windows — with no “None” and no “Unsure.” A resident who opposes design standards altogether has no honest box to check; the question requires them to name elements to regulate.
Near the end: “Would you support a compromise allowing demolition with limited design standards for rebuilt homes?” The words “compromise” and “limited” are reassurance words, chosen to make no sound unreasonable — who is against a limited compromise? It fits the larger pattern: the survey never asks the plain question — “should the City create a binding ordinance that lets a board deny building permits based on how a home looks?” — and instead slices that one decision into a dozen small, agreeable pieces.
No single one of these questions is disqualifying on its own. But notice the pattern: every one leans the same direction — toward “yes, regulate something.” A survey whose wording, missing options, and omissions all tilt one way isn’t measuring what residents think — it’s producing a number the City can cite.
One more tell. Several questions are asked twice, in different forms — the Design Review Board question appears once as check-all-that-apply boxes and once as a single-choice list; “how much trust do you have in the City” uses two different scales; “would design standards impact property values” is asked two different ways. When the same question is posed inconsistently, the answers cannot be cleanly combined — a real problem for a survey the City says it wants to analyze as data.
In the interest of full transparency, here is the City’s entire survey — every section and question, in the order residents received it. Our notes above flag only the handful of questions we believe are structured in a way that will skew the results; everything else is reproduced here, unedited, so you can read all of it and decide for yourself. Tap any page to enlarge.
"We are running a parallel, address-based, privacy-protected survey below. It asks the same questions the City asks — plus the ones the City didn't. We'll publish the methodology and the raw counts. The council deserves both numbers."
The proposed ordinance arrived in the public conversation more or less assembled. Multiple drafts, design reviews, an exploratory committee, attorney input — most of it happened before residents had any meaningful chance to weigh in. The process did not break any law. But a few questions about how it got built deserve straightforward answers, and answering them honestly would build trust on every side of this debate.
These are questions, not accusations. Every fact below is from publicly posted City of Trussville meeting minutes. Read the questions, follow the citations, and reach your own conclusions.
For roughly twenty years, Cahaba Project construction plans have gone through an advisory review. Under current code (R-CP §30.6), the Cahaba Project advisory committee reviews plans for new construction, demolition, or major renovation and submits a written recommendation to Engineering & Inspections — but those recommendations are not legally binding. The City has no legal authority to mandate aesthetic compliance on private property without a binding overlay ordinance — and for two decades, no such ordinance has existed. Then in January 2024 — per public Planning & Zoning Commission minutes — Chairman Darrell Skipper proposed forming an exploratory committee to draft exactly that: a new binding overlay ordinance that would convert advisory recommendations into mandatory rules. That committee, with input from City staff and the City attorney, produced what is now on the table.
The minutes are specific about how it started. Under “Miscellaneous,” the Commission “listened to Amy O’Brien Peterson’s presentation on a proposed Cahaba Village Historic District Overlay,” and recorded that “Design Review already endorsed it as a concept.” The exploratory committee was then directed to work with her on the ordinance text. Ms. O’Brien Peterson is the president and co-founder of the Cahaba Homestead Heritage Foundation, a nonprofit dedicated to historic preservation in the district. So the binding overlay did not begin as the City’s response to a documented, neighborhood-wide problem — it began as a concept brought forward by a preservation organization and pre-endorsed by the preservation-minded Design Review Committee before the Commission ever took it up.
“Under Miscellaneous, the Commission then listened to Amy O’Brien Peterson’s presentation on a proposed Cahaba Village Historic District Overlay. Design Review already endorsed it as a concept. The Commission expressed general support for the concept but opposed the idea of a $10,000 demolition fee. Chairman Skipper suggested that exploratory PZ committee (Short, Dawkins, Robson) work with her, Malchus and city attorney Chesley Payne on a proposed Zoning Ordinance amendment…” — City of Trussville Planning & Zoning Commission, January 2024 minutes (quoted verbatim)
📄 Read the official minutes (PDF) → (mirror copy on this site)
Fair questions that remain:
This matters for how residents weigh the proposal. A binding rule adopted to solve a real, documented neighborhood crisis is one thing; a binding rule that began as one advocacy organization’s preservation initiative is another. Bringing an idea to the City is entirely legitimate civic engagement — but the public record points to the second story, which is reason to judge the ordinance on its own merits rather than assume it answers a problem the whole neighborhood agreed it had.
Source: City of Trussville Planning & Zoning Commission, January 2024 meeting minutes (posted at trussville.org); Foundation leadership per the Cahaba Homestead Heritage Foundation.
Per the same January 2024 P&Z minutes, the drafting committee was:
These are the names behind the binding rules 287 households would have to live under. Worth asking publicly:
The answers would either build confidence or surface a real concern. Either is more useful to residents than not knowing.
Source: City of Trussville Planning & Zoning Commission, January 2024 meeting minutes (posted at trussville.org) · mirror copy.
The exploratory work spanned roughly two years. The full proposed ordinance text became publicly available in May 2026 — late in the process. There is no formal rule requiring every working draft be made public. But for an ordinance that singles out one specific neighborhood, regulates aesthetics on private property, and binds the property rights of 287 households, more transparency would be appropriate.
The basic question: why did residents see a near-finished product instead of a work in progress?
The survey deconstructed in the previous section is not how a city that wants honest input designs a survey. The question wording was leading. The "leave the current rules alone" option was missing from the response choices. The mailer framed the proposal as largely already decided.
These were design choices. They were made by someone, for reasons. The City could explain who designed the instrument and why those specific design decisions were made. As of this writing, that explanation has not been offered.
There is a credibility problem worth naming. The City is asking residents to accept a new binding rule layer over their private property at the same time it has visibly failed to enforce rules already on the books that would address many of the same concerns:
Fair question: if the City isn't enforcing the rules it already has, why is the proposed solution a whole new set of rules — instead of simply enforcing the ones already on the books?
None of these questions are intended as personal attack. The people named are public officials and staff acting in their public capacity, and most are doing the work residents elected them to do in good faith.
The questions are about process — because a process that was honest at every step produces an ordinance residents can trust even when they disagree with parts of it. A process that wasn't fully transparent produces an ordinance that will be resented and contested for years regardless of how the vote falls.
Transparency is the cheapest way to build the trust this debate needs. There is still time.
We are not attorneys. But we read the ordinance, and we read the Alabama land-use law. Below are four genuine legal questions an Alabama land-use attorney would want to evaluate before this passes. These are not predictions of how a court will rule — they are open questions the council and city attorney should answer on the record before the vote.
Section VI.C exempts homes "constructed after the Cahaba Project was transferred to the City of Trussville" from the Section VI(B) design standards for repairs and remodels. That is the opposite of how nearly every historic preservation ordinance in the country is written — normally, contributing historic resources get exempted or eased; non-historic infill gets regulated more strictly. Trussville's draft inverts that. Two homeowners on the same street, neither doing anything wrong, would face two completely different rulebooks based on when their house was built.
A rational basis is required when government classifies property owners differently within a single zoning district. Village of Willowbrook v. Olech, 528 U.S. 562 (2000).
If a tornado, fire, or fallen tree destroys more than 50% of your home's replacement value, the ordinance forbids you from rebuilding what you had — you must build to the new ordinance instead. But your homeowner's insurance policy is written to rebuild the home you actually had. So a natural disaster becomes the moment the City overrides your home's design: your coverage is meant to restore what you lost, the ordinance won't let you, and you're forced to absorb the gap between the two — with no compensation from the City. (To be clear, the City does not receive your insurance money; the loss is the value and design you can no longer rebuild.)
Regulatory takings analysis weighs economic impact, interference with distinct investment-backed expectations, and the character of the government action. Penn Central Transp. Co. v. New York City, 438 U.S. 104 (1978). Some jurisdictions include a rebuild-after-disaster ("act of God") exception so owners aren't penalized for a tornado or fire; Trussville's draft does not.
Alabama courts have long treated zoning as something that should be part of a comprehensive plan for the whole municipality, and have held that singling out one small area for unique treatment can be invalid "spot zoning" — particularly when the comprehensive plan is outdated or being rewritten. Trussville is currently rewriting its comprehensive plan — the 20-year “Trussville 2.0” update, undertaken with the Regional Planning Commission of Greater Birmingham (the City Council approved the RPCGB agreement in January 2026). The new plan is still in progress, so the overlay would be adopted ahead of it, not as part of it.
Johnson v. City of Huntsville, 249 Ala. 36 (1947); Episcopal Foundation of Jefferson County v. Williams, 281 Ala. 363 (1967); Haas v. City of Mobile, 289 Ala. 16 (1972).
Alabama Code § 11-68-13(b) requires an Architectural Review Board (created under the state's Historic Preservation chapter) to have at least five members with "demonstrated training or experience in the fields of history, architecture, architectural history, urban planning, archaeology, or law." The proposed Trussville DRB has 7 members but only one required to have an architecture or construction background. Appeals from a Chapter 68 board go to circuit court; appeals from this city-created Design Review Board (city Code Chapter 2, Article IV) go back to the same City Council that adopted the rules.
Birmingham, by contrast, staffs an 11-member Design Review Committee with mandated professional credentials, and routes appeals to the Circuit Court of Jefferson County. That is the standard template for binding design review.
If the City wants to do something real for this neighborhood right now, the single highest-value step has nothing to do with design review — and the Council could pass it this month.
If the City genuinely wants to preserve the look and feel of the Cahaba Project, the most effective tools are not the ones that restrict — they're the ones that reward. Positive incentives consistently outperform negative restrictions in almost every policy domain. Homeowners who receive something tangible for keeping an original cottage will fight to keep it. Homeowners forbidden from changing what they own will resent the rule and look for ways around it.
The cheapest way to preserve an old home is to make its owner want to. Every successful historic preservation program in America — from the federal level down — is built on this idea.
Homeowners who maintain their original 1938 cottage in genuinely historic condition — original footprint, original materials, original roof line, original windows or appropriate reproductions — receive a meaningful annual preservation grant from the City, set to roughly offset the City's portion of their annual property tax. Tiered by how much of the original character is preserved: a perfectly preserved cottage earns the biggest reward; partial preservation earns a smaller one; major modification earns none. Voluntary. Earned, not mandated. (We frame this as a grant rather than a property-tax abatement on purpose: Alabama's tax-uniformity rules limit a city's power to exempt one class of homes from ad valorem tax, but appropriating grant funds is squarely within the City's authority. The city attorney can confirm the cleanest structure.)
A modest annual fund — even $25,000–$50,000 city-wide — for matching grants to homeowners who restore historic exterior features. Repainting in historic colors. Reproduction wood windows. Restored metal-shingle roofs. The City contributes; the homeowner contributes; both sides win. Charleston and other historic cities run homeowner restoration-grant and incentive programs along these lines, with strong results.
Any homeowner planning a renovation or new build can request a free consultation with a city-funded architectural consultant who knows the Cahaba Project's history and design vocabulary. Voluntary. Advisory. Helpful — not punitive. The homeowner gets expert guidance without surrendering their right to decide. The neighborhood gets better outcomes because most people listen to good advice when it's offered respectfully.
An annual award publicly recognizing the homeowner who has done the most exemplary work preserving or sensitively rebuilding in the district. A small bronze plaque at the property. A story in the Trussville Tribune. A photo at City Hall. Costs the City almost nothing. Creates a culture of preservation by celebrating it — not by punishing those who don't participate.
The four proposals above can be enacted by the City alone. This one depends on willing collaboration with the Cahaba Homestead Heritage Foundation, and on legal review — but it is worth raising openly. And there is a clear logic to it: because the overlay concept was itself brought to the City by CHHF’s president (documented in the Process Concerns section above), the Foundation is plainly committed to this neighborhood’s preservation — which makes it the natural partner to help fund the homeowners who do the actual preserving.
According to CHHF's own published statements, the Foundation has received substantial grant funding aimed at the historic district — including a $100,000 grant from the Alabama Historical Commission, which the Foundation's website indicates has been received in multiple recent years. CHHF describes these funds as enabling the Foundation "to address all areas of [its] mission" of perpetuating and enhancing the district's historic character. Additional Foundation funds have supported the Stone Gateway markers, Heritage Days events, and other educational and outreach activities — all legitimate uses.
Worth asking publicly: alongside everything CHHF already does, could a portion of those existing grant resources be partnered with the City to fund direct financial rewards for homeowners who actually preserve their original 1938 cottages to historic standards? A partnership structure might look like:
The principle: the homes themselves are the historic district. Funded restoration work on those homes directly preserves what the National Register lists. Stone gateways and entrance markers are beautiful and welcome — and they don't preserve a single 1938 cottage. A homeowner-incentive program funded jointly would.
This is a constructive proposal. It would cost the City modestly. It would preserve far more original character than a binding overlay ever could. And it would do so by aligning the City's interests with homeowners' interests, rather than putting them in opposition.
Whether the Council embraces these ideas — or politely declines to consider them — will be a meaningful signal about what this ordinance is truly designed to accomplish. If preservation is the goal, positive incentives belong in the conversation.
In any neighborhood debate, the loudest voices and the most organized groups don't necessarily represent the majority. They represent themselves. The Cahaba Project is no exception, and the residents who would otherwise speak for the leave-it-alone-with-incentives view currently have no organized voice at all.
There is currently no organized group speaking for the residents who:
The 121 residents representing 92 properties who signed the informal leave-it-alone petition collected before this site existed are a documented baseline of that opposition. That number was reached without any organized campaign, by a single grassroots effort — and it predates wider awareness of the proposal, since most residents have not yet engaged with it and many do not know it is happening at all.
The site you are reading was built by one Cahaba Project resident, with no organizational backing, no advocacy budget, and no claim to represent anyone but themselves. It exists because the leave-it-alone-with-incentives view was not being articulated anywhere — and because without articulation, that view would simply not be heard by the City Council when the vote happens.
If you read this site and disagree, that is your right and you should make your view known too. If you read it and agree, please show up — at meetings, in emails to the Council, in conversations with neighbors. A single resident's website cannot do for representation what fifty residents speaking up themselves can. The whole point of this site is to lower the cost of being informed enough to participate — not to substitute for participation.
Every claim here was researched as carefully as one resident could manage: the draft ordinance and the current code were read against primary sources, the figures double-checked, and anything still uncertain was flagged rather than stated as fact. Even so, this is one person’s work, and honest mistakes are possible. If you find an error — or think a point is missing, or isn’t fair to the other side — please write to us at contact@cahabaproject.com and we will correct it. This was made in good faith: to help neighbors get informed, and to bring the community together around a decision that affects us all.
287 homes. One response per address, up to two adults per household, every address checked to confirm it’s a real home in the neighborhood. This is not a vote — only the City Council can adopt or reject the ordinance. It is the survey the City's should have been: it includes the choice the City left out — “leave the current rules as they are” — asks every question in plain, balanced language, and the results go straight to the Mayor and Council, so they decide knowing what residents actually want.
Your name will not be posted publicly. Your address will not appear in the results. Only the total counts, with the full methodology and raw data published openly so anyone can check the math. The names, addresses, and emails behind the count stay private — used only to confirm responses come from the neighborhood and to prevent duplicates.
An informal neighborhood petition, organized and verified by a handful of Cahaba Project property owners and longtime residents before this site existed, has already collected:
Every signer asked the City to leave the current rules in place — the precise option the City's own survey never offered as a choice. The petition was hand-collected and address-verified, and was counted deliberately by property, not signature: because the overlay would apply to every property in the neighborhood, the share of homes on record matters more than a raw signature count. A single household is never double-counted, and an owner of more than one home is reflected for each property. Only Cahaba Project properties were counted — every signature was verified to an address inside the neighborhood, so the petition reflects only the residents the ordinance would actually govern, not outside voices. The signatures are available for the Council to review on request. Whatever the City's official survey eventually shows, this is already a documented baseline of grassroots opposition that did not require any organized opposition campaign to produce.
A petition, the City’s survey, and this survey are three different things — and the difference matters. The petition above is real, documented opposition: 121 residents, representing 92 of the neighborhood’s roughly 287 homes — about 32% — asked the City to keep the current rules. And it was never circulated publicly: those names were gathered quietly, by a handful of property owners and longtime residents, in a short stretch of time. That makes 32% a floor, not a ceiling — a number the Council should take seriously, not wave off. But a petition only records the people who already agree; by design it cannot show how the whole neighborhood feels, or where support for the overlay exists. The City’s survey was meant to measure that — yet it never offered “leave the rules as they are” as a choice, and its methodology and raw results were never made public. This survey is built to do what neither does: it asks every household, in plain and balanced language, with a genuine option to support the overlay or keep the current rules — and it publishes the full method and every count so anyone can check the math. We run it openly and neighborhood-wide to show the true breadth of opinion the petition only began to capture — because the Council deserves the fairest, fullest picture of where residents actually stand, and a result reached that openly is the hardest to dismiss.
Note: This is a community-administered survey, not a binding vote. Only the City Council can adopt or reject the ordinance. Our goal is to give them — and you — a clearer picture than the City's survey alone provides.
The council vote is coming in months. Every action below matters more now than it will after.
One short, civil note from a real Cahaba Project resident outweighs ten Facebook comments. We've drafted a template you can personalize — covers the legal questions, the survey concerns, and the basic ask. It takes 90 seconds.
Open the Email Template →The Council vote is coming. We'll send you the date as soon as it's announced, plus the speaking points, what to expect, and tips from people who've done this before. Sign up for one email — that's it.
This is decided by the people below — the five Council members vote, the Mayor signs. A short, civil note from a real resident carries more weight than anything posted online. Add a line in your own words, then send it.
Edit anything before sending — then replace the parts shown in red with your own words (a sentence, your name, and your street):
Dear Mayor Short and Members of the City Council,
I'm a resident of the Cahaba Project. Before the City places new binding rules on what we may do with our own homes, I'm asking you to focus on what should come first: the safety and quality of life of the people who live here. The proposed Historic Overlay spends the City's attention on home aesthetics while bigger, more urgent priorities go unaddressed.
Start with safety. The single most effective step the City could take for this neighborhood is to adopt the strongest lawful protections against unwanted door-to-door solicitation — and educate residents about them. About a third of home burglaries occur through the front door, daytime burglaries (when solicitors operate) now outnumber nighttime ones, and the U.S. Supreme Court has recognized that burglars pose as door-to-door canvassers to case homes. The law doesn't permit a flat ban, but it allows the strongest lawful version: a City-enforced Do-Not-Knock registry, "No Solicitation" signs that carry legal weight, ID badges and background checks for commercial solicitors, narrow daytime-only hours, and real resident education. That would do more for this neighborhood than any design rule.
Fix what the City already owns and controls — before writing new rules for residents:
- Enforce the nuisance, property-maintenance, and parking ordinances already on the books.
- Repair the City's own neglected public sidewalks in the neighborhood, where slabs heaved by tree roots have become genuine trip hazards — a safety and accessibility problem the City is responsible for, not homeowners.
- Clean up and screen the City's own Public Works yard and the construction debris sitting unscreened inside our neighborhood, in plain view of the park and the walking trail. The most visible blight in the district belongs to the City — yet the ordinance exempts City property.
And there's a better path than mandates — one the City owes real due diligence before taking anyone's property rights. Preservation works best when it's rewarded, not forced. Because neither the federal nor the state historic tax credit currently reaches owner-occupied homes like ours, the most effective tools are local ones the City can create itself: a preservation grant tied to the City’s share of the property tax, and a modest façade matching-grant fund, the kind Charleston and other historic cities run. This is the genuine win-win: it answers the real concern some neighbors raise, rewards the owners who actually preserve, and does it without taking property rights or singling out one subdivision.
The overlay itself solves a problem that isn't a crisis. By the City's own record, more than 90% of the original homes still stand after nearly 90 years; most losses came over decades from fire, weather, and age, not recent teardowns; and as original-cottage prices climb past $300,000-$500,000, buying one simply to demolish and rebuild is already becoming uneconomical.
Please also answer, publicly: Why replace a 20-year advisory system that worked with a binding mandate — and why now? Why treat a mailed survey as a vote of the neighborhood? Why would the Design Review Board need no resident of the Cahaba Project, with appeals only to the Council and not a court? Who has the City already approached to serve on that new board, and what are their credentials? Why does Section VI.C exempt newer homes while binding the original cottages? And why bind the property rights of 287 homes — and no others?
With respect, this is not a crisis, and the facts bear that out. The idea has come up before without the City choosing to mandate it, and the advisory rules already in place have been working. The City has more than enough real priorities; this is not one that needs government compulsion — and forcing it now risks dividing the community further. Please don't take that step.
[Add a sentence or two in your own words — your home, your street, why this matters to you.]
Thank you for putting residents' safety and rights first, and for weighing these questions before any vote.
[Your name]
[Your street, Cahaba Project, Trussville]
Works on any device: tap "Copy addresses" and "Copy the full letter," then open your email (Gmail, Outlook, Apple Mail, or webmail in your browser), paste the addresses into the "To" line and the letter into the body, and send.
On a phone or a computer with a mail app installed, "Open in your email app" does this for you in one tap — it opens a shorter version, since some apps limit message length. If that button doesn't do anything on your device, just use the copy-and-paste steps above; they always work.
Change is hard. Some people see it as healthy and embrace it. Others find it threatening and resist it. Both responses are deeply human, and neither is wrong on its own.
The Cahaba Project is going through change. Building codes have evolved. Family needs have evolved. Design aesthetics have evolved. And now the City is considering changes to the rules themselves. When change happens this fast — and when the rules around it are themselves changing — emotions surface. People deal with them in different ways. That is normal, and worth acknowledging.
There is nothing wrong with caring about houses. Caring about the look and feel of this place is the very reason most of us live here. The 1938 cottages are beautiful. The new homes are also beautiful. Both belong.
What this site is asking — gently — is that the Cahaba Project care more about the people next door than about what they are building.
A number of yard signs have appeared in the neighborhood reading "Keep It Quaint." We understand the love behind them. The original Cahaba Project cottages are charming, distinctive, and worth caring about — nobody serious disputes that.
But the phrase has, in places, been used as a kind of moral marker. Our homes are original and lovely; your new build is not. That use, intentional or not, draws a line between residents that nobody is well served by.
A small footnote of fact worth knowing: the original 1938 Cahaba Project cottages were built from a small number of standardized federal plans. They are charming as a collective streetscape, but as individual structures, the same handful of designs were repeated dozens of times across the neighborhood. The "quaint" we cherish describes the place — not the individuality of each house. Today's new builds, by contrast, are largely one-of-a-kind, designed by individual architects for individual families. Both styles have their place. Neither makes its homeowner a better or worse human being.
If a slogan is going to live on our lawns, perhaps it could be one the whole neighborhood can stand behind. Keep It Cahaba would do just fine.
When a family purchases a home in the Cahaba Project and decides to undertake a substantial remodel — or to tear down and rebuild — they have rarely made that decision lightly. Most have been planning for a year or more. They have hired architects. They have dreamed about hosting their children's birthday parties on the back porch. They have imagined Sunday lunches with grandparents, Christmas mornings, church small-group meetings, neighbors over for football games. They are investing a real portion of their savings — often a large portion — into a permanent stake in this community.
To meet those families with public bashing on social media, with personal insults, with the implication that they are somehow ruining a neighborhood by trying to make a life in it, is not a debate tactic. It is just unkind. And it stops being a conversation about preservation the moment it becomes an attack on a person.
A neighbor's choice in roof shape, in siding, in floor plan — none of those things make them a worse human being. None of them make them less welcome. The single fastest way to drive away the next generation of families this neighborhood needs is to greet them with hostility the moment they take ownership of a home.
This site is not asking anyone to change their preferences. If you love the original cottages, love them. If you love the new homes, love them. If you wish the neighborhood looked exactly like it did in 1955, that is a valid feeling. If you believe the neighborhood should evolve with the families who live in it, that is also valid.
What we are asking is simpler: care more about the people next door than about what they are building. Some of us have lived here for two years. Some have lived here for sixty. All of us chose this place. All of us, in our own way, are trying to make a life in it.
Let the Council have the debate about the ordinance. Let residents share their views with civility. And then — whichever way the vote goes — let us be the kind of neighborhood that knows the difference between the building and the family who lives in it.
That is the only kind of preservation worth having.