kontent-jekyll 0.11.2 → 0.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 223fb2ce1eee60fc1038e8040676d944185960dadbbf723954f3a2abb341f281
-  data.tar.gz: 55dfa5c312f2fd48471a66c9388a91be743f1060c80a1a2dcf4904ce2d60ce2d
+  metadata.gz: 2348ee20002939b60bfaa7c4bd6ce7da395747ee6024e2ad9249816d787ee26a
+  data.tar.gz: aeca8c81e53d30e0c9d6c881a6f5e1b25e29a711443d0f8d7fdb639c422ffdc9
 SHA512:
-  metadata.gz: f261c178131eaf68a018f147d3ac2d1db2a2369b4c860666b426565856348fd169b24478f891978dc87cd929e3c1acce1317378548add7945807749423cdac3f
-  data.tar.gz: 811bf655837934e04d6ebcca18be5333891a3d99f2404429b41a3dfb4e152f8b81b0a2dd413ecf090a2f660db0fdd5d5730c24ccfe2fd717e55814a70d3fb735
+  metadata.gz: 1239aa5f4408d69fe650ff6251410558be3409adcef832513f7f6617e5f73a9a1c924aebe27909ed9082a69ccc3266f258e451d08ccbdff37425b6e2d21fbab8
+  data.tar.gz: 80b22d1d6955a0af7c999cd6c9e3244f39810ac25bdea0918d2cc3f0134545f05d3a075900f8218e137d4966e60b92a3511a807e009113a0d58f50919e07d7a0

data/.github/CODEOWNERS

