Process Framework Best Practices - File and Folder Structure

[EMadd2015]

Project structure being a matter of preference, I understand this isn't too pressing, but I had some confusion arise from the Best Practices section for the Process Framework.

https://learn.microsoft.com/en-us/semantic-kernel/frameworks/process/process-best-practices#file-and-folder-layout-structure

Organizing your project files in a logical and maintainable structure is crucial for collaboration and scalability. A recommended file layout may include:

• Processes/: A directory for all defined processes.
• Steps/: A dedicated directory for reusable Steps.
• Functions/: A folder containing your Kernel Function definitions.

The only examples of the Process Framework I've found package the KernelFunction methods within the class that represents a Kernel Process Step. Should we then be using partial classes to separate these files into different directories? I suppose this would separate functions from the nested class that's used as a wrapper for the complex input of a step (since Kernel Functions can only accept one parameter other than the context), but I'm just not very clear about the separation of Steps and Functions, especially since there are no examples that follow this practice.

[moonbox3]

Adding @esttenorio