Skip to content

Conversation

emilieschario
Copy link
Contributor

@emilieschario emilieschario commented Sep 23, 2025

Description

Title

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated

@emilieschario emilieschario self-assigned this Sep 23, 2025
@emilieschario emilieschario marked this pull request as ready for review September 23, 2025 10:57

The aim is to avoid institutional knowledge building up inside our heads without
also being written down for others to share. We could do that all on the internal
Google Drive, but by publishing in the handbook it allows for an open and honest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other reason is that a google doc that everyone can edit is just a messy list of suggestions. A handbook with approval flow is policy -- company wide.

Google Drive, but by publishing in the handbook it allows for an open and honest
conversation about what we do.

Our handbook is more than just a collection of policies; it is the living embodiment of our core values. We believe that documenting our work and culture is essential to our success, and this handbook is how we put our values into practice every single day. It's how we ensure that information wants to be free, and that our collaborative community can thrive.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Our handbook is more than just a collection of policies; it is the living embodiment of our core values. We believe that documenting our work and culture is essential to our success, and this handbook is how we put our values into practice every single day. It's how we ensure that information wants to be free, and that our collaborative community can thrive.
Our handbook is more than just a collection of policies; it is the living embodiment of our core values. We believe that documenting our work and culture is essential to our success, and this handbook is how we put our values into practice every single day.
It's how we ensure that information wants to be free, and that our collaborative community can thrive.

and contributions can be made through pull-requests. How to contribute
is capture [in a guide](https://github.com/FlowFuse/website#flowfuse-website).

The handbook is here for the whole company to help maintain. Pull-requests are welcome and [strongly encouraged](#contributing).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is now a link to 6 lines up.

Suggested change
The handbook is here for the whole company to help maintain. Pull-requests are welcome and [strongly encouraged](#contributing).
The handbook is here for the whole company to help maintain. **Pull-requests are welcome and strongly encouraged**.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants