<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Diego Perez on Medium]]></title>
        <description><![CDATA[Stories by Diego Perez on Medium]]></description>
        <link>https://medium.com/@i_maka?source=rss-175e412d11c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*41bVVMMEsFeN96ay.jpg</url>
            <title>Stories by Diego Perez on Medium</title>
            <link>https://medium.com/@i_maka?source=rss-175e412d11c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:36:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@i_maka/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Build an Ecommerce App with Personalization using Angular and Cosmic JS]]></title>
            <link>https://medium.com/hackernoon/build-an-ecommerce-app-with-personalization-using-angular-and-cosmic-js-9eba6f33b042?source=rss-175e412d11c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9eba6f33b042</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[cosmic-js]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Diego Perez]]></dc:creator>
            <pubDate>Thu, 02 May 2019 16:33:30 GMT</pubDate>
            <atom:updated>2019-05-15T07:33:50.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*8bZBjo0KHVCcGf2Y3wqneQ.png" /></figure><p><em>This article will assume some basic knowledge of Angular so it can focus on the specific task at hand. Feel free to ask me about any specifics on the implementation you may find unclear</em></p><h3>TL; DR</h3><p>Take a look at the <a href="https://github.com/cosmicjs/angular-ecommerce-personalization">repository</a> and <a href="https://cosmicjs.com/apps/ecommerce-personalization">install the app</a>, or <a href="https://cosmicjs.com/apps/ecommerce-personalization/demo">view a demo</a>.</p><h3>What we’re going to build</h3><p>This site will be a very simplistic representation of an e-commerce website. Its purpose is to show how we can offer a customized experience for everyone. Our data will be stored and served by Cosmic JS and we will use Angular for our Front-End.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_tjeSzGT_xilbC8zSHKvkA.png" /></figure><h3>How it will work</h3><p>Our store-front will be just a product listing page, showing all products stored in Cosmic JS, randomly sorted. The products will belong to a number of categories, and each product will show 3 buttons to mock the following behaviors:</p><ul><li>view -&gt; value: 1</li><li>add to cart -&gt; value: 2</li><li>buy -&gt; value: 3</li></ul><p>These will represent different degrees of interest.</p><p>The user will interact with the site and their interests will be stored in their profile, increasing the corresponding value of each product’s categories.</p><p>A full interaction would be something like: the user clicks on “buy” a “swimwear” product, increasing its profile score for products belonging to “swimwear”. The page then will sort the page showing more prominently the products belonging to “swimwear”.</p><h3>Preparing our bucket</h3><p>The first thing we’ll do is prepare our Cosmic JS bucket. We have to create an empty bucket and three object types:</p><ul><li>Categories</li><li>Products</li><li>Users</li></ul><p>Each user will store a sessionID and a JSON object for interests.<br>Each product will have a price, a collection of categories and an image.<br>Categories won&#39;t need any metadata, we will just use its title.</p><p>If you are as lazy as I am, you can always <strong>replicate the demo bucket</strong> by <a href="https://cosmicjs.com/apps/ecommerce-personalization">installing the app</a>.</p><h3>Preparing the site</h3><p>The first thing we need to do is create a new Angular site (I always recommend using the CLI for that). Now, let’s create an HTTP interceptor that will handle the authentication against the Cosmic JS API, so we don’t need to add this in every call. It will append the read_key parameter for the GET requests and the write_key for everything else.</p><pre>@Injectable({ providedIn: &#39;root&#39; })<br>export class CosmicInterceptor implements HttpInterceptor {<br>  intercept(req: HttpRequest&lt;any&gt;, next: HttpHandler): Observable&lt;HttpEvent&lt;any&gt;&gt; {<br>    if (req.url.match(/api.cosmicjs/)) {<br>      let params = new HttpParams({ fromString: req.params.toString() });<br>      if (req.method === &#39;GET&#39;) {<br>        params = params.append(&#39;read_key&#39;, environment.read_key);</pre><pre>        req = req.clone({<br>          params: params<br>        });<br>      } else {<br>        let payload = JSON.parse(req.body);<br>        payload.write_key = environment.write_key;</pre><pre>        req = req.clone({<br>          body: payload<br>        });<br>      }<br>    }<br>    return next.handle(req);<br>  }<br>}</pre><p>The product listing will be our only page, so after creating the component, our routes should look like this:</p><pre>const routes: Routes = [{ path: &#39;&#39;, component: ProductListingComponent }];</pre><h3>The product listing page</h3><p>We need to show the products, so let’s define our model:</p><pre>import { Category } from &#39;./category&#39;;</pre><pre>export class Product {<br>  _id: string;<br>  slug: string;<br>  title: string;<br>  price: string;<br>  categories: Category[];<br>  image: string;</pre><pre>  constructor(obj) {<br>    this._id = obj._id;<br>    this.slug = obj.slug;<br>    this.title = obj.title;<br>    this.price = obj.metadata.price;<br>    this.image = obj.metadata.image.url;<br>    this.categories = [];</pre><pre>    if (obj.metadata &amp;&amp; obj.metadata.categories) {<br>      obj.metadata.categories.map(category =&gt; this.categories.push(new Category(category)));<br>    }<br>  }<br>}</pre><p><em>*We’ll talk about the Category there later.</em></p><p>Now let’s begin populating our service with methods. First of all, we need a getProducts() method:</p><pre>private products$: Observable&lt;Product[]&gt;;</pre><pre>getProducts(): Observable&lt;Product[]&gt; {<br>    if (!this.products$) {<br>      this.products$ = this.http.get&lt;Product[]&gt;(this.productsUrl).pipe(<br>        tap(_ =&gt; console.log(&#39;fetched products&#39;)),<br>        map(_ =&gt; {<br>          return _[&#39;objects&#39;].map(element =&gt; new Product(element));<br>        }),<br>        shareReplay(1),<br>        catchError(this.handleError(&#39;getProducts&#39;, []))<br>      );<br>    }<br>    return this.products$;<br>  }</pre><p><em>*We are caching the response, our products won’t change that often and we are going to call this method A LOT…</em></p><p>The component itself will be quite simple. For now, it will only have the call two calls to our service:</p><pre>import { Component, OnInit } from &#39;@angular/core&#39;;<br>import { CosmicService } from &#39;src/app/core/_services/cosmic.service&#39;;<br>import { Product } from &#39;@models/product&#39;;<br>import { UserService } from &#39;src/app/core/_services/user.service&#39;;<br>import { User } from &#39;@models/user&#39;;</pre><pre>@Component({<br>  selector: &#39;app-product-listing&#39;,<br>  templateUrl: &#39;./product-listing.component.html&#39;,<br>  styleUrls: [&#39;./product-listing.component.scss&#39;]<br>})<br>export class ProductListingComponent implements OnInit {<br>  public productList: Product[];<br>  public user: User;</pre><pre>  constructor(private cosmicService: CosmicService, private userService: UserService) {}</pre><pre>  ngOnInit() {<br>    this.userService.user$.subscribe(user =&gt; {<br>      this.user = user;<br>    });<br>    this.cosmicService.getProducts().subscribe(products =&gt; (this.productList = products));<br>  }<br>}</pre><p>And this is the HTML:</p><pre>&lt;div class=&quot;columns&quot; *ngIf=&quot;productList &amp;&amp; user&quot;&gt;<br>  &lt;ng-container *ngFor=&quot;let product of (productList | customSort:user.interests)&quot;&gt;<br>          &lt;div class=&quot;product-tile column is-one-third&quot;&gt;<br>            &lt;img src=&quot;{{ product.image }}&quot; class=&quot;image&quot;/&gt;<br>            &lt;div class=&quot;level is-size-4 is-uppercase&quot;&gt;<br>                &lt;span class=&quot;level-item&quot;&gt;{{product.title}}&lt;/span&gt;<br>                &lt;span class=&quot;level-item has-text-weight-bold&quot;&gt;${{product.price}}&lt;/span&gt;<br>            &lt;/div&gt;<br>            &lt;app-actions [product]=&quot;product&quot;&gt;&lt;/app-actions&gt;<br>          &lt;/div&gt;<br>  &lt;/ng-container&gt;<br>&lt;/div&gt;</pre><p>Have you noticed that app-actions component? It will take care of the actions the user will perform over each product. But let&#39;s talk about the user before that...</p><h3>Everything about the user</h3><p>Our user model will be the most “complex” of all. As we will be creating users from the site and retrieving them from Cosmic JS, we need a more flexible constructor. We also added methods to build a payload object for posting to Cosmic JS and another one for managing the interests.</p><pre>import { Category } from &#39;./category&#39;;</pre><pre>export class User {<br>  _id: string;<br>  slug: string;<br>  interests: JSON;</pre><pre>  constructor(obj?) {<br>    this._id = obj ? obj._id : &#39;&#39;;<br>    this.slug = obj ? obj.slug : &#39;&#39;;<br>    this.interests = obj ? JSON.parse(obj.metadata.interests) : {};<br>  }</pre><pre>  postBody() {<br>    return {<br>      title: this.slug,<br>      type_slug: &#39;users&#39;,<br>      metafields: [<br>        {<br>          key: &#39;interests&#39;,<br>          value: JSON.stringify(this.interests)<br>        }<br>      ]<br>    };<br>  }</pre><pre>  putBody() {<br>    return {<br>      title: this.slug,<br>      slug: this.slug,<br>      metafields: [<br>        {<br>          key: &#39;interests&#39;,<br>          value: JSON.stringify(this.interests)<br>        }<br>      ]<br>    };<br>  }</pre><pre>  increaseInterest(category: Category, weight: number) {<br>    if (!this.interests[category.title]) {<br>      this.interests[category.title] = weight;<br>    } else {<br>      this.interests[category.title] += weight;<br>    }<br>  }<br>}</pre><p>We won’t build a proper authentication journey for our example. Each user will have a sessionID in the browser’s local storage, and we will use that to create and identify users. We’ll keep the user instance on session storage for convenience. In order to keep things tidy, let’s create a user service:</p><pre>import { Injectable } from &#39;@angular/core&#39;;<br>import { User } from &#39;@models/user&#39;;<br>import { CosmicService } from &#39;./cosmic.service&#39;;<br>import { BehaviorSubject } from &#39;rxjs&#39;;</pre><pre>@Injectable({<br>  providedIn: &#39;root&#39;<br>})<br>export class UserService {<br>  private userSource = new BehaviorSubject&lt;User&gt;(new User());<br>  public user$ = this.userSource.asObservable();</pre><pre>  constructor(private cosmicService: CosmicService) {}</pre><pre>  init() {<br>    let sessionID = localStorage.getItem(&#39;sessionID&#39;);</pre><pre>    if (!sessionID) {<br>      const user = new User();</pre><pre>      sessionID = Math.random()<br>        .toString(36)<br>        .substr(2, 9);</pre><pre>      localStorage.setItem(&#39;sessionID&#39;, sessionID);<br>      user.slug = sessionID;</pre><pre>      this.cosmicService.setUser(user).subscribe(user =&gt; {<br>        this.setSessionUser(user);<br>      });<br>    } else if (!sessionStorage.getItem(&#39;user&#39;)) {<br>      this.cosmicService.getUser(sessionID).subscribe(user =&gt; this.setSessionUser(user));<br>    }<br>  }</pre><pre>  setSessionUser(user: User) {<br>    sessionStorage.setItem(&#39;user&#39;, JSON.stringify(user));<br>    this.userSource.next(user);<br>  }</pre><pre>  getSessionUser(): User {<br>    const user = sessionStorage.getItem(&#39;user&#39;);</pre><pre>    if (user) {<br>      return Object.assign(new User(), JSON.parse(user));<br>    } else {<br>      return null;<br>    }<br>  }<br>}</pre><p>The init() method will be used on our app.component.ts:</p><pre>constructor(private userService: UserService) {}</pre><pre>  ngOnInit() {<br>    this.userService.init();<br>  }</pre><p>We will also need a way of setting and getting the user, let’s extend our cosmic.service with the following methods:</p><pre>getUser(slug: string): Observable&lt;User&gt; {<br>    const url = `${this.singleObjectUrl}/${slug}`;<br>    return this.http.get&lt;User&gt;(url).pipe(<br>      tap(_ =&gt; console.log(`fetched user: ${slug}`)),<br>      map(_ =&gt; {<br>        return new User(_[&#39;object&#39;]);<br>      }),<br>      catchError(this.handleError&lt;User&gt;(`getUser: ${slug}`))<br>    );<br>  }</pre><pre>  setUser(user: User) {<br>    return this.http.post&lt;User&gt;(this.addObjectPath, JSON.stringify(user.postBody())).pipe(<br>      map(_ =&gt; {<br>        return new User(_[&#39;object&#39;]);<br>      }),<br>      catchError(this.handleError&lt;User&gt;())<br>    );<br>  }</pre><p>Also, note that we created an observable user$ that emits every time we set (or update) the user in session, you already saw the subscription on the product listing. More on this at the end of the article.</p><p>Back to the actions.component. It is a set of three buttons, as follows:</p><pre>&lt;div class=&quot;buttons has-addons is-centered&quot;&gt;<br>  &lt;a class=&quot;button is-primary&quot; (click)=&quot;viewProduct()&quot;&gt;<br>    &lt;span class=&quot;icon is-small&quot;&gt;<br>      &lt;i class=&quot;fa fa-eye&quot;&gt;&lt;/i&gt;<br>    &lt;/span&gt;<br>    &lt;span&gt;View&lt;/span&gt;<br>  &lt;/a&gt;<br>  &lt;a class=&quot;button is-warning&quot; (click)=&quot;addProductToCart()&quot;&gt;<br>    &lt;span class=&quot;icon is-small&quot;&gt;<br>      &lt;i class=&quot;fa fa-shopping-cart&quot;&gt;&lt;/i&gt;<br>    &lt;/span&gt;<br>    &lt;span&gt;Add to cart&lt;/span&gt;<br>  &lt;/a&gt;<br>  &lt;a class=&quot;button is-success&quot; (click)=&quot;buyProduct()&quot;&gt;<br>    &lt;span class=&quot;icon is-small&quot;&gt;<br>      &lt;i class=&quot;fa fa-dollar&quot;&gt;&lt;/i&gt;<br>    &lt;/span&gt;<br>    &lt;span&gt;Buy!&lt;/span&gt;<br>  &lt;/a&gt;<br>&lt;/div&gt;</pre><p>And the methods look like this:</p><pre>@Input() product: Product;</pre><pre>  viewProduct() {<br>    this.increaseInterest(1);<br>  }</pre><pre>  addProductToCart() {<br>    this.increaseInterest(2);<br>  }</pre><pre>  buyProduct() {<br>    this.increaseInterest(3);<br>  }</pre><pre>  increaseInterest(weight: number) {<br>    const user: User = this.userService.getSessionUser();<br>    this.product.categories.forEach((category: Category) =&gt; {<br>      user.increaseInterest(category, weight);<br>    }, this);</pre><pre>    this.userService.setSessionUser(user);<br>    this.cosmicService.updateUser(user).subscribe();<br>  }</pre><p>When updating the interests, we also refresh the user in session and we also update the user in Cosmic JS, we never know when or how the user will leave the site! Let’s go back to our cosmic.service and add this method:</p><pre>updateUser(user: User) {<br>    return this.http.put&lt;User&gt;(this.editObjectPath, JSON.stringify(user.putBody())).pipe(<br>      map(_ =&gt; {<br>        return new User(_[&#39;object&#39;]);<br>      }),<br>      catchError(this.handleError&lt;User&gt;())<br>    );<br>  }</pre><h3>Wrapping everything up</h3><p>We have now a way to show products, create users and their interests, update them and store them. That’s it… almost. How does the product listing page change based on all this? There is one last thing we haven’t go through yet - the customSort pipe on product-listing.component. Here is how it looks like:</p><pre>@Pipe({<br>  name: &#39;customSort&#39;<br>})<br>export class CustomSortPipe implements PipeTransform {<br>  transform(value: Product[], interests: JSON): Product[] {<br>    value.sort((a: Product, b: Product) =&gt; {<br>      const aWeight = this.getWeight(a.categories, interests);<br>      const bWeight = this.getWeight(b.categories, interests);</pre><pre>      if (aWeight &lt; bWeight) {<br>        return 1;<br>      } else if (aWeight &gt; bWeight) {<br>        return -1;<br>      } else {<br>        return 0;<br>      }<br>    });<br>    return value;<br>  }</pre><pre>  getWeight(categories: Category[], interests: JSON) {<br>    let weight = 0;<br>    categories.forEach(category =&gt; {<br>      weight += interests[category.title] || 0;<br>    });<br>    return weight;<br>  }<br>}</pre><p>This pipe will take the product list and order it by weight, based on the user’s interests provided via arguments…</p><p>And that’s the magic: the product listing page is subscribed to the changes in the session user, so every time the user performs an action, the user changes and the sorting re-executes with the changes.</p><p>That’s all, I hope this would have demonstrated how to offer a customized experience for your users with the help of Angular and Cosmic JS.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9eba6f33b042" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/build-an-ecommerce-app-with-personalization-using-angular-and-cosmic-js-9eba6f33b042">Build an Ecommerce App with Personalization using Angular and Cosmic JS</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a simple company website with Cosmic JS and Angular]]></title>
            <link>https://medium.com/hackernoon/how-to-create-a-simple-company-website-with-cosmic-js-and-angular-476896ca0ed4?source=rss-175e412d11c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/476896ca0ed4</guid>
            <category><![CDATA[cosmic-js]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[website-company]]></category>
            <category><![CDATA[cosmic-js-and-angular]]></category>
            <category><![CDATA[cms]]></category>
            <dc:creator><![CDATA[Diego Perez]]></dc:creator>
            <pubDate>Wed, 02 Jan 2019 23:48:28 GMT</pubDate>
            <atom:updated>2019-01-08T07:35:59.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*jq8yXeQa6BAxAcFvuAjL1Q.jpeg" /></figure><p><em>* This article will assume some basic knowledge of Angular so it can focus on the specific task of requesting and showing data from Cosmic JS</em></p><h3>TL; DR</h3><p>Take a look at <a href="https://github.com/cosmicjs/angular-company-website">the repository</a> and <a href="https://cosmicjs.com/apps/angular-company-website">install the app</a></p><p><strong>What is this app about?</strong></p><p>A typical company website is just a set of pages structured in a more or less simple navigation. We want to create a website that allows the user to create any number of pages and decide the structure for the navigation, without the need to wait for a code release. For that, we are going to rely on Cosmic JS and create the structure to hold this project. On this example, our bucket will have the following object types:</p><ul><li>Pages. This is a simple object, with no additional metafields.</li><li>Navigation. It will hold a collection of Pages.</li><li>Presets. This is a configuration object with a list of attributes that will help us start our app. It will hold the value for the homepage and the main navigation that we will use for the menu of our site.</li></ul><p><strong>Using the API</strong></p><p>Now that we defined the structure of our data, we need to create our Angular app (I recommend using the Angular CLI) and create a service to make our calls to the Cosmic JS API. See how simple is to request a single page object from Cosmic JS:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4acff249c5df9f5ef0dd5c6388dc94c/href">https://medium.com/media/a4acff249c5df9f5ef0dd5c6388dc94c/href</a></iframe><p>Note that, for nested objects, Cosmic JS will not return the full tree, so sometimes you will need to concatenate calls to make the most of our service, e.g.: When fetching the main presets, you would probably want to include the navigation pages.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ed4ec69bbd00923929d507f963232afe/href">https://medium.com/media/ed4ec69bbd00923929d507f963232afe/href</a></iframe><p>Our api calls need to be authenticated with a read key, we can include that on each method, but the easiest may be to create an interceptor. This will intercept all http requests, so we check if it’s a Cosmic JS request and append the read key where necessary.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/092cf4c0d51a94836e827b3e59493987/href">https://medium.com/media/092cf4c0d51a94836e827b3e59493987/href</a></iframe><p><strong>Routing to the pages</strong></p><p>At this point, our website does nothing, the first thing it needs to do is to know how to load its first page. We need to create a routed module for the Pages, and set it to load on the root. Once inside the module, on its own routing, we will set a route for the parameter :slug to load the Page Component. And what happens when there is no route specified? This will be our most common scenario, for that, we set an empty route with a Guard.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4047264c21b8c16a5a600f66d89c9fbb/href">https://medium.com/media/4047264c21b8c16a5a600f66d89c9fbb/href</a></iframe><p>A guard will be executing when matching a route and before loading the component, so we will use it to fetch the main presets from Cosmic JS, and redirect the app to the homepage we stablished.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1189638b1d4bd58930814258ae0ea16b/href">https://medium.com/media/1189638b1d4bd58930814258ae0ea16b/href</a></iframe><p><strong>Components</strong></p><p>Now we have a route configuration that will load the Page component, and this is the way to load a page using the slug from the parameter list:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/60fa2c5a5fa7c6eba733d40e71c7993d/href">https://medium.com/media/60fa2c5a5fa7c6eba733d40e71c7993d/href</a></iframe><p>With this, we have a way to navigate via url, but we should also load a menu so the user can see the pages available. For that, we will add a menu component on the core module, as it will be shared throughout the app. Our menu will be composed of a navigation list, a logo and the company name; all of this is defined on the presets, so the menu will have a call like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/635f5ec8018774225cb3779870e11a84/href">https://medium.com/media/635f5ec8018774225cb3779870e11a84/href</a></iframe><p>All of this would allow you to quickly create a website using Angular and Cosmic JS, all that is left to do is to create the templates and extend the configuration to meet your needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=476896ca0ed4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-create-a-simple-company-website-with-cosmic-js-and-angular-476896ca0ed4">How to create a simple company website with Cosmic JS and Angular</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>