-
Notifications
You must be signed in to change notification settings - Fork 1
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
2.1 Omega 2 #114
Comments
Ready for initial review. I wasn't quite sure what you were looking for here, so I've included all diagrams from the Omega2 diagram PDF. |
@remingtontr I have quite a few suggestions/comments/markups for this article. I'm sure a lot of this wording has been copied from the original documentation, but my biggest suggestion is to keep a professional tone. The original docs were for the maker space, but now our audience is more in the B2B space, which is why I'm suggesting we clean up the tone. Let's give this another revision please. |
I've revised the article for tone and made some edits. |
Much improved! Good work. |
@remingtontr agreed - let's remove that table, and proceed with the PR |
NOTE: _This Subtask is linked to a larger Task List_ticket #113
Task Owner:
Who owns this task and will approve the final deliverables?
Lazar
Objectives & Goals:
1. How does this task relate to the value track(s)?
This article provides an overview of the Omega2 module which helps users decide which one is best suited for the development needs. These are articles are targeting users early in the decision process when they are trying to figure out what module to develop with.
2. Create a short statement explaining the objectives and goals for this ticket.
The objectives of the Omega2 article is to provide provide a comprehensive overview of the options available to a new user and provide the with high level information they would use in their decision process.
Reference Material:
1. Provide hyperlinks for helpful and related information.
Please refer to outline:
https://docs.google.com/document/d/1N0GZG83dOvpB2MxFTK3Ez3AGx8D9avBp6x9aHxjGCRg/edit
Deliverables or Desired Outcome:
1. What are the task owners expectations?
2. What does the task owner require for a successful completion of the ticket?
Date Required By:
1. When is the scope required to be completed?
2. Is this a hard date? Specify if the task is a dependency of another task or if it will impact a customer requirement.
The text was updated successfully, but these errors were encountered: