Chore/starting doc plateform

[franckgaudin]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 00f270f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for wl-untitled ready!

Name	Link
🔨 Latest commit	00f270f
🔍 Latest deploy log	https://app.netlify.com/sites/wl-untitled/deploys/64591204a3b014000999720f
😎 Deploy Preview	https://deploy-preview-1--wl-untitled.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[patricklafrance]

Our standard is to use PascalCase to name components files.

layout.tsx -> Layout.tsx

[patricklafrance]

(To be compliant with our policies, this repository should be configured to get at least one reviewer approval before merging back into main)

@alexasselin008 listed our policies here: https://github.com/workleap

[franckgaudin]

Our standard is to use PascalCase to name components files.

layout.tsx -> Layout.tsx

For the structure of the app, I based myself on the conventions of Nextjs. If we apply this convention in the structure of next we will end up with page.tsx, Layout.tsx, etc... because to render the content it is absolutely necessary that page is in lower case.

For everything that concerns the components ./components/* the convention is respected.

[franckgaudin]

(To be compliant with our policies, this repository should be configured to get at least one reviewer approval before merging back into main)

@alexasselin008 listed our policies here: https://github.com/workleap

The configurations are in place, once the project is public they will be applied.

[patricklafrance]

(To be compliant with our policies, this repository should be configured to get at least one reviewer approval before merging back into main)
@alexasselin008 listed our policies here: https://github.com/workleap

The configurations are in place, once the project is public they will be applied.

Got it, is there any specific reason for the project to not being public yet?

For SOC2 compliance those policies must be in place through the whole development effort.

[fraincs]

Good job

[patricklafrance]

It seems to have been merged with unresolved issues, is there a plan to address those?

[franckgaudin]

It seemed to me that all the issues were answered, what problem was not addressed?

[patricklafrance]

There are 12 issues marked as "Outdated" rather than "Resolved". It doesn't seems possible to link to specific comment.

[franckgaudin]

They are indicated as "Outdated" however they have been taken into account and modified. The status is added when code is pushed on the branch, I don't know if there is a way to change it by resolut.
Maybe you know it?

[patricklafrance]

Good question, not sure!

Yeah we now expect to use Github Discussions for those rather than issues. It's more adapted and offer a great separation between actual bugs and discussions / questions.

What's you take on using Github Discussion for questions / discussions? This is something I am looking to push for every repo. I am wondering thought if it's overkill for repos like this one.

According to Netlify docs, it seem that you should specify a packageManager field with the required version.

Did you try the packageManager field? If so, does it work?

[franckgaudin]

 Did you try the packageManager field? If so, does it work?

I set it up and it worked well 👍🏻

What's you take on using Github Discussion for questions / discussions? This is something I am looking to push for every repo. I am wondering thought if it's overkill for repos like this one.

In fact I created this repo with the intention of including the Design System Components, that's why it's a Monorepo. In this context I think that the implementation of Discussion is a good thing.

[patricklafrance]

Awesome, thanks for sharing :)