kiejo

It sounds like https://astro.build might be a good fit if you're looking to generate mostly HTML and only use JS for a few interactive components on the page. It's still very new and I haven't worked with it yet.

Thanks for the kind words. Unfortunately we have no plans for a self-hosted version. We understand that this is a no go for certain companies and types of information.

Thanks for the information! We did not notice any anomality and are receiving signups, but are looking into what might have caused the issue. In case it's a persistent issue for you, it would be awesome if you could contact us via email so we can further investigate the issue.

If you want something similar to Dropbox Paper, but better optimized towards long-term documentation, you should give Nuclino (https://www.nuclino.com) a try. In terms of organization capabilities it is similar to Confluence. But I'm the CTO so I'm obviously biased.

Thanks for mentioning us (I'm the CTO)! Let me know if you have more feedback or questions.

It's not that I haven't heard about leaking traffic to third parties before. What I meant is that so far none of our users have complained about this being a concern for them.

Great to hear you like the design and feel of the product :) We're currently beta testing a desktop app for Windows, MacOS, and Linux, but haven't started work on a mobile app yet. Of course we see the value in mobile and we'll get there eventually!

From my experience ProseMirror is not the easiest editor to get started with, but it gives you a lot of power in terms of customization and flexibility. Recently a more feature rich table module was released, which might come closer to what you expect in case you haven't seen it yet: https://github.com/prosemirror/prosemirror-tables. Once you get the hang of it, implementing custom plugins and behaviors is not that hard. There will be a 1.0 release with more extensive documentation soon, which will make it a lot easier to get started. You can find more information here: https://discuss.prosemirror.net/t/planning-new-documentation.

Apart from that, the maintainer is very responsive and often times issues get fixed in a matter of hours! And the community behind ProseMirror is very helpful and seems to be steadily growing :)

Thanks! There was a similar question with an answer a little further down the comments: https://news.ycombinator.com/item?id=14866580

Hope this helps :)

Thanks for reporting this! We're aware of the issue and will fix it as soon as possible.

Thanks for the feedback! This is the first time that we hear about this concern, but we will look into it. Serving these kinds of resources (fonts, icons) ourselves has a disadvantage in terms of caching, so we'll have to decide if it's worth the trade-off.

To give you a rough idea:

For the frontend we use React, MobX, ProseMirror, and Webpack.

The backend uses Node.js, Express, µWS, and Postgres.

At Nuclino we're very happy with MobX and I would say that it is definitely suitable for complex projects and that it mostly depends on the overall architecture that you choose. MobX is rather unopinionated and there are many ways to work with it. You can even use it in a Redux style architecture if you want! In the end it all depends on your requirements and preferences. For us, choosing MobX was key to building Nuclino the way it is today as there are a few key features which would have been much harder to build with Redux.

Have a look at ProseMirror (http://prosemirror.net). It works quite well on Android and iOS and the maintainer is super responsive and has already fixed a lot of Android/iOS specific issues.

Edit: The landing page of the project does not seem to be optimized well for mobile. When on mobile, make sure to try the editor on http://prosemirror.net/examples/basic instead, as the landing page causes some unwanted scrolling for me on mobile.

We're using MobX and React for nuclino.com and for us it has scaled very well for something which is much more than just a todo list app. We're very focused on performance and creating a snappy experience and so far we didn't have to do much performance tuning that was specific to MobX. Happy to answer any more specific questions.

Your tool looks interesting, congrats on your beta launch! I'd be interested in the technologies you used to build the editor, especially the real-time collaboration part. What libraries are you using or is it something custom built? I'm working on something similar (https://www.nuclino.com) and we've been pretty happy with ProseMirror as the basis of our editor so far. Here's our HN post from a few weeks ago, if you're interested: https://news.ycombinator.com/item?id=11211241

We just deployed a new version which fixes this! You can now just paste a link into the editor.

Great! Let us know how it goes with your colleagues :)

That's strange, the button should actually work. This is probably related to a bug in Safari. Would be great if you could try it in Chrome, as it is the only browser we currently test in.

Sure, we'll write you an email!

Thanks for the input, we are generally open to that, but we still have to see how much demand there is for a self-hosted solution.

Great to hear that as we have comments on our roadmap. We're not sure yet how the best experince for commenting would look like.

Would you prefer inline comments, that appear directly inside the page or comments that appear on the side like in Google Docs?

We haven't decided on this yet. We are still evaluating how a free version might look like.

Thanks for the input! We might add an open "Test Team" to the landing page. Until then you're free to use a spam address to convince yourself of the product ;)

Good point, we have export on our roadmap. (Of course we use replication and perform daily backups to S3, but I understand your concerns nevertheless)

What kind of export would you like to see? Exporting the whole content of a team as HTML, generating PDFs for all the pages, generating Markdown files? Any preferences?

There's currently a bug that forces you to hit Space after pasting a link, for it to be recognized as a link. We'll fix this soon, but for now you can just hit Space after the link.

Great question, we are using similar tools!

Slack is where our conversations live, but trying to keep more persistent and organized information there didn't work well for us.

We are also using Google Drive, but mainly for file management and working on documents which require full control over the styling and layout (e.g. legal documents that need to be printed). For more dynamic content and ad-hoc information, it feels too heavy to us.

Github (Wiki) is great for static text content and fine grained change tracking. Besides that, it's rather hard to use for non-developers as you pointed out.

We use Nuclino for collaborating on rich content that is more persistent than conversations in Slack and which does not need the overhead of a system like Google Drive. We haven't used Quip too much, but feel that it's rather similar to Google Drive with the files, folders, documents, spreadsheets and the likes.

To keep the core experience lightweight in the long term, we plan on supporting integrations that extend Nuclino.

We're using ES6 and React on the frontend and the editor is based on ProseMirror. On the backend we use Docker, Node.js, and OrientDB.

So far we're pretty happy with the stack, especially React turned out to be a great choice for us on the frontend!

Glad you like it and thanks for your input regarding the landing page. There's definitely more work to do. What we're currently working on is some videos that will describe different use cases and how to use Nuclino. The other points you mentioned will follow soon.

Currently, we don't have any importing functionality, but we'll work on that in the near future. It might also be possible that we will provide an API that allows users to create custom import scripts for arbitrary file formats.

We plan on charging a monthly fee per user similar to the premium offerings of products like Slack, Trello, and Asana. We're also thinking about offering a free version with a limited feature set, but have not decided how this will look exactly.

Thanks for the feedback! It's always hard to get contrast right on all the different screens, but we'll look into it.

I can say that we've reached about 500 pages in our team and it's still working great. Nevertheless, we definitely plan on introducing more advanced organization and visualization features for teams with large amounts of documents.