it looks like six projects on top of each other, so does the project need at least six devs?

It’s modular by design. It doesn’t require multiple devs, although any volunteers would be welcome. This is what I do and I know how to put it all together. But it won’t be in a week. I’m ok with that. This is important to me.

one thing i liked were the credits, i thought about buying some "cashu credits" one thing i didn't like were categories, categories need an already defined ontology

The categories are up to the editor or publisher. Completely customizable. The current magazine is a showcase and the catagories are my own choice. It’s possible they only make any sense to me. The plan is to make it possible for anyone to create their own, on the scale of a specialized blog or a full blown newspaper with world news coverage.

so it's like a curated blog

Yes, with a baked-in feature that it is not limited to one author/npub. A curated collection of lists.

so in nostr terms it would be kind 30004, but instead of just being a static list it's also a filter, making everything more difficult

In nostr terms it’s nested curated publication events, kind 30040, like Alexandria uses, to define the magazine and its categories and possibly subcategories, and those contain a sorted list of articles. It functions as a folder structure.

the problem is that the event type has a filter that the client does and not the relays, because you have ["type", "magazine"], but you can have an event that is only for magazine and that follows for that specific one, so it'ok. It is probably already possible to do what I say in Coracle, this is an example https://njump.me/naddr1qvzqqqrujgpzqkfzjh8jkzd8l9247sadku6vhm52snhgjtknlyeku6sfkeqn5rdeqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgkwaehxw309ahx7um5wgkhyetvv9ujuctswqhszyrhwden5te0dehhxarj9ekk7mf0qythwumn8ghj7mn0wd68ytnnw3skkete9ehx2ap0qqfrqvfc8ymnyv3jxqcnqvphxcenjvehzzdp38

I’m not sure I follow. As far as I can tell, you’re saying that there are multiple ways available already to achieve a curated list on nostr. I’m aware. I just like this one for all the possibilities I can see for this and I’m trying to implement them to see if it will work out as I imagined. The root index event that describes the magazine is replaceable and can be updated whenever and the npub that created the magazine can also publish an RSS-like nostr feed. An editor or publisher would create a magazine npub first, then the events, instead of publishing with their own npub. And the root event can be used as a reference to build out the whole magazine either with my client or a custom web interface in any style.

if you create a new npub it's the communi-keys approach, (I'm not saying this to follow this or that), but as difficult as it is

NostrHub

NostrHub | Discover and Publish NIPs

Explore official NIPs and publish your own custom NIPs on NostrHub.

Nusa has extensive experience with index events and isn't intimidated by the hierarchical structure.

Communi-keys have their own thing going on. It all overlaps on some level, but my focus are publications. I’m aiming at a special purpose interface that is clear and useful, specialized for this one thing - creating magazine style publications.