License information on the repo usually relates to the product itself not stuffed that are linked to your product, or stuff that are generated as an output of your product. Because average user for your app might not go to github to check for license, They would stumble to your app via search engine, use it and get the final layout for their own work. But whatever you decide, It would be better to add an html license comment block inside the downloaded file ( along with a copy license file inside archive ). I would suggest update readme with " This is a meta repo for issue management and community engagement "Īnd for the downloadable output file, It should ideally be creative common since you are kinda providing a functional template. Looking forward to see where you take this ahead. I thought you were using css-grid to achieve positioning until I downloaded the file. ![]() I know they make things build easier, but I personally hate the unnessary nested-div hell. My only complain is Jquery, and outdated bootstrap. I really liked how easy to use and intuitive it is. I would have preferred a slightly larger font-size and padding on the navigation (top-right "structure-component-editor" part) for people like me with bad eyesight. There are some UI jumping issues ( I am on firefox ) when I drag large item ( Chart Lines with nav). If you plan to use repo as an issue tracker + community engagement platform, Update your license and Readme to make it clear. ![]() If you plan to open-source it, provide source code. You gave a github repo link, But there is no source code on it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |