Prep for version 1.0.0

.Rbuildignore

@@ -1,15 +1,22 @@
 ^_pkgdown\.yml$
-^docs$
-^pkgdown$
+^\.direnv$
+^\.DS_Store$
+^\.envrc$
+^\.github$
+^\.lintr$
+^\.Rproj\.user$
+^CONTRIBUTING.md$
+^cran-comments\.md$
+^CRAN-SUBMISSION$
+^Crashpad$
+^data-raw$
 ^doc$
+^docs$
+^flake\.lock$
+^flake\.nix$
 ^Meta$
-^README\.Rmd$
-^cran-comments\.md$
-^qtkit\.Rproj$
-^\.Rproj\.user$
-^qtkit\.code-workspace$
-^.github$
+^Library$
 ^LICENSE\.md$
+^pkgdown$
+^README\.Rmd$
 ^vignettes/articles$
-^.DS_Store$
-^CRAN-SUBMISSION$

.Rprofile

@@ -0,0 +1,6 @@
+# Add local library to the search path
+# for packages not on Nix
+.libPaths(new = c("Library", .libPaths()))
+
+# Set CRAN mirror
+options(repos = c(CRAN = "https://cran.rstudio.com"))

.envrc

@@ -0,0 +1 @@
+use flake

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,126 @@
+# Contributor Covenant 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 codeofconduct@posit.co.
+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][homepage],
+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/inclusion].
+
+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>.
+
+[homepage]: https://www.contributor-covenant.org

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report
+about: Create a report to help us improve qtkit
+---
+
+### Tips for a helpful bug report:
+
+- If you have a question, please don't use this form. Instead, ask on:
+
+  1. <https://github.com/qtalr/discussions>
+  2. <https://community.rstudio.com/>
+  3. <https://stackoverflow.com/>
+
+- Please include a **minimal reproducible example**, a reprex, to demonstrate the bug.
+  If you've never heard of a reprex, please read ["Make a reprex"](https://www.tidyverse.org/help/#reprex).
+  Do not include session info unless it is explicitly asked for.
+
+- If you can, use one of the built-in R datasets or a small toy dataset that exposes the bug.
+  If for some reason, the bug only occurs on your original data, try to limit the number of rows that are necessary to expose the bug.
+  Share such data by copying `dput()` output rather than an external file.
+
+- Please check whether somebody has reported the same problem in the [issues](https://github.com/qtalr/qtkit/issues).
+
+Delete these instructions once you have read them.
+
+---
+
+I found a problem with ...
+
+I expected ...
+
+Here is the code to reproduce the bug:
+
+```r
+# copy your code to the clipboard and run:
+reprex::reprex()
+```

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: qtalr Community Discussion
+    url: https:://github.com/qtalr/discussions
+    about: Please ask questions and discuss here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,33 @@
+---
+name: 'Feature Request'
+about: Suggest a change or new feature in qtkit
+---
+
+### Tips for a helpful feature request:
+
+- If you have a question, please don't use this form. Instead, ask on:
+
+  1. <https://github.com/qtalr/discussions>
+  2. <https://community.rstudio.com/>
+  3. <https://stackoverflow.com/>
+
+- See the [contributing guidelines](https://github.com/qtalr/qtkit/blob/main/CONTRIBUTING.md).
+
+- qtkit is a package primarily aimed a supporting the textbook ["An Introduction to Quantitative Text Analysis: Reproducible Research Using R"](https://qtalr.com/). Therefore, consider whether the functionality you propose will enhance and extend this goal. Improvements to its current functionality or to infrastructure are considered in scope for feature requests.
+
+- Please motivate the need for change, if applicable with a **minimal reproducible** example (reprex).
+  If you've never heard of a reprex, please read ["Make a reprex"](https://www.tidyverse.org/help/#reprex).
+  Do not include session info unless it is explicitly asked for.
+
+Delete this instructions once you've read them.
+
+---
+
+In situations when ...
+
+I would like to be able to ...
+
+```r
+# copy your code to the clipboard and run:
+reprex::reprex()
+```

.github/workflows/R-CMD-check.yaml

@@ -2,9 +2,9 @@
 # Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
 on:
   push:
-    branches: [main, master]
+    branches: [main, latest]
   pull_request:
-    branches: [main, master]
+    branches: [main, latest]
 
 name: R-CMD-check
 
@@ -39,6 +39,10 @@ jobs:
           http-user-agent: ${{ matrix.config.http-user-agent }}
           use-public-rspm: true
 
+      - name: Setup Chrome
+        if: runner.os == 'Windows'
+        uses: browser-actions/setup-chrome@latest
+
       - uses: r-lib/actions/setup-r-dependencies@v2
         with:
           extra-packages: any::rcmdcheck

.gitignore

@@ -1,28 +1,27 @@
-# RStudio
-.Rproj.user
+# R
 .Rhistory
 .Rdata
 .Ruserdata
 .Renviron
-*.Rproj
-
-# VSCode
-*.code-workspace
-.lintr
 
-# R
-.httr-oauth
-data-raw
+# Package
+data-raw/
 inst/doc
 vignettes/articles/_site/
 vignettes/articles/data/
+docs/
+Meta/
+
+# Flake
+.direnv/
 
 # macOS
 .DS_Store
 
 # Misc
 *_cache
 packages.bib
-docs
-/doc/
-/Meta/
+doc/
+Library/
+.lintr
+