• Split Header
• Get Started with iconography
• Solar with field/farm in the background
• Two groupings of statistics like we discussed early on (fully designed)
• Use of a "teal" type of color that is complement the primary blue.

• Another stock photo illustrating solar surrounded by farm land & community
• Full header with background (ADA Compliance / contrast)
• Introduced new concepts on some headings
• Introduced "Our Promise" which speaks to your "About" area. with alternate layout (each links directly to interiors, with main button going to top level about)
• No teal, all elements are hue modifications off the primary Nautilus blue (compare footer areas from v1a)

• Inside page for Community Solar.
• More alternate headings and header.
• Focused more on community than farms, but similar principle of having both in-frame.
• Shows the graphic we created in the context we envisioned originally.
• General story is told below in a modern alternating content block layout
• Interactive FAQ Collapse Panels below.

• Same header image as Community 1a, but fluid layout (edge to edge)
• Again showing the 2nd interactive illustration we created. Note: once one is decided on, we will add interactions during code phsae.
• Alternate way of listing talking points for each section below vs. simple bullet lists. Bit more punch, but we're unclear of the content that will be needed which usually dictates design.

Last but not least, the "Find Your Community Results" block on Community 1b:

We spent a great deal of time discussing this internally, but the global footer block "Find Your Community" we had intended to be an interactive block that was able to solve two things at once.

1) Locations

2) Legislation

These were both talking points in earlier meetings, and why not solve them at the same time! This design shows what the "search results" would look like, and would be a real-time piece of functionality. Meaning, you are not carted off to a different page (more friction).

This component would be awesome, but does come with some technical caveats. For one, we would need your app/portal team to create some kind of API Endpoint for us to talk to. This would allow us to send a zip code to them, and get back results for specific things.

It is possible for us to add this within our system, but it might create a lot of overhead for you guys down the road.

I recommend we talk about this component, because it does have some logistical concerns. But we're up to the challenge and hopefully we can build something interactive like this to make users happier and increase conversions, which is always our endgame :)