bilingual-jekyll-resume-theme 0.1.1 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e95865459117ab43ae43114972d1ae82245a2d459b51e1d9980396400d18a79e
-  data.tar.gz: 470648d6f71bed91528b11cbefe960747741116c428b013e3f058fe1c5f00b48
+  metadata.gz: f2f1c7e48b7ef1d8f1c500e1faccfeb19ebb5d9653b0ad5724bd2cd391e15261
+  data.tar.gz: c117b219149ec9daa3b2bc180058ce787da21dbe1ebcffb497dfefa8c8481fa7
 SHA512:
-  metadata.gz: 94e77ff29daca018126fdc63b4e8a4445216ad52dafd895e5acd63bc65aa230350c6474254163fb11a9929cdfa900948d83c9dd4cef5d071b825e073abdd050b
-  data.tar.gz: 432b7ecb3b58cc6ef27bcb7d2c040dfda60cf0b3793e8a1d184b6602eac0856d83a369401251d7387f563253cfee877da96da8b88d7a5331d2bde4590bb996d2
+  metadata.gz: 8c3f397191c599b514a94fb3cd9c287a7badf6aeb62651e105a9b6740d96161ba5b8a17bc3f0055adfb877af0869f4118a4abab49abd859ca4e0d6affa7ea86f
+  data.tar.gz: 3aaeebda86f58edea05c94aa4f5ecbe3078ceef449c78fca7edbacaea6b591e1a4a18d67ea422e351123763284ac0ca94d4e51b158312f95e65eaf29afbf90cb

data/CHANGELOG.md

@@ -0,0 +1,85 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+## [0.3.0] - 2025-11-03
+
+### Added
+* Add SCSS/SASS Guide Documentation ([`77c9e2e`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/77c9e2e6a83188382e5c26033955438438d78beb))
+
+* Add _config.yml Guide Documentation and a full sample file ([`a08d4f5`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/a08d4f5675ca902e8a2b5e23a2f3d2b4b5e02902))
+
+* Add _layouts Guide Documentation ([`94830fe`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/94830fe4ac59667cc1514e45e5fc82af18440b5e))
+
+* Add _includes Guide Documentation ([`b586225`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/b5862259e2f3d955b71417ec9506b1a778c5440a))
+
+* Add Data Structure Documentation ([`077184c`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/077184ccd038441c0bfbd7644228d6efd743e75f))
+
+* Add comments to the dynamic data loader ar&en layouts ([`4efe0a4`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/4efe0a453f2ca767d55f601ca7b02c7372357e74))
+
+
+### Changed
+* Add WARP.md file ([`ff38359`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/ff383590d783e17af1432d257f4f325b101dc574))
+
+* Upload changelog file ([`d4ba77b`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/d4ba77b2f17a1d53f9e7e93db57569840fd0e03f))
+
+* Create git-cliff config file ([`ad72acd`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/ad72acd74d03bc42c8380ff7d0a5362de66fff81))
+
+
+### Fixed
+* Update dynamic data loader to use specific active_resume_path variables for Arabic and English ([`f4852cc`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/f4852cc01410deb358df978041a980a6e671ed00))
+
+## [0.2.0] - 2025-11-02
+
+### Added
+* Add runtime dependency plugins ([`7b21773`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/7b2177300f683939b9cb045fc3403db962d56193))
+
+
+### Changed
+* Update to version 0.2.0 ([`bd1ab3a`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/bd1ab3af75041c5b17109bd3c20fd3c971266dd8))
+
+
+### Fixed
+* Correct theme asset paths for gem ([`189fc46`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/189fc4693cdce7c2195909405bf97e1647d1aad8))
+
+* Fix spec.files ([`92003e7`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/92003e7865100961b60376bd63daa1b8705e4e81))
+
+## [0.1.1] - 2025-11-02
+
+### Added
+* Add assets folder ([`41fbb34`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/41fbb34708d28da99e1730cffdd485b3e6a1e1af))
+
+* Add _sass folder ([`15ddfe1`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/15ddfe1245dbc855eebd481d1529bfad28bf6916))
+
+* Add _layouts folder ([`0d2bd65`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/0d2bd65458760b7787a7fcca16fb9b5d805c8857))
+
+* Add _includes folder ([`8c87411`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/8c87411b64a9a66870a1e71f13e8d08ed3a29680))
+
+* Add CODE_OF_CONDUCT.MD ([`abea110`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/abea11088296b04f3f7ccbd845f7268c84b3e9cf))
+
+* Add .whitesource configuration file ([`1958aa0`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/1958aa04a25ce3aa8c60ddda3a5e9eb9fe43d79c))
+
+
+### Changed
+* Update to version 0.1.1 ([`07c61a7`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/07c61a70da763e2258020c41c3d2198eb89dc1f7))
+
+* Update gemspec with metadata ([`2c1f1a7`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/2c1f1a7138314e6481edaa96391640d35349515e))
+
+* Merge pull request #1 from kmutahar/whitesource/configure ([`058663b`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/058663b282b2b839cb244a80dc4a1ca0cbdaedab))
+
+## [0.1.0] - 2025-11-02
+
+### Changed
+* Update gemspec with correct email, summary, and homepage ([`39e7b88`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/39e7b8872c1092c52261c9524245ebf73804a99e))
+
+* Update LICENSE file with orginal author copyright ([`ff03b02`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/ff03b02b285c14ac393b0ee71596961fb760c5b9))
+
+* Initial commit (New Theme Template) ([`00af662`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/00af6628dfec7aefe0ef7d7083bf98c9713a5ffd))
+
+[0.3.0]: https://github.com/kmutahar/bilingual-jekyll-resume-theme/compare/v0.2.0...v0.3.0
+[0.2.0]: https://github.com/kmutahar/bilingual-jekyll-resume-theme/compare/v0.1.1...v0.2.0
+[0.1.1]: https://github.com/kmutahar/bilingual-jekyll-resume-theme/compare/v0.1.0...v0.1.1
+
+<!-- generated by git-cliff -->

