feat: change labels from howtos to projects

[benfurber]

PR Checklist

• - Commit messages are descriptive, it will be used in our Release Notes
• - Unit and e2e tests for the changes that have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Feature (adds functionality)

What is the current behavior?

User things are named 'How to', 'how-tos', etc.

What is the new behavior?

Top level is called 'Library', children are called 'projects'. This change is for labels and urls only. Developer things are still called howtos until we migrate the DB.

Does this PR introduce a breaking change?

• Yes
• No

Git Issues

Part of #3989

[cypress]

onearmy-community-platform    Run #6684

Run Properties:   Passed #6684  •  9d055855d3: chore: adding commit to force fly deployment

Project	onearmy-community-platform
Branch Review	pull/4027
Run status	Passed #6684
Run duration	05m 23s
Commit	9d055855d3: chore: adding commit to force fly deployment
Committer	Ben Furber
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	3
Pending	0
Skipped	0
Passing	76
View all changes introduced in this branch ↗︎

[davehakkens]

thought I left a comment before but dont see it anymore.
Question: Is there a conscious reason on why you choose different wording from the issue?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.68%. Comparing base (7a248b8) to head (9d05585).
Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4027   +/-   ##
=======================================
  Coverage   69.68%   69.68%           
=======================================
  Files          39       39           
  Lines        1237     1237           
  Branches      258      258           
=======================================
  Hits          862      862           
  Misses        353      353           
  Partials       22       22           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[benfurber]

thought I left a comment before but dont see it anymore. Question: Is there a conscious reason on why you choose different wording from the issue?

Yes. Definitely went with what seemed most natural to me personally. The principle I tried to go with wast a project is the main unit, the main 'thing' that should be labelled and so only went with library when talking about all the projects collectively. But very happy to debate the grammar.

[davehakkens]

Ah i see. It was actually written the other way around, making library the most used word.

• To avoid confusing it with items in research module
• to have a clear link with navbar navigation

[benfurber]

@davehakkens See your point. I'll update. Applying your approach but with some suggestions:

Create button
"Add your how-to" -> "Add to the library" or "Add your project to the library"

Create page
"Create a how-to" -> "Add to the library" or "Add your project to the library"

Profiles/Contribution tab:
"How-to's" -> "Library Projects"

Thoughts?

[davehakkens]

Adding 'project' to the wording often makes it to long for the layout making it look strange

Would avoid it

[benfurber]

@davehakkens Have a look at this now.

[davehakkens]

The url doest go anywhere. And the preview doesnt show any changes at first glance, not sure if i'm seeing the latest?

[benfurber]

@davehakkens Actually freshly deployed now: https://community-platform-pr-4027.fly.dev/library?sort=Newest

[davehakkens]

I see the same as the screenshot above. Is that the latest?

[benfurber]

@davehakkens If you refresh and everything you don't see this?

[davehakkens]

Nice works for me, two changes that would be nice:

1. Change text in searchbar

2. Change text in the header