@@ -0,0 +1,4 @@
+# Users referenced in this file will automatically be requested as reviewers for PRs that modify the given paths.
+# See https://help.github.com/articles/about-code-owners/
+
+* @RadoslavK

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+### Brief bug description
+
+What went wrong?
+
+### Repro steps
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+### Expected behavior
+
+What the correct behavior is?
+
+### Test environment
+
+ - Platform/OS: [e.g. .NET Core 2.1, iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+### Additional context
+
+Add any other context about the problem here.
+
+### Screenshots
+
+Add links to screenshots, if possible.

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+### Motivation
+
+Why is this feature required? What problems does it solve?
+
+### Proposed solution
+
+An ideal solution for the above problems.
+
+### Additional context
+
+Add any other context, screenshots, or reference links about the feature request here.

data/.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,13 @@
+---
+name: Question
+about: Ask a question
+
+---
+
+### Question
+
+What do you want to ask?
+
+### Reference
+
+* URL

data/.github/ISSUE_TEMPLATE/spike.md

@@ -0,0 +1,17 @@
+---
+name: Spike
+about: Suggest an analysis of a problem
+
+---
+
+### Expected result
+
+What do we want to explore and why? Which questions do we want to answer with this spike?
+
+### Additional context
+
+Add any other context or guidelines here.
+
+### Resources
+
+* URL

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+### Motivation
+
+Which issue does this fix? Fixes #`issue number`
+
+If no issue exists, what is the fix or new feature? Were there any reasons to fix/implement things that are not obvious?
+
+### Checklist
+
+- [ ] Code follows coding conventions held in this repo
+- [ ] Automated tests have been added
+- [ ] Tests are passing
+- [ ] Docs have been updated (if applicable)
+- [ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults
+
+### How to test
+
+If manual testing is required, what are the steps?

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,48 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at DevelopersCommunity@kentico.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/
+
+![Analytics](https://kentico-ga-beacon.azurewebsites.net/api/UA-69014260-4/Kentico/Home/master/CODE_OF_CONDUCT.md?pixel)

data/CONTRIBUTING.md

@@ -0,0 +1,72 @@
+# Ways to contribute 
+<img align="right" width="100" height="100" src="https://i.imgur.com/PYTV0jP.png">
+
+There are many different ways in which you can contribute. One of the easiest ways is simply to use our software and provide us with your feedback through the right channel. You can also help us improve the open-source projects by submitting pull requests with code and documentation changes.
+
+## Where to get support
+Please note that **level of provided support is always determined by the [LICENSE](LICENSE.md)** of a given open-source project. Also, always make sure you use the **[latest version](../../releases)** of any given OS project. We can't provide any help for older versions. We don't want to make things complicated so we try to take the same approach in all our repositories. 
+
+### I found a bug in a Kentico's open-source project
+<img align="right" width="100" height="100" src="https://i.imgur.com/TYIQdpv.png">
+
+Sorry to hear that. Just log a new [GitHub issue](../../issues) and someone will take a look at it. Remember, the more information you provide, the easier it will be to fix the issue. If you feel like it, you can also fix the bug on your own and submit a new pull request.
+
+### I need help with using the projects and/or coding
+<img align="right" width="100" height="100" src="https://cdn.sstatic.net/Sites/stackoverflow/company/img/logos/so/so-icon.svg">
+
+To get help with coding and structuring your projects, use [StackOverflow](https://stackoverflow.com/) to ask questions with one of the following tags:
+- [`kentico-kontent`](https://stackoverflow.com/questions/tagged/kentico-kontent)
+- [`kentico`](https://stackoverflow.com/questions/tagged/kentico)
+
+Our team members and the community monitor these channels on a regular basis.
+
+### I want to report a security bug
+<img align="right" width="100" height="100" src="https://i.imgur.com/z82nnJB.png">
+
+Security issues and bugs should be reported privately, via email, to the Kentico Developer Community Team developerscommunity@kentico.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
+
+
+### I have an idea for a new feature (or feedback on existing functionality)
+<img align="right" width="100" height="100" src="https://i.imgur.com/rUFkyPy.png">
+
+Everybody loves new features! You can submit a new [feature request](../../issues) or you can code it on your own and [send us a pull request](#submitting-pull-requests). In either case, don't forget to mention what's the use case and what's the expected output.
+
+
+## Submitting pull requests
+<img align="right" width="100" height="100" src="https://i.imgur.com/aSeiliy.png">
+
+Unless you're fixing a typo, it's usually a good idea to discuss the feature before you submit a pull request with code changes, so let's start with submitting a new [GitHub issue](../../issues) and discussing the whether it fits the vision of a given project.
+You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](https://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that all code submissions will be rigorously reviewed and tested by the Kentico Maintainers teams, and only those that meet an high bar for both quality and design/roadmap appropriateness will be merged into the source.
+
+
+### Example - process of contribution
+If not stated otherwise, we use [feature branch workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow). 
+
+To start with coding, fork the repository you want to contribute to, create a new branch, and start coding. Once the functionality is [done](#Definition-of-Done), you can submit a [pull request](https://help.github.com/articles/about-pull-requests/). 
+
+### Definition of Done
+<img align="right" width="100" height="100" src="https://i.imgur.com/g82Ohdv.png">
+
+- New/fixed code is covered with tests
+- CI can build the code
+- All tests are pass
+- New version number follows [semantic versioning](https://semver.org/)
+- Coding style (spaces, indentation) is in line with the rest of the code in a given repository
+- Documentation is updated (e.g. code examples in README, Wiki pages, etc.)
+- All `public` members are documented (using XML doc, phpdoc, etc.)
+- Code doesn't contain any secrets (private keys, etc.)
+- Commit messages are clear. Please read these articles: [Writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages), [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), [On commit messages](https://who-t.blogspot.com/2009/12/on-commit-messages.html)
+
+
+### Feedback
+<img align="right" width="100" height="100" src="https://i.imgur.com/ZQfNzJJ.png">
+
+Your pull request will now go through extensive checks by the subject matter experts on our team. Please be patient. Update your pull request according to feedback until it is approved by one of the Kentico maintainers. After that, one of our team members may adjust the branch you merge into based on the expected release schedule.
+
+
+## Code of Conduct
+<img align="right" width="100" height="100" src="https://i.imgur.com/cObdKQy.png">
+
+The Kentico team is committed to fostering a welcoming community, therefore this project has adopted the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). If you have any additional questions or comments, you can contact us directly at developerscommunity@kentico.com.
+
+![Analytics](https://kentico-ga-beacon.azurewebsites.net/api/UA-69014260-4/Kentico/Home/master/CONTRIBUTING.md?pixel)

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    kontent-jekyll (0.11.2)
+    kontent-jekyll (0.12.0)
       kontent-delivery-sdk-ruby (~> 2.0)
 
 GEM

data/README.md

@@ -1,3 +1,8 @@
+[![Build Status](https://api.travis-ci.com/RadoslavK/kontent-jekyll.svg?branch=master)](https://travis-ci.com/RadoslavK/kontent-jekyll)
+[![Join the chat at https://kentico-community.slack.com](https://img.shields.io/badge/join-slack-E6186D.svg)](https://kentico-community.slack.com)
+[![Stack Overflow](https://img.shields.io/badge/Stack%20Overflow-ASK%20NOW-FE7A16.svg?logo=stackoverflow&logoColor=white)](https://stackoverflow.com/tags/kentico-kontent)
+ [![Version](https://img.shields.io/gem/v/kontent-jekyll.svg?style=flat)](https://rubygems.org/gems/kontent-jekyll)
+
 # Jekyll Kentico
 
 Jekyll Kentico is utilizing Kentico Kontent, headless CMS, as a content repository and integrates it with Jekyll static site generator. You can generate posts, pages, collections and data items.
@@ -39,3 +44,17 @@ kentico:
   posts:                                                      
     type: blog_post                                           
 ```
+
+## Feedback & Contributing
+
+Check out the [contributing](https://github.com/RadoslavK/kontent-jekyll/blob/master/CONTRIBUTING.md) page to see the best places to file issues, start discussions, and begin contributing.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Kontent-Jekyll project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/RadoslavK/kontent-jekyll/blob/master/CODE_OF_CONDUCT.md).
+
+![Analytics](https://kentico-ga-beacon.azurewebsites.net/api/UA-69014260-4/RadoslavK/kontent-jekyll?pixel)

data/lib/kontent-jekyll/generator.rb

@@ -11,6 +11,7 @@ module Kentico
 
     class ContentGenerator < Jekyll::Generator
       include SiteProcessing
+
       DEFAULT_LANGUAGE = nil
 
       safe true

data/lib/kontent-jekyll/models/kentico_page.rb

@@ -0,0 +1,35 @@
+module Kentico
+  module Kontent
+    module Models
+      ##
+      # Custom page that mimics the behavior of a regular Jekyll::Page
+      # without trying to locate the file on the filesystem.
+
+      class KenticoPage < Jekyll::Page
+        def initialize(site, page_info)
+          @site = site
+          @base = site.source
+          @dir = page_info.collection && "_#{page_info.collection}" || ''
+          @name = page_info.filename
+          @path = if site.in_theme_dir(@base) == @base
+                    site.in_theme_dir(@base, @dir, @name)
+                  else
+                    site.in_source_dir(@base, @dir, @name)
+                  end
+
+          self.process(@name)
+
+          self.data = page_info.front_matter
+          self.content = page_info.content
+
+          data.default_proc = proc do |_, key|
+            site.frontmatter_defaults.find(File.join(@dir, @name), type, key)
+          end
+
+          ::Jekyll::Hooks.trigger :pages, :post_init, self
+        end
+      end
+    end
+  end
+end
+

data/lib/kontent-jekyll/site_processing/site_processor.rb

@@ -2,6 +2,8 @@ require 'date'
 
 require 'kontent-jekyll/constants/page_type'
 
+require 'kontent-jekyll/models/kentico_page'
+
 require 'kontent-jekyll/resolvers/front_matter_resolver'
 require 'kontent-jekyll/resolvers/content_resolver'
 require 'kontent-jekyll/resolvers/data_resolver'
@@ -19,6 +21,7 @@ module Kentico
         include Constants
         include Resolvers
         include Utils
+        include Models
 
         ##
         # These collections have specific purposes in the original Jekyll generation will be omitted.
@@ -59,7 +62,7 @@ module Kentico
             are_pages_from_collection = collection_name && !collection_name.empty? && !RESERVED_COLLECTIONS.include?(collection_name)
 
             unless are_pages_from_collection
-              @site.pages += pages_data.map { |page_data| create_kentico_page(@site, page_data) }
+              @site.pages += pages_data.map { |page_data| KenticoPage.new(@site, page_data) }
               next
             end
 
@@ -179,45 +182,6 @@ module Kentico
 
         private
 
-        ##
-        # Creates a Jekyll::Page.
-
-        def create_kentico_page(site, page_info)
-          page = Jekyll::Page.allocate
-
-          ## A hack to create a Jekyll::Page with custom constructor without overriding the class
-          # because jekyll-redirect-from can work only with Jekyll::Page instances.
-          # Once this PR https://github.com/jekyll/jekyll-redirect-from/pull/204 is merged and released
-          # we can create a subclass of the Page and simplify the code.
-
-          page.define_singleton_method(:initialize) do
-            @site = site
-            @base = site.source
-            @dir = ''
-            @name = page_info.filename
-            @path = if site.in_theme_dir(@base) == @base
-                      site.in_theme_dir(@base, @dir, @name)
-                    else
-                      site.in_source_dir(@base, @dir, @name)
-                    end
-
-            self.process(@name)
-
-            self.data = page_info.front_matter
-            self.content = page_info.content
-
-            data.default_proc = proc do |_, key|
-              site.frontmatter_defaults.find(File.join(@dir, @name), type, key)
-            end
-
-            Jekyll::Hooks.trigger :pages, :post_init, self
-
-            self
-          end
-
-          page.initialize
-        end
-
         ##
         # Creates a Jekyll::Document. Used for collections.
 

data/lib/kontent-jekyll/version.rb

@@ -1,5 +1,5 @@
 module Kentico
   module Kontent
-    VERSION = '0.11.2'
+    VERSION = '0.12.0'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: kontent-jekyll
 version: !ruby/object:Gem::Version
-  version: 0.11.2
+  version: 0.12.0
 platform: ruby
 authors:
 - RadoslavK
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-01-10 00:00:00.000000000 Z
+date: 2020-01-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -117,9 +117,17 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".github/CODEOWNERS"
+- ".github/ISSUE_TEMPLATE/bug_report.md"
+- ".github/ISSUE_TEMPLATE/feature_request.md"
+- ".github/ISSUE_TEMPLATE/question.md"
+- ".github/ISSUE_TEMPLATE/spike.md"
+- ".github/PULL_REQUEST_TEMPLATE.md"
 - ".gitignore"
 - ".rspec"
 - ".travis.yml"
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
 - Gemfile
 - Gemfile.lock
 - LICENSE
@@ -134,6 +142,7 @@ files:
 - lib/kontent-jekyll/constants/page_type.rb
 - lib/kontent-jekyll/gem_name.rb
 - lib/kontent-jekyll/generator.rb
+- lib/kontent-jekyll/models/kentico_page.rb
 - lib/kontent-jekyll/resolvers/content_link_resolver.rb
 - lib/kontent-jekyll/resolvers/content_resolver.rb
 - lib/kontent-jekyll/resolvers/data_resolver.rb