Hello team!

Please don't forget to add an [on-chain identity](https://support.polkadot.network/support/solutions/articles/65000181981-how-to-set-and-clear-an-identity) to your Polkadot account.

Thank you.

Hello Counselors - thank you for considering our proposal. My name is William Wright and I am working on this project with Sam Anderson. I am extremely excited about building within Polkadot. This ecosystem was my "red pill" into the crytpo space and helped me change career paths: leaving TradFi for this roller-coaster ride... 

Sam and I would really appreciate feedback. We understand that no proposal is perfect, but we believe that a version of "Connect the DOTs" will really help different Polkadot users. DOT is a tech heavy protocol that is primed for quicker expansion if we can improve the user interaction! Funding from this proposal would really help us prioritize this project and build the v1 MVP that we can continue to improve with more community feedback. 

Excited for this phase and TY!
-William

**Link to Full Proposal**:
[Connect the DOTs - Proposal](https://docs.google.com/document/d/1CduiRi_ZF9StcKSSWeJqYzVOU_hwsFoImirZOhqBfsc/edit?usp=sharing)

**The Current Problem with Polkadot**
 
Today, information within the Polkadot ecosystem is located across individual parachain/project websites, social media sites, and videos/podcasts. Information remains siloed and difficult to access for users depending on their purpose. The “hub” sites that do exist fall victim to Polkadot’s achilles heel: technical heavy, data repository interfaces that don't focus on the user experience. Polkadot has some of the best tech in the world and we want to help make this beautiful technology accessible to masses. 

The end result of this: Polkadot is being held back from its full potential. The average new user does not know where to begin or gets scared off when they’re asked to interact with developer style interfaces. We can see this across a broad depth of market data. Polkadot always leads in developer activity, and yet gets nowhere near the activity and traction as many ecosystems that are less developed and less impressive technically. 

**The Solution** 

Our overarching objective is to help participants better navigate the Polkadot ecosystem: increasing exposure and understanding by aggregating “everything Polkadot” and presenting digestible, key information in a simple user interface (“UI”). We will accomplish this by collecting and gathering information via a variety of sources, maintaining a community database, and building a user-friendly front end website. 

Our project will always focus on the end user. Whether the user is new to crypto or a seasoned veteran of the industry. Being a one-stop-shop can be daunting, so we will start with two smaller goals:

1. Be the best, intuitive onboarding tool for new users

2. Connect with teams, collaborators, investment teams, foundations, etc to define and curate the proper direction on where the ecosystem is headed

We do not want to present data merely because we collected it. Rather, we want to synthesize the disparate data and present it in a way that users can easily interact with in a simple manner. 

Collectively, this encompasses our main objective: making the Polkadot ecosystem easy to understand and navigate regardless of who you are.

**The Results**

As part of our process, we will be focusing on specific results in order to determine if our efforts are paying off. The first result will be general traffic to our website. Every visit that goes to a website that focuses on Polkadot and the surrounding ecosystem will help drive awareness and adoption. The more eyeballs and clicks we can get, the broader the reach becomes.

The second result will be to drive traffic to DApps of teams. Onboarding users is where everyone must start, but from there we want to help users take full advantage of the ecosystem. By helping explain what DApps can accomplish, curating different ways in which they can be used, and providing links to DApps themselves as well as helpful content from around the internet, we will be able to leverage our user reach to help benefit all DApps across the ecosystem. 

Approve a proposal. At a later time, the proposal will be allocated to the beneficiary
and the original deposit will be returned.

May only be called from `T::ApproveOrigin`.

# <weight>
- Complexity: O(1).
- DbReads: `Proposals`, `Approvals`
- DbWrite: `Approvals`
# </weight>

#380 Connect the DOTs