From da771af8ef985d8282a87c7ade6c856ca73d2fae Mon Sep 17 00:00:00 2001 From: Ed Chalstrey Date: Thu, 27 Jun 2024 10:17:30 +0100 Subject: [PATCH 01/41] scroll adjust works but ticks missing --- .../apps/core/templates/core/world_map.html | 53 ++++++++++++++----- 1 file changed, 39 insertions(+), 14 deletions(-) diff --git a/seshat/apps/core/templates/core/world_map.html b/seshat/apps/core/templates/core/world_map.html index 19bf0f1ee..0a03bbadf 100644 --- a/seshat/apps/core/templates/core/world_map.html +++ b/seshat/apps/core/templates/core/world_map.html @@ -75,15 +75,26 @@ } #variableLegend { - position: absolute; - bottom: 75; - right: 0; - background-color: rgba(255, 255, 255, 0.8); /* Semi-transparent white */ - padding: 10px; - border-radius: 5px; - max-width: 200px; - z-index: 999; -} + position: absolute; + bottom: 75; + right: 0; + background-color: rgba(255, 255, 255, 0.8); /* Semi-transparent white */ + padding: 10px; + border-radius: 5px; + max-width: 200px; + z-index: 999; + } + + /* Hide scrollbar for WebKit browsers */ + #sliderdiv::-webkit-scrollbar { + display: none; + } + + /* Hide scrollbar for IE, Edge, and Firefox */ + #sliderdiv { + -ms-overflow-style: none; /* IE and Edge */ + scrollbar-width: none; /* Firefox */ + } @@ -190,13 +201,14 @@

Base Map

-
+
-
+
- +
@@ -207,6 +219,19 @@

Base Map

