Update unconfoundedr documentation

Author: actions-user

packages/myrpackage/404.html

@@ -0,0 +1,3 @@
+Content not found. Please use links in the navbar.
+
+# Page not found (404)

packages/myrpackage/404.md

@@ -0,0 +1,132 @@
+# Contributor Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in
+our community a harassment-free experience for everyone, regardless of
+age, body size, visible or invisible disability, ethnicity, sex
+characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance,
+race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open,
+welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our
+  mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political
+  attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair
+corrective action in response to any behavior that they deem
+inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other
+contributions that are not aligned to this Code of Conduct, and will
+communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also
+applies when an individual is officially representing the community in
+public spaces. Examples of representing our community include using an
+official e-mail address, posting via an official social media account,
+or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may
+be reported to the community leaders responsible for enforcement at
+<[email protected]>. All complaints will be reviewed and investigated
+promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security
+of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in
+determining the consequences for any action they deem in violation of
+this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior
+deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders,
+providing clarity around the nature of the violation and an explanation
+of why the behavior was inappropriate. A public apology may be
+requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, for a specified period of
+time. This includes avoiding interactions in community spaces as well as
+external channels like social media. Violating these terms may lead to a
+temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards,
+including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No
+public or private interaction with the people involved, including
+unsolicited interaction with those enforcing the Code of Conduct, is
+allowed during this period. Violating these terms may lead to a
+permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of
+individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction
+within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor
+Covenant](https://www.contributor-covenant.org), version 2.1, available
+at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla’s code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ
+at <https://www.contributor-covenant.org/faq>. Translations are
+available at <https://www.contributor-covenant.org/translations>.

packages/myrpackage/CODE_OF_CONDUCT.html

@@ -0,0 +1,167 @@
+# Contributing to myrpackage
+
+Thank you for considering contributing to myrpackage! This document
+provides guidelines for contributing to the project.
+
+## Code of Conduct
+
+Please note that the myrpackage project is released with a [Contributor
+Code of
+Conduct](https://diogoribeiro7.github.io/packages/myrpackage/CODE_OF_CONDUCT.md).
+By participating in this project you agree to abide by its terms.
+
+## How to Contribute
+
+### Reporting Bugs
+
+If you find a bug, please create an issue on GitHub with the following
+information:
+
+1.  A clear title and description
+2.  Steps to reproduce the behavior
+3.  Expected behavior
+4.  Actual behavior
+5.  Environment details (R version, package version, OS)
+6.  If possible, a minimal reproducible example
+
+### Suggesting Enhancements
+
+For feature requests, please create an issue on GitHub with:
+
+1.  A clear title and description
+2.  Why this feature would be useful
+3.  Example code showing how the feature would be used
+4.  Any relevant references or context
+
+### Pull Requests
+
+1.  Fork the repository
+2.  Create a new branch for your feature or bugfix
+3.  Make your changes
+4.  Add tests for your changes
+5.  Ensure all tests pass with `devtools::test()`
+6.  Update documentation with `devtools::document()`
+7.  Run R CMD check with `devtools::check()`
+8.  Submit a pull request
+
+## Development Workflow
+
+### Setting Up Development Environment
+
+1.  Clone the repository
+2.  Open the project in RStudio (or your preferred R IDE)
+3.  Install development dependencies:
+
+``` r
+# Install development dependencies
+devtools::install_dev_deps()
+
+# Install the package in development mode
+devtools::load_all()
+```
+
+### Running Tests
+
+``` r
+# Run all tests
+devtools::test()
+
+# Run specific tests
+testthat::test_file("tests/testthat/test-hello.R")
+
+# Check test coverage
+covr::package_coverage()
+```
+
+### Documentation
+
+``` r
+# Generate documentation
+devtools::document()
+
+# Preview documentation
+devtools::dev_help("hello")
+
+# Build vignettes
+devtools::build_vignettes()
+
+# Build README
+devtools::build_readme()
+```
+
+### Code Style
+
+We follow the [tidyverse style guide](https://style.tidyverse.org/).
+Please ensure your code adheres to this style.
+
+You can use the following tools to check and fix style issues:
+
+``` r
+# Check code style
+lintr::lint_package()
+
+# Auto-format code
+styler::style_pkg()
+```
+
+### Commit Messages
+
+Please use clear and descriptive commit messages. We recommend following
+the [conventional commits](https://www.conventionalcommits.org/)
+specification:
+
+- `feat`: A new feature
+- `fix`: A bug fix
+- `docs`: Documentation changes
+- `style`: Changes that do not affect code behavior (formatting, etc.)
+- `refactor`: Code changes that neither fix a bug nor add a feature
+- `test`: Adding or fixing tests
+- `chore`: Changes to the build process or auxiliary tools
+
+### Pre-commit Checks
+
+Before committing, please run:
+
+``` r
+# Document the package
+devtools::document()
+
+# Run tests
+devtools::test()
+
+# Run R CMD check
+devtools::check()
+```
+
+## Release Process
+
+1.  Update version number in DESCRIPTION
+2.  Update NEWS.md with changes
+3.  Run full checks:
+
+``` r
+devtools::check()
+rcmdcheck::rcmdcheck(args = c("--no-manual", "--as-cran"))
+```
+
+4.  Build the package:
+
+``` r
+devtools::build()
+```
+
+5.  Tag the release in Git:
+
+``` r
+usethis::use_git_tag("v0.1.0")
+```
+
+## Getting Help
+
+If you need help or have questions, you can:
+
+- Open an issue on GitHub
+- Reach out to the package maintainer: Diogo Ribeiro
+  (<[email protected]>)
+
+Thank you for contributing!

packages/myrpackage/CODE_OF_CONDUCT.md

@@ -0,0 +1,4 @@
+# License
+
+    YEAR: 2025
+    COPYRIGHT HOLDER: Diogo Ribeiro

packages/myrpackage/CONTRIBUTING.html

@@ -0,0 +1,22 @@
+# MIT License
+
+Copyright (c) 2025 Diogo Ribeiro
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the
+“Software”), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.