# 11.0: Wrap-up

Nice job! This was a long tutorial and hopefully you learned a lot form it.

A 'social media' site is obviously a huge undertaking. We have some functionality built out - but, there is a lot of room to experiment, change things you didn't like, add new features you'd like to see, etc.

Trying to implement your own features will be a great way to learn. Hopefully, the tutorial showed you the process of implementing a feature and you feel comfortable to try it out yourself. You may have some ideas, but if you need something to get started:

* The site is not very responsive and there are a lot of front-end improvements that could be made. If you have an eye for design and this is something you can enjoy - this would be a great way to improve the site.
* A 'news feed'. Right now users are 'following' other users - but, there's not much going on for them to follow. You could add functionality for `User`s to be able to make posts that show up in the news feed of the `User`s following them.
* You could also play around with the [GitHub API](https://developer.github.com/v3/repos/). There's quite a lot that could be added to the app from there. Users could enter their GitHub handle on registration, and you could have their activity on GitHub show up in a newsfeed, for example.
* Real-time messaging. Right now, we have a somewhat interesting messaging system. The problem is, messages that a user sends show up immediately - but, messages sent by another user will not show up for the recipient until the page is refreshed. Not a great user experience. You could consider hosting the messaging portion of the application on another database like `Firebase`. You could also use the same backend and use Microsoft's [SignalR](https://blogs.msdn.microsoft.com/webdev/2018/02/27/asp-net-core-2-1-0-preview1-getting-started-with-signalr/) though, at the time of writing - it's still experimental for ASP.NET Core.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://eleven-fifty-academy.gitbook.io/dotnet-302-core/11-appendix/11.0-wrap-up.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.