Skip to content

Content: GW Case Study #163

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.

Sign up for GitHub

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

Jump to bottom
Closed
shaloo opened this issue Feb 9, 2020 · 2 comments
Closed

Content: GW Case Study #163

shaloo opened this issue Feb 9, 2020 · 2 comments
Assignees
@shaloo
Labels
content

Comments

@shaloo
Copy link
Contributor

shaloo commented Feb 9, 2020

Adding GW case study as discussed here:

Also Utilizing all feedback wrt layout received in issue82 as well. Creating a separate issue to ensure clarity in two different case study reviews / inputs.
@shaloo shaloo self-assigned this Feb 9, 2020
@shaloo shaloo added the content label Feb 9, 2020
@shaloo
Copy link
Contributor Author

shaloo commented Feb 9, 2020

This won't work - need to have gh_82 merge in (for common cs related image dir etc) before I can process/check in GW case study too. Holding on checkins until @rgommers approves that one.

@shaloo
Copy link
Contributor Author

shaloo commented Feb 9, 2020

Closing this issue, both current case studies BH and GW will be checked in part of #82

@shaloo shaloo closed this as completed Feb 9, 2020
@shaloo shaloo mentioned this issue Feb 10, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shaloo shaloo

Labels
content
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shaloo