What functions should a flexible, easy-to-use, and scalable WCM system contain?

I have been engaged in software development for eight years. From the initial VB6.0 development to VS2005 and VC ++, I have been engaged in java development, mainly to complete some projects, including medium and large websites, OA, and CRM systems, but I have always dreamed of creating a "single point of management, multi-point publishing" WCM system; I have used a lot of similar software at home and abroad over the years, but I always feel that I have not achieved what I want. So I hope you can share more posts here, we have improved an open-source WCM system that suits China's national conditions. The following is a summary of the features (functions) that the WCM system should possess. At present, we have achieved 1/3, further improvement ......

1. Support for "single point management and multi-point release": management and release separation;

2. Supports real-time and out-of-the-box Template management results, and supports mobile terminal transcoding or mobile phone templates;

3. Automatically or manually change the foreground template (page );

4. Support customization of topic and content metadata (including display name, display mode, and verification );

5. Support for custom forms (similar to 4) to implement comments, comments, and suggestions. Work with the workflow (ACTIVITY) to complete the "approval" for submitting data in custom forms );

6. Supports workflow models without complicated processes;

7. Support access with permissions accurate to the record level (public institutions use more );

8. Support access to sites, columns, and Content Documents (same as above );

9. Supports confidentiality management of documents (optional );

10. Websites and columns can customize keywords (sensitive words and keywords );

11. In the UI design, perform common operations on one page as much as possible, instead of continuously redirecting and switching on different pages;

12. In terms of operations, the prompt information should be simple and easy to understand. For operations in order, we should adopt the common "next" approach or better user experience;

13. In terms of performance, theoretically unlimited sites can be supported (just theoretically), and memory buffering is used for common data;

14. The frontend and backend users are managed separately (including permissions );

15. Support SSO management (separate system, support for multiple integration methods and reserved interfaces );

16. Quick index search is supported;

17. Reserved multilingual interfaces.

Sorry, the writing is a bit messy. I hope you will give more comments. In a short time, I will upload the source of V0.1 to git, and I also welcome the oscer that I am interested in.

What functions should a flexible, easy-to-use, and scalable WCM system contain?