Skip to content

Evaluate project structure improvements #3

@vaceslav

Description

@vaceslav

Overview

Project structure analysis completed. Current structure follows modern .NET best practices with flat solution layout and feature-based organization.

Current Assessment

Rating: 9/10 - Modern and well-organized

Strengths

  • ✅ Flat solution structure (modern approach for 6 projects)
  • ✅ Feature-based organization in core library (Conditionals/, Loops/, Visitors/)
  • ✅ Clear naming convention (TriasDev.Templify.*)
  • ✅ GUI follows MVVM pattern
  • ✅ Test structure mirrors core library
  • ✅ Comprehensive documentation

Optional Improvements to Consider

  1. Directory.Build.props - Centralize common .csproj properties (version, authors, copyright)
  2. Solution folders - Only if solution grows beyond 10 projects
  3. Consolidate documentation - Currently split between root and TriasDev.Templify/ folder
  4. Clarify TemplifyGuiPackage/ - Document purpose or remove if obsolete

Recommendation

Keep current structure. No critical changes needed. The flat layout is preferred over src/tests split for solutions of this size.

References

  • Modern .NET project structure guidelines
  • Feature folders pattern (preferred over layered architecture)
  • MVVM pattern for Avalonia applications

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions