-
-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help wanted (v1): Improve documentation #1056
Comments
Hi, I’ve been using EventFlow for a few weeks. During this time, I read a lot of EventFlow documentation and looked at the source code. I made some notes on how the documentation can be improved, because it was hard for me to understand how to:
I also found some typos in the documentation. What do you think would be useful to add to the documentation from my list? I can help with that. |
Hi @alexeyfv ❤️ that all sounds very useful. As mentioned, the documentation is far from what I had envisioned originally. |
Nice. I'll prepare the 1st pull request about working with aggregates without CQRS in the near time. Any suggestions on where to put this example? |
Improvements to the Aggregate page: #1069 |
Improvements to the |
The new documentation site is now properly up and running on https://geteventflow.net/, and while GitHub Workspaces have helped cleanup and make the documentation (somewhat) ready for a real release of v1, there's still several areas that could do with a loving hand.
Here's a list of areas the needs improvements.
Documentation improvements
General quality and features
If you decide to help out, then please create relatively small PRs with isolated changes to minimize the chance of others working on the same.
The text was updated successfully, but these errors were encountered: