Some more things that I encountered as I tried to add a second article: Whenever I publish something new from my terminal, I am immediately logged off and I have to keep logging back in to make small changes to the articles that I have written.
Also I couldn't publish a second article correctly. It seemed like name clashes were present, as I had made a second "references" section for the second article. But why is that? Shouldn't it all be allowed as the two "references" sections have different parents and thus are not identical. I am most probably missing something there, but I couldn't find an easy solution to my problem by reading the docs. (I keep my .bigb files in a separate directories and publish whichever one I want. I don't know if that's the correct way though.) I tried following your web editor suggestion and renaming my "references" section to "references | [article name]" but when executing the command, no changes were found.
I remember that I published my first article with a hack that I have already forgotten. And this of course is not the standard way that you wanted. I find the publication process a bit too complex for a beginner, especially for one who has no knowledge of computer science! (thankfully I have some, but even this was not enough in my case. I even watched some videos on how to publish projects and yet I couldn't find a way that made me comfortable).
Again, I apologize for my misuse of the website. I am surely not reading the docs enough.
P.S: Is there a way to not have a new line every time I put some latex in the text? Also: My new article's structure looks like this:
For some reason Bleach was never put as an actual section in the web, but instead all of the children nodes were published parentless. Why is that?
OK I fixed the homepage problem: ourbigbook.com/pioyi at: github.com/ourbigbook/ourbigbook/commit/e586bfa5cd977b55d16198193630cd892b4404b7 It was linked to an edge case of unlisted articles I hadn't tested.
Later on let me know how your local files look for --web upload. In principle, everything should work even if the articles already exist on server, it should just restructure everything to look exactly like your local output tree.
I'll check the homepage 500 issue. The more bugs found the better!
Also maybe some things to check (not that they are 100% bugs): 1) When viewing parent/children articles sometimes the dropdown menu doesn't work when clicked (the upside down triangle).
1) Do you mean on table of contents? It's currently broken: docs.ourbigbook.com/todo#toc-js-folding-broken-on-web I have to fix this, it just keep escaping the top of my list somehow.
2) My idea is to one day allow storing undeletable post history as well, so that when you link to someone's permalink, it NEVER ever goes down. This is similar to what Wikipedia and Stack Overflow do. If this ever becomes a problem we can reconsider, but generally speaking storage is cheap and CPU-hours are relatively expensive.
My new article seemed awesome when I previewed it via the index.html file but when I uploaded it (with --web) the inheritance was broken. Maybe that's because the article already existed and I tried to push it again! Yes, that makes sense.
I'll have a look at what you mean when I can restore your homepage :-) Also, if you manage to push your .bigb files into a github repo, that might help debug/understand issues (even though ultimately I should be able to figure it out from db).
I feel kind of bad for all the requests that I am making, I should preview my stuff before committing it.
Not at all, if anything comes up feel free to immediately comment without too much thinking. Because I have basically no users besides myself, any feedback is extremely valuable in guiding what I should do next.
Wow I must have seriously messed up. Not only did I manage to make duplicates of my current article, but also somehow got my home webpage to crash. I surely am a bad user! At least I got my local file uploaded, not in the way I wanted though (inheritance is not working as expected from the file structure. But that probably is my fault).
Also maybe some things to check (not that they are 100% bugs): 1) When viewing parent/children articles sometimes the dropdown menu doesn't work when clicked (the upside down triangle). 2) Why not just delete articles instead of unlisting them? Isn't it bad for the server's storage?
I feel kind of bad for all the requests that I am making, I should preview my stuff before committing it.
My new article seemed awesome when I previewed it via the index.html file but when I uploaded it (with --web) the inheritance was broken. Maybe that's because the article already existed and I tried to push it again! Yes, that makes sense.
Yes, give it a try and let me know if you face any issues. I want both to be amazing, but perhaps cli is a bit better now for those who can use it. Give the Visual Code Extension a try.
Thanks for all the tips. I will start using the cli version, it seems much more comfortable, at least for me
Oh that was really fast. I checked a few minutes ago and I though I was crazy. Nice work
Thank you so much for reporting this.
Dollar signs: by default dollar signs are for mathematics as in:
I like $\sqrt{1+1}$ as a number.
which renders as:
I like as a number.
To have a literal dollar you have to escape it with a backslash as in:
I have \$10 for lunch.
which renders as:
I have $10 for lunch.
The equals sign space: = would generate a header, but you can't create headers directly on the web editor. You should instead create new sections by just creating new articles with the New button. Then you set the parent to the other article as shown at: www.youtube.com/watch?v=yQRjLyqILl0 Note that the UI changed slightly from that older video, the parent selection is now under the "metadata" tab in the editor.
If you find any other issues or have any doubts do let me know and I'll try to fix/reply ASAP. This serious editor bug was there because I use mostly local editing, but I want the editor to work perfectly as well.
I think their focus moved more and more to automatic data collection as opposed to UGC.
Golden was of interest, thanks for mentioning it. It also had much less strict notability guidelines than wikipedia which is another serious issue with the platform. Unfortunately they shutdown signup got merged into another financial intellicence thing: Section "Golden (wiki, 2019)".
It's almost certain that there are remaining XSSes though given I wrote the markup from scratch. But you'll have to work harder than that.
This page is not the top Google hit for "bawuzzzz". I love it so much.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 5. . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact