[Docs] Publish Code Style Guide

[brucearctor]

Description

It is great for a project to have consistent code formatting/style. This is often accomplished by a linting, and as part of pre-commit tests. But, it would also be helpful if a styleguide were published to make the choices/opinions explicit.

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[samhita-alla]

@SmritiSatyanV, could you link the google doc we have? Should we have the page in the community tab of our docs?

The task here is to convert the google doc to a flyte doc page.

[SmritiSatyanV]

https://docs.google.com/document/d/1rhEZqd3Ae8Y9HUxg7yF6LarHrfIHKnPyeke8aMSPgis/edit?usp=sharing - here's the google doc

[SmritiSatyanV]

The user specifies code guide here. What we have is a documentation style guide. I think we need to have a separate code style guide..

[samhita-alla]

Oh, okay. Do we have an issue for porting the doc style guide to our docs?

[SmritiSatyanV]

#2388 @samhita-alla

[akarsh-jain-790]

Hey, I would like to work on this issue.

[akarsh-jain-790]

https://docs.google.com/document/d/1rhEZqd3Ae8Y9HUxg7yF6LarHrfIHKnPyeke8aMSPgis/edit?usp=sharing - here's the google doc

If I'm right I just have to convert the google doc to a flyte doc page ?

[github-actions]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