Links to new features, behaviors, helpful information and resources that should be reviewed to be included in Oqtane.Docs

[thabaum]

Links And Information Worth Reviewing

I feel we need to start posting links to information that can help keep Oqtane.Docs current.

I encourage others to post any ideas you have for links to information that would be helpful here in Ideas. This is a great place for our community and maintainers to review things that are not issues, but may enhance Oqtane.Docs project documentation.

I come across them all the time, write an idea down such as clarifying things so it can reduce issues created in the Oqtane.Framework project. You will see me now post these types of links to information that should be merged or introduced.

Pull requests on any of the links I create in discussions to resourceful things are more than welcome so that the maintainers of Oqtane.Docs can review your solution to this inclusion. I am hoping to see some teamwork to make this dream work. I am in no competition or race towards submitting more than others although I might. It is my just my way to express the need to do something and if it can be done sooner than later if I can make time, get it done now while it is on my mind and move on to the next before I forget about it or it gets stale.

If you post links and don't want to deal with submitting the PR just let us know you have no plan to submit a PR and this opens the field up for others looking for ways to contribute. For some a way to get their first contribution on GitHub ever.

From my past experience some contributors put up issues they are working to resolve. Others put them up hoping for someone in the community to resolve. If someone does not state they are going to handle it then really it is open to all to submit a solution with a pull request. This is a golden chance for anyone that can get to understand the project to help the community. Most all contributors of the Oqtane Framework should be able to handle DocFX contributions once they review Oqtane Documentation..

My general workflow:

1. Identify an issue
2. See if I can resolve it
3. Create an issue with details and helpful information related to it.
4. Submit a pull request with a solution if I found one.
5. Maintainer accepts, asks for adjustments or closes it due to it not being the acceptable solution.
6. If not acceptable another solution as a pull request is committed by myself that I feel will meet criteria as acceptable or by another contributor willing to share a solution which can be the maintainer(s) to close the issue.

It is a process if you are new as in this is your first time contributing on GitHub you need to be sure to accept all the contribution agreements to release rights to your work and allow a maintainer to merge it if accepted.

I look forward to any contributions of posting links to information worth reviewing such as behavior changes and new features in ideas here.

I believe framework developers should try to link any updates to include here at least. Maybe they don't work this project but a link to something they helped with would be awesome help and only take a moment.

Community members can also look at each release and post up the link to behavior changes, or features using it as cheat sheet to identify and post them here. I think it would be helpful if as a community we do this. Some should be created as "issues" rather than "discussion ideas" however they all should definitely be identified and documented upon release somehow.

Excited this new Ideas board is here I thought I would share a few, thanks again @iJungleboy .

Any other ideas on how we can streamline documentation on this project I would love to hear!

Cheers!