To get started, create a GitHub account and log into this website. Then, set your public profile name under the "My Profile" section.

You can always find page-specific instructions under the "Show More Information" dropdowns located at the top of most pages or on the FAQs page in the footer.

Next, create a booklist on the "My Bookshelf" page, and try adding some books to it. You can add books from your collection or search for new books to add.

Using GitHub as an authentication provider allows us to offload some of the complicated, repetitive, and error-prone operations like resetting passwords, verifying emails to reduce spam, implementing transactional emails, and securely storing password hashes. IvyStreetBlog does not store password hashes, nor has access to password hashes as part of the information provided by GitHub. The way we determine you are who you say you are is by obtaining the email you provide GitHub (after they determine it is valid) and using that email to create an account on our website. Since the email you provide to GitHub might be different than the email other providers have registered, like Gmail, we've chosen to provide GitHub as the only authentication provider at this time.

The sign-up process is easy and free. Also, there are built-in tools in GitHub that will let us make this website better, such as issue tracking. So if you have any problems with this site or suggestions, feel free to submit your bug report or feature request in the form of an issue located here. Please include relevant details to help us understand and resolve the issue or implement the feature request.

Please note that changing emails in GitHub will result in getting a duplicate account created in IvyStreetBlog, so try to use only one email with GitHub if at all possible.

If you are under 18 years old, you must have your parent or guardian complete the registration process on your behalf using their own GitHub account. Your parent or guardian will be solely responsible for reviewing and accepting the terms of use.

Booklists are a way to share unique and insightful perspectives with others. A booklist is simply a list of books that you add from your collection. The key point is that the book must have made some impact on you, and that's why you remembered it and recommend it to others.

A booklist is a collection of these books that are united by some theme, event, or idea. Use the booklist description to describe who the booklist is for generally (remember, no personally identifiable information), like anyone interested in learning about poetry or a certain theory or genre.

You may also use the description field to give more information on recommendations you are seeking in this booklist. For instance, you might say, "I'm looking for books that are similar to this one, but with a different perspective." This will help others understand what you're looking for and provide better recommendations.

A collection is your personal collection of books, which can be added to one or many booklists. A book can exist in the collection without being added to any booklists, but you would be able to put it in your reading list.

A book can be added to the collection from several places, but it's important to remember that adding a book to the collection does not automatically add it to the booklist or reading list. Once a book is in your collection, you can add the book into whichever booklist you'd like or add the book to your reading list.

To add more details than title and author, you must go to 'My Collection'. This is where you can delete or archive books as well.

When a booklist is marked as private, other users will not be able to find it on the public bookshelf. It's basically an 'off switch' for the booklist while you're curating the booklist. When you're ready for the booklist to appear on the public bookshelf, you can make the booklist visible for others to see.

When a user views the booklist full of books on the public bookshelf, they can add any of the books to their reading lists or add any of the books to any of their own booklists.

Private reading lists are perfect for curating a list of books to put on hold at the library, where the librarians will find them for you and collect them all for you to pick up.

A few things happen when you have a public booklist.

First, when a user navigates to your public booklist page (at a URL that looks something like baseUrl/public-bookshelf/public-booklist/66385c63205c1f4ab1c9f3e2), they will be able to see all of the books you've added to that booklist and will be able to add those books to their reading list or their booklists. Your public booklist will be accessible to anyone, including those without an account.

Second, your public profile name becomes part of the URL that people can use to view all of your public booklists. Users are able to browse your other public booklists by pressing your public profile name on the public booklist page.

Third, you're able to share your public booklist with anyone, including people without an account. There is a share button where you can even print a QR code that can be made into a sticker or something. You can text and email the link to the public booklist.

A bookshelf is a collection of booklists. There is a 'public bookshelf', which is comprised of all the public booklists of all the users, and 'my bookshelf'. The public bookshelf can be accessed through the link in the footer, while 'my bookshelf' is only accessible to the authorized user after logging in.

'My Bookshelf' is a place to create and maintain both public and private booklists. The 'Public Bookshelf' is a place to browse and discover public booklists created by other users. You can add books from the public bookshelf to your reading list or any of your booklists. It is organized with the booklist that was most recently updated first.

A reading list is a list of books you've marked as 'to read' by simply adding them to your reading list. It's a private book tracker in case you find a book that you quickly just want to read. You can add books to the reading list directly from your collection or any booklist, including others' public booklists.

Once you read the book, you can mark the book as 'finished' and then you have the opportunity to write a review. Reviews are only visible to you and are a way of keeping track of what you thought of the book.

Removing a book from the reading list only removes it from your reading list and not the collection or other booklists. Howevever, removing a book from the reading list will remove any review you've written for that book.

The public profile name will be included as the base path of the URL to your public bookshelf. For instance, if you set it to 'example-profile-name' then the URL that would show your public bookshelf would be something like 'baseUrl/example-profile-name'.

Others will see the public profile name on any of your public booklists and can click it to get to your public bookshelf.

