{"action":"created","issue":{"url":"https://api.github.com/repos/liferay/clay/issues/1111","repository_url":"https://api.github.com/repos/liferay/clay","labels_url":"https://api.github.com/repos/liferay/clay/issues/1111/labels{/name}","comments_url":"https://api.github.com/repos/liferay/clay/issues/1111/comments","events_url":"https://api.github.com/repos/liferay/clay/issues/1111/events","html_url":"https://github.com/liferay/clay/issues/1111","id":354413908,"node_id":"MDU6SXNzdWUzNTQ0MTM5MDg=","number":1111,"title":"Clayui.com documentation, how enhance it? 🤔","user":{"login":"diegonvs","id":7663513,"node_id":"MDQ6VXNlcjc2NjM1MTM=","avatar_url":"https://avatars0.githubusercontent.com/u/7663513?v=4","gravatar_id":"","url":"https://api.github.com/users/diegonvs","html_url":"https://github.com/diegonvs","followers_url":"https://api.github.com/users/diegonvs/followers","following_url":"https://api.github.com/users/diegonvs/following{/other_user}","gists_url":"https://api.github.com/users/diegonvs/gists{/gist_id}","starred_url":"https://api.github.com/users/diegonvs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/diegonvs/subscriptions","organizations_url":"https://api.github.com/users/diegonvs/orgs","repos_url":"https://api.github.com/users/diegonvs/repos","events_url":"https://api.github.com/users/diegonvs/events{/privacy}","received_events_url":"https://api.github.com/users/diegonvs/received_events","type":"User","site_admin":false},"labels":[{"id":253392102,"node_id":"MDU6TGFiZWwyNTMzOTIxMDI=","url":"https://api.github.com/repos/liferay/clay/labels/docs","name":"docs","color":"006b75","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-08-27T17:51:32Z","updated_at":"2018-09-05T14:44:55Z","closed_at":null,"author_association":"MEMBER","body":"I've fill this issue to share some thoughts and start a discussion about how we can improve our website docs.\r\n\r\n- We will work on integration of `clay-paver` on clayui.com. So, we are thinking of putting it on another page so we do not conflict with other css files, do you guys have any suggestions?\r\n\r\n- Our LATAM design intern @gabbebarbosa, had made a document during his internship rotation describing some enhancements on clay docs website.\r\n\r\nCheck it out here:\r\n\r\n![documentation-clay](https://user-images.githubusercontent.com/7663513/44673606-68d13e00-aa02-11e8-9f66-0e7ca72774d2.png)\r\nNote that she had put a table with some API description on each component.\r\n\r\nAlso, she said that would be great for us have a section to fill a issue if the provide documentation is wrong. I've noticed that we have a icon that redirect to Github issues but isn't too much.\r\n\r\n- Last weekend i attended to [Braziljs conf](https://braziljs.org/conf/) and i talked too much with a lot of Front End developers, including a girl that works on a company that has a design pattern system and component library similar our. She said that a lot of problems using a design system on his company was solved by: \r\n  - A good documentation, including API full description like: http://circuit.sumup.com/#/components/blockquote. I think Gabbe's layout work will solve it.  \r\n  - A place to workbench API like Storybook, @matuzalemsteles had built a utility to use this feature on current documentation with /try page. Like: http://circuit.sumup.com/storybook/\r\n  - A section to include Best Practices for each component.\r\n\r\n\r\n\r\n\r\n/cc @pat270  @matuzalemsteles @jbalsas @marcoscv-work "},"comment":{"url":"https://api.github.com/repos/liferay/clay/issues/comments/418757752","html_url":"https://github.com/liferay/clay/issues/1111#issuecomment-418757752","issue_url":"https://api.github.com/repos/liferay/clay/issues/1111","id":418757752,"node_id":"MDEyOklzc3VlQ29tbWVudDQxODc1Nzc1Mg==","user":{"login":"jbalsas","id":905006,"node_id":"MDQ6VXNlcjkwNTAwNg==","avatar_url":"https://avatars1.githubusercontent.com/u/905006?v=4","gravatar_id":"","url":"https://api.github.com/users/jbalsas","html_url":"https://github.com/jbalsas","followers_url":"https://api.github.com/users/jbalsas/followers","following_url":"https://api.github.com/users/jbalsas/following{/other_user}","gists_url":"https://api.github.com/users/jbalsas/gists{/gist_id}","starred_url":"https://api.github.com/users/jbalsas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbalsas/subscriptions","organizations_url":"https://api.github.com/users/jbalsas/orgs","repos_url":"https://api.github.com/users/jbalsas/repos","events_url":"https://api.github.com/users/jbalsas/events{/privacy}","received_events_url":"https://api.github.com/users/jbalsas/received_events","type":"User","site_admin":false},"created_at":"2018-09-05T14:44:55Z","updated_at":"2018-09-05T14:44:55Z","author_association":"MEMBER","body":"Hey @matuzalemsteles, @diegonvs, now that we've pushed through with the API docs for the components, and while we discuss how to [Improve the clayui.com deploy process](https://github.com/liferay/clay/issues/1170), could you guys focus on the following, please?\r\n\r\n- [ ] Incorporate the contents from http://pat270.github.io/lexicon/ into these sections so we can remove it. Only things that serve as developer reference should be published to the site and it all should live in the same site\r\n- [ ] @pat270 has been using http://pat270.github.io/lexicon/ for local development and smoke testing. We should set this up somehow so it can be used locally within the clay-css package, but without the risk of producing a live site. @pat270, can you share with @diegonvs and @matuzalemsteles what you need so they can help you out here?\r\n\r\nJust today we had again an issue where someone was looking how to create a simple loading indicator and had to end up looking at http://pat270.github.io/lexicon/content/loaders/ rather than https://clayui.com\r\n\r\nThis is our biggest barrier on usage and consistency. We need to address this\r\n\r\nPlease, could you take a look at the structure proposal and go through the current docs to merge in what's not in the right place and see what should be brought over from @pat270's site?\r\n\r\nAfter we're done with this, we should be able to redirect the other site to https://clayui.com"}}
{"actor":{"display_login":"jbalsas"}}