Give students answers to all questions.
Explain in extreme detail how each result was reached.
And when they've had enough, then can read answers and understand while the problem is fresh in their minds.
If you don't give answers, no one will be able to use your online material without you being there to hold their hands.
Forbidding students from publishing their answers also goes against let students learn by teaching.
OPEN LOOK is a graphical user interface (GUI) standard that was developed by Sun Microsystems in the late 1980s. It was designed for use with the SunOS operating system and aimed to provide a more user-friendly environment for interacting with computer systems compared to traditional command-line interfaces. The key features of OPEN LOOK include: 1. **Window Management**: The interface supports multiple overlapping windows, allowing users to manage various applications simultaneously.
Chorus Systèmes SA is a company that specializes in developing software and solutions for various industries, particularly in the field of product lifecycle management (PLM) and manufacturing. The company provides tools that assist organizations in managing their product data and processes throughout the entire lifecycle, from initial design through production and maintenance. Their offerings often include solutions for 3D modeling, simulation, and collaboration, aimed at improving efficiency, fostering innovation, and enhancing communication among teams.
The Common Open Software Environment (COSE) is an initiative that was developed in the early 1990s aimed at promoting the use of open standards in software environments, particularly in the context of Unix and Unix-like operating systems. COSE was focused on creating a consistent framework for software development, interoperability, and portability across different systems, which would help alleviate the fragmentation of the software market and facilitate the development of applications that could work across various platforms.
The Intel Binary Compatibility Standard (IBCS) is a specification that defines a standard set of requirements for binary compatibility among different operating systems and software environments, specifically for Intel architectures. The goal of IBCS is to enable applications compiled for one environment to run on another, facilitating interoperability across various systems and minimizing the need for recompilation.
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!
Intro to OurBigBook
. Source. We have two killer features:
- 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-calculusArticles 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/derivativeVideo 2. OurBigBook Web topics demo. Source. - 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.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 3. Visual Studio Code extension installation.
Figure 4. Visual Studio Code extension tree navigation.
Figure 5. Web editor. 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.Video 4. OurBigBook Visual Studio Code extension editing and navigation demo. Source. 
- Infinitely deep tables of contents:
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