Merge branch 'master' into jsartoolkitNFT-example

Author: kalwalt

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

Gemfile

@@ -11,7 +11,7 @@ gem "jekyll", "~> 3.9.0"
 # This is the default theme for new Jekyll sites. You may change this to anything you like.
 gem "bulma-clean-theme"
 group :jekyll_plugins do
-  gem 'jekyll-pwa-plugin'
+  gem "jekyll-pwa-plugin", "2.2.3"
 end
 # If you want to use GitHub Pages, remove the "gem "jekyll"" above and
 # uncomment the line below. To upgrade, run `bundle update github-pages`.

LICENSE

@@ -7,4 +7,4 @@
 
   gtag('config', 'G-S3HVPJX68V');
 </script>
-<link rel="manifest" href="manifest.json">
+<link rel="manifest" href="/manifest.json">

_includes/head-scripts.html

@@ -0,0 +1,34 @@
+---
+layout: post
+slug: New WebARKit Netlify Open Source team
+title: WebARKit has obtained the Netlify Open Source Team plan
+subtitle: Latest news around WebARKit,Jsartoolkit5 and ARnft development
+description: We obtained a nice gitft for Christhmas, the upgrade to the
+  OpenSource Team plan for our Netlify account We added a new jsartoolkit5
+  example and we are discussing the future development of ARnft and WebARKit.
+author: Walter Perdan
+date: 2020-12-26 17:12
+lang: en
+seo:
+  datePublished: 2020-12-26
+  type: NewsArticle
+  author: Walter Perdan
+image: /resources/webarkit-logo-social.jpg
+intro_paragraph: WebARKit is evolving to a more robust Open Source community,
+  read the article for more...
+---
+# We are now a Netlify Open Source Team!
+
+![Webarkit Netlify Open Source Team](/assets/images/uploads/webar_kit_netlify_open_source_team.jpg "Screenshot fo the board for the WebARKit Netlify Open Source Team.")
+
+That is the most important news, our request was accepted some days before Christhmas, what better gift! [Netlify](https://www.netlify.com/) is a well known web service. Another important news: we have also our **OpenCollective** profile: [WebArKit](https://opencollective.com/webarkit); we have just started this journey, so wait until we have finish the setup.
+
+A lot of discussions and sharing of ideas about the future of **WebARKit** and **ARnft**, for sure in the next weeks , month we will release a new improved version of ARnft and probably the first WebAR Kit version. We don't set up a milestone or a releasing date, but we are working on this. 
+
+Recently i have also relased a new ARnft version with some nice features see this [PR](https://github.com/webarkit/ARnft/pull/154), this is about Threejs rendering system. I added some important event listeners that let you built more advanced stuff. I also removed the Ofscreencanvas that was causing an issue. 
+
+About Arnft: our idea is to make ARnft more agnostic in rispect to every rendering engine. Our plan is to evolve it to a modular system in which the developer may choose his preferred render engine (Three.js, Babylonjs....) without any constrictions. For doing this we will switch to a typed script version of the library, that will let us more freedom and will add more flexibility. 
+
+If you want partecipate to the discussion, join us on the discussions board see this topic: [The Future of ARnft and WebARKit](https://github.com/webarkit/ARnft/discussions/156) 
+
+More to come...

_posts/2020-12-26-new-webarkit-netlify-open-source-team.md

@@ -0,0 +1,37 @@
+---
+layout: post
+slug: "jsartoolkitnft typescript version "
+title: The new jsartoolkitNFT with Typescript support
+subtitle: New feature added for a better development experience
+description: jsartoolkitNFT was converted to the typesrcipt language, in this
+  flash article we illustrate this feature and what's the next plans.
+author: Walter Perdan
+date: 2021-04-07 12:04
+lang: en
+seo:
+  datePublished: 2021-04-07
+  type: NewsArticle
+  author: Walter Perdan
+image: https://github.com/webarkit/ARnft/blob/master/examples/Data/arNFT-logo.gif
+intro_paragraph: We developed a new jsartolkitNFT for a better development
+  phase, easy integration and our upcoming new ARnft library.
+---
+We started to develop a **Typescript** version of [jsartoolkitNFT](https://github.com/webarkit/jsartoolkitNFT)  because we plan to transcode our libraries with this language. That was the first step, the next one will be transcoding [ARnft](https://github.com/webarkit/ARnft), the process is on the way see the [PR](https://github.com/webarkit/ARnft/pull/158), but this wasn't possible without before porting  jsartoolkitNFT. 
+
+**JsartoolkitNFT** our small libraries for **WebAR** has arrived to [0.9.1](https://github.com/webarkit/jsartoolkitNFT/releases/tag/0.9.1) version, and you can install as a module with npm:
+
+`npm install @kalwalt/jsartoolkit-nft`
+
+We will publish in the webarkit scoped name when it will be almost stable. We will advise you in our blog with all the informations.
+
+We didn't make any improve apart the Typescript langauage conversion, there are still some little refinements to do in the code, that is planned to realize.
+
+In regards of the new Typescript feature, you don't need to download any other typed library, `types` folder is present  in the root folder, so everything you need to do is to install the package and import it in you project:
+
+`import AR from "@kalwalt/jsartoolkit-nft"`
+
+If you are developing on a Javascript or Typescript ambient this does the same. But in a Typescript environnment you will get all of the advantages, let say intellisense support and type checking. 
+
+We are sure that you will develop many interesting projects with it. Let us know on what are you working!
+
+See you in a next Blog article!

_posts/2021-04-07-jsartoolkitnft-typescript-version.md

@@ -31,13 +31,14 @@ collections: # A list of collections the CMS should be able to edit
       - {label: "Layout", name: "layout", widget: "hidden", default: "post"}
       - {label: "Slug", name: "slug", widget: "string"}
       - {label: "Title", name: "title", widget: "string", tagname: "h1"}
+      - {label: "SubTitle", name: "subtitle", widget: "string", tagname: "h2"}
       - {label: "Description", name: "description", widget: "text"}
       - label: "Author"
         name: "author"
         widget: "select"
         options:
           - { label: "Walter Perdan", value: "Walter Perdan" }
-      - {label: "Publish Date", name: "date", widget: "datetime", format: "YYYY-MM-DD HH:MM:SS"}
+      - {label: "Publish Date", name: "date", widget: "datetime", format: "YYYY-MM-DD HH:MM"}
       - {label: "Language", name: "lang", widget: "text", default: "en"}
       - label: "Seo"
         name: "seo"
@@ -57,4 +58,4 @@ collections: # A list of collections the CMS should be able to edit
           - {label: "Date_Published", name: "datePublished", widget: "date", format: "YYYY-MM-DD"}
       - {label: "Image_path", name: "image", widget: "string"}
       - {label: "Intro Paragraph", name: "intro_paragraph", widget: "markdown", required: false}
-      - {label: "Body", name: "body", widget: "markdown", required: false}
+      - {label: "Body", name: "body", widget: "markdown", required: false}

admin/config.yml

@@ -1,7 +1,7 @@
 {
   "name": "WebARKit",
   "short_name": "WebARKit",
-  "start_url": ".",
+  "start_url": "/",
   "display": "standalone",
   "background_color": "#fff",
   "theme_color": "#1E2A78",

assets/images/uploads/webar_kit_netlify_open_source_team.jpg

@@ -1,7 +1,7 @@
 // set names for both precache & runtime cache
 workbox.core.setCacheNameDetails({
     prefix: 'webarkit-site',
-    suffix: 'v1',
+    suffix: 'v1.0',
     precache: 'precache',
     runtime: 'runtime-cache'
 });
@@ -21,12 +21,12 @@ workbox.routing.registerRoute(
 
 // use `cacheFirst` strategy for images
 workbox.routing.registerRoute(
-    /assets\/(img|icons|svg|json)/,
+    /assets\/(img|icons|svg)/,
     workbox.strategies.cacheFirst()
 );
 
 // use `cacheFirst` strategy for images
 workbox.routing.registerRoute(
-    /\.(?:js|css|png|gif|jpg|svg|json)$/,
+    /\.(?:js|css|png|gif|jpg|svg)$/,
     workbox.strategies.cacheFirst()
 );