calepa.ca.gov No paid content found

California gardening is less a single set of rules than a set of regional decisions. The state spans cool coastal fog belts, hot inland valleys, and low-desert heat, so the same plant can thrive in one part of California and fail in another. If you are starting or troubleshooting a home garden here, the practical approach is to identify your climate zone first, then match plants, watering, and timing to that zone — and to use your local UC Master Gardener program for region-specific answers. The Master Gardener Association of San Diego County, part of the UCCE San Diego County Master Gardener Program, is one example of this University of California network in action.

Why California gardening depends on where you live

California's growing conditions are shaped by distance from the coast, elevation, and how much heat or fog a site receives. Two gardens an hour apart can have different frost dates, different summer peaks, and different pest pressure.

A useful way to think about it:

• Coastal areas — milder temperatures, more fog and humidity, less extreme heat. Frost is rare in many spots, but cool summers can slow heat-loving crops like tomatoes and peppers.
• Inland valleys and foothills — hotter summers, colder winters, and a wider swing between day and night temperatures. Heat-loving crops do well, but water demand is higher.
• Desert and low-desert areas — intense summer heat, very low humidity, and large day-to-night temperature drops. Timing shifts to avoid the worst heat, and irrigation is central.

Because of this, "California gardening" advice only works when it is tied to a place. Sunset climate zones and USDA hardiness zones are both used, but they answer different questions: USDA zones describe winter cold, while Sunset zones also account for summer heat, rainfall patterns, and length of growing season — which matters more for many California gardeners.

Getting started: a region-first sequence

1. Identify your zone. Look up your USDA hardiness zone and, if possible, your Sunset climate zone. Note your average first and last frost dates.
2. Observe your site. Track how many hours of direct sun each planting area gets, where water pools, and which spots stay hottest. Inland and desert gardens often need afternoon shade for tender plants.
3. Choose plants that fit the zone, not the other way around. Heat- and drought-adapted plants are lower-risk in hot inland and desert sites; cool-season vegetables and fog-tolerant plants suit many coastal gardens.
4. Plan irrigation before planting. Drip irrigation and mulching reduce water use and stabilize soil moisture, which matters in every region but especially where summers are hot and dry.
5. Plant at the right time. In much of California, cool-season crops go in during fall and winter, while warm-season crops go in after the last frost. Desert gardeners often split the year into two distinct growing seasons.
6. Monitor pests and problems early. Check plants regularly, identify the problem before treating it, and prefer the least-disruptive control that solves it.

How to verify it's working: healthy new growth, soil that stays consistently moist but not waterlogged, and pest problems caught while still small. If plants stall, the usual culprits are wrong plant for the zone, wrong planting time, or irrigation that is too shallow or too frequent.

Common California gardening challenges

• Drought and water restrictions. Water availability and local rules vary by region and change over time. Efficient irrigation, mulch, and appropriate plant selection reduce demand. Check your local water agency for current rules rather than assuming.
• Heat stress. Inland and desert gardens can lose flowers or fruit set during extreme heat. Afternoon shade, shade cloth, and adjusted watering help.
• Pests and disease. Warm, dry conditions favor some pests; coastal humidity favors others. Correct identification comes first, because the wrong treatment wastes effort and can harm beneficial insects.
• Soil differences. California soils range from heavy clay to sandy and alkaline. Adding organic matter and mulching improves most soils, but the starting point differs by location.
• Fire-safe landscaping. In fire-prone areas, plant choice and maintenance near structures matter. This is a regional concern worth checking with local guidance.

Where to get help: UC Master Gardener programs

The University of California Cooperative Extension (UCCE) runs Master Gardener programs across California counties. Master Gardeners are trained volunteers who provide research-based home gardening advice. The Master Gardener Association of San Diego County is one county-level example, operating under the UCCE San Diego County Master Gardener Program.

What these programs typically offer:

• Local advice matched to your county's climate and conditions
• Help with plant problems, pests, and soil questions
• Educational resources such as workshops, demonstration gardens, and publications
• A way to ask specific questions rather than relying on generic advice

To use them, find the Master Gardener program for your county through UC Cooperative Extension, then use the contact or help-desk channel that program provides. Because services and formats differ by county, confirm what your local program offers directly.

Making it work for your garden

The most reliable California gardening strategy is local: know your zone, plant for your conditions, water efficiently, and get region-specific help when something goes wrong. A coastal gardener and a desert gardener can both succeed — but not with the same plant list or calendar. Start with your zone and your site, then lean on your county's UC Master Gardener program for answers that actually fit where you garden.

