{"id":13762308,"url":"https://visualanalyticshealthcare.github.io/homepage/","last_synced_at":"2025-05-10T15:31:24.883Z","repository":{"id":152929265,"uuid":"566961130","full_name":"visualanalyticshealthcare/homepage","owner":"visualanalyticshealthcare","description":"The homepage of VAHC workshop","archived":false,"fork":false,"pushed_at":"2024-11-07T23:45:39.000Z","size":348517,"stargazers_count":2,"open_issues_count":0,"forks_count":2,"subscribers_count":1,"default_branch":"main","last_synced_at":"2024-11-08T00:35:27.719Z","etag":null,"topics":["data-visualization","healthcare","visual-analytics"],"latest_commit_sha":null,"homepage":"https://visualanalyticshealthcare.github.io/homepage/","language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/visualanalyticshealthcare.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-11-16T19:27:16.000Z","updated_at":"2024-11-07T23:43:47.000Z","dependencies_parsed_at":"2023-10-15T18:49:03.273Z","dependency_job_id":"1e97d330-9e09-4766-a517-3d13ee18a7ef","html_url":"https://github.com/visualanalyticshealthcare/homepage","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/visualanalyticshealthcare%2Fhomepage","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/visualanalyticshealthcare%2Fhomepage/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/visualanalyticshealthcare%2Fhomepage/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/visualanalyticshealthcare%2Fhomepage/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/visualanalyticshealthcare","download_url":"https://codeload.github.com/visualanalyticshealthcare/homepage/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":224974208,"owners_count":17401100,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["data-visualization","healthcare","visual-analytics"],"created_at":"2024-08-03T14:00:38.566Z","updated_at":"2025-05-10T15:31:24.870Z","avatar_url":"https://github.com/visualanalyticshealthcare.png","language":"HTML","funding_links":[],"categories":["Conferences"],"sub_categories":[],"readme":"VAHC Homepage\n=============\n\nThe homepage of Workshop on Visual Analytics in Healthcare (VAHC).\n\n\nUpdate Content\n--------------\n\nYou can use the online VSCode editor to update any `.md` files and GitHub Action will automatically rebuild and publish the website after saving changes online (it will be committed to the `main` branch).\n\n\nInstall and Quick Start\n-----------------------\n\nThe VAHC homepage is built based on [Pelican](https://getpelican.com/), a Python-powered static site generator. You can install Pelican via several different methods. The simplest is via Pip and specify using markdown:\n\n```bash\npython -m pip install \"pelican[markdown]\"\n```\n\nThen, you can clone the repo and go to the root folder of the cloned repo:\n\n```bash\npelican -r -l\n```\n\nThe default local dev site will be served at `http://localhost:8000/`.\nYou can now open web browser and check the website for development.\n\n\nDeployment\n----------\n\nTo deploy the generated static site on GitHub Pages, the following steps should be followed:\n\n1. Enable workflow permissions. In \"Settings / Action / General\", ensure the \"Workflow permissions\" is set to \"Read and write permissions\".\n2. Enable GitHub Action and add a new workflow `main.yml`. \n   Copy the following content to create the workflow action. \n   It will take a few minutes to run. Once it shows completed without any error in the Action, you can move next step.\n3. Enable the GitHub Pages. In \"Settings / Pages\", select:\n    - Source: Deploy from a branch\n    - Branch: gh-pages, /(root)\n\nIf everything works fine, you can find the `gh-pages` branch has been deployed on GitHub Pages and you can access it.\n\n```yaml\n# This is a basic workflow to help you get started with Actions\n\nname: Deploy Latest Pages by Pelican\n\n# Controls when the workflow will run\non:\n  # Triggers the workflow on push or pull request events but only for the \"main\" branch\n  push:\n    branches: [ \"main\" ]\n  pull_request:\n    branches: [ \"main\" ]\n\n  # Allows you to run this workflow manually from the Actions tab\n  workflow_dispatch:\n\n# A workflow run is made up of one or more jobs that can run sequentially or in parallel\njobs:\n  # This workflow contains a single job called \"build\"\n  build:\n    # The type of runner that the job will run on\n    runs-on: ubuntu-latest\n\n    # Steps represent a sequence of tasks that will be executed as part of the job\n    steps:\n      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it\n      - uses: actions/checkout@v3\n\n      # Runs a single command using the runners shell\n      - name: Run a one-line script\n        run: echo Hello, Pelican!\n          \n      # Runs a build for pelican\n      - name: GitHub Pages Pelican Build Action\n        uses: nelsonjchen/gh-pages-pelican-action@0.1.10\n        env:\n          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n```\n\n\nSettings\n--------\n\nDue to the special needs of hosting a conference website, some settings in the `pelicanconf.py` have been customized to support conference hosting workflow.\n\n1. `DEFAULT_YEAR`. It's obvious that you need to set this variable to the conference year accordingly.\n2. `PAST_EVENTS`. This will be used for generating the footer links to past events.\n3. `*_SAVE_AS`. Some features are not used by a simple conference website, such as author page, tag page, archive page, category page, etc. So, they are all disabled and removed from output list.\n\n\nCreate New Site\n---------------\n\nThe content structure of each year is very similar (or just the same) to previous year. So you can create a new website for the coming year as follows:\n\n1. Duplicate a latest year folder in `content` and rename to target year. For example, copy the folder `2023`, paste and rename it to `2024` for the 2024.\n2. Update the `Category` value in **ALL** `.md` files in the newly created folder. For example, update `Category: 2024` in the `2024\\index.md`, `2024\\call-for-papers.md`, etc. As this category value will be used to generate the URL and folder, please ensure you updated **ALL** category information correctly. Otherwise the generated HTML files of other year may be affected.\n3. Update the contents of each article in the new folder.\n\nProceedings Generation\n--------------------\n\nThe repository includes utilities to generate proceedings pages from CSV submissions:\n\n1. `utils/csv2proc_pages.py`: A Python script that converts submissions CSV to proceedings pages\n   - Input: `content/{year}/submissions.csv` with columns: id, type, authors, title, abstract, publication_date, citation_conference_title\n   - Outputs:\n     - Individual HTML pages in `content/proceedings/{year}/`\n     - Proceedings markdown in `content/{year}/proceedings.md`\n   - Usage:\n     ```bash\n     cd utils\n     python csv2proc_pages.py \u003cyear\u003e\n     # Example: python csv2proc_pages.py 2024\n     ```\n\n2. `utils/test_csv2proc_pages.py`: Unit tests for the proceedings generator\n   - Tests CSV parsing, proceedings markdown generation, and HTML page generation\n   - Usage:\n     ```bash\n     cd utils\n     python -m unittest test_csv2proc_pages.py\n     ```\n\nThe CSV file should have the following required fields:\n- `id`: Unique identifier for the submission\n- `type`: Type of submission (e.g., \"Poster\", \"Paper\", \"Demo\")\n- `authors`: Comma-separated list of authors\n- `title`: Paper title\n- `abstract`: Paper abstract\n- `publication_date`: Publication date (YYYY-MM-DD)\n- `citation_conference_title`: Full conference title\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/visualanalyticshealthcare.github.io%2Fhomepage%2F","html_url":"https://awesome.ecosyste.ms/projects/visualanalyticshealthcare.github.io%2Fhomepage%2F","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/visualanalyticshealthcare.github.io%2Fhomepage%2F/lists"}