Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build blog post workflow doc #4

Open
jcasman opened this issue Oct 9, 2023 · 2 comments
Open

Build blog post workflow doc #4

jcasman opened this issue Oct 9, 2023 · 2 comments
Assignees
Labels
difficulty: medium Should be feasible with only minimal research on strategy documentation Improvements or additions to documentation

Comments

@jcasman
Copy link
Collaborator

jcasman commented Oct 9, 2023

Oppkey needs multiple staff (Jesse, Erik, Ilenia) to be able to post blogs to the quarto-demo repo and website. Erik to walk through the steps, Jesse to document. Together we make a doc that is usable by staff who are not local (Ilenia) or who have forgotten the steps (maybe we pick up doing blog posts after an extended break).

@jcasman jcasman added documentation Improvements or additions to documentation difficulty: medium Should be feasible with only minimal research on strategy labels Oct 9, 2023
@codetricity
Copy link
Collaborator

There are likely three deployment options:

  1. non-technical staff that receive a .qmd document from a member of the working group
  2. technical staff (likely an intern or a contract staff in Oppkey network) who interview working group member and then write post, possibly with code snippets
  3. working group member who does a fork and pull request

Is it possible to create a single document suitable for all three scenarios?

@jcasman
Copy link
Collaborator Author

jcasman commented Oct 15, 2023

I will bring this up with Erik on Monday, since I intend to work with him on the Quarto workflow documentation together. I believe #2 and #3 are basically subsets of #1. But I'll plan on having 3 different sections covering the three scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty: medium Should be feasible with only minimal research on strategy documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants