关于我的项目和这些 JavaScript 框架，我哪里做错了？

Your choice of framework might not constrain your UI choices as much as you may be imagining. This recent Henri Bergius article about decoupling content management illustrates the point much better than I could -- and, incidentally, links to a pretty sweet looking pure-JavaScript (framework-independent) in-place content editor.

I would suggest first coming up with specific UI requirements for your project. Which of the frameworks you've tried have you taken for a spin?

Personally, I got into ExtJS development because the projects I work on require a lot of customization of controls/widgets. ExtJS has a ton of them right out of the box and can always be extended, combined, or munged into whatever monstrosity your business requires.

ExtJS 4 also allows you to "skin" your UI's to further customize the look and feel.

If you are new to JavaScript, and are comfortable with Java, you might even look into a server-side solution such as GWT, JSF, or even Vaadin

Not sure about your timeline and resources, but when I'm trying to decide between multiple frameworks/environments, I just go ahead and try to quickly build a prototype. Even if it's just one or two major functions, I find that all the research and documentation in the world won't ever match actually trying to build something with the tools. I say take a day with each and see how far you get. That'll give you a pretty good indication of which tools are up to the task and feel most comfortable for you.

You are not alone!

VanillaJS and Ampersand .. are great examples of the serious drive for simpler, more modular JavaScript.

There's even a Book about it.

Simplicity is being driven by an under-rated es6 feature: Modules and the SystemJS implementation standard. It even can be used on non-es6 systems.

How cool is that!

One suggestion about Backbone, if you decide to use it you should go for Marionnete since it's Backbone but with a better architectural structure and more opinionated ( i personally feel that Backbone doesn't set any guidelines and that's feels like a downside in large apps ).

I worked with it for a few months combining different js libs and doesn't get in your way like other frameworks and the message pipeline is a really good way to connect components through out the app but keep them decouple.

Here you have a great talk that made me decide for it : https://www.youtube.com/watch?v=qWr7x9wk6_c

And here you have a demo prototype that also has the drag and drop element plus other js libs connected. Would love to heard what you think about my code since i have 1.5 years working on web development... i'm still a newbie : https://github.com/Drasky-Vanderhoff/marionette-demo/

About Knockout, is really good if you want interaction with the content you already have and you won't be connecting constantly with the backend. I worked with it for 6 months and i end up needing to use a lot of other js libs for routing; plus i end up repeating a lot of the structures that Backbone and other JS Frameworks end up having. What i will say is that it won't get in your way at all and be a tool rather than a constrain. Also this was almost a year ago so a few things have changed.

One thing, if you find Knockback ( Knockout + Backbone )... avoid it, the documentation is not as good as it should be and it will take you a lot more time to learn it. If you want to go for it make a fast prototype first to see if is what you want.

I would say you are wrong in your overall choice of candidates as you are omitting Angular and Ember both of which are better suited than any of the other frameworks listed.

Overall, I'd say Angular.js is the framework for this one.

Emphasis on Routing

Much of what you are talking about (several sidebars for navigation, a single page app) are functions of routing, or how the front end interprets the text in your URL navigation bar.

Both Angular.js and Ember have excellent routers that allow you to accomplish everything you require without additional code.

For your benefit, here is a quick breakdown of the features in Angular that can be used to create your single page wiki

The Structure of the Site Itself

Angular has an amazing library called UI router allows you both to create custom navigation and to set up an SEO friendly structure of revealing your content. Multiple views would allow a top toolbar as well.

Ui router tutorial: http://cacodaemon.de/index.php?id=57

WYSIWYG Editor

Angular is built on live two-way binding (when you change something somewhere, it automatically changes everywhere else.) Therefore it comes packaged with a lot of features that work well with this kind of editor. A few good ones have already been made and you only need to implement them.

http://textangular.com/

Graphs and Other Neat Stuff

Angular directives are designed to do things like create Chart components that are reusable. They are not totally different than Wordpress Widgets. Many of these have already been developed and can be dropped into your Angular project.

http://www.sitepoint.com/creating-charting-directives-using-angularjs-d3-js/

Regarding Ember, I do not know much about it so I cannot speak to its particular features.

meteor is all the rage nowadays (the most starred full-stack JavaScript framework on GitHub and Meteorpedia is a wiki engine written in Meteor.

The launch video will get you hooked by 1:28.

It's agnostic with regards to the UI, and has been tested extensively with Bootstrap and Famo.us. It also generates mobile apps from the same codebase.