Lack of structure documentation of new site

[Deele]

Seeing current pace of contributions, it seems that there are some sort of issues that cause slowdowns and lack of new contributors joining.

Repository issues is good tool for writing down things that needs to be done, but it lacks general picture and without reading through all the issues, people are not able to understand where this is heading.

From my point of view, except for existing developers that are busy and do not find spare attention resource for new contributions, there could be a problem, that new website project is not properly documented and it is hard to see big picture, zoom in, and contribute one small thing at the time, without sinking deep into whole site and keep context in head that greatly slows down pace of development.

In such documentation, all the pages, all the blocks/widgets should be listed and all the required functions should be noted. Already done and partially finished components should be appropriately marked. Such information would greatly help existing and new contributors get into context of project much faster and have a material for reference when questions arise.

I am willing to contribute work in creating such documentation in format of Wiki section in this repository and I would appreciate any information you, existing contributors, can give, in any (raw) format, that would describe blocks that you are creating or already have created, so that information can be used & converted to mentioned documentation, so that everyone would know in what direction this project is heading.

[samdark]

I've enabled wiki. Please check if editing is available to you.

[samdark]

#94 - good source of info.

[cebe]

What is currently stopping us from switching the new site is the following:

• User system
  • Login is working with the old forum login
  • We need to find a way (preferrably OAuth to make the forum auto login with the site account)
    This was the other way round before but we want to keep control of the login code.
  • bage system needs to be ported from the old website (WIP Importing user system from current website #156)
• Extensions from old website need to be ported to not throw away content, it should be integrated with the new extension list via packagist. There is no concept for this yet. Port extensions from old website #15 - I would not make it read-only. This is also related to where to put api documentation and guide for official extensions? #19
• Wiki from old website need to be ported to not throw away content Wiki in read only mode #16 - I would not make it read-only.
• Decision on whether to replace the forum and with which solution. Currently because of lack of time I'd prefer to keep current forum and release the site first. Then afterwards discuss that topic again and switch forum to a more modern solution. Replacement for the old forum software #84

[Deele]

First iteration is done.

There are many consistency issues that is yet to be dealt with. For example, "About" stuff should go into "about" controller, the same for pages related to "Development", "Support" and "Learn", where "Support" section is my attempt to separate support from development.

[jacmoe]

About controller? Imo that would be over engineering it.

[samdark]

I agree that this particular suggestion sounds like over-engineering.