Open bbertucc opened 3 months ago
Hey @bbertucc ,
Thanks for tagging me in and sharing the details. This project sounds like a great opportunity, especially with the chance to kick off the Accessibility Navigator program.
To make sure I’m clear on what’s needed and can come up with an accurate budget, I’ve got a few questions:
What’s Their Vision?: Can you give me a bit more detail on what the Wisdom Foundation is imagining for the new nola311.org? Besides the chat-based UX, are there any other design elements or features they’re really focused on? I want to make sure I’m aligned with what they’re expecting.
What Exactly Do They Want Me to Do?: Am I just creating the Figma mockups, or will I be handling the full frontend development as well? If I’m building it, do they have any existing frameworks or components they want to use, or am I starting from scratch?
How Will We Work Together?: What’s the plan for working with their development team? Will I be leading the frontend build and then collaborating with them, or will I just be handing over the designs and offering support?
Accessibility Expectations: Since accessibility is a key part of this, do they have specific standards or guidelines in mind (like WCAG 2.1 AA)? Knowing this upfront will help me design and build with those benchmarks in mind.
Timeline & Deadlines: Besides the review of the Figma mockups around August 28th, are there any other key dates or milestones I should know about? This will help me plan my time and resources.
Post-Launch Involvement: After the frontend is done and tested, will they need ongoing support or updates from me? I’d like to understand what they’re expecting after the initial launch.
Once I have a better idea of these details, I can put together a budget that covers everything they’re looking for and make sure we’re all on the same page.
Looking forward to hearing more!
@wilsuriel03 - repsonses here:
What’s Their Vision?: Can you give me a bit more detail on what the Wisdom Foundation is imagining for the new nola311.org? Besides the chat-based UX, are there any other design elements or features they’re really focused on? I want to make sure I’m aligned with what they’re expecting.
They are really open to anything! The goal is to deliver an accessible UX to NOLA311 that can eventually be expanded to other city services. This would be a very basic early version to prove the concept.
What Exactly Do They Want Me to Do?: Am I just creating the Figma mockups, or will I be handling the full frontend development as well? If I’m building it, do they have any existing frameworks or components they want to use, or am I starting from scratch?
We'll start with a Figma mockup. They don't have any existing frameworks. I showed them radix. The Figma mockup could lead to more opportunities like a frontend development, let's just focus on the Figma mock up for now.
How Will We Work Together?: What’s the plan for working with their development team? Will I be leading the frontend build and then collaborating with them, or will I just be handing over the designs and offering support?
Initially, you'll just be providing designs. We'll have a discussion with them to present these ideas. Then we'll figure out what future collaboration can look like.
Accessibility Expectations: Since accessibility is a key part of this, do they have specific standards or guidelines in mind (like WCAG 2.1 AA)? Knowing this upfront will help me design and build with those benchmarks in mind.
WCAG 2.1 AA. I would also like @kevinandrews1 to review any content that's created, if he's up for it.
Timeline & Deadlines: Besides the review of the Figma mockups around August 28th, are there any other key dates or milestones I should know about? This will help me plan my time and resources.
August 28 is the only date right now. We'll plan to have a meeting around then with the client. Then we can discuss where we go from there.
Post-Launch Involvement: After the frontend is done and tested, will they need ongoing support or updates from me? I’d like to understand what they’re expecting after the initial launch.
We haven't discussed Post launch involvement. That would come after this initial Figma development. They have no expectations now. I personally would love for equalify to get deeper involved with the city of New Orleans through this project. This project could also help us figure out the kinks in our "Accessibility Navigator" program.
Apologies for it being kind of vague right now. But if we just focus on the Figma template by August 28, I promise that things will work out as we go from there.
Happy to answer any other questions!
@bbertucc
Thanks for the info! I’ve got a couple more questions that will help me get started on the right foot and put together a budget for the project:
Design Direction: If the goal is to enhance the current landing page at nola311, should I stick with the existing design elements like colors and overall layout, or are they looking for something more transformative? For instance, are they open to exploring new color schemes, typography, or even a different structure altogether? Understanding how far they’re willing to go with the redesign will help me come up with a mockup that hits the mark.
Content Updates: Are there any plans to update or change the existing content? For example, do they want to add new sections, modify the current messaging, or streamline any of the existing features? Knowing this will be key in shaping the layout and ensuring the content fits seamlessly with the new design.
Once I have a clearer picture of these aspects, I can start brainstorming and get a draft mockup ready. This will also help in creating a budget and timeline to keep things moving smoothly.
Looking forward to your thoughts so I can get started as soon as possible!
Design Direction: If the goal is to enhance the current landing page at nola311, should I stick with the existing design elements like colors and overall layout, or are they looking for something more transformative? For instance, are they open to exploring new color schemes, typography, or even a different structure altogether? Understanding how far they’re willing to go with the redesign will help me come up with a mockup that hits the mark.
City of New Orleans has no style guy that I can find. That said, any deviation of style should have a clear rationale. And I would suggest that you use the current logo on nola.gov. We want them to approve this. But you can make a point about how some design changes improve accessibility.
Content Updates: Are there any plans to update or change the existing content? For example, do they want to add new sections, modify the current messaging, or streamline any of the existing features? Knowing this will be key in shaping the layout and ensuring the content fits seamlessly with the new design.
Yes. The current site will be heavily simplified. It's going to be a new FAQ, model on the content here. There should also be key ways a user can submit a request and check on an existing request.
I would budget for one round of pretty major revisions. Or, you can create two options: an option that is focused around a chat experience (like ChatGPT) and an option that's focused around a form experience, which will deliver AI based responses. Whatever you think is best for your workflow.
@wilsuriel03 and I agreed on a price for his work on this bounty: $2,750. 50% paid upfront and 50% on delivery. I just paid the first 50%.
One of our first customers is the Wisdom Foundation. They are reimagining nola311.org. They were super interested in our Accessibility Navigators helping them develop the nola311.org frontend. While this isn't what Equalify will do for every client, I think we should provide this client, who are paying, with the front end they're interested in.
I would like to use a portion of our cash ($5720) to deliver a front end they can use. This would lead to additional work with the city of New Orleans, finger's crossed.
Here's what they are interested in:
Assigning @kevinandrews1 and @wilsuriel03. Could you two come up with a budget for this project? Again, this is not what we would normally do. But we are in Early Days. This project can kickstart our Accessibility Navigator program, which could become a more solid stream of revenue for everyone involved.