feat: implement modular UMass theme components and supporting generation scripts for home page structure

2026-07-29 23:03:29 +07:00
parent c1e0e39aad
commit 317df123bb
37 changed files with 7044 additions and 192 deletions
@@ -1,19 +1,19 @@
 # website_sisvietnam.vn

-
-
 ## Database Configuration

 ### Development Database (H2 Console)
+
 - **Profile**: `dev`
 - **Database Type**: H2 (File-based, embedded)
 - **JDBC URL**: `jdbc:h2:file:./build/h2db/db/sisvietnamvn`
 - **Username**: `sisvietnamvn`
- **Password**: *(leave blank)*
+- **Password**: _(leave blank)_
 - **Console Access**: [http://localhost:8080/h2-console](http://localhost:8080/h2-console) (requires app running in dev profile)
 - **Config File**: [application-dev.yml](file:///d:/website_sisvietnam_moi/website_sisvietnam.vn/sisvietnamvn/src/main/resources/config/application-dev.yml)

 ### Production Database
+
 - **Profile**: `prod`
 - **Database Type**: Oracle Database
 - **JDBC URL**: `jdbc:oracle:thin:@localhost:1521:xe`
@@ -21,6 +21,7 @@
 - **Config File**: [application-prod.yml](file:///d:/website_sisvietnam_moi/website_sisvietnam.vn/sisvietnamvn/src/main/resources/config/application-prod.yml)

 ### Schema Management
+
 - **Tool**: Liquibase
 - **Changelog Folder**: [src/main/resources/config/liquibase/](file:///d:/website_sisvietnam_moi/website_sisvietnam.vn/sisvietnamvn/src/main/resources/config/liquibase/)

@@ -32,8 +33,8 @@ Already a pro? Just edit this README.md and make it your own. Want to make it ea

 ## Add your files

-* [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
-* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+- [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
+- [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:

 ```
 cd existing_repo
@@ -44,27 +45,27 @@ git push -uf origin main

 ## Integrate with your tools

-* [Set up project integrations](http://[IP_ADDRESS]/pvdhien/website_sisvietnam.vn/-/settings/integrations)
+- [Set up project integrations](http://[IP_ADDRESS]/pvdhien/website_sisvietnam.vn/-/settings/integrations)

 ## Collaborate with your team

-* [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
-* [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
-* [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
-* [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
-* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+- [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
+- [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
+- [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
+- [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
+- [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)

 ## Test and Deploy

 Use the built-in continuous integration in GitLab.

-* [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
-* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
-* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
-* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
-* [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
+- [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
+- [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
+- [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
+- [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
+- [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)

-***
+---

 # Editing this README

@@ -75,30 +76,39 @@ When you're ready to make this README your own, just edit this file and use the
 Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

 ## Name
+
 Choose a self-explaining name for your project.

 ## Description
+
 Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

 ## Badges
+
 On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

 ## Visuals
+
 Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

 ## Installation
+
 Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

 ## Usage
+
 Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

 ## Support
+
 Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

 ## Roadmap
+
 If you have ideas for releases in the future, it is a good idea to list them in the README.

 ## Contributing
+
 State if you are open to contributions and what your requirements are for accepting them.

 For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
@@ -106,14 +116,16 @@ For people who want to make changes to your project, it's helpful to have some d
 You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

 ## Authors and acknowledgment
+
 Show your appreciation to those who have contributed to the project.

 ## License
+
 For open source projects, say how it is licensed.

 ## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

 cd ..\sisvietnamvn\
 .\gradlew bootRun
@@ -130,33 +142,53 @@ Bạn có thể refresh lại trang web để kiểm tra màu sắc trên menu h

 ## How to Debug (VS Code)

-1. **Start the Application in Debug Mode**:
-   Open a terminal in the project directory (`sisvietnamvn_main`) and run:
-   ```bash
-   ./gradlew bootRun --debug-jvm
-   ```
-   The application will start and pause, displaying: `Listening for transport dt_socket at address: 5005`.
+1.  **Start the Application in Debug Mode**:
+    Open a terminal in the project directory (`sisvietnamvn_main`) and run:

-2. **Configure VS Code**:
-   Ensure your `.vscode/launch.json` has the following configuration:
-   ```json
-   {
-     "type": "java",
-     "name": "Debug (Attach) - Port 5005",
-     "request": "attach",
-     "hostName": "127.0.0.1",
-     "port": 5005,
-     "projectName": "sisvietnamvn"
-   }
-   ```
+    ```bash
+    ./gradlew bootRun --debug-jvm
+    ```

-3. **Attach the Debugger**:
-   - Go to the **Run and Debug** view in VS Code (`Ctrl+Shift+D`).
-   - Select **Debug (Attach) - Port 5005** from the dropdown at the top.
-   - Click the green **Play** button (or press `F5`).
-   - The application will resume booting.
+    The application will start and pause, displaying: `Listening for transport dt_socket at address: 5005`.

-4. **Set Breakpoints & Debug**:
-   - Open any Java file (e.g., `SwiperSliderPlugin.java`).
-   - Click in the left margin next to a line number to place a red breakpoint.
-   - Trigger the code (e.g., by navigating to the page in your browser). Execution will pause at your breakpoint, allowing you to inspect variables!
+2.  **Configure VS Code**:
+    Ensure your `.vscode/launch.json` has the following configuration:
+
+    ```json
+    {
+      "type": "java",
+      "name": "Debug (Attach) - Port 5005",
+      "request": "attach",
+      "hostName": "127.0.0.1",
+      "port": 5005,
+      "projectName": "sisvietnamvn"
+    }
+    ```
+
+3.  **Attach the Debugger**:
+    - Go to the **Run and Debug** view in VS Code (`Ctrl+Shift+D`).
+    - Select **Debug (Attach) - Port 5005** from the dropdown at the top.
+    - Click the green **Play** button (or press `F5`).
+    - The application will resume booting.
+
+4.  **Set Breakpoints & Debug**: - Open any Java file (e.g., `SwiperSliderPlugin.java`). - Click in the left margin next to a line number to place a red breakpoint. - Trigger the code (e.g., by navigating to the page in your browser). Execution will pause at your breakpoint, allowing you to inspect variables!
+
+//script test video fallback on homepage
+const video = document.querySelector('video');
+if (video) {
+// Hide the video element and its controls
+const ambientVideoContainer = video.closest('.f--ambient-video');
+if (ambientVideoContainer) ambientVideoContainer.style.display = 'none';
+
+      const controls = document.querySelector('.video-controls');
+      if (controls) controls.style.display = 'none';
+
+      // Show the fallback block containing the seeded Swiper carousel
+      const fallback = document.getElementById('hero-video-fallback');
+      if (fallback) fallback.style.display = 'block';
+
+      console.log("Fallback triggered successfully.");
+
+} else {
+console.log("No video element found on this page.");
+}