{"action":"opened","issue":{"url":"https://api.github.com/repos/Codeinwp/themeisle-companion/issues/171","repository_url":"https://api.github.com/repos/Codeinwp/themeisle-companion","labels_url":"https://api.github.com/repos/Codeinwp/themeisle-companion/issues/171/labels{/name}","comments_url":"https://api.github.com/repos/Codeinwp/themeisle-companion/issues/171/comments","events_url":"https://api.github.com/repos/Codeinwp/themeisle-companion/issues/171/events","html_url":"https://github.com/Codeinwp/themeisle-companion/issues/171","id":284976024,"number":171,"title":"chart/table/review/shareable blocks/widgets","user":{"login":"ineagu","id":1849868,"avatar_url":"https://avatars3.githubusercontent.com/u/1849868?v=4","gravatar_id":"","url":"https://api.github.com/users/ineagu","html_url":"https://github.com/ineagu","followers_url":"https://api.github.com/users/ineagu/followers","following_url":"https://api.github.com/users/ineagu/following{/other_user}","gists_url":"https://api.github.com/users/ineagu/gists{/gist_id}","starred_url":"https://api.github.com/users/ineagu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ineagu/subscriptions","organizations_url":"https://api.github.com/users/ineagu/orgs","repos_url":"https://api.github.com/users/ineagu/repos","events_url":"https://api.github.com/users/ineagu/events{/privacy}","received_events_url":"https://api.github.com/users/ineagu/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-12-28T19:29:49Z","updated_at":"2017-12-28T19:29:49Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"@selul I think I pretty much got an idea about what orbitfox can be, at least in the modules part.\r\n\r\nWe will develop content blocks used for page/post building, that works with any major builder. This means:\r\n\r\n- we should develop in such a way that those are consistent and settings aren't block specific\r\n- we should make sure we can build them in same way across builders.\r\n- messaging will emphasize the blocks like: \"the chart block\" or \" post grid block\" or \" social share icons\", how they will be configured for different builders won't be the main point.\r\n\r\nA great example is : https://siteorigin.com/widgets-bundle/, widgets that work with any page builder + wp default widget area ( not sure how it works, but we need to look into it ).\r\n\r\nNext steps would be to have a list of free/pro widgets that we plan to build ( e.g we use a lot on codeinwp blog : charts, shareable boxes, tables + newsletter box ).\r\n\r\nSame templates would ideally at some point be builder agnostic.\r\n\r\nThe reason why I am thinking to struggle in building for different platforms is to make sure that our code is de-coupled enough so it can adapt later on to different wp changes."}}
{"actor":{"display_login":"ineagu"}}