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

synchronize user manual page btw app template and app directory #147

Closed
keighrim opened this issue May 22, 2023 · 2 comments · Fixed by #169
Closed

synchronize user manual page btw app template and app directory #147

keighrim opened this issue May 22, 2023 · 2 comments · Fixed by #169
Labels
🏗️C Relating to Continuous Deployment 📝D Improvements or additions to documentation
Milestone

Comments

@keighrim
Copy link
Member

Because

(related to clamsproject/apps#21)

There's a PR open in the app directory (clamsproject/apps#41) that publishes the general app user manual as a webpage under the app-directory.

My reasoning behind the PR was that sdk.clams.ai holds documentation for app developers, while apps.clams.ai holds information for the app users.

That said, the one that's included in the app scaffolding needs to be retired or synchronized.

Done when

CLAMS-generic-readme.md file is removed and instead add a link to the app user manual to the main readme .

Or keep it as is and find a way to automatically synchronize its contents to https://apps.clams.ai/clamsapp .

Additional context

No response

@github-project-automation github-project-automation bot moved this to Todo in infra May 22, 2023
@clams-bot clams-bot added this to infra May 22, 2023
@keighrim keighrim added 📝D Improvements or additions to documentation 🏗️C Relating to Continuous Deployment labels May 22, 2023
@keighrim
Copy link
Member Author

My primary concern with clamsproject/apps#41 is that it separates the user manual from the sdk repository, but there's chance of a SDK update causing changes in the app usability (even minor, like recent additional of multivalued runtime parameters). In such a case, SDK developers also need to update something that's now part of the SDK repository, and I don't like that fragmentation.

Here's one way to create an automatic synchronization mechanism;

  1. On SDK repo side, we keep the user manual up to date in the SDK repository (because SDK is the piece of software that determines the behaviors of apps, and thus the contents of the manual)
  2. On apps repo side, we use https://github.com/rolinh/jekyll-remote-markdown/ for automatic synchronization (this can only be done after add proper jekyll config/theme  apps#42 is resolved)
  3. When there's a push to the SDK main branch that has changes in the user manual file, we manually invoke jekyll-build workflow on the apps repo side.

One problem is that once we set up a manual jekyll-build workflow, it will replace the default github pages workflow. Hence we need to carefully design the workflow to make sure the app registration workflow is not affected.

@keighrim
Copy link
Member Author

keighrim commented Jan 1, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏗️C Relating to Continuous Deployment 📝D Improvements or additions to documentation
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant