Easier to reason about src file hierarchy

[SleeplessOne1917]

Easier to reason about src file hierarchy

[dessalines]

Went with "Page" as a suffix instead of "Activity". Not a diehard on this change, but I'm unfamiliar with the convention of calling these "activities" instead of "pages", which threw me off at first.

page is fine. The main thing is to make sure Page / Activity / Routes / Screen (s) are easily distinguishable from inner components.

It arguably makes more sense to colocate these with the relevant components instead of throwing them in the common serverfns directory.

You never know where these might be used elsewhere tho, and its best to keep them separate from UI items. In android these are called viewmodels (a place to fetch and persist reactive data across screens), and the top-level pages can use one or more of them. For example an AccountServerFns or a CommunityServerFns will probably be used for multiple screens. So it does make sense to have them in their own folder separate from ui/components, even if most of the time its 1 route using 1 component.

As for top level screens tho, it does make sense to put those in a ui/components So I'd recommend:

• src
  • ui
    • components
      • home
        • home_page.rs
        • home.rs (for extras specific to home)
      • common (shared UI components)
      • utils (UI-specific utils)
  • serverfns
    • home_fns.rs
  • utils

The other things look fine to me.