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
Some project descriptions are on the long side, in my opinion. It's not great for the website.
I found two outlier projects that had descriptions that were over 800 characters, and shortened both of them substantially—without really getting rid of important information.
@XeniaMonika, this might be something that you could look into. There are still 11 projects with descriptions over 700 characters. I think, somewhat subjectively, that we should at least be able to set an upper limit of 600. Perhaps that could even be enforced in the schema. Let me know what you think.
The text was updated successfully, but these errors were encountered:
Everything passes with the current upper limit of 750 characters. If I try lowering it to 700, there are seven files that fail. It probably wouldn't take much time to shorten those. I don't know how much lower we would want to go, but anyway, you can see how adjusting the schema and then fixing any errors that crop up in the tests is a good workflow.
Some project descriptions are on the long side, in my opinion. It's not great for the website.
I found two outlier projects that had descriptions that were over 800 characters, and shortened both of them substantially—without really getting rid of important information.
@XeniaMonika, this might be something that you could look into. There are still 11 projects with descriptions over 700 characters. I think, somewhat subjectively, that we should at least be able to set an upper limit of 600. Perhaps that could even be enforced in the schema. Let me know what you think.
The text was updated successfully, but these errors were encountered: