You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think by having a main and unique place where all the information for the user is available (in this case labwc.github.io) would be great as it'd allow people to discover better the project.
Thus, maybe implementing some contents of the README file onto the website would be interesting
I suggest the following to do:
Add scope and IRC channel links under the website
Add dedicated page to see NEWS.md (though maybe unnecessary)
Copy project description to a new page on the website, so people can now what the project is about more deeply
Add translations info to the website
Maybe cleanup the README file and redirect to website?
Though here it arises the question whether the README should be like the information file for "advanced" users/contributors while the website should be more of the presentation, thus not needing some of the technical information from the README
Also adding so I don't create a new issue:
Add svg favicon (possible if there's available labwc2-with-text.png as svg)
Add meta information to the website head for better discovering (social share preview) (super unnecessary but could look well)
The text was updated successfully, but these errors were encountered:
I think by having a main and unique place where all the information for the user is available (in this case labwc.github.io) would be great as it'd allow people to discover better the project.
Thus, maybe implementing some contents of the README file onto the website would be interesting
I suggest the following to do:
Though here it arises the question whether the README should be like the information file for "advanced" users/contributors while the website should be more of the presentation, thus not needing some of the technical information from the README
Also adding so I don't create a new issue:
The text was updated successfully, but these errors were encountered: