Hi @SPIPFan , answering in English as you mentioned earlier you were not as fluent in French as in English.
I do not think you can reasonably expect to receive the kind of help you are asking for. I understand that you would like someone to do some sort of peer-programming while you develop your platform (the person would look at what you do with a screen-sharing tool while you code and tell you if you are doing something wrong); and/or the person would possibly do your « skeleton » for you, working from your static HTML templates. This is a lot of work for any volunteer, and depending on the objective of your platform (you mentioned it is for a volunteer organization, then a company website), this may not be an « ethically correct » thing to do (if it’s for a company, then someone needs to get paid for the job).
You also mentioned you were learning, or trying to learn, Spip. Having someone else do the actual work of programming is not the best way to learn.
As a few people on this thread mentioned, they will be happy to help if you invest a bit more of yourself into your own project. That is, if you start writing your own skeletons, by following the Spip documentation, maybe using ChatGPT if relevant, and ask questions in the forum when you are stuck with specific points; then you’re very likely to get friendly answers.
Spip is actually not that hard. You need to know a bit of HTML, CSS (that’s where the responsive stuff is usually managed), then the Spip syntax, which is well described in the docs. You could bootstrap your development by using an existing template for a skeleton instead of starting from scratch (Squelettes éditoriaux - SPIP-Contrib).
Some important questions to ask yourself ahead of the project would be thinking of the website’s architecture - what information is displayed, where, and how; by making mockups (I’m an old-fashioned person and I tend to draw my templates on paper and pin them on the wall so that I can keep an eye of them while creating the website); and the question of having one or several languages, which in Spip needs to be decided very early on in the project as it impacts the architecture quite a bit.
Hope this helps a bit, looking forward to seeing your more specific Spip questions in the future 