data/CODE_OF_CONDUCT.MD

@@ -0,0 +1,92 @@
+
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **please open an issue at https://github.com/kmutahar/bilingual-jekyll-resume-theme/issues/new**
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+****
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+

data/_layouts/resume-ar.html

@@ -1,16 +1,147 @@
+{% comment %}
+=============================================================================
+DYNAMIC DATA LOADER FOR JEKYLL
+=============================================================================
+This entire block dynamically sets the 'resume_data' variable.
+Its goal is to find the correct data folder (or "data object") based on the 
+'active_resume_path_ar' variable set in your _config.yml file.
+
+The rest of the template can then use 'resume_data' 
+(e.g., 'resume_data.experience', 'resume_data.links') without 
+caring *where* that data actually came from.
+{% endcomment %}
+
+{% comment %}
+    STEP 1: Get the path string from the config file.
+    'site.active_resume_path_ar' reads the value from _config.yml.
+    We assign it to a new, shorter variable called 'data_path_string'.
+{% endcomment %}
 {% assign data_path_string = site.active_resume_path_ar %}
 
+{% comment %}
+    STEP 2: Check if the path is empty.
+    This 'if' statement checks if 'data_path_string' is either an
+    empty string ("") or 'nil' (which means it wasn't defined at all).
+    This is our "default" or "fallback" case for files in the root _data/ folder.
+{% endcomment %}
 {% if data_path_string == "" or data_path_string == nil %}
+    
+    {% comment %}
+        FALLBACK CASE: The path was empty.
+        We assign 'resume_data' to be the top-level 'site.data' object.
+        This means the rest of the template will look for files directly in 
+        the _data/ folder (e.g., 'site.data.experience' from _data/experience.yml).
+    {% endcomment %}
     {% assign resume_data = site.data %}
-{% else %}
+    
+    {% else %}
+    
+    {% comment %}
+        ACTIVE CASE: A path was provided (e.g., "ar" or "ProjectManager").
+        Now we need to "drill down" to find the correct data object.
+    {% endcomment %}
+    
+    {% comment %}
+        STEP 3: Split the path string into parts.
+        The 'split: "."' filter takes the string and breaks it into an
+        array (a list) using the dot '.' as the separator.
+        If data_path_string = "2025-06.20250621-PM"
+        Then path_parts = ["2025-06", "20250621-PM"]
+        If data_path_string = "ar"
+        Then path_parts = ["ar"]
+    {% endcomment %}
     {% assign path_parts = data_path_string | split: '.' %}
+    
+    {% comment %}
+        STEP 4: Set the starting point for our loop.
+        We create a temporary variable 'data_object' and set it to the 
+        very top of the data tree, 'site.data'. This is the object
+        we will "drill down" into.
+    {% endcomment %}
     {% assign data_object = site.data %}
+    
+    {% comment %}
+        STEP 5: The Loop.
+        This 'for' loop iterates over the 'path_parts' array we created.
+        For each 'part' in the list, it will run the code inside.
+    {% endcomment %}
     {% for part in path_parts %}
+        
+        {% comment %}
+            THE CORE LOGIC: Drilling Down with Bracket Notation.
+            
+            This is the most important line. It re-assigns 'data_object'
+            to be a *child* of itself, using the current 'part' as the key.
+            
+            It uses BRACKET NOTATION: data_object[part]
+            
+            WHY BRACKET NOTATION?
+            In Liquid, you can access data in two ways:
+            1. Dot Notation:    site.data.ar
+            2. Bracket Notation: site.data['ar']
+            
+            Dot notation fails if the key starts with a number (like "2025-06").
+            Liquid sees 'site.data.2025-06' and gets confused.
+            
+            Bracket notation *always* works because it treats the key as a
+            string, no matter what it contains. 'site.data['2025-06']' is valid.
+            
+            Since our 'part' variable holds a string, 'data_object[part]' is
+            the perfect way to safely access the next level down.
+            
+            HOW THE LOOP WORKS (Example: Your path is _data/2025-06/20250621-PM/)
+            
+            - Your config string is: data_path_string = "2025-06.20250621-PM"
+            - The split array is:   path_parts = ["2025-06", "20250621-PM"]
+            
+            - Before loop: data_object = site.data
+            
+            - Loop 1: 
+            - part = "2025-06"
+            - code runs: data_object = data_object["2025-06"]
+            - result:    data_object = site.data['2025-06']
+            
+            - Loop 2:
+            - part = "20250621-PM"
+            - code runs: data_object = data_object["20250621-PM"]
+            - result:    data_object = site.data['2025-06']['20250621-PM']
+            
+            - Loop ends.
+        {% endcomment %}
         {% assign data_object = data_object[part] %}
+    
     {% endfor %}
+    
+    {% comment %}
+        STEP 6: Final Assignment.
+        
+        After the loop has finished, 'data_object' holds our target folder 
+        (e.g., site.data.ar or site.data['2025-06']['20250621-PM']).
+        
+        We now assign this final object to the 'resume_data' variable that
+        the rest of the template will use.
+    {% endcomment %}
     {% assign resume_data = data_object %}
+
 {% endif %}
 
+{% comment %}
+=============================================================================
+DYNAMIC DATA LOADER ENDS
+=============================================================================
+
+From this point on, you can just use 'resume_data' variable.
+
+- If config was empty (""):
+resume_data.experience == site.data.experience
+
+- If config was "ar":
+resume_data.experience == site.data.ar.experience
+
+- If config was "2025-06.20250621-PM":
+resume_data.experience == site.data['2025-06']['20250621-PM'].experience
+{% endcomment %}
+
 <!DOCTYPE html>
 <html lang="ar" dir="rtl">
     <!-- هذه الصفحة تم تحديثها آخر مرة في {{ "now" | date: "%Y-%m-%d %H:%M:%S" }}Z -->

data/_layouts/resume-en.html

@@ -1,16 +1,147 @@
+{% comment %}
+=============================================================================
+DYNAMIC DATA LOADER FOR JEKYLL
+=============================================================================
+This entire block dynamically sets the 'resume_data' variable.
+Its goal is to find the correct data folder (or "data object") based on the 
+'active_resume_path_en' variable set in your _config.yml file.
+
+The rest of the template can then use 'resume_data' 
+(e.g., 'resume_data.experience', 'resume_data.links') without 
+caring *where* that data actually came from.
+{% endcomment %}
+
+{% comment %}
+    STEP 1: Get the path string from the config file.
+    'site.active_resume_path_en' reads the value from _config.yml.
+    We assign it to a new, shorter variable called 'data_path_string'.
+{% endcomment %}
 {% assign data_path_string = site.active_resume_path_en %}
 
+{% comment %}
+    STEP 2: Check if the path is empty.
+    This 'if' statement checks if 'data_path_string' is either an
+    empty string ("") or 'nil' (which means it wasn't defined at all).
+    This is our "default" or "fallback" case for files in the root _data/ folder.
+{% endcomment %}
 {% if data_path_string == "" or data_path_string == nil %}
+    
+    {% comment %}
+        FALLBACK CASE: The path was empty.
+        We assign 'resume_data' to be the top-level 'site.data' object.
+        This means the rest of the template will look for files directly in 
+        the _data/ folder (e.g., 'site.data.experience' from _data/experience.yml).
+    {% endcomment %}
     {% assign resume_data = site.data %}
-{% else %}
+    
+    {% else %}
+    
+    {% comment %}
+        ACTIVE CASE: A path was provided (e.g., "en" or "ProjectManager").
+        Now we need to "drill down" to find the correct data object.
+    {% endcomment %}
+    
+    {% comment %}
+        STEP 3: Split the path string into parts.
+        The 'split: "."' filter takes the string and breaks it into an
+        array (a list) using the dot '.' as the separator.
+        If data_path_string = "2025-06.20250621-PM"
+        Then path_parts = ["2025-06", "20250621-PM"]
+        If data_path_string = "en"
+        Then path_parts = ["en"]
+    {% endcomment %}
     {% assign path_parts = data_path_string | split: '.' %}
+    
+    {% comment %}
+        STEP 4: Set the starting point for our loop.
+        We create a temporary variable 'data_object' and set it to the 
+        very top of the data tree, 'site.data'. This is the object
+        we will "drill down" into.
+    {% endcomment %}
     {% assign data_object = site.data %}
+    
+    {% comment %}
+        STEP 5: The Loop.
+        This 'for' loop iterates over the 'path_parts' array we created.
+        For each 'part' in the list, it will run the code inside.
+    {% endcomment %}
     {% for part in path_parts %}
+        
+        {% comment %}
+            THE CORE LOGIC: Drilling Down with Bracket Notation.
+            
+            This is the most important line. It re-assigns 'data_object'
+            to be a *child* of itself, using the current 'part' as the key.
+            
+            It uses BRACKET NOTATION: data_object[part]
+            
+            WHY BRACKET NOTATION?
+            In Liquid, you can access data in two ways:
+            1. Dot Notation:    site.data.en
+            2. Bracket Notation: site.data['en']
+            
+            Dot notation fails if the key starts with a number (like "2025-06").
+            Liquid sees 'site.data.2025-06' and gets confused.
+            
+            Bracket notation *always* works because it treats the key as a
+            string, no matter what it contains. 'site.data['2025-06']' is valid.
+            
+            Since our 'part' variable holds a string, 'data_object[part]' is
+            the perfect way to safely access the next level down.
+            
+            HOW THE LOOP WORKS (Example: Your path is _data/2025-06/20250621-PM/)
+            
+            - Your config string is: data_path_string = "2025-06.20250621-PM"
+            - The split array is:   path_parts = ["2025-06", "20250621-PM"]
+            
+            - Before loop: data_object = site.data
+            
+            - Loop 1: 
+            - part = "2025-06"
+            - code runs: data_object = data_object["2025-06"]
+            - result:    data_object = site.data['2025-06']
+            
+            - Loop 2:
+            - part = "20250621-PM"
+            - code runs: data_object = data_object["20250621-PM"]
+            - result:    data_object = site.data['2025-06']['20250621-PM']
+            
+            - Loop ends.
+        {% endcomment %}
         {% assign data_object = data_object[part] %}
+    
     {% endfor %}
+    
+    {% comment %}
+        STEP 6: Final Assignment.
+        
+        After the loop has finished, 'data_object' holds our target folder 
+        (e.g., site.data.en or site.data['2025-06']['20250621-PM']).
+        
+        We now assign this final object to the 'resume_data' variable that
+        the rest of the template will use.
+    {% endcomment %}
     {% assign resume_data = data_object %}
+
 {% endif %}
 
+{% comment %}
+=============================================================================
+DYNAMIC DATA LOADER ENDS
+=============================================================================
+
+From this point on, you can just use 'resume_data' variable.
+
+- If config was empty (""):
+resume_data.experience == site.data.experience
+
+- If config was "en":
+resume_data.experience == site.data.en.experience
+
+- If config was "2025-06.20250621-PM":
+resume_data.experience == site.data['2025-06']['20250621-PM'].experience
+{% endcomment %}
+
 <!DOCTYPE html>
 <html lang="en">
     <!-- This page was last updated on {{ "now" | date: "%Y-%m-%d %H:%M:%S" }}Z -->

data/assets/css/cv-ar.scss

@@ -3,17 +3,17 @@
 
 // "Reset" styles and SCSS reusable components
 // Arabic CV entrypoint: load base styles then RTL overrides
-@use "../../_sass/normalize";
-@use "../../_sass/mixins";
-@use "../../_sass/variables";
+@use "normalize";
+@use "mixins";
+@use "variables";
 
 // Generic site base & layout styles
-@use "../../_sass/base";
-@use "../../_sass/layout";
+@use "base";
+@use "layout";
 
 // Layouts
-@use "../../_sass/resume";
-@use "../../_sass/all-pages";
+@use "resume";
+@use "all-pages";
 
 // RTL-specific overrides and Arabic typography
-@use "../../_sass/resume-rtl";
+@use "resume-rtl";

data/assets/css/cv.scss

@@ -2,15 +2,15 @@
 ---
 
 // "Reset" styles and SCSS reusable components
-@use "../../_sass/normalize";
-@use "../../_sass/mixins";
-@use "../../_sass/variables";
+@use "normalize";
+@use "mixins";
+@use "variables";
 
 // Generic site base & layout styles
-@use "../../_sass/base";
-@use "../../_sass/layout";
+@use "base";
+@use "layout";
 
 // Layouts
-@use "../../_sass/resume";
+@use "resume";
 
-@use "../../_sass/all-pages";
+@use "all-pages";

data/assets/css/main.scss

@@ -1,6 +1,6 @@
 --- 
 --- 
 // "Reset" styles and SCSS reusable components
-@use "../../_sass/normalize";
-@use "../../_sass/profile";
-@use "../../_sass/all-pages";
+@use "normalize";
+@use "profile";
+@use "all-pages";