bilingual-jekyll-resume-theme 0.2.0 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b9bec0f201360e9a1545125d8d705157d598ede774277a40010482551c7bc573
-  data.tar.gz: 10e6920fa4dd1625de5f29d40789e7af2623ffb99d7b47009ce108bc9c4ddde9
+  metadata.gz: 82f9ca0be84e6576a493181eb0efe5878302db7196f3843f8468d2048a975995
+  data.tar.gz: 9b477efb312e3a1e6d71c3ac8e6ab4e95c04f3a2053ec7042412fc659b6148df
 SHA512:
-  metadata.gz: d4d5a66b1e531660b2f99e842fe74eb4cec711263ab53a9dee5ae4dea7813ae9c261765b801e130af16900123c01d66e0e155d3cd518b1567d5b75297773b2fd
-  data.tar.gz: '09d2aef20d74e2ee4473c39e0323ab9ac1a4120d8f8baf7f877ba21dce7a9939e7172454323df0d09aebd348219291566f52af6618bb3ad66779ad03bab429f9'
+  metadata.gz: 4cb13f53c7a175d3e353ad4bf169786d314c79c838b0aafafba6d57fec578b82fecf5171ae4cbac95f9c2ea2080146e7ae74d0b8067e4c834932af60c4172325
+  data.tar.gz: 14a87ccc8f9ed64072ac5b210ed74e0047753a274987e2fd52c527cb728c7bb2f6e3aab22a091299051b8bdefbd8387966b524d0f61302ef835516fee4f9b19f

data/CHANGELOG.md

@@ -0,0 +1,91 @@
+# 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.1] - 2025-11-03
+
+### Added
+* Add arabic name to resume and config file ([`c6b224d`](https://github.com/kmutahar/bilingual-jekyll-resume-theme/commit/c6b224d13f8602b8b6f30d0d630817dc6fa55e3a))
+
+## [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.1]: https://github.com/kmutahar/bilingual-jekyll-resume-theme/compare/v0.3.0...v0.3.1
+[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/_includes/resume-section-ar.html

@@ -200,7 +200,7 @@
         {% for project in resume_data.projects %}
             {% if project.active == true %}
                 <div class="resume-item" itemscope itemtype="http://schema.org/CreativeWork">
-                    <meta itemprop="creator" content="{{ site.name.first }} {{ site.name.middle }} {{ site.name.last }}" itemtype="http://schema.org/Person" />
+                    <meta itemprop="creator" content="{{ site.name_ar.first }} {{ site.name_ar.middle }} {{ site.name_ar.last }}" itemtype="http://schema.org/Person" />
                     <h3 class="resume-item-title" itemprop="name" style="display: inline-block;">
                         {% if project.url %}
                             <a href="{{ project.url }}" target="_blank" rel="noopener nofollow noreferrer" itemprop="url">{{ project.project }}</a>

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 -->
@@ -42,7 +173,7 @@
 
                 <!-- Your name is defined in the _config.yml file -->
                 <h1 class="header-name" itemprop="name">
-                    {{ site.name.first }} {{ site.name.middle }} {{ site.name.last }}
+                    {{ site.name_ar.first }} {{ site.name_ar.middle }} {{ site.name_ar.last }}
                 </h1>
 
                 {% if site.display_header_contact_info == true %}

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 -->