Demo site and Docs site can be the same about awesome-css-frameworks HOT 2 CLOSED

Thanks for the suggestion. As this list is about CSS frameworks, almost every project listed has a demo. For many projects, that is the project website itself. Some projects (also) have the documentation directly on the project page.

Currently it is handled with this logic:

• If the project's repository links to another URL, then use it as the main project link. Otherwise use the repository URL.
• If there is a demo URL which is not the main project URL, add it.
• If there is a docs URL which is not the main project URL, add it.
• If the main project link is not the repository, add a repository link. (I'm aware that this is a little inconsistent at the moment)

I'd like to add as few links as possible per project and avoid having mutliple links pointing to the exact same resource. I see an advantage of your suggestion, but it might also lead to inconsistent entries. E.g. what would you do when the main project URL includes the documentation? In the end, it is always about balancing between the template and having useful entries. For example, some entries already have a slightly different structure.

Overall, I'm a little hesitant to implement your suggestion. I don't see it as making things much clearer to the users of this list.

from awesome-css-frameworks.

got it why you dont wanna do that

from awesome-css-frameworks.