Migrating the existing portal

.prettierignore

@@ -0,0 +1,4 @@
+.cache
+package.json
+package-lock.json
+public

.prettierrc

@@ -0,0 +1,4 @@
+{
+  "arrowParens": "avoid",
+  "semi": false
+}

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing
+
+[Loginradius Engineering Portal](https://www.loginradius.com/engineering/blog) is [MIT](LICENSE) licensed and accept contributions via GitHub pull requests. This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted.
+
+
+## Getting Started
+
+ - Fork the repository on GitHub
+ - Read the [Blog writing guideline](GUIDELINES.md) for writing and publishing your blog
+ - If you find any bug/typo/fix in our existing blog posts, please create a pull request as mentioned in Contribution Flow
+
+## Contribution Flow
+This is a rough outline of what a contributor's workflow looks like:
+
+ - Create a topic branch from where you want to base your work (usually master).
+ - Make commits of logical units.
+ - Make sure your commit messages are in the proper format (see below).
+ - Push your changes to a topic branch in your fork of the repository.
+ - Make sure to proofread the content before submitting
+ - Submit a pull request to the original repository.
+
+Thanks for your contributions!
+
+## What we are looking for
+
+ - A well-articulated technology-related blog posts
+ - The post should be of 600-900 words.
+ - The topic must relate to technology/programming/coding.
+ - Post must not be published elsewhere.
+ - The author gets only these link in bio, GitHub, StackOverflow, LinkedIn.
+ - The post should adhere to our [Blog writing guideline](GUIDELINES.md)
+
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make 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 Responsibilities
+
+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 behaviours that they deem inappropriate, threatening, offensive, or harmful.

GUIDELINES.md

@@ -0,0 +1,66 @@
+## Guidelines to submit the blog in Engineering Portal
+
+Here are some guidelines that you must follow while writing the blog for engineering portal:
+
+1. Write the post in Markdown format, it's easy, fast, multi-platform and you can edit it in any editor like vscode have `HTML` preview. My favourite is [Dillinger](https://dillinger.io/), where you find the sample content to understand the syntax of markdown.
+
+2. The blog should have the cover image with the aspect ratio of **3:2**, we recommend using image size of **1024px x 768px** and the minimum image size can be **600px x 400px**.
+
+3. The blog should have the metatags at the top of you MD files which should have the below properties.
+    * **title (Required)** : A meaningfull title.
+    Note: This title will appear in the post so no need to again include it in the `md` files.
+    * **date (Required)**: A date should be in `YYYY-MM-DD` format. And the date should not be greater than the current date.
+    * **coverImage (Required)**: The name of the image with format should come here. Please make sure the image should be present in the directory where your `.md` the file is there.
+    * **author (Required)**: The name of the author, make sure the author name should match with the one you have added in you Pull Request description.
+    * **tags: (optional)** : You can add the relevant the in the Array of string `for eg: ["NodeJs"]`. Please make sure tags should not be more than three.
+    * **description** (optional): You can add the short description, which will appear in the card of your blog, it should not be more than 160 characters. If you don't specify the description by default the first 160 characters of your blog will be shown.
+
+    This is an example of the meta info in your blog
+    ```
+    ---
+    title: Hello this is a title
+    date: "2020-06-11"
+    coverImage: "coverImage.png"
+    author: "Jon Doe"
+    description: "This is for test"
+    ---
+    
+    Your blog will start here...
+    
+    ```
+4. As discussed above while submitting the pull request you need to mention the **author details** in the pull request description. The format should be as below.
+    * **id (required)**: The name of the author, it should be same as the name in the meta tags of the blog.
+    * **bio (optional)**: A short intro about you.
+    * **social profiles (optional)**: You need to mention the id of your social profiles, supported social profiles will be GitHub, StackOverflow, LinkedIn, medium, twitter.
+    Note: For StackOverflow, you need to add your id which is in **number**, for eg: `https://stackoverflow.com/users/5688477/modi-mohammed` for this URL id will be `5688477`.
+
+    This is an example of the author info
+    
+    ```
+    id: Jon Doe
+    bio: A short intro about me
+    github: 
+    stackoverflow: 
+    linkedin: 
+    medium: 
+    twitter: 
+    ```
+
+## Some tips that you can keep in mind while writing the blog.
+
+- Keep post's language simple and easy to understand, we are making our blogs for the mass and our audience doesn't need to be only native English speakers
+
+- Use short paragraphs, break down longer paragraphs into smaller one, people lose their interest more while reading a long paragraph
+
+- Use headers to structure your post, use large headers for the main heading and smaller for sub-sections in it
+
+- Try to use complete words then abbreviations, spell out an acronym that isn’t well-known
+
+- If your code contains code snippet, don't forget to syntax highlighting it, You can also specify the programming language for which you want syntax highlighting.
+ **For example:** in markdown typing, ```js will give you JavaScript syntax highlighting.
+
+- Try to use images/screenshots in your post to example things better, images are also visible when you share the post in social media
+
+- Always provide a GitHub demo link whenever you post contains the code.
+
+- Simplicity, Ease of Implementation of the content, developer-friendly and effectiveness 

content/author.yaml

@@ -0,0 +1,121 @@
+- id: Team LoginRadius
+  bio: LoginRadius is a leading provider of cloud-based Customer Identity and Access Management (cIAM) platform.
+  github: 'LoginRadius'
+
+- id: Puneet Singh
+  bio: Very curious about this world and blogging whenever learning something new
+  github: "puneetsingh24"
+  stackoverflow: "3879440"
+  linkedin: "puneetsingh24"
+
+- id: Ravi Teja Ghanta
+  bio: First curious cat at Gatsby Curious Community. Blogs at dev.wgao19.cc.
+  github: 'ravitejag'
+
+- id: Govind Malviya
+  bio: Director of Product Development @ LoginRadius. Likes tech, reading/writing, founding things.
+  github: "GovindMalviya"
+
+- id: Zakary Hughes
+  bio: Zak is our resident front end development and design intern. He studied web design and development at the Northern Alberta Institute of Technology. One of his passions, outside of work, is fitness. Legend has it that he once ate a two-bite brownie in a single bite.
+
+- id: Chris Yee
+  bio: A software engineer who graduated with a Bachelor of Software Engineering from the University of British Columbia.
+
+- id: Zoie Carnegie
+  bio: Graduated from NAIT Digital Media and IT specializing in application development. PHP is my favorite language. I am a continuous learner always trying new languages, applications, frameworks. Passions are Programming, Photography and Travel.
+
+- id: Greg Sakai
+  bio: Greg Sakai is a Software Developer at LoginRadius. He is currently studying Computer Science part time, and he loves all things JavaScript. In his spare time, he likes doing homework.
+
+- id: Kunal
+  bio: Kunal is a Software Developer at LoginRadius, the rapidly-expanding social login and sharing provider.He graduated in Computer Science and considers himself a learner of life.He loves to play cricket, football and computer games.
+  github: "SuperKunal"
+
+- id: Mayank Agarwal
+  bio: Mayank is a Software developer at LoginRadius. He graduated with a Bachelor of Technology Degree in Computer Science. He loves to play cricket, watching TV series and listening music.
+  github: "mayankagrwal"
+
+- id: Carling
+  bio: Carling is the Edmonton office manager at LoginRadius – a leading Customer Identity Management Platform. She graduated from the University of Alberta with a Bachelor of Commerce degree with Distinction. She’s a member of Mensa Canada and would love to challenge you to a game of NERTS. Connect with Carling on Linkedin or Twitter
+
+- id: Ruben Gonzalez
+  bio: Ruben is a Computer Science student at The University of British Columbia. His main interests include web development, AI, classical music, and social justice. Originally from Colombia, he also is fluent in Spanish.
+  github: "rubenprograms"
+
+- id: Mark Duan
+
+- id: Shefali Yaduvanshi
+  bio: Shefali Yaduvanshi is a Quality Analyst at LoginRadius. She believes in delivering good quality in software. She loves sketching, and playing Kabaddi in free time.
+
+- id: Solomon Yu
+  bio: Very curious about this world and blogging whenever learning something new
+
+- id: Pascal Noel
+  bio: Software Engineer and adventure seeker with a knack for fun facts. Originally from the East Coast of Canada, moved to Vancouver to enjoy its mild climate and now staying for its scenic hikes.
+
+- id: Hitesh Pamnani
+  bio: An enthusiastic developer with hands-on-experience in various tech platforms. Settled as an Android developer from past 4 years, worked on some interesting stuff and looking forward to more. Loves gadgets, soothing music and spending time with family.
+
+- id: Giriraj Yadav
+  bio: My name is Giriraj Yadav and I am a Software Developer, currently living in Jaipur, India. I have 4.3 years experience as a Java developer and I have been working with LoginRadius since 2016. After Completing my Masters in Computer Application, I spend much of my time in Java Development and surf internet for better inspirations.
+
+- id: Karl Wittig
+  bio: Karl is a Software Developer at LoginRadius, the rapidly-expanding social login and sharing provider. He graduated from NAIT with a diploma in Computer Engineering Technologies. He enjoys snowboarding, watching TV series and gaming.
+
+- id: Versha Gupta
+  bio: Versha is a Software Developer at LoginRadius. She graduated with a Bachelor of Technology Degree in Computer Science Engineering. 
+
+- id: Lucius Yu
+  bio: Lucius is a Software Developer at LoginRadius. He was born and raised in China, but came to Edmonton to graduate from the University of Alberta, double majoring in Computer Sciences and Mathematics. Besides coding, which is his real passion, he enjoys playing ping pong and swimming.
+
+- id: Andy Yeung
+  bio: Software Developer at LoginRadius with an interest in big data and basketball..
+
+- id: Ti Zhang
+  bio: Software engineer at LoginRadius with a love for good security practices and bad puns.
+
+- id: Thompson Sanjoto
+  bio: I’m a Software Engineer, I can do backend, frontend, networking, and mobile. Born and raised at Jakarta, Indonesia and went to pursue a Computer Science Degree at the University of British Columbia. Now I’m in Vancouver, BC with LoginRadius.
+
+- id: Eric Chan
+  bio: Eric is a Software Engineer at LoginRadius. Born in Hong Kong he immigrated to Vancouver in order to pursue a degree focused in Computer Science at UBC. During his spare time, Eric enjoys playing sports recreationally, as well as developing fun projects! Check out his GitHub here.
+
+- id: Sreekant
+
+- id: Vincent Lin
+
+- id: Indrasen
+  bio: He is a software engineer who continually seeks clean, elegant solutions to business challenges. His lifelong passion for technology drives him to proactively expand horizons, constantly exploring and evaluating new languages, platforms, frameworks and tools.
+
+- id: Ashish Sharma
+  bio: Ashish is a software engineer who continually seeks clean, elegant solutions to business challenges. His lifelong passion for technology drives him to proactively expand horizons, constantly exploring and evaluating new languages, platforms, frameworks and tools.
+  github: "ashish8947"
+  medium: "@sharma.ashish894789"
+
+- id: Aman Agrawal
+  bio: Aman is a software developer at LoginRadius and keen to learn and work upon new technologies.
+  github: "aman-agrwl"
+
+- id: Mohammed Modi
+  bio: Mohammed Modi is a software developer at LoginRadius and have an experience in working in most of the javascript framework including React, NodeJS, Angular etc.
+  github: "mohammed786"
+  stackoverflow: "5688477"
+  linkedin: "mohammed-modi-2016307a"
+  medium: "@mohammedmodi"
+  twitter: "momscoolguy"
+
+- id: Sudhey Sharma
+  bio: I am a testing consultant, coach * enthusiast, who's been in the software testing industry since 2004. Currently, I am working as QA Manager. Striving to improve the testing craft.
+  github: "sudheysharma"
+
+- id: Himanshi Sharma
+  bio: I am Full Stack Automation Engineer,  working since 7 years in IT Industry. I have keen interest in test automation primarily because of the wide range of challenging problems inherited in this field.
+  github: "Himanshi0512"
+  stackoverflow: "4460619"
+  linkedin: "himanshi-sharma-06464634"
+
+- id: Ankit Singh
+  bio: Very curious about this world and blogging whenever learning something new
+  github: "Imankitt"
+