A government or municipal website is a public-service platform, not a marketing site. Before you build or redesign one, plan for four things that rarely appear on a business site: accessibility compliance, public-records and transparency obligations, a document-heavy content model (agendas, minutes, permits, ordinances), and procurement rules that shape who can bid and how the project is managed. If your project is a small town site with a handful of pages, the same four apply — just at a smaller scale. The sections below cover what each one changes in practice, plus how to choose a CMS and run the redesign.

How a municipal site differs from a business site

The practical consequence: decisions that are cosmetic on a business site — URL structure, document naming, who can publish — become governance questions on a municipal site.

Core features a city or local government site needs

• Meeting agendas and minutes, posted on a predictable schedule and archived by date, with the meeting body (council, planning commission, board) clearly labeled.
• Public documents: ordinances, resolutions, budgets, bids/RFPs, and forms — ideally in a searchable document library rather than scattered PDFs.
• Permits and licenses: what's required, how to apply, fees, and status where the process allows it.
• Staff and department directories: who to contact, for what, and how — with roles that survive staff turnover.
• News, alerts, and notices: emergency notices, road closures, public hearings.
• Payments and service requests where the jurisdiction supports them (utility bills, taxes, reporting a problem).
• Calendar consolidating public meetings and community events.
• Search that works on documents, not just pages — residents usually arrive looking for a specific form or record.

Choosing a CMS: municipal-specific vs general-purpose

There is no single correct answer; it depends on your publishing volume, IT capacity, and procurement constraints.

A CMS built for municipalities tends to fit when:

• You need agenda/minutes workflows and document archiving out of the box.
• Many non-technical staff across departments will publish.
• You want accessibility features and compliance tooling built into the authoring experience rather than bolted on.
• You prefer a vendor who already understands government procurement and records practices.

A general-purpose CMS can work when:

• You have in-house developers or a strong IT department to configure and maintain it.
• Your content model is simple and your publishing team is small.
• You need tight integration with systems you already run and are prepared to build the government-specific pieces yourself.

Evaluate both against the same criteria: accessibility conformance, document management, multi-department permissions, search quality, hosting and security, migration support, and total cost over the contract term. Ask each vendor to demonstrate a real agenda-to-archive workflow, not a slide.

Accessibility and compliance considerations

Accessibility is the requirement most likely to change your design and content decisions, so treat it as a constraint from day one rather than a cleanup task.

• Target a recognized standard (commonly WCAG 2.x at the level your jurisdiction or funder requires) and state it in the RFP so vendors respond to the same bar.
• Plan for accessible documents, not just accessible pages. A scanned, untagged PDF of a meeting packet is a common failure point; build a process for producing tagged, readable documents.
• Budget for ongoing testing and remediation — every new page and uploaded file can introduce a new issue.
• Consider captioning and transcripts for public meeting video, and plain-language alternatives for complex notices.
• Keep an accessible way to contact the government for anyone who cannot use the site.

Accessibility also interacts with procurement: if conformance is a contract requirement with defined acceptance testing, you have recourse when deliverables fall short.

Typical steps and stakeholders in a municipal redesign

1. Define the project and the decision-makers. Identify an executive sponsor (often the city manager or an equivalent), a project lead, and a working group with representatives from IT, communications, the clerk's office, and major departments.
2. Inventory content and documents. You will find duplicates, outdated PDFs, and orphaned pages. Decide what is migrated, rewritten, or retired — this is usually the largest hidden cost.
3. Write requirements, including accessibility and records. Specify the CMS capabilities, document workflows, integrations, hosting, security, training, and support you need.
4. Run procurement. Follow your jurisdiction's rules for RFPs, evaluation criteria, and vendor selection; publish the timeline.
5. Design with residents, not just staff. Test navigation and search with realistic tasks ("find the permit for a fence," "read last month's council minutes").
6. Migrate and redirect. Preserve URLs where possible and set up redirects so public links and citations don't break.
7. Train publishers across departments and document who owns which section.
8. Launch, then maintain. Schedule content reviews, accessibility audits, and a plan for the next refresh.

Common pitfalls to plan around

• Underestimating document migration. Meeting archives and permit forms are often the bulk of the work.
• Treating accessibility as a final QA step instead of a design and authoring requirement.
• No content ownership after launch, so pages go stale and residents lose trust in the site.
• Broken public links from a redesign that changes URL structure without redirects.
• Assuming a new CMS fixes content problems — it doesn't; the content model and governance do.

If you are early in the process, the highest-value first step is a content and document inventory plus a written accessibility target. Those two artifacts shape your requirements, your budget, and your vendor questions more than any feature list.