+ + {% block content %} {% if content.include_polity_map %} From bc2967a564c95c6b487a6de0bc5c8099cc279319 Mon Sep 17 00:00:00 2001 From: Kalle Westerling Date: Thu, 4 Jul 2024 09:35:04 +0100 Subject: [PATCH 40/41] Fixing up unnecessary `docs` import causing docs rendering issues --- docs/source/conf.py | 5 ----- 1 file changed, 5 deletions(-) diff --git a/docs/source/conf.py b/docs/source/conf.py index 2361951bb..571b3fda2 100644 --- a/docs/source/conf.py +++ b/docs/source/conf.py @@ -16,7 +16,6 @@ sys.path.insert(0, os.path.abspath('../..')) os.environ['DJANGO_SETTINGS_MODULE'] = 'seshat.settings.base' -import sphinx_rtd_theme import seshat @@ -36,7 +35,6 @@ "sphinx.ext.autodoc", "sphinx.ext.autosummary", "sphinx.ext.doctest", - # "sphinx_rtd_theme", "myst_parser", "autoapi.extension", "sphinx_copybutton", @@ -106,10 +104,7 @@ # https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output html_theme = "sphinx_book_theme" - -# html_theme_path = [sphinx_rtd_theme.get_html_theme_path()] html_static_path = ["_static"] - html_theme_options = { "use_download_button": True, } From 7ddd3b1785f0cab28842def831971f818c6bd25d Mon Sep 17 00:00:00 2001 From: Kalle Westerling Date: Thu, 4 Jul 2024 09:57:48 +0100 Subject: [PATCH 41/41] Create issue templates Fixes Seshat-Global-History-Databank/seshat#2 --- .github/ISSUE_TEMPLATE/BUG_REPORT.yml | 80 +++++++++++++++++ .github/ISSUE_TEMPLATE/DOCS_IMPROVEMENT.yml | 53 +++++++++++ .github/ISSUE_TEMPLATE/USER_STORY.yml | 97 +++++++++++++++++++++ 3 files changed, 230 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/BUG_REPORT.yml create mode 100644 .github/ISSUE_TEMPLATE/DOCS_IMPROVEMENT.yml create mode 100644 .github/ISSUE_TEMPLATE/USER_STORY.yml diff --git a/.github/ISSUE_TEMPLATE/BUG_REPORT.yml b/.github/ISSUE_TEMPLATE/BUG_REPORT.yml new file mode 100644 index 000000000..1ce966773 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/BUG_REPORT.yml @@ -0,0 +1,80 @@ +name: "🐛 Bug Report" +description: Create a new ticket for a bug. +title: "🐛 [BUG] - " +labels: [ + "bug" +] +body: + - type: textarea + id: description + attributes: + label: "Description" + description: Please enter an explicit description of your issue + placeholder: Short and explicit description of your incident... + validations: + required: true + # - type: input + # id: reprod-url + # attributes: + # label: "Reproduction URL" + # description: Please enter your GitHub URL to provide a reproduction of the issue + # placeholder: ex. https://github.com/USERNAME/REPO-NAME + # validations: + # required: true + - type: textarea + id: reprod + attributes: + label: "Reproduction steps" + description: Please enter an explicit description of your issue + value: | + 1. Go to '...' + 2. Click on '....' + 3. Scroll down to '....' + 4. See error + render: bash + validations: + required: true + - type: textarea + id: screenshot + attributes: + label: "Screenshots" + description: If applicable, add screenshots to help explain your problem. + value: | + ![DESCRIPTION](LINK.png) + render: bash + validations: + required: false + - type: textarea + id: logs + attributes: + label: "Logs" + description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks. + render: bash + validations: + required: false + - type: dropdown + id: browsers + attributes: + label: "Browsers" + description: What browsers are you seeing the problem on ? + multiple: true + options: + - Firefox + - Chrome + - Safari + - Microsoft Edge + - Opera + validations: + required: false + - type: dropdown + id: os + attributes: + label: "OS" + description: What is the impacted environment ? + multiple: true + options: + - Windows + - Linux + - Mac + validations: + required: false \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/DOCS_IMPROVEMENT.yml b/.github/ISSUE_TEMPLATE/DOCS_IMPROVEMENT.yml new file mode 100644 index 000000000..2d1d9a133 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/DOCS_IMPROVEMENT.yml @@ -0,0 +1,53 @@ +name: Documentation Improvement + +description: Suggest changes or improvements to the documentation. + +title: "📚 [Documentation] <title>" + +labels: ["documentation"] + +body: + - type: markdown + attributes: + value: | + ## Documentation Improvement Request + + Thank you for taking the time to help improve our documentation! Please provide the details of your suggestion below. + + ### Example + + **Section of Documentation**: Installation Instructions + + **Description of Improvement**: Add a troubleshooting guide for common installation issues on Windows. + + **Benefits of Improvement**: Helps users resolve installation problems quickly, reducing frustration and support requests. + + **Additional Context**: Based on frequent questions from users in the community forums. + + - type: input + id: section + attributes: + label: Section of Documentation + description: Which section of the documentation does this improvement pertain to? + placeholder: "e.g., Installation Instructions, User Guide, API Reference" + + - type: textarea + id: description + attributes: + label: Description of Improvement + description: Provide a detailed description of the improvement you are suggesting. + placeholder: "Describe the change or addition you would like to see." + + - type: input + id: benefits + attributes: + label: Benefits of Improvement + description: Explain how this improvement will benefit users. + placeholder: "e.g., clearer instructions, easier navigation, more comprehensive coverage" + + - type: textarea + id: context + attributes: + label: Additional Context + description: Add any other context or information related to this improvement request. + placeholder: "Include any relevant links, examples, or references." diff --git a/.github/ISSUE_TEMPLATE/USER_STORY.yml b/.github/ISSUE_TEMPLATE/USER_STORY.yml new file mode 100644 index 000000000..f7772233d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/USER_STORY.yml @@ -0,0 +1,97 @@ +name: Feature request +description: To create a new feature request, we ask that you write a user story. +title: "👤 [User Story]: " +labels: ["feature-request"] +body: + - type: markdown + attributes: + value: | + Thank you for contributing an idea for a new feature! Please fill out the user story details below to help us understand your vision for the new feature. + + - type: input + id: role + attributes: + label: Role + description: Who is the user for this story? + placeholder: ex. As a [Admin] + validations: + required: true + + - type: input + id: feature + attributes: + label: Desired Feature + description: What is the feature you would like to have? + placeholder: I want to [feature description] + validations: + required: true + + - type: input + id: benefit + attributes: + label: Benefit + description: What is the benefit of this feature? + placeholder: So that I can [benefit description] + validations: + required: true + + - type: textarea + id: acceptance-criteria + attributes: + label: Acceptance Criteria + description: + Please describe the conditions that must be met for this story to be + considered complete. + placeholder: | + **GIVEN** [precondition] + **AND** [another precondition if necessary] + **WHEN** [action taken by the user] + **THEN** [expected outcome] + **AND** [another outcome if necessary] + validations: + required: true + + - type: textarea + id: dependencies + attributes: + label: Dependencies + description: Are there any other tasks that need to be completed first? + placeholder: | + - [ ] Dependency 1 (include issue link) + - [ ] Dependency 2 (include issue link) + validations: + required: false + + - type: textarea + id: technical-notes + attributes: + label: Technical Notes + description: + Any technical notes, potential challenges, or architectural + considerations for implementation? + placeholder: | + - Note 1 + - Note 2 + validations: + required: false + + - type: checkboxes + id: definition-of-done + attributes: + label: Definition of Done + description: + Please confirm the following are completed before this story can be + considered done. + options: + - label: The feature fulfills all acceptance criteria. + - label: The code is reviewed and meets team coding standards. + - label: All unit, integration, and end-to-end tests are passed. + - label: The feature meets accessibility standards set for the project. + - label: + The code passes the CI/CD pipeline quality controls (style and + linting). + - label: The feature is merged into the main branch. + - label: The feature is deployed and functional in the QA environment. + - label: + The feature was demonstrated to the team and accepted by the product + owner. \ No newline at end of file