The public profile name should be a sort of secret code that has no personally identifiable information. It can be a superhero, a character in a novel, or just something random. The idea is to keep your identity private while still allowing others to access your public booklists.

The owner of a booklist has the ability to open their booklist to recommendations. This means other users can recommend books from their collection to the booklist. Then the user who owns the booklist that received the recommendation can either accept or reject that recommendation.

When you open the booklist to recommendations, a new tile appears below the list of books on the public booklist page, where anyone might submit recommendations to your booklist. You'll be able to see that your booklist is open for recommendations on the 'My Bookshelf' page, and when someone submits a recommendation, you'll see a link to a page where you can view the recommendation and either accept it or reject it.

To leave a recommendation, find a booklist that is open to recommendations using the public bookshelf located in the footer. On the public booklist page, scroll to the bottom, and there should be a tile available for you to select a book from your collection to recommend to the booklist.

If the book you want to recommend is not in your collection yet, add it to your collection first, and then select it and add your reason for recommending it to the booklist.

To review your recommendations, go to the "My Bookshelf" page, and if there are any recommendations people have left, a yellow link will appear on your booklist. Click that link, and you can approve or reject the recommendations.

Webauthn is a modern way to authenticate that doesn't require a password, but requires you to register your device with the authentication provider, in this case GitHub. Once your device is registered, you will be able to log in using your device's built-in mechanism, such as Face ID.

Since this website will most likely be accessed from a phone, it makes sense to use this method of authentication. Registering your device is optional, but recommended, since otherwise you’ll need to remember the password every time you want to log in.

To register your device, visit https://github.com/settings/security (on a desktop) after registering for your Github account and clicking 'Add a passkey'. Please make sure your device screen is unlocked prior to scanning the QR code to register your device with GitHub.

The initial attempt might require enabling passkeys on your device and choosing where you want to store your passkeys. Once these selections are made, the user can restart the 'Add a passkey' process and that should allow you to complete successfully.

For more information, please visit https://fidoalliance.org/passkeys/.

You can add the website as an icon on your home screen for quick access. Here's how:

• On iOS: Open Safari, navigate to the website, and select 'Add to Home Screen'.
• On Android: Open Chrome, navigate to the website, and select 'Add to Home Screen'.

If you encounter any bugs or have suggestions for new features, we encourage you to submit them through our GitHub repository's issue tracker. This allows us to keep track of reported issues and feature requests, prioritize them, and work on addressing them in a structured manner.

1. To submit a bug report or feature request, visit our GitHub repository at https://github.com/sprintup/ivystreetblog.
2. Click on the "Issues" tab, and then click on the "New Issue" button.
3. Choose the appropriate issue template (e.g., "Bug Report" or "Feature Request") and fill out the required information as detailed as possible.
4. For bug reports, please provide steps to reproduce the issue, any error messages you receive, and any other relevant information that could help us diagnose and fix the problem.
5. For feature requests, please describe the proposed feature, why you think it would be beneficial, and any additional details or use cases that could help us understand and implement the feature.

By submitting issues through our GitHub repository, you'll help us improve the platform and provide a better experience for all users. We appreciate your feedback and contributions to making IvyStreetBlog even better.

We welcome contributions from the community to help improve IvyStreetBlog. If you're familiar with GitHub and would like to contribute code changes, you can do so by submitting a pull request.

1. Fork the IvyStreetBlog repository to your own GitHub account.
2. Clone your forked repository to your local machine using Git.
3. Create a new branch for your changes, following the Git branching model of your choice.
4. Make your desired changes to the codebase, ensuring that your code follows best practices and is well-documented.
5. Commit your changes to your local branch and push them to your forked repository on GitHub.
6. From your forked repository on GitHub, open a new pull request to merge your changes into the main IvyStreetBlog repository.
7. Provide a clear and concise description of your changes, including any relevant issue numbers or references.

Our team will review your pull request, provide feedback if necessary, and merge it into the main codebase if it meets our contribution guidelines. We appreciate your contributions and look forward to collaborating with you to make IvyStreetBlog even better.

IvyStreetBlog is an open-source project, which means that the codebase is freely available for anyone to use, modify, and distribute for their own purposes. If you're running your own free little library and would like to use IvyStreetBlog as a companion website, you're welcome to do so.

1. Fork the IvyStreetBlog repository to your own GitHub account.
2. Clone your forked repository to your local machine using Git.
3. Modify the codebase as needed to fit your specific requirements, such as changing the branding, styling, or functionality.
4. Deploy the modified codebase to a hosting platform of your choice, such as Vercel, Netlify, or your own server.
5. Customize the deployed website to match the branding and information specific to your free little library.

By using IvyStreetBlog as a starting point, you'll have a solid foundation for creating a companion website for your free little library, allowing you to share information, manage book collections, and engage with your community. Feel free to modify the codebase as needed, and don't hesitate to contribute any improvements or bug fixes back to the main IvyStreetBlog repository.