Classification Experiment #333
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… depth 🔧 (footer.html): add Masonry layout script for improved UI flexibility ♻️ (list.html): refactor tag list layout for better readability and maintainability The Definition of Done documentation is expanded to provide a more comprehensive understanding of its importance, including organizational and team-specific criteria. This aims to improve transparency, consistency, and quality across teams. The footer now includes the Masonry layout script to enhance the visual presentation of content. The tag list layout is refactored to improve readability and maintainability, ensuring a more organized and user-friendly interface.
…and Write-ErrorLog for improved logging clarity The changes replace the use of Write-Debug with Write-InfoLog and Write-ErrorLog to provide more meaningful and clear logging messages. This enhances the readability and understanding of the log outputs, making it easier to distinguish between informational messages and error messages during the execution of the script.
…unt of deleted images Remove trailing whitespace in the Hugo setup step for consistency. Capture the count of deleted images in the Delete-LocalImageFiles function and log this information. This change enhances the transparency of the image deletion process by providing a count of deleted images, which can be useful for monitoring and debugging purposes. Additionally, the logging level for individual file deletions is changed from info to debug to reduce verbosity in standard logs.
…workflow ♻️ (list.html): simplify tag list layout by removing redundant range logic In the GitHub Actions workflow, a new step is added to delete specific local data files. This ensures that unnecessary files do not persist, which can help in maintaining a clean working environment and prevent potential issues with outdated or incorrect data. In the HTML layout for tags, the logic is simplified by removing the 'after 3' range. This change reduces complexity and potential redundancy in the code, making it easier to maintain and understand. The previous logic was likely unnecessary for the current requirements.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-pond-042d21b03-333.westeurope.5.azurestaticapps.net |
…ability and structure The changes enhance the readability and structure of the category and tag list templates. The section headers for "Categories" and "Tags" are now more prominent with updated heading levels, improving the visual hierarchy. The layout adjustments ensure a more consistent and user-friendly presentation of categories and tags, making it easier for users to navigate and understand the content. Additionally, the code refactoring improves maintainability and aligns with best practices for template organization.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-pond-042d21b03-333.westeurope.5.azurestaticapps.net |
…ging Refactor the GitHub Actions workflow to include a cleanup step for local data files and improve logging. The job name is updated to reflect the new functionality. Introduce a new PowerShell script `CleanupDataFiles.ps1` to handle the deletion of local data files with improved error handling and logging. This change aims to streamline the workflow by ensuring local files are cleaned up after offloading, reducing storage usage, and providing better insight into the process through logging.
…nd file handling Enhance the scripts to provide more informative logging and handle cases where no files are found. The changes include: - Adding checks for the presence of files before attempting deletion, logging a message if no files are found. - Calculating and logging the total size of files to be deleted, providing better insight into the operation. - Replacing `Write-Debug` with `Write-DebugLog` and `Write-ErrorLog` for consistency and clarity in logging. These improvements aim to make the scripts more robust and user-friendly by providing detailed feedback during execution.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-pond-042d21b03-333.westeurope.5.azurestaticapps.net |
…tion logging with progress tracking Improve the logging mechanism in the file deletion scripts by adding progress tracking. This change provides better visibility into the deletion process by logging progress at defined intervals (every 10%). This is particularly useful for large datasets, allowing users to monitor the progress and ensuring that the script is functioning as expected. Additionally, the log messages are refined for clarity, indicating the total number of files processed and the completion status.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-pond-042d21b03-333.westeurope.5.azurestaticapps.net |
… image upload and link rewriting scripts Improve the logging mechanism by replacing `Write-Debug` with more specific logging functions like `Write-InfoLog`, `Write-ErrorLog`, and `Write-DebugLog` to provide clearer and more meaningful log messages. Add progress tracking for the HTML link rewriting process, logging progress at 10% intervals to give better visibility into the script's execution status. These changes enhance the script's usability and maintainability by providing more informative feedback during execution.
…sistency The job names in the GitHub Actions workflow are updated to provide a more thematic and consistent naming convention. This change aims to enhance the readability and understanding of the workflow by using more descriptive and imaginative names, aligning with the project's theme.
The job names in the GitHub Actions workflow are updated to be more descriptive and consistent. This change improves readability and understanding of the workflow steps, making it easier for developers to follow the process. The previous names were more abstract and less intuitive, which could lead to confusion.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-pond-042d21b03-333.westeurope.5.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://yellow-pond-042d21b03-333.westeurope.5.azurestaticapps.net |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 (content): enhance Definition of Done documentation for clarity and depth
🔧 (footer.html): add Masonry layout script for improved UI flexibility
♻️ (list.html): refactor tag list layout for better readability and maintainability
The Definition of Done documentation is expanded to provide a more comprehensive understanding of its importance, including organizational and team-specific criteria. This aims to improve transparency, consistency, and quality across teams. The footer now includes the Masonry layout script to enhance the visual presentation of content. The tag list layout is refactored to improve readability and maintainability, ensuring a more organized and user-friendly interface.