Site Architecture vs group Architecture

Problem

We are building a desktop app that should prioritize the content over visuals. On the other hand, we are building sites that show this content, but here we might need to enable more tools to publishers so they can organize the content the way visually fits to them. We need to deal with this Dichotomy, so we better define it properly.

Ideas

Group Architecture: Data that will be stored in the P2P group.

Site Architecture: Data that does not necessarily need to be in the group P2P. It only matters inside the site

The app should prioritize content, not aesthetics

Sites should enable publishers to organize content the way it fits to them, grouo the content the way they want and display it in many different ways.

The app gives the reader the hability to "time travel" over documents and groups. Maybe in sites this is not what publishers want? maybe this is what we as a society need anyways?

This difference between Site architecture and Group Architecture defines what data should be part of what and where should we store it. For example, the Title of a group should be part of the group architecture, not the site. Another example, Sitemap: should this be part of the group architecture or Site architecture?

Containing:Problem

Ideas

Published:8 mo. ago Thursday, March 14th, 2024

Author:

z6MksZZ3...qdmESQGx

First Version

Open in Mintter app