Skip to content
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

move the "Masonry for the compliance literate" documentation in #220

Closed
afeld opened this issue Aug 30, 2016 · 2 comments
Closed

move the "Masonry for the compliance literate" documentation in #220

afeld opened this issue Aug 30, 2016 · 2 comments
Assignees
Labels

Comments

@afeld
Copy link
Member

afeld commented Aug 30, 2016

Broken out from cloud-gov/product#253.

https://docs.google.com/document/d/1mNV7yzrorBF4YD9uIOr75KOPCrta8eMkk0Gf8edhyZs/edit

@afeld afeld added the HighBar label Aug 30, 2016
@afeld
Copy link
Member Author

afeld commented Aug 31, 2016

Not exactly sure of the best place for this to live...the README is getting long enough that we might want to start splitting it out to different Markdown files under a docs/ folder or something (or maybe move documentation to the website)...that is a whole other can of worms though, and thus should probably be its own issue ("content strategy for Masonry/OpenControl").

/cc @brittag

@brittag
Copy link
Member

brittag commented Sep 1, 2016

I'd do something simple for now - make a docs/ folder, put a .md file in it, link to that from the README. Then when we have a chance to talk about overall content strategy for Masonry/OpenControl, we can figure out where best to put it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants