Kamran Ahmed
3 years ago
commit
579d39e104
217 changed files with 36763 additions and 0 deletions
@ -0,0 +1,18 @@ |
||||
{ |
||||
"extends": [ |
||||
"next", |
||||
"next/core-web-vitals", |
||||
"prettier" |
||||
], |
||||
"rules": { |
||||
"@next/next/no-img-element": [ |
||||
"off" |
||||
], |
||||
"react/display-name": [ |
||||
"off" |
||||
], |
||||
"react/jsx-no-target-blank": [ |
||||
"off" |
||||
] |
||||
} |
||||
} |
||||
@ -0,0 +1,2 @@ |
||||
# These are supported funding model platforms |
||||
github: kamranahmedse |
||||
@ -0,0 +1,36 @@ |
||||
<!-- |
||||
Please do not remove anything written below. |
||||
|
||||
Fill the details and open the issue. Any issue that |
||||
doesn't have all of these filled in will be closed, |
||||
if yours is closed reopen with everything filled in. |
||||
--> |
||||
|
||||
#### What roadmap is this issue about? |
||||
|
||||
- [ ] Frontend Roadmap |
||||
- [ ] Backend Roadmap |
||||
- [ ] DevOps Roadmap |
||||
- [ ] All Roadmaps |
||||
|
||||
#### What is this issue about? |
||||
|
||||
- [ ] Functionality of the website |
||||
- [ ] Discussion for a pull request I would want to open. |
||||
- [ ] Addition of a new item |
||||
- [ ] Removal of some existing item |
||||
- [ ] Changing in arrangement |
||||
- [ ] General suggestion |
||||
- [ ] Sharing an Idea |
||||
- [ ] Something else |
||||
|
||||
#### Please acknowledge the below listed |
||||
|
||||
- [ ] This is not a duplicate issue. I have searched and there is no existing issue for this. |
||||
- [ ] I understand that these roadmaps are highly opinionated. The purpose is to not to include everything out there in these roadmaps but to have everything that is most relevant today comparing to the other options listed. |
||||
- [ ] I have read the [contribution docs](../contributing) before opening this issue. |
||||
|
||||
|
||||
#### Enter the details about the issue here |
||||
|
||||
<!-- Please enter the issue details here --> |
||||
@ -0,0 +1,19 @@ |
||||
#### What roadmap does this PR target? |
||||
|
||||
- [ ] Code Change |
||||
- [ ] Frontend Roadmap |
||||
- [ ] Backend Roadmap |
||||
- [ ] DevOps Roadmap |
||||
- [ ] All Roadmaps |
||||
- [ ] Guides |
||||
|
||||
#### Please acknowledge the items listed below |
||||
|
||||
- [ ] I have discussed this contribution and got a go-ahead in an issue before opening this pull request. |
||||
- [ ] This is not a duplicate issue. I have searched and there is no existing issue for this. |
||||
- [ ] I understand that these roadmaps are highly opinionated. The purpose is to not to include everything out there in these roadmaps but to have everything that is most relevant today comparing to the other options listed. |
||||
- [ ] I have read the [contribution docs](../contributing) before opening this PR. |
||||
|
||||
#### Enter the details about the contribution |
||||
|
||||
<!-- Enter the details here --> |
||||
@ -0,0 +1,31 @@ |
||||
name: Deployment to GitHub Pages |
||||
on: |
||||
push: |
||||
branches: [ master ] |
||||
env: |
||||
ROADMAP_GA_SECRET: ${{ secrets.GA_SECRET }} |
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
||||
CI: true |
||||
NEXT_TELEMETRY_DISABLED: 1 |
||||
jobs: |
||||
build: |
||||
runs-on: ubuntu-latest |
||||
steps: |
||||
- uses: actions/checkout@v2 |
||||
- uses: actions/setup-node@v1 |
||||
with: |
||||
node-version: 12 |
||||
- name: Setup Environment |
||||
run: | |
||||
npm install -g yarn |
||||
yarn install |
||||
- name: Generate meta and builld |
||||
run: | |
||||
yarn meta |
||||
yarn build |
||||
- name: Deploy to GitHub Pages |
||||
run: | |
||||
git config user.email "kamranahmed.se@gmail.com" |
||||
git config user.name "Kamran Ahmed" |
||||
git remote set-url origin https://x-access-token:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git |
||||
npm run deploy |
||||
@ -0,0 +1,36 @@ |
||||
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files. |
||||
out |
||||
|
||||
# dependencies |
||||
/node_modules |
||||
/.pnp |
||||
.pnp.js |
||||
|
||||
# testing |
||||
/coverage |
||||
|
||||
# next.js |
||||
/.next/ |
||||
/out/ |
||||
|
||||
# production |
||||
/build |
||||
|
||||
# misc |
||||
.idea |
||||
.DS_Store |
||||
*.pem |
||||
|
||||
# debug |
||||
npm-debug.log* |
||||
yarn-debug.log* |
||||
yarn-error.log* |
||||
|
||||
# local env files |
||||
.env.local |
||||
.env.development.local |
||||
.env.test.local |
||||
.env.production.local |
||||
|
||||
# vercel |
||||
.vercel |
||||
@ -0,0 +1,5 @@ |
||||
{ |
||||
"semi": true, |
||||
"singleQuote": true, |
||||
"tabWidth": 2 |
||||
} |
||||
@ -0,0 +1,39 @@ |
||||
<p align="center"> |
||||
<img src="public/brand.png" height="128"> |
||||
<h2 align="center">roadmap.sh</h2> |
||||
<p align="center">Community driven roadmaps, articles and resources for developers<p> |
||||
<p align="center"> |
||||
<a href="https://roadmap.sh/guides"> |
||||
<img src="https://img.shields.io/badge/-Guides-0a0a0a.svg?style=flat&colorA=0a0a0a" alt="roadmaps" /> |
||||
</a> |
||||
<a href="https://roadmap.sh/roadmaps"> |
||||
<img src="https://img.shields.io/badge/-Roadmaps-0a0a0a.svg?style=flat&colorA=0a0a0a" alt="roadmaps" /> |
||||
</a> |
||||
<a href="./contributing/guide.md"> |
||||
<img src="https://img.shields.io/badge/%E2%9D%A4-Contribute-0a0a0a.svg?style=flat&colorA=0a0a0a" alt="roadmaps" /> |
||||
</a> |
||||
</p> |
||||
</p> |
||||
|
||||
[roadmap.sh](https://roadmap.sh) is the community effort to create knowledge that is approachable for the developers. |
||||
|
||||
The website is built with Next.js, contains roadmaps which are the step by step guides for developers, guides which are the easier to understand explanations on the complex topics. Anyone can contribute to the website by suggesting changes to existing paths, adding learning resources, becoming an author by adding new guides, updating the existing guides. |
||||
|
||||
## Development |
||||
|
||||
Clone the repository, install the dependencies and start the application |
||||
|
||||
```bash |
||||
git clone https://github.com/kamranahmedse/roadmap.sh |
||||
yarn install |
||||
yarn dev |
||||
``` |
||||
|
||||
## Contributions |
||||
|
||||
* Add new Roadmap |
||||
* Suggest changes to existing roadmap |
||||
* Write an article |
||||
* Improve the site's codebase |
||||
* Write tests |
||||
|
||||
@ -0,0 +1,60 @@ |
||||
import { Box, Container, Flex, Heading, Image, Link, Text } from '@chakra-ui/react'; |
||||
import React from 'react'; |
||||
|
||||
type ContentPageHeaderProps = { |
||||
formattedDate: string; |
||||
title: string; |
||||
subtitle: string; |
||||
author?: { |
||||
name: string; |
||||
twitter: string; |
||||
picture: string; |
||||
}, |
||||
subLink?: { |
||||
text: string; |
||||
url: string; |
||||
} |
||||
}; |
||||
|
||||
export function ContentPageHeader(props: ContentPageHeaderProps) { |
||||
const { title, subtitle, author = null, formattedDate, subLink = null } = props; |
||||
|
||||
return ( |
||||
<Box pt={['35px', '35px', '70px']} pb={['35px', '35px', '55px']} borderBottomWidth={1} mb='30px'> |
||||
<Container maxW='container.md' position='relative' textAlign={['left', 'left', 'center']}> |
||||
<Flex alignItems='center' justifyContent={['flex-start', 'flex-start', 'center']} |
||||
fontSize={['12px', '12px', '14px']}> |
||||
|
||||
{author?.name && ( |
||||
<> |
||||
<Link |
||||
d={['none', 'flex', 'flex']} |
||||
target='_blank' |
||||
href={`https://twitter.com/${author.twitter}`} |
||||
alignItems='center' |
||||
fontWeight={600} |
||||
color='gray.500' |
||||
> |
||||
<Image alt={''} rounded={'full'} mr='7px' w='22px' src={author.picture} /> |
||||
{author.name} |
||||
</Link> |
||||
<Text d={['none', 'inline', 'inline']} mx='7px' color='gray.500' as='span'>·</Text> |
||||
</> |
||||
)} |
||||
|
||||
<Text color='gray.500' as='span'>{formattedDate}</Text> |
||||
{subLink?.text && ( |
||||
<> |
||||
<Text d={['none', 'none', 'inline']} mx='7px' color='gray.500' as='span'>·</Text> |
||||
<Link d={['none', 'none', 'inline']} color='blue.500' fontWeight={500} |
||||
href={subLink.url} target={'_blank'}>{subLink.text}</Link> |
||||
</> |
||||
)} |
||||
</Flex> |
||||
<Heading as='h1' color='black' fontSize={['30px', '30px', '45px']} lineHeight={['40px', '40px', '53px']} |
||||
fontWeight={700} my={['5px', '5px', '10px']}>{title}</Heading> |
||||
<Text fontSize={['14px', '14px', '16px']} color='gray.700'>{subtitle}</Text> |
||||
</Container> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,37 @@ |
||||
export const CustomAd = () => { |
||||
return ( |
||||
<div id='carbonads'> |
||||
<span> |
||||
<span className='carbon-wrap'> |
||||
<a |
||||
href='https://freemote.com/strategy?sl=roadmap' |
||||
className='carbon-img' |
||||
target='_blank' |
||||
> |
||||
<img |
||||
src='/fm-img.png' |
||||
alt='FM Logo' |
||||
height='100' |
||||
width='130' |
||||
style={{ maxWidth: '130px', border: 'none' }} |
||||
/> |
||||
</a> |
||||
<a |
||||
href='https://freemote.com/strategy?sl=roadmap' |
||||
className='carbon-text' |
||||
target='_blank' |
||||
> |
||||
He Went from ZERO TO $74,000 as a Full Time Developer in 7 Weeks |
||||
</a> |
||||
</span> |
||||
<a |
||||
href='https://github.com/sponsors/kamranahmedse' |
||||
className='carbon-poweredby' |
||||
target='_blank' |
||||
> |
||||
Sponsored by |
||||
</a> |
||||
</span> |
||||
</div> |
||||
); |
||||
}; |
||||
@ -0,0 +1,46 @@ |
||||
import { Box, Link, Text } from '@chakra-ui/react'; |
||||
|
||||
type DimmedMoreProps = { |
||||
text: string; |
||||
href: string; |
||||
}; |
||||
|
||||
export function DimmedMore(props: DimmedMoreProps) { |
||||
const { text, href } = props; |
||||
|
||||
return ( |
||||
<Box position='relative' textAlign='center' bottom='20px'> |
||||
<Box |
||||
opacity={1} |
||||
pointerEvents='none' |
||||
position='absolute' |
||||
bottom={0} |
||||
height='200px' |
||||
width='100%' |
||||
background='linear-gradient(180deg, transparent, white)' |
||||
/> |
||||
|
||||
<Link |
||||
rounded='20px' |
||||
display='inline' |
||||
bg='green.600' |
||||
color='white' |
||||
p='7px 20px' |
||||
href={href} |
||||
fontWeight={800} |
||||
fontSize='11px' |
||||
textTransform='uppercase' |
||||
my='25px' |
||||
position='relative' |
||||
_hover={{ |
||||
textDecoration: 'none', |
||||
'& .forward-arrow': { |
||||
transform: 'translateX(3px)' |
||||
} |
||||
}}> |
||||
{text} |
||||
<Text d='inline-block' as='span' transition='200ms' ml='4px' className='forward-arrow'>→</Text> |
||||
</Link> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,79 @@ |
||||
import { Box, Container, Flex, Image, Link, Stack, Text } from '@chakra-ui/react'; |
||||
import siteConfig from '../content/site.json'; |
||||
import { CustomAd } from './custom-ad'; |
||||
|
||||
function NavigationLinks() { |
||||
return ( |
||||
<> |
||||
<Stack isInline d={['none', 'none', 'flex']} color='gray.400' fontWeight={600} spacing='30px'> |
||||
<Link _hover={{ color: 'white' }} href='/roadmaps'>Roadmaps</Link> |
||||
<Link _hover={{ color: 'white' }} href='/guides'>Guides</Link> |
||||
<Link _hover={{ color: 'white' }} href='/watch'>Videos</Link> |
||||
<Link _hover={{ color: 'white' }} href='/about'>About</Link> |
||||
<Link _hover={{ color: 'white' }} href={siteConfig.url.youtube} target='_blank'>YouTube</Link> |
||||
</Stack> |
||||
|
||||
<Stack d={['flex', 'flex', 'none']} color='gray.400' fontWeight={600} spacing={0}> |
||||
<Link py='7px' borderBottomWidth={1} borderBottomColor='gray.800' _hover={{ color: 'white' }} |
||||
href='/roadmaps'>Roadmaps</Link> |
||||
<Link py='7px' borderBottomWidth={1} borderBottomColor='gray.800' _hover={{ color: 'white' }} |
||||
href='/guides'>Guides</Link> |
||||
<Link py='7px' borderBottomWidth={1} borderBottomColor='gray.800' _hover={{ color: 'white' }} |
||||
href='/watch'>Videos</Link> |
||||
<Link py='7px' borderBottomWidth={1} borderBottomColor='gray.800' _hover={{ color: 'white' }} |
||||
href='/thanks'>Thanks</Link> |
||||
<Link py='7px' borderBottomWidth={1} borderBottomColor='gray.800' _hover={{ color: 'white' }} |
||||
href='/about'>About</Link> |
||||
<Link py='7px' _hover={{ color: 'white' }} target='_blank' |
||||
href={siteConfig.url.youtube}>YouTube</Link> |
||||
</Stack> |
||||
</> |
||||
); |
||||
} |
||||
|
||||
export function Footer() { |
||||
return ( |
||||
<Box bg='gray.900' p={['25px 0', '25px 0', '40px 0']}> |
||||
<Container maxW='container.md'> |
||||
<NavigationLinks /> |
||||
|
||||
<Box mt={['40px', '40px', '50px']} mb='40px' maxW='500px'> |
||||
<Flex spacing={0} alignItems='center' color='gray.400'> |
||||
<Link d='flex' alignItems='center' fontWeight={600} _hover={{ textDecoration: 'none', color: 'white' }} |
||||
href='/'> |
||||
<Image alt='' h='25px' w='25px' src='/logo.svg' mr='6px' /> |
||||
roadmap.sh |
||||
</Link> |
||||
<Text as='span' mx='7px'>by</Text> |
||||
<Link bg='blue.500' px='6px' py='2px' rounded='4px' color='white' fontWeight={600} fontSize='13px' |
||||
_hover={{ textDecoration: 'none', bg: 'blue.600' }} href={siteConfig.url.twitter} |
||||
target='_blank'>@kamranahmedse</Link> |
||||
</Flex> |
||||
|
||||
<Text my='15px' fontSize='14px' color='gray.500'>Community created roadmaps, articles, resources and |
||||
journeys to help you choose your path and grow in your career.</Text> |
||||
|
||||
<Text fontSize='14px' color='gray.500'> |
||||
<Text as='span' mr='10px'>© roadmap.sh</Text>· |
||||
<Link href='/about' _hover={{ textDecoration: 'none', color: 'white' }} color='gray.400' |
||||
mx='10px'>FAQs</Link>· |
||||
<Link href='/terms' _hover={{ textDecoration: 'none', color: 'white' }} color='gray.400' |
||||
mx='10px'>Terms</Link>· |
||||
<Link href='/privacy' _hover={{ textDecoration: 'none', color: 'white' }} color='gray.400' |
||||
mx='10px'>Privacy</Link> |
||||
</Text> |
||||
</Box> |
||||
</Container> |
||||
|
||||
<CustomAd /> |
||||
{process.env.GA_SECRET && false && ( |
||||
<script |
||||
async |
||||
type='text/javascript' |
||||
src='//cdn.carbonads.com/carbon.js?serve=CE7DLK3Y&placement=roadmapsh' |
||||
id='_carbonads_js' |
||||
/> |
||||
)} |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,111 @@ |
||||
import { Box, CloseButton, Container, Flex, IconButton, Image, Link, Stack, Text } from '@chakra-ui/react'; |
||||
import { HamburgerIcon } from '@chakra-ui/icons'; |
||||
import { useState } from 'react'; |
||||
import siteConfig from '../content/site.json'; |
||||
|
||||
type MenuLinkProps = { |
||||
text: string; |
||||
link: string; |
||||
}; |
||||
|
||||
function MenuLink(props: MenuLinkProps) { |
||||
const { text, link } = props; |
||||
|
||||
return <Link |
||||
borderBottomWidth={0} |
||||
borderBottomColor='gray.500' |
||||
_hover={{ textDecoration: 'none', borderBottomColor: 'white' }} |
||||
fontWeight={500} |
||||
href={link} |
||||
> |
||||
{text} |
||||
</Link>; |
||||
} |
||||
|
||||
function DesktopMenuLinks() { |
||||
return ( |
||||
<Stack d={['none', 'flex', 'flex']} shouldWrapChildren isInline spacing='15px' alignItems='center' color='gray.50' |
||||
fontSize='15px'> |
||||
<MenuLink text={'Roadmaps'} link={'/roadmaps'} /> |
||||
<MenuLink text={'Guides'} link={'/guides'} /> |
||||
<MenuLink text={'Videos'} link={'/watch'} /> |
||||
|
||||
<Link ml='10px' bgGradient='linear(to-l, yellow.700, red.600)' p='7px 10px' rounded='4px' |
||||
_hover={{ textDecoration: 'none', bgGradient: 'linear(to-l, red.800, yellow.700)' }} |
||||
fontWeight={500} href={'/signup'}>Subscribe</Link> |
||||
</Stack> |
||||
); |
||||
} |
||||
|
||||
function MobileMenuLinks() { |
||||
const [isOpen, setIsOpen] = useState(false); |
||||
|
||||
return ( |
||||
<> |
||||
<IconButton |
||||
rounded='5px' |
||||
padding={0} |
||||
aria-label={'Menu'} |
||||
d={['block', 'none', 'none']} |
||||
icon={<HamburgerIcon color='white' w='25px' height='25px' />} |
||||
color='white' |
||||
cursor='pointer' |
||||
h='auto' |
||||
bg='transparent' |
||||
_hover={{ bg: 'transparent' }} |
||||
_active={{ bg: 'transparent' }} |
||||
_focus={{ bg: 'transparent' }} |
||||
onClick={() => setIsOpen(true)} |
||||
/> |
||||
|
||||
{isOpen && ( |
||||
<Stack color='gray.100' |
||||
fontSize={['22px', '22px', '22px', '32px']} |
||||
alignItems='center' |
||||
justifyContent='center' |
||||
pos='fixed' |
||||
left={0} |
||||
right={0} |
||||
bottom={0} |
||||
top={0} |
||||
bg='gray.900' |
||||
spacing='12px' |
||||
zIndex={1} |
||||
> |
||||
<Link href='/roadmaps'>Roadmaps</Link> |
||||
<Link href='/guides'>Guides</Link> |
||||
<Link href='/watch'>Videos</Link> |
||||
<Link target='_blank' href={siteConfig.url.youtube}>YouTube</Link> |
||||
<Link href='/signup'>Subscribe</Link> |
||||
<CloseButton onClick={() => setIsOpen(false)} pos='fixed' top='3px' right='15px' size='lg' /> |
||||
</Stack> |
||||
)} |
||||
</> |
||||
); |
||||
} |
||||
|
||||
export function GlobalHeader() { |
||||
return ( |
||||
<Box bg='gray.900' p='20px 0'> |
||||
<Container maxW='container.md'> |
||||
<Flex justifyContent='space-between' alignItems='center'> |
||||
<Box> |
||||
<Link w='100%' |
||||
d='flex' |
||||
href='/' |
||||
alignItems='center' |
||||
color='white' |
||||
fontWeight={600} |
||||
_hover={{ textDecoration: 'none' }} |
||||
fontSize='18px'> |
||||
<Image alt='' h='30px' w='30px' src='/logo.svg' mr='10px' /> |
||||
<Text d={['block', 'none', 'block']} as='span'>roadmap.sh</Text> |
||||
</Link> |
||||
</Box> |
||||
<DesktopMenuLinks /> |
||||
<MobileMenuLinks /> |
||||
</Flex> |
||||
</Container> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,31 @@ |
||||
import { Badge, Box, Heading, Link, Text } from '@chakra-ui/react'; |
||||
|
||||
type GuideGridItemProps = { |
||||
title: string; |
||||
href: string; |
||||
subtitle: string; |
||||
date: string; |
||||
isNew?: boolean; |
||||
colorIndex?: number; |
||||
}; |
||||
|
||||
const bgColorList = [ |
||||
'gray.700', |
||||
'purple.800' |
||||
]; |
||||
|
||||
export function GuideGridItem(props: GuideGridItemProps) { |
||||
const { title, subtitle, date, isNew = false, colorIndex = 0, href } = props; |
||||
|
||||
return ( |
||||
<Box _hover={{ textDecoration: 'none', transform: 'scale(1.02)' }} as={Link} href={href} shadow='xl' p='20px' |
||||
rounded='10px' bg={bgColorList[colorIndex] ?? bgColorList[0]} flex={1}> |
||||
<Text mb='10px' fontSize='13px' color='gray.400'> |
||||
{isNew && <Badge colorScheme={'yellow'} mr='10px'>New</Badge>} |
||||
{date} |
||||
</Text> |
||||
<Heading color='white' mb={'6px'} fontSize='20px'>{title}</Heading> |
||||
<Text color='gray.300' fontSize='14px'>{subtitle}</Text> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,73 @@ |
||||
import NextHead from 'next/head'; |
||||
import siteConfig from '../content/site.json'; |
||||
|
||||
type HelmetProps = { |
||||
title?: string; |
||||
keywords?: string[]; |
||||
canonical?: string; |
||||
description?: string; |
||||
}; |
||||
|
||||
const Helmet = (props: HelmetProps) => ( |
||||
<NextHead> |
||||
<meta charSet='UTF-8' /> |
||||
|
||||
<title>{props.title || siteConfig.title}</title> |
||||
<meta name='description' content={props.description || siteConfig.description} /> |
||||
|
||||
<meta name='author' content={siteConfig.author} /> |
||||
<meta name='keywords' content={props.keywords ? props.keywords.join(',') : siteConfig.keywords.join(',')} /> |
||||
|
||||
<meta name='viewport' |
||||
content='width=device-width, user-scalable=yes, initial-scale=1.0, maximum-scale=3.0, minimum-scale=1.0' /> |
||||
{props.canonical && <link rel='canonical' href={props.canonical} />} |
||||
<meta httpEquiv='Content-Language' content='en' /> |
||||
|
||||
<meta property='og:title' content={props.title || siteConfig.title} /> |
||||
<meta property='og:description' content={props.description || siteConfig.description} /> |
||||
<meta property='og:image' content={`${siteConfig.url.web}${siteConfig.logoSquare}`} /> |
||||
<meta property='og:url' content={siteConfig.url.web} /> |
||||
<meta property='og:type' content='website' /> |
||||
<meta property='article:publisher' content={`https://facebook.com/${siteConfig.facebook}`} /> |
||||
<meta property='og:site_name' content={siteConfig.name} /> |
||||
<meta property='article:author' content={siteConfig.author} /> |
||||
|
||||
<meta name='twitter:card' content='summary' /> |
||||
<meta name='twitter:site' content={`@${siteConfig.twitter}`} /> |
||||
<meta name='twitter:title' content={props.title || siteConfig.title} /> |
||||
<meta name='twitter:description' content={props.description || siteConfig.description} /> |
||||
<meta name='twitter:image' content={`${siteConfig.url.web}${siteConfig.logoSquare}`} /> |
||||
<meta name='twitter:image:alt' content='roadmap.sh' /> |
||||
|
||||
<meta name='mobile-web-app-capable' content='yes' /> |
||||
<meta name='apple-mobile-web-app-capable' content='yes' /> |
||||
<meta name='apple-mobile-web-app-status-bar-style' content='black-translucent' /> |
||||
<link rel='apple-touch-icon' sizes='180x180' href='/manifest/apple-touch-icon.png' /> |
||||
<meta name='msapplication-TileColor' content='#101010' /> |
||||
<meta name='theme-color' content='#848a9a' /> |
||||
|
||||
<link rel='manifest' href='/manifest/manifest.json' /> |
||||
<link rel='icon' type='image/png' sizes='32x32' href='/manifest/icon32.png' /> |
||||
<link rel='icon' type='image/png' sizes='16x16' href='/manifest/icon16.png' /> |
||||
<link rel='shortcut icon' href='/manifest/favicon.ico' type='image/x-icon' /> |
||||
<link rel='icon' href='/manifest/favicon.ico' type='image/x-icon' /> |
||||
|
||||
{ /* Global Site Tag (gtag.js) - Google Analytics */} |
||||
{process.env.GA_SECRET && ( |
||||
<> |
||||
<script async src={`https://www.googletagmanager.com/gtag/js?id=${process.env.GA_SECRET}`} /> |
||||
<script dangerouslySetInnerHTML={{ |
||||
__html: ` |
||||
window.dataLayer = window.dataLayer || []; |
||||
function gtag(){dataLayer.push(arguments);} |
||||
gtag('js', new Date()); |
||||
gtag('config', '${process.env.GA_SECRET}'); |
||||
` |
||||
}} /> |
||||
</> |
||||
)} |
||||
|
||||
</NextHead> |
||||
); |
||||
|
||||
export default Helmet; |
||||
|
After Width: | Height: | Size: 298 B |
|
After Width: | Height: | Size: 841 B |
|
After Width: | Height: | Size: 474 B |
|
After Width: | Height: | Size: 550 B |
@ -0,0 +1,21 @@ |
||||
export function VideoIcon(props: any) { |
||||
return ( |
||||
<svg |
||||
stroke='currentColor' |
||||
fill='currentColor' |
||||
strokeWidth='0' |
||||
viewBox='0 0 24 24' |
||||
height='1em' |
||||
width='1em' |
||||
xmlns='http://www.w3.org/2000/svg' |
||||
{...props} |
||||
> |
||||
<g> |
||||
<path fill='none' d='M0 0h24v24H0z' /> |
||||
<path |
||||
d='M3 3.993C3 3.445 3.445 3 3.993 3h16.014c.548 0 .993.445.993.993v16.014a.994.994 0 0 1-.993.993H3.993A.994.994 0 0 1 3 20.007V3.993zm7.622 4.422a.4.4 0 0 0-.622.332v6.506a.4.4 0 0 0 .622.332l4.879-3.252a.4.4 0 0 0 0-.666l-4.88-3.252z' |
||||
/> |
||||
</g> |
||||
</svg> |
||||
); |
||||
} |
||||
@ -0,0 +1,47 @@ |
||||
import React from 'react'; |
||||
import { Badge, Flex, Link, Text } from '@chakra-ui/react'; |
||||
|
||||
type LinksListItemProps = { |
||||
href: string; |
||||
title: string; |
||||
subtitle: string; |
||||
badgeText?: string; |
||||
icon?: React.ReactChild; |
||||
hideSubtitleOnMobile?: boolean; |
||||
}; |
||||
|
||||
export function LinksListItem(props: LinksListItemProps) { |
||||
const { title, subtitle, badgeText, icon, hideSubtitleOnMobile = false, href } = props; |
||||
|
||||
return ( |
||||
<Link |
||||
href={href} |
||||
fontSize={['14px', '14px', '15px']} |
||||
py='9px' |
||||
d='flex' |
||||
flexDirection={['column', 'row', 'row']} |
||||
fontWeight={500} |
||||
color='gray.600' |
||||
alignItems={['flex-start', 'center']} |
||||
justifyContent={'space-between'} |
||||
_hover={{ |
||||
textDecoration: 'none', |
||||
color: 'blue.400', |
||||
'& .list-item-title': { |
||||
transform: 'translateX(10px)' |
||||
} |
||||
}} |
||||
isTruncated |
||||
maxWidth='100%' |
||||
> |
||||
<Flex alignItems='center' className='list-item-title' transition={'200ms'}> |
||||
{icon} |
||||
<Text maxWidth={'345px'} isTruncated as='span'>{title}</Text> |
||||
{badgeText && |
||||
<Badge pos='relative' top='1px' variant='subtle' colorScheme='purple' ml='10px'>{badgeText}</Badge>} |
||||
</Flex> |
||||
<Text d={[hideSubtitleOnMobile ? 'none' : 'inline', 'inline']} mt={['3px', 0]} as='span' |
||||
fontSize={['11px', '11px', '12px']} color='gray.500'>{subtitle}</Text> |
||||
</Link> |
||||
); |
||||
} |
||||
@ -0,0 +1,21 @@ |
||||
import React from 'react'; |
||||
import { StackDivider, VStack } from '@chakra-ui/react'; |
||||
|
||||
type LinksListProps = { |
||||
children: React.ReactNode |
||||
}; |
||||
|
||||
export function LinksList(props: LinksListProps) { |
||||
const { children } = props; |
||||
|
||||
return ( |
||||
<VStack |
||||
rounded='5px' |
||||
divider={<StackDivider borderColor='gray.200' />} |
||||
spacing={0} |
||||
align='stretch' |
||||
> |
||||
{children} |
||||
</VStack> |
||||
); |
||||
} |
||||
@ -0,0 +1,20 @@ |
||||
import React from 'react'; |
||||
// @ts-ignore
|
||||
import { MDXProvider } from '@mdx-js/react'; |
||||
import { ChakraProvider } from '@chakra-ui/react'; |
||||
import MdxComponents from './mdx-components'; |
||||
import { roadmapTheme } from '../../styles/theme'; |
||||
|
||||
type MdRendererType = { |
||||
children: React.ReactNode |
||||
}; |
||||
|
||||
export default function MdRenderer(props: MdRendererType) { |
||||
return ( |
||||
<ChakraProvider theme={roadmapTheme} resetCSS> |
||||
<MDXProvider components={MdxComponents}> |
||||
{props.children} |
||||
</MDXProvider> |
||||
</ChakraProvider> |
||||
); |
||||
}; |
||||
@ -0,0 +1,26 @@ |
||||
import React from 'react'; |
||||
import styled from 'styled-components'; |
||||
|
||||
type EnrichedLinkProps = { |
||||
href: string; |
||||
children: React.ReactNode |
||||
} |
||||
|
||||
const Link = styled.a` |
||||
font-weight: 600; |
||||
text-decoration: underline; |
||||
`;
|
||||
|
||||
const EnrichedLink = (props: EnrichedLinkProps) => { |
||||
// Is external URL or is a media URL
|
||||
const isExternalUrl = /(^http(s)?:\/\/)|(\.(png|svg|jpeg|jpg)$)/.test(props.href); |
||||
|
||||
return ( |
||||
<Link href={props.href} target={isExternalUrl ? '_blank' : '_self'}> |
||||
{props.children} |
||||
</Link> |
||||
); |
||||
}; |
||||
|
||||
export default EnrichedLink; |
||||
|
||||
@ -0,0 +1,22 @@ |
||||
import React from 'react'; |
||||
|
||||
type BadgeLinkType = { |
||||
target: string; |
||||
variant: string; |
||||
badgeText: string; |
||||
href: string; |
||||
children: React.ReactNode |
||||
}; |
||||
|
||||
export function BadgeLink(props: BadgeLinkType) { |
||||
const { target = '_blank', variant = 'success', badgeText, href, children } = props; |
||||
|
||||
return ( |
||||
<p className='mb-0'> |
||||
<a href={href} target={target}> |
||||
<span style={{ position: 'relative', top: '-2px' }} |
||||
className={`badge badge-${variant}`}>{badgeText}</span> {children} |
||||
</a> |
||||
</p> |
||||
); |
||||
} |
||||
@ -0,0 +1,27 @@ |
||||
import styled from 'styled-components'; |
||||
|
||||
const BlockQuote = styled.blockquote` |
||||
padding: 16px 20px; |
||||
position: relative; |
||||
background: #e8e8e8; |
||||
border-radius: 5px; |
||||
margin-bottom: 18px; |
||||
|
||||
h1, h2, h3, h4, h5, h6 { |
||||
margin-top: 0; |
||||
} |
||||
|
||||
p + h4 { |
||||
margin-top: 15px; |
||||
} |
||||
|
||||
p { |
||||
margin: 0; |
||||
|
||||
& + p { |
||||
margin-top: 10px; |
||||
} |
||||
} |
||||
`;
|
||||
|
||||
export default BlockQuote; |
||||
@ -0,0 +1,10 @@ |
||||
import React from 'react'; |
||||
import { Code as ChakraCode } from '@chakra-ui/react'; |
||||
|
||||
type CodeType = { |
||||
children: React.ReactNode; |
||||
} |
||||
|
||||
export default function Code(props: CodeType) { |
||||
return <ChakraCode bg='blue.500'>{props.children}</ChakraCode>; |
||||
} |
||||
@ -0,0 +1,81 @@ |
||||
import React from 'react'; |
||||
import styled from 'styled-components'; |
||||
import LinkIcon from 'components/icons/link.svg'; |
||||
|
||||
const linkify = (Component: React.FunctionComponent<any>) => { |
||||
return function EnrichedHeading(props: { children: string }): React.ReactNode { |
||||
const text = props.children; |
||||
const id = text.toLowerCase && text |
||||
.toLowerCase() |
||||
.replace(/[^\x00-\x7F]/g, '') |
||||
.replace(/\s+/g, '-') |
||||
.replace(/[?!]/g, ''); |
||||
|
||||
return ( |
||||
<Component id={id}> |
||||
<HeaderLink href={`#${id}`}> |
||||
<LinkIcon /> |
||||
</HeaderLink> |
||||
{props.children} |
||||
</Component> |
||||
); |
||||
}; |
||||
}; |
||||
|
||||
const HeaderLink = styled.a` |
||||
position: absolute; |
||||
top: 0; |
||||
left: -25px; |
||||
width: 25px; |
||||
display: none; |
||||
height: 100%; |
||||
align-items: center; |
||||
justify-content: flex-start; |
||||
`;
|
||||
|
||||
const H1 = styled.h1` |
||||
position: relative; |
||||
font-size: 42px; |
||||
line-height: 40px; |
||||
font-weight: 700; |
||||
margin: 32px 0 10px !important; |
||||
|
||||
&:hover ${HeaderLink} { |
||||
display: flex; |
||||
} |
||||
`;
|
||||
|
||||
const H2 = styled(H1).attrs({ as: 'h2' })` |
||||
font-size: 32px; |
||||
`;
|
||||
|
||||
const H3 = styled(H1).attrs({ as: 'h3' })` |
||||
margin: 22px 0 8px; |
||||
font-size: 30px; |
||||
`;
|
||||
|
||||
const H4 = styled(H1).attrs({ as: 'h4' })` |
||||
margin: 18px 0 8px; |
||||
font-size: 24px; |
||||
`;
|
||||
|
||||
const H5 = styled(H1).attrs({ as: 'h5' })` |
||||
margin: 14px 0 8px; |
||||
font-size: 18px; |
||||
`;
|
||||
|
||||
const H6 = styled(H1).attrs({ as: 'h6' })` |
||||
margin: 12px 0 8px; |
||||
font-size: 18px; |
||||
`;
|
||||
|
||||
const Headings = { |
||||
h1: linkify(H1), |
||||
h2: linkify(H2), |
||||
h3: linkify(H3), |
||||
h4: linkify(H4), |
||||
h5: linkify(H5), |
||||
h6: linkify(H6) |
||||
}; |
||||
|
||||
export default Headings; |
||||
@ -0,0 +1,47 @@ |
||||
import styled from 'styled-components'; |
||||
|
||||
type IFrameProps = { |
||||
title: string; |
||||
src: string; |
||||
}; |
||||
|
||||
const AspectRatioBox = styled.div` |
||||
position: relative; |
||||
max-width: 100%; |
||||
margin-bottom: 18px; |
||||
|
||||
&:before { |
||||
height: 0; |
||||
content: ""; |
||||
display: block; |
||||
padding-bottom: 50%; |
||||
} |
||||
|
||||
& > iframe { |
||||
overflow: hidden; |
||||
position: absolute; |
||||
top: 0; |
||||
right: 0; |
||||
bottom: 0; |
||||
left: 0; |
||||
display: flex; |
||||
justify-content: center; |
||||
align-items: center; |
||||
width: 100%; |
||||
height: 100%; |
||||
} |
||||
`;
|
||||
|
||||
export default function IFrame(props: IFrameProps) { |
||||
return ( |
||||
<AspectRatioBox> |
||||
<iframe |
||||
frameBorder={0} |
||||
title={props.title} |
||||
src={props.src} |
||||
allow={'accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture'} |
||||
allowFullScreen |
||||
/> |
||||
</AspectRatioBox> |
||||
); |
||||
} |
||||
@ -0,0 +1,7 @@ |
||||
import styled from 'styled-components'; |
||||
|
||||
export const Img = styled.img` |
||||
max-width: 100%; |
||||
margin: 25px auto; |
||||
display: block; |
||||
`;
|
||||
@ -0,0 +1,30 @@ |
||||
import { Code } from '@chakra-ui/react'; |
||||
import { P } from './p'; |
||||
import Headings from './heading'; |
||||
import { Pre } from './pre'; |
||||
import BlockQuote from './blockquote'; |
||||
import { Table } from './table'; |
||||
import IFrame from './iframe'; |
||||
import { Img } from './img'; |
||||
import EnrichedLink from './a'; |
||||
import { BadgeLink } from './badge-link'; |
||||
import { Li, Ul } from './ul'; |
||||
import PremiumBlock from './premium-block'; |
||||
|
||||
const MdxComponents = { |
||||
p: P, |
||||
...Headings, |
||||
pre: Pre, |
||||
blockquote: BlockQuote, |
||||
a: EnrichedLink, |
||||
table: Table, |
||||
iframe: IFrame, |
||||
img: Img, |
||||
code: Code, |
||||
BadgeLink: BadgeLink, |
||||
PremiumBlock: PremiumBlock, |
||||
ul: Ul, |
||||
li: Li |
||||
}; |
||||
|
||||
export default MdxComponents; |
||||
@ -0,0 +1,14 @@ |
||||
import React from 'react'; |
||||
import { Text } from '@chakra-ui/react'; |
||||
import styled from 'styled-components'; |
||||
|
||||
type EnrichedTextType = { |
||||
children: React.ReactNode; |
||||
} |
||||
|
||||
export const P = styled.p` |
||||
line-height: 27px; |
||||
font-size: 16px; |
||||
color: black; |
||||
margin-bottom: 18px; |
||||
`;
|
||||
@ -0,0 +1,12 @@ |
||||
import styled from 'styled-components'; |
||||
|
||||
export const Pre = styled.pre` |
||||
margin: 25px -25px 25px -25px !important; |
||||
padding: 20px 25px !important; |
||||
border-radius: 10px; |
||||
line-height: 1.5 !important; |
||||
|
||||
code { |
||||
background: transparent; |
||||
} |
||||
`;
|
||||
@ -0,0 +1,19 @@ |
||||
import React from 'react'; |
||||
import { Box, Button, Heading, Text } from '@chakra-ui/react'; |
||||
import { LockIcon } from '@chakra-ui/icons'; |
||||
|
||||
type PremiumBlockProps = { |
||||
title: string; |
||||
description: string; |
||||
}; |
||||
|
||||
export default function PremiumBlock(props: PremiumBlockProps) { |
||||
return ( |
||||
<Box p='40px' textAlign='center' rounded='5px' mb='18px' bg='gray.50' borderWidth={1}> |
||||
<LockIcon color='gray.300' height='45px' w='45px' mb='18px' /> |
||||
<Heading as='h3' fontSize='30px' mb='10px'>{props.title}</Heading> |
||||
<Text mb='18px'>{props.description}</Text> |
||||
<Button colorScheme='green'>Become a Member</Button> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,25 @@ |
||||
import styled from 'styled-components'; |
||||
|
||||
export const Table = styled.table` |
||||
border-collapse: separate; |
||||
width: 100%; |
||||
border-spacing: 0; |
||||
margin: 20px 0; |
||||
|
||||
th { |
||||
color: #666; |
||||
font-size: 12px; |
||||
font-weight: 400; |
||||
background: #FAFAFA; |
||||
text-transform: uppercase; |
||||
height: 40px; |
||||
vertical-align: middle; |
||||
padding: 5px 10px; |
||||
} |
||||
|
||||
td { |
||||
font-size: 14px; |
||||
padding: 10px; |
||||
border-bottom: 1px solid #EAEAEA; |
||||
} |
||||
`;
|
||||
@ -0,0 +1,12 @@ |
||||
import React from 'react'; |
||||
import { UnorderedList } from '@chakra-ui/react'; |
||||
import styled from 'styled-components'; |
||||
|
||||
export const Ul = styled.ul` |
||||
margin-left: 40px; |
||||
margin-bottom: 18px; |
||||
`;
|
||||
|
||||
export const Li = styled.li` |
||||
margin-bottom: 7px; |
||||
`;
|
||||
@ -0,0 +1,46 @@ |
||||
import { Box, Container, Heading, Link, Text } from '@chakra-ui/react'; |
||||
|
||||
export function OpensourceBanner() { |
||||
return ( |
||||
<Box borderTopWidth={1} pt={['45px', '45px', '70px']} pb={['20px', '20px', '30px']} textAlign='center'> |
||||
<Container maxW='container.md'> |
||||
<Heading fontSize={['25px', '25px', '35px']} mb={['10px', '10px', '20px']}>Open Source</Heading> |
||||
<Text lineHeight='26px' fontSize={['15px', '15px', '16px']} mb='20px'>The project is OpenSource, |
||||
<Link |
||||
_hover={{ textDecoration: 'none' }} |
||||
href='https://github.com/search?o=desc&q=stars%3A%3E100000&s=stars&type=Repositories' |
||||
target='_blank' |
||||
borderBottomWidth={1} |
||||
fontWeight={600} |
||||
>7th most starred project on GitHub</Link> and is visited by hundreds of thousands of |
||||
developers every month.</Text> |
||||
<iframe |
||||
src='https://ghbtns.com/github-btn.html?user=kamranahmedse&repo=developer-roadmap&type=star&count=true&size=large' |
||||
frameBorder='0' |
||||
scrolling='0' |
||||
width='170' |
||||
height='30' |
||||
style={{ margin: 'auto', marginBottom: '30px' }} |
||||
title='GitHub' |
||||
/> |
||||
|
||||
<Text lineHeight={['25px', '25px', '26px']} fontSize={['15px', '15px', '16px']} mb='15px'>A considerable amount of my time is spent doing unpaid |
||||
community work on things that I hope will help humanity in some way. Your sponsorship helps me continue to |
||||
produce more open-source and free educational material consumed by hundreds of thousands of developers every |
||||
month.</Text> |
||||
|
||||
<Box> |
||||
<iframe |
||||
src='https://ghbtns.com/github-btn.html?user=kamranahmedse&type=sponsor&size=large' |
||||
frameBorder='0' |
||||
scrolling='0' |
||||
width='260' |
||||
height='30' |
||||
title='GitHub' |
||||
style={{ margin: 'auto' }} |
||||
/> |
||||
</Box> |
||||
</Container> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,35 @@ |
||||
import { Box, Container, Heading, Text } from '@chakra-ui/react'; |
||||
import React from 'react'; |
||||
|
||||
type PageHeaderProps = { |
||||
title: string; |
||||
subtitle: string; |
||||
children?: React.ReactNode; |
||||
}; |
||||
|
||||
export function PageHeader(props: PageHeaderProps) { |
||||
const { title, subtitle, children } = props; |
||||
|
||||
return ( |
||||
<Box pt={['25px', '20px', '45px']} pb={['20px', '15px', '30px']} borderBottomWidth={1} mb='30px'> |
||||
<Container maxW='container.md' position='relative'> |
||||
<Heading |
||||
as='h1' |
||||
color='black' |
||||
fontSize={['33px', '33px', '40px']} |
||||
fontWeight={700} |
||||
mb={['2px', '2px', '5px']} |
||||
> |
||||
{title} |
||||
</Heading> |
||||
<Text fontSize={['14px', '14px', '15px']}>{subtitle}</Text> |
||||
</Container> |
||||
|
||||
{children && ( |
||||
<Container maxW='container.md'> |
||||
{children} |
||||
</Container> |
||||
)} |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,47 @@ |
||||
import { Box, Heading, Link, Text, Tooltip } from '@chakra-ui/react'; |
||||
import { InfoIcon } from '@chakra-ui/icons'; |
||||
|
||||
type RoadmapGridItemProps = { |
||||
title: string; |
||||
subtitle: string; |
||||
isCommunity?: boolean; |
||||
colorIndex?: number; |
||||
url: string; |
||||
}; |
||||
|
||||
const bgColorList = [ |
||||
'blue.900', |
||||
'red.800', |
||||
'green.800', |
||||
'teal.800', |
||||
'gray.800', |
||||
'red.900' |
||||
]; |
||||
|
||||
export function HomeRoadmapItem(props: RoadmapGridItemProps) { |
||||
const { title, subtitle, isCommunity, colorIndex = 0, url } = props; |
||||
|
||||
return ( |
||||
<Box |
||||
as={Link} |
||||
href={url} |
||||
_hover={{ textDecoration: 'none', transform: 'scale(1.02)' }} |
||||
flex={1} |
||||
shadow='2xl' |
||||
bg={bgColorList[colorIndex] ?? bgColorList[0]} |
||||
color='white' |
||||
p='15px' |
||||
rounded='10px' |
||||
pos='relative' |
||||
> |
||||
{isCommunity && ( |
||||
<Tooltip label={'Community contribution'} hasArrow placement='top'> |
||||
<InfoIcon opacity={0.5} position='absolute' top='10px' right='10px' /> |
||||
</Tooltip> |
||||
)} |
||||
|
||||
<Heading fontSize={['17px', '17px', '22px']} mb='5px'>{title}</Heading> |
||||
<Text color='gray.200' fontSize={['13px']}>{subtitle}</Text> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,89 @@ |
||||
import { Badge, Box, Flex, Heading, Link, Text, Tooltip } from '@chakra-ui/react'; |
||||
import { InfoIcon } from '@chakra-ui/icons'; |
||||
|
||||
type RoadmapGridItemProps = { |
||||
title: string; |
||||
subtitle: string; |
||||
href: string; |
||||
isCommunity?: boolean; |
||||
isUpcoming?: boolean; |
||||
colorIndex?: number; |
||||
}; |
||||
|
||||
const bgColorList = [ |
||||
'gray.900', |
||||
'purple.900', |
||||
'blue.900', |
||||
'red.900', |
||||
'green.900', |
||||
'teal.900', |
||||
'yellow.900', |
||||
'cyan.900', |
||||
'pink.900', |
||||
|
||||
'gray.800', |
||||
'purple.800', |
||||
'blue.800', |
||||
'red.800', |
||||
'green.800', |
||||
'teal.800', |
||||
'yellow.800', |
||||
'cyan.800', |
||||
'pink.800', |
||||
|
||||
'gray.700', |
||||
'purple.700', |
||||
'blue.700', |
||||
'red.700', |
||||
'green.700', |
||||
'teal.700', |
||||
'yellow.700', |
||||
'cyan.700', |
||||
'pink.700', |
||||
|
||||
'gray.600', |
||||
'purple.600', |
||||
'blue.600', |
||||
'red.600', |
||||
'green.600', |
||||
'teal.600', |
||||
'yellow.600', |
||||
'cyan.600', |
||||
'pink.600' |
||||
]; |
||||
|
||||
export function RoadmapGridItem(props: RoadmapGridItemProps) { |
||||
const { title, subtitle, isCommunity = false, isUpcoming = false, colorIndex = 0, href = '/' } = props; |
||||
|
||||
return ( |
||||
<Box _hover={{ textDecoration: 'none', transform: 'scale(1.02)' }} as={Link} href={href} shadow='xl' p='20px' |
||||
rounded='10px' bg={bgColorList[colorIndex] ?? bgColorList[0]} flex={1} pos='relative'> |
||||
|
||||
{isCommunity && ( |
||||
<Tooltip label={'Community contribution'} hasArrow placement='top'> |
||||
<InfoIcon opacity={0.5} color='gray.100' position='absolute' top='10px' right='10px' /> |
||||
</Tooltip> |
||||
)} |
||||
|
||||
<Heading color='white' mb={'6px'} fontSize='20px'>{title}</Heading> |
||||
<Text color='gray.300' fontSize='14px'>{subtitle}</Text> |
||||
|
||||
{isUpcoming && ( |
||||
<Flex |
||||
alignItems='center' |
||||
justifyContent='center' |
||||
pos='absolute' |
||||
left={0} |
||||
right={0} |
||||
top={0} |
||||
bottom={0} |
||||
rounded='10px' |
||||
> |
||||
<Text color='white' bg='yellow.900' zIndex={1} fontWeight={600} p={'5px 10px'} |
||||
rounded='10px'>Upcoming</Text> |
||||
<Box bg={'black'} pos='absolute' top={0} left={0} right={0} bottom={0} rounded={'10px'} opacity={0.5} /> |
||||
</Flex> |
||||
)} |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,40 @@ |
||||
import { Box, Button, Container, Flex, Heading, Link, Text } from '@chakra-ui/react'; |
||||
import siteConfig from '../content/site.json'; |
||||
|
||||
export function UpdatesBanner() { |
||||
return ( |
||||
<Box borderTopWidth={1} mt='60px' pt={['40px', '40px', '70px']} pb={['40px', '45px', '80px']} textAlign='left' |
||||
bg='gray.800'> |
||||
<Container maxW='container.md'> |
||||
<Heading color={'gray.100'} fontSize={['25px', '25px', '35px']} mb={['5px', '5px', '15px']}>Stay |
||||
Informed</Heading> |
||||
<Text color='gray.400' lineHeight='26px' fontSize={['15px', '15px', '16px']} mb='20px'>Subscribe yourself to get |
||||
updates, new |
||||
guides, videos and roadmaps in your inbox.</Text> |
||||
|
||||
<Flex flexDirection={['column', 'column', 'row']}> |
||||
<Box mr={['0', '0', '20px']} mb={['15px', '15px', 0]}> |
||||
<Button as={Link} href='/signup' width={['full', 'auto']} fontSize={['14px', '14px', '16px']} |
||||
variant='outline' borderWidth={2} |
||||
colorScheme='green' _hover={{ color: 'green.200', textDecoration: 'none' }}> |
||||
Subscribe to Updates |
||||
</Button> |
||||
<Text color='gray.500' fontSize='13px' mt='5px'>Free subscription for updates</Text> |
||||
</Box> |
||||
<Box> |
||||
<Button as={Link} |
||||
href={siteConfig.url.sponsor} |
||||
target='_blank' |
||||
width={['full', 'auto']} |
||||
fontSize={['14px', '14px', '16px']} |
||||
_hover={{ textDecoration: 'none', bg: 'yellow.500' }} |
||||
colorScheme='yellow'>Updates & Paid Content</Button> |
||||
<Text color='gray.500' fontSize='13px' mt='5px'>Support the project by paying as little as <Text as='span' |
||||
fontWeight={600}>5$ |
||||
per month</Text></Text> |
||||
</Box> |
||||
</Flex> |
||||
</Container> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,70 @@ |
||||
import { Badge, Box, Heading, Link, Text } from '@chakra-ui/react'; |
||||
|
||||
type VideoGridItemProps = { |
||||
href: string; |
||||
title: string; |
||||
subtitle: string; |
||||
date: string; |
||||
isNew?: boolean; |
||||
isPro?: boolean; |
||||
colorIndex?: number; |
||||
}; |
||||
|
||||
const bgColorList = [ |
||||
'gray.900', |
||||
'purple.900', |
||||
'blue.900', |
||||
'red.900', |
||||
'green.900', |
||||
'teal.900', |
||||
'yellow.900', |
||||
'cyan.900', |
||||
'pink.900', |
||||
|
||||
'gray.800', |
||||
'purple.800', |
||||
'blue.800', |
||||
'red.800', |
||||
'green.800', |
||||
'teal.800', |
||||
'yellow.800', |
||||
'cyan.800', |
||||
'pink.800', |
||||
|
||||
'gray.700', |
||||
'purple.700', |
||||
'blue.700', |
||||
'red.700', |
||||
'green.700', |
||||
'teal.700', |
||||
'yellow.700', |
||||
'cyan.700', |
||||
'pink.700', |
||||
|
||||
'gray.600', |
||||
'purple.600', |
||||
'blue.600', |
||||
'red.600', |
||||
'green.600', |
||||
'teal.600', |
||||
'yellow.600', |
||||
'cyan.600', |
||||
'pink.600' |
||||
]; |
||||
|
||||
export function VideoGridItem(props: VideoGridItemProps) { |
||||
const { title, subtitle, date, isNew = false, isPro = false, colorIndex = 0, href } = props; |
||||
|
||||
return ( |
||||
<Box _hover={{ textDecoration: 'none', transform: 'scale(1.02)' }} as={Link} href={ href } shadow='xl' p='20px' |
||||
rounded='10px' bg={bgColorList[colorIndex] ?? bgColorList[0]} flex={1}> |
||||
<Text mb='7px' fontSize='12px' color='gray.400'> |
||||
{isNew && <Badge colorScheme={'yellow'} mr='10px'>New</Badge>} |
||||
{isPro && <Badge colorScheme={'blue'} mr='10px'>PRO</Badge>} |
||||
{date} |
||||
</Text> |
||||
<Heading color='white' mb={'6px'} fontSize='20px' lineHeight={'28px'}>{title}</Heading> |
||||
<Text color='gray.300' fontSize='14px'>{subtitle}</Text> |
||||
</Box> |
||||
); |
||||
} |
||||
@ -0,0 +1,43 @@ |
||||
[ |
||||
{ |
||||
"username": "kamranahmedse", |
||||
"name": "Kamran Ahmed", |
||||
"twitter": "kamranahmedse", |
||||
"picture": "/authors/kamranahmedse.jpeg", |
||||
"bio": "Lead engineer at Tajawal. Lover of all things web and opensource. Created roadmap.sh to help the confused ones." |
||||
}, |
||||
{ |
||||
"username": "jesse", |
||||
"name": "Jesse Li", |
||||
"twitter": "__jesse_li", |
||||
"picture": "/authors/jesse.png", |
||||
"bio": "Software engineer." |
||||
}, |
||||
{ |
||||
"username": "dmytrobol", |
||||
"name": "Dmytro Bolkachov", |
||||
"twitter": "dmytrobol", |
||||
"picture": "/authors/dmytrobol.png", |
||||
"bio": "JavaScript Lad, Movie buff and coder interested in everything web related" |
||||
}, |
||||
{ |
||||
"username": "spekulatius", |
||||
"name": "Peter Thaleikis", |
||||
"twitter": "spekulatius1984", |
||||
"picture": "/authors/spekulatius.jpg", |
||||
"bio": "Developer building side-projects for fun, lover of the web and open source" |
||||
}, |
||||
{ |
||||
"username": "ebrahimbharmal007", |
||||
"name": "Ebrahim Bharmal", |
||||
"twitter": "BharmalEbrahim", |
||||
"picture": "/authors/ebrahimbharmal007.png", |
||||
"bio": "Love building projects using tools completely new to me. Python forever. Senior at University of Texas at Arlington (2021)" |
||||
}, |
||||
{ |
||||
"username": "lesovsky", |
||||
"name": "Alexey Lesovsky", |
||||
"bio": "Linux system administrator and PostgreSQL DBA at DataEgret.", |
||||
"picture": "/authors/lesovsky.jpeg" |
||||
} |
||||
] |
||||
@ -0,0 +1,229 @@ |
||||
[ |
||||
{ |
||||
"id": "ci-cd", |
||||
"title": "What is CI and CD?", |
||||
"description": "Learn the basics of CI/CD and how to implement that with GitHub Actions.", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-07-09T19:59:14.191Z", |
||||
"createdAt": "2020-07-09T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "sso", |
||||
"title": "SSO — Single Sign On", |
||||
"description": "Learn the basics of SAML and understand how does Single Sign On work.", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-07-01T19:59:14.191Z", |
||||
"createdAt": "2020-07-01T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "oauth", |
||||
"title": "OAuth — Open Authorization", |
||||
"description": "Learn and understand what is OAuth and how it works", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-06-28T19:59:14.191Z", |
||||
"createdAt": "2020-06-28T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "jwt-authentication", |
||||
"title": "JWT Authentication", |
||||
"description": "Understand what is JWT authentication and how is it implemented", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-06-20T19:59:14.191Z", |
||||
"createdAt": "2020-06-20T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "token-authentication", |
||||
"title": "Token Based Authentication", |
||||
"description": "Understand what is token based authentication and how it is implemented", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-06-02T20:59:14.191Z", |
||||
"createdAt": "2020-06-02T20:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "session-authentication", |
||||
"title": "Session Based Authentication", |
||||
"description": "Understand what is session based authentication and how it is implemented", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-05-26T20:59:14.191Z", |
||||
"createdAt": "2020-05-26T20:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "basic-authentication", |
||||
"title": "Basic Authentication", |
||||
"description": "Understand what is basic authentication and how it is implemented", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-05-19T20:59:14.191Z", |
||||
"createdAt": "2020-05-19T20:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "character-encodings", |
||||
"title": "Character Encodings", |
||||
"description": "Covers the basics of character encodings and explains ASCII vs Unicode", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-05-14T20:59:14.191Z", |
||||
"createdAt": "2020-05-14T20:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "unfamiliar-codebase", |
||||
"title": "Unfamiliar Codebase", |
||||
"description": "Tips on getting getting familiar with an unfamiliar codebase", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-05-04T20:59:14.191Z", |
||||
"createdAt": "2020-05-04T20:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "why-build-it-and-they-will-come-wont-work-anymore", |
||||
"title": "Build it and they will come?", |
||||
"description": "Why “build it and they will come” alone won’t work anymore", |
||||
"isPro": false, |
||||
"authorUsername": "spekulatius", |
||||
"updatedAt": "2020-05-04T12:59:14.191Z", |
||||
"createdAt": "2020-05-04T12:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "dhcp-in-one-picture", |
||||
"title": "DHCP in One Picture", |
||||
"description": "Here is what happens when a new device joins the network.", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-04-28T15:48:21.191Z", |
||||
"createdAt": "2020-04-28T15:48:21.191Z" |
||||
}, |
||||
{ |
||||
"id": "ssl-tls-https-ssh", |
||||
"title": "SSL vs TLS vs SSH", |
||||
"description": "Quick tidbit on the differences between SSL, TLS, HTTPS and SSH", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-04-22T15:48:21.191Z", |
||||
"createdAt": "2020-04-22T15:48:21.191Z" |
||||
}, |
||||
{ |
||||
"id": "asymptotic-notation", |
||||
"title": "Asymptotic Notation", |
||||
"description": "Learn the basics of measuring the time and space complexity of algorithms", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-04-03T15:48:21.191Z", |
||||
"createdAt": "2020-04-03T15:48:21.191Z" |
||||
}, |
||||
{ |
||||
"id": "big-o-notation", |
||||
"title": "Big-O Notation", |
||||
"description": "Easy to understand explanation of Big-O notation without any fancy terms", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-03-15T15:48:21.191Z", |
||||
"createdAt": "2020-03-15T15:48:21.191Z" |
||||
}, |
||||
{ |
||||
"id": "random-numbers", |
||||
"title": "Random Numbers: Are they?", |
||||
"description": "Learn how they are generated and why they may not be truly random.", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-03-14T15:48:21.191Z", |
||||
"createdAt": "2020-03-14T15:48:21.191Z" |
||||
}, |
||||
{ |
||||
"id": "scaling-databases", |
||||
"title": "Scaling Databases", |
||||
"description": "Learn the ups and downs of different database scaling strategies", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2020-02-18T15:48:21.191Z", |
||||
"createdAt": "2020-02-18T15:48:21.191Z" |
||||
}, |
||||
{ |
||||
"id": "what-is-internet", |
||||
"title": "How does the internet work?", |
||||
"description": "Learn the basics of internet and everything involved with this short video series", |
||||
"isPro": false, |
||||
"authorUsername": "dmytrobol", |
||||
"updatedAt": "2020-02-29T15:48:21.191Z", |
||||
"createdAt": "2020-02-29T15:48:21.191Z" |
||||
}, |
||||
{ |
||||
"id": "torrent-client", |
||||
"title": "Building a BitTorrent Client", |
||||
"description": "Learn everything you need to know about BitTorrent by writing a client in Go", |
||||
"isPro": false, |
||||
"authorUsername": "jesse", |
||||
"updatedAt": "2020-01-17T15:48:21.191Z", |
||||
"createdAt": "2020-01-17T15:48:21.191Z", |
||||
"canonical": "https://blog.jse.li/posts/torrent/" |
||||
}, |
||||
{ |
||||
"id": "levels-of-seniority", |
||||
"title": "Levels of Seniority", |
||||
"description": "How to Step Up as a Junior, Mid Level or a Senior Developer?", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2019-12-03T12:13:00.860Z", |
||||
"createdAt": "2019-12-03T12:13:00.860Z" |
||||
}, |
||||
{ |
||||
"id": "design-patterns-for-humans", |
||||
"title": "Design Patterns for Humans", |
||||
"description": "A language agnostic, ultra-simplified explanation to design patterns", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2019-10-09T12:00:00.860Z", |
||||
"createdAt": "2019-01-23T17:00:00.860Z" |
||||
}, |
||||
{ |
||||
"id": "journey-to-http2", |
||||
"title": "Journey to HTTP/2", |
||||
"description": "The evolution of HTTP. How it all started and where we stand today", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"createdAt": "2018-12-04T12:00:00.860Z", |
||||
"updatedAt": "2018-12-04T12:00:00.860Z", |
||||
"isDraft": true |
||||
}, |
||||
{ |
||||
"id": "dns-in-one-picture", |
||||
"title": "DNS in One Picture", |
||||
"description": "Quick illustrative guide on how a website is found on the internet.", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"updatedAt": "2018-12-04T12:00:00.860Z", |
||||
"createdAt": "2018-12-04T17:00:00.860Z" |
||||
}, |
||||
{ |
||||
"id": "http-caching", |
||||
"title": "HTTP Caching", |
||||
"description": "Everything you need to know about web caching", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"createdAt": "2018-11-29T17:00:00.860Z", |
||||
"updatedAt": "2018-11-29T17:00:00.860Z" |
||||
}, |
||||
{ |
||||
"id": "history-of-javascript", |
||||
"title": "Brief History of JavaScript", |
||||
"description": "How JavaScript was introduced and evolved over the years", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"createdAt": "2017-10-28T17:00:00.860Z", |
||||
"updatedAt": "2017-10-28T17:00:00.860Z" |
||||
}, |
||||
{ |
||||
"id": "proxy-servers", |
||||
"title": "Proxy Servers", |
||||
"description": "How do proxy servers work and what are forward and reverse proxies?", |
||||
"isPro": false, |
||||
"authorUsername": "ebrahimbharmal007", |
||||
"createdAt": "2020-07-24T12:40:18", |
||||
"updatedAt": "2020-07-24T12:40:18" |
||||
} |
||||
] |
||||
@ -0,0 +1,16 @@ |
||||
export const guideMeta = { |
||||
"title": "WebStorm — Project History", |
||||
"description": "Learn how to peek through the history of any git repository to learn how it grew.", |
||||
"url": "/guides/project-history", |
||||
"fileName": "project-history", |
||||
"featured": true, |
||||
"author": "kamranahmedse", |
||||
"updatedAt": "2020-07-16T19:59:14.191Z", |
||||
"createdAt": "2020-07-16T19:59:14.191Z" |
||||
}; |
||||
|
||||
Asymptotic notation is the standard way of measuring the time and space that an algorithm will consume as the input grows. In one of my last guides, I covered "Big-O notation" and a lot of you asked for a similar one for Asymptotic notation. You can find the [previous guide here](/guides/big-o-notation). |
||||
|
||||
[](/guides/asymptotic-notation.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1243861514907418624) where this image was posted. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/basic-authentication.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1261783266044063748) where this image was posted. |
||||
@ -0,0 +1,5 @@ |
||||
Big-O notation is the mathematical notation that helps analyse the algorithms to get an idea about how they might perform as the input grows. The image below explains Big-O in a simple way without using any fancy terminology. |
||||
|
||||
[](/guides/big-o-notation.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1235708842610212864) where this image was posted. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/character-encodings.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1259631582362689537) where this image was posted. |
||||
@ -0,0 +1,5 @@ |
||||
The image below details the differences between the continuous integration and continuous delivery. Also, here is the [accompanying video on implementing that with GitHub actions](https://www.youtube.com/watch?v=nyKZTKQS_EQ). |
||||
|
||||
[](/guides/ci-cd.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1282806173939511298) where this image was posted. |
||||
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,3 @@ |
||||
[](/guides/dhcp.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1254142557417857025) where this image was posted. |
||||
@ -0,0 +1,5 @@ |
||||
DNS or Domain Name System is one of the fundamental blocks of the internet. As a developer, you should have at-least the basic understanding of how it works. This article is a brief introduction to what is DNS and how it works. |
||||
|
||||
DNS at its simplest is like a phonebook on your mobile phone. Whenever you have to call one of your contacts, you can either dial their number from your memory or use their name which will then be used by your mobile phone to search their number in your phone book to call them. Every time you make a new friend, or your existing friend gets a mobile phone, you have to memorize their phone number or save it in your phonebook to be able to call them later on. DNS or Domain Name System, in a similar fashion, is a mechanism that allows you to browse websites on the internet. Just like your mobile phone does not know how to call without knowing the phone number, your browser does not know how to open a website just by the domain name; it needs to know the IP Address for the website to open. You can either type the IP Address to open, or provide the domain name and press enter which will then be used by your browser to find the IP address by going through several hoops. The picture below is the illustration of how your browser finds a website on the internet. |
||||
|
||||
[](https://i.imgur.com/z9rwm5A.png) |
||||
@ -0,0 +1,41 @@ |
||||
Around 10 years ago, Jeff Atwood (the founder of stackoverflow) made a case that JavaScript is going to be the future and he coined the “Atwood Law” which states that *Any application that can be written in JavaScript will eventually be written in JavaScript*. Fast-forward to today, 10 years later, if you look at it it rings truer than ever. JavaScript is continuing to gain more and more adoption. |
||||
|
||||
### JavaScript is announced |
||||
JavaScript was initially created by [Brendan Eich](https://twitter.com/BrendanEich) of NetScape and was first announced in a press release by Netscape in 1995. It has a bizarre history of naming; initally it was named `Mocha` by the creator, which was later renamed to `LiveScript`. In 1996, about a year later after the release, NetScape decided to rename it to be `JavaScript` with hopes of capitalizing on the Java community (although JavaScript did not have any relationship with Java) and released Netscape 2.0 with the official support of JavaScript. |
||||
|
||||
### ES1, ES2 and ES3 |
||||
In 1996, Netscape decided to submit it to [ECMA International](https://en.wikipedia.org/wiki/Ecma_International) with the hopes of getting it standardized. First edition of the standard specification was released in 1997 and the language was standardized. After the initial release, `ECMAScript` was continued to be worked upon and in no-time two more versions were released ECMAScript 2 in 1998 and ECMAScript 3 in 1999. |
||||
|
||||
### Decade of Silence and ES4 |
||||
After the release of ES3 in 1999, there was a complete silence for a decade and no changes were made to the official standard. There was some work on the fourth edition in the initial days; some of the features that were being discussed included classes, modules, static typings, destructuring etc. It was being targeted to be released by 2008 but was abandoned due to political differences concerning language complexity. However, the vendors kept introducing the extensions to the language and the developers were left scratching their heads — adding polyfills to battle compatibility issues between different browsers. |
||||
|
||||
### From silence to ES5 |
||||
Google, Microsoft, Yahoo and other disputers of ES4 came together and decided to work on a less ambitious update to ES3 tentatively named ES3.1. But the teams were still fighting about what to include from ES4 and what not. Finally, in 2009 ES5 was released mainly focusing on fixing the compatibility and security issues etc. But there wasn’t much of a splash in the water — it took ages for the vendors to incorporate the standards and many developers were still using ES3 without being aware of the “modern” standards. |
||||
|
||||
### Release of ES6 — ECMAScript 2015 |
||||
After a few years of the release of ES5, things started to change, TC39 (the committee under ECMA international responsible for ECMAScript standardization) kept working on the next version of ECMAScript (ES6) which was originally named ES Harmony, before being eventually released with the name ES2015. ES2015 adds significant features and syntactic sugar to allow writing complex applications. Some of the features that ES6 has to offer, include Classes, Modules, Arrows, Enhanced object literals, Template strings, Destructuring, Default param values + rest + spread, Let and Const, Iterators + for..of, Generators, Maps + Sets, Proxies, Symbols, Promises, math + number + string + array + object APIs [etc](http://es6-features.org/#Constants) |
||||
|
||||
Browser support for ES6 is still scarce but everything that ES6 has to offer is still available to developers by transpiling the ES6 code to ES5. With the release of 6th version of ECMAScript, TC39 decided to move to yearly model of releasing updates to ECMAScript so to make sure that the new features are added as soon as they are approved and we don’t have to wait for the full specification to be drafted and approved — thus 6th version of ECMAScript was renamed as ECMAScript 2015 or ES2015 before the release in June 2015. And the next versions of ECMAScript were decided to published in June of every year. |
||||
|
||||
### Release of ES7 — ECMAScript 2016 |
||||
In June 2016, seventh version of ECMAScript was released. As ECMAScript has been moved to an yearly release model, ECMAScript 2016 (ES2016) comparatively did not have much to offer. ES2016 includes just two new features |
||||
|
||||
* Exponentiation operator `**` |
||||
* `Array.prototype.includes` |
||||
|
||||
### Release of ES8 — ECMAScript 2017 |
||||
The eighth version of ECMAScript was released in June 2017. The key highlight of ES8 was the addition of async functions. Here is the list of new features in ES8 |
||||
|
||||
* `Object.values()` and `Object.entries()` |
||||
* String padding i.e. `String.prototype.padEnd()` and `String.prototype.padStart()` |
||||
* `Object.getOwnPropertyDescriptors` |
||||
* Trailing commas in function parameter lists and calls |
||||
* Async functions |
||||
|
||||
### What is ESNext then? |
||||
ESNext is a dynamic name that refers to whatever the current version of ECMAScript is at the given time. For example, at the time of this writing `ES2017` or `ES8` is `ESNext`. |
||||
|
||||
### What does the future hold? |
||||
Since the release of ES6, [TC39](https://github.com/tc39) has quite streamlined their process. TC39 operates through a Github organization now and there are [several proposals](https://github.com/tc39/proposals) for new features or syntax to be added to the next versions of ECMAScript. Any one can go ahead and [submit a proposal](https://github.com/tc39/proposals) thus resulting in increasing the participation from the community. Every proposal goes through [four stages of maturity](https://tc39.github.io/process-document/) before it makes it into the specification. |
||||
|
||||
And that about wraps it up. Feel free to leave your feedback in the comments section below. Also here are the links to original language specifications [ES6](https://www.ecma-international.org/ecma-262/6.0/), [ES7](https://www.ecma-international.org/ecma-262/7.0/) and [ES8](https://www.ecma-international.org/ecma-262/8.0/). |
||||
@ -0,0 +1,251 @@ |
||||
As users, we easily get frustrated by the buffering videos, the images that take seconds to load, pages that got stuck because the content is being loaded. Loading the resources from some cache is much faster than fetching the same from the originating server. It reduces latency, speeds up the loading of resources, decreases the load on server, cuts down the bandwidth costs etc. |
||||
|
||||
### Introduction |
||||
|
||||
What is web cache? It is something that sits somewhere between the client and the server, continuously looking at the requests and their responses, looking for any responses that can be cached. So that there is less time consumed when the same request is made again. |
||||
|
||||
 |
||||
|
||||
> Note that this image is just to give you an idea. Depending upon the type of cache, the place where it is implemented could vary. More on this later. |
||||
|
||||
Before we get into further details, let me give you an overview of the terms that will be used, further in the article |
||||
|
||||
- **Client** could be your browser or any application requesting the server for some resource |
||||
- **Origin Server**, the source of truth, houses all the content required by the client and is responsible for fulfilling the client requests. |
||||
- **Stale Content** is the cached but expired content |
||||
- **Fresh Content** is the content available in cache that hasn't expired yet |
||||
- **Cache Validation** is the process of contacting the server to check the validity of the cached content and get it updated for when it is going to expire |
||||
- **Cache Invalidation** is the process of removing any stale content available in the cache |
||||
|
||||
 |
||||
|
||||
### Caching Locations |
||||
|
||||
Web cache can be shared or private depending upon the location where it exists. Here is the list of different caching locations |
||||
|
||||
- [Browser Cache](#browser-cache) |
||||
- [Proxy Cache](#proxy-cache) |
||||
- [Reverse Proxy Cache](#reverse-proxy-cache) |
||||
|
||||
#### Browser Cache |
||||
|
||||
You might have noticed that when you click the back button in your browser it takes less time to load the page than the time that it took during the first load; this is the browser cache in play. Browser cache is the most common location for caching and browsers usually reserve some space for it. |
||||
|
||||
 |
||||
|
||||
A browser cache is limited to just one user and unlike other caches, it can store the "private" responses. More on it later. |
||||
|
||||
#### Proxy Cache |
||||
|
||||
Unlike browser cache which serves a single user, proxy caches may serve hundreds of different users accessing the same content. They are usually implemented on a broader level by ISPs or any other independent entities for example. |
||||
|
||||
 |
||||
|
||||
#### Reverse Proxy Cache |
||||
|
||||
Reverse proxy cache or surrogate cache is implemented close to the origin servers in order to reduce the load on server. Unlike proxy caches which are implemented by ISPs etc to reduce the bandwidth usage in a network, surrogates or reverse proxy caches are implemented near to the origin servers by the server administrators to reduce the load on server. |
||||
|
||||
 |
||||
|
||||
Although you can control the reverse proxy caches (since it is implemented by you on your server) you can not avoid or control browser and proxy caches. And if your website is not configured to use these caches properly, it will still be cached using whatever the defaults are set on these caches. |
||||
|
||||
### Caching Headers |
||||
|
||||
So, how do we control the web cache? Whenever the server emits some response, it is accompanied with some HTTP headers to guide the caches whether and how to cache this response. Content provider is the one that has to make sure to return proper HTTP headers to force the caches on how to cache the content. |
||||
|
||||
- [Expires](#expires) |
||||
- [Pragma](#pragma) |
||||
- [Cache-Control](#cache-control) |
||||
- [private](#private) |
||||
- [public](#public) |
||||
- [no-store](#no-store) |
||||
- [no-cache](#no-cache) |
||||
- [max-age: seconds](#max-age) |
||||
- [s-maxage: seconds](#s-maxage) |
||||
- [must-revalidate](#must-revalidate) |
||||
- [proxy-revalidate](#proxy-revalidate) |
||||
- [Mixing Values](#mixing-values) |
||||
- [Validators](#validators) |
||||
- [ETag](#etag) |
||||
- [Last-Modified](#last-modified) |
||||
|
||||
#### Expires |
||||
|
||||
Before HTTP/1.1 and introduction of `Cache-Control`, there was `Expires` header which is simply a timestamp telling the caches how long should some content be considered fresh. Possible value to this header is absolute expiry date; where date has to be in GMT. Below is the sample header |
||||
|
||||
```html |
||||
Expires: Mon, 13 Mar 2017 12:22:00 GMT |
||||
``` |
||||
|
||||
It should be noted that the date cannot be more than a year and if the date format is wrong, content will be considered stale. Also, the clock on cache has to be in sync with the clock on server, otherwise the desired results might not be achieved. |
||||
|
||||
Although, `Expires` header is still valid and is supported widely by the caches, preference should be given to HTTP/1.1 successor of it i.e. `Cache-Control`. |
||||
|
||||
#### Pragma |
||||
|
||||
Another one from the old, pre HTTP/1.1 days, is `Pragma`. Everything that it could do is now possible using the cache-control header given below. However, one thing I would like to point out about it is, you might see `Pragma: no-cache` being used here and there in hopes of stopping the response from being cached. It might not necessarily work; as HTTP specification discusses it in the request headers and there is no mention of it in the response headers. Rather `Cache-Control` header should be used to control the caching. |
||||
|
||||
#### Cache-Control |
||||
|
||||
Cache-Control specifies how long and in what manner should the content be cached. This family of headers was introduced in HTTP/1.1 to overcome the limitations of the `Expires` header. |
||||
|
||||
Value for the `Cache-Control` header is composite i.e. it can have multiple directive/values. Let's look at the possible values that this header may contain. |
||||
|
||||
##### private |
||||
Setting the cache to `private` means that the content will not be cached in any of the proxies and it will only be cached by the client (i.e. browser) |
||||
|
||||
```html |
||||
Cache-Control: private |
||||
``` |
||||
|
||||
Having said that, don't let it fool you in to thinking that setting this header will make your data any secure; you still have to use SSL for that purpose. |
||||
|
||||
##### public |
||||
|
||||
If set to `public`, apart from being cached by the client, it can also be cached by the proxies; serving many other users |
||||
|
||||
```html |
||||
Cache-Control: public |
||||
``` |
||||
|
||||
##### no-store |
||||
**`no-store`** specifies that the content is not to be cached by any of the caches |
||||
|
||||
```html |
||||
Cache-Control: no-store |
||||
``` |
||||
|
||||
##### no-cache |
||||
**`no-cache`** indicates that the cache can be maintained but the cached content is to be re-validated (using `ETag` for example) from the server before being served. That is, there is still a request to server but for validation and not to download the cached content. |
||||
|
||||
```html |
||||
Cache-Control: max-age=3600, no-cache, public |
||||
``` |
||||
|
||||
##### max-age: seconds |
||||
**`max-age`** specifies the number of seconds for which the content will be cached. For example, if the `cache-control` looks like below: |
||||
|
||||
```html |
||||
Cache-Control: max-age=3600, public |
||||
``` |
||||
it would mean that the content is publicly cacheable and will be considered stale after 60 minutes |
||||
|
||||
##### s-maxage: seconds |
||||
**`s-maxage`** here `s-` prefix stands for shared. This directive specifically targets the shared caches. Like `max-age` it also gets the number of seconds for which something is to be cached. If present, it will override `max-age` and `expires` headers for shared caching. |
||||
|
||||
```html |
||||
Cache-Control: s-maxage=3600, public |
||||
``` |
||||
|
||||
##### must-revalidate |
||||
**`must-revalidate`** it might happen sometimes that if you have network problems and the content cannot be retrieved from the server, browser may serve stale content without validation. `must-revalidate` avoids that. If this directive is present, it means that stale content cannot be served in any case and the data must be re-validated from the server before serving. |
||||
|
||||
```html |
||||
Cache-Control: max-age=3600, public, must-revalidate |
||||
``` |
||||
|
||||
##### proxy-revalidate |
||||
**`proxy-revalidate`** is similar to `must-revalidate` but it specifies the same for shared or proxy caches. In other words `proxy-revalidate` is to `must-revalidate` as `s-maxage` is to `max-age`. But why did they not call it `s-revalidate`?. I have no idea why, if you have any clue please leave a comment below. |
||||
|
||||
##### Mixing Values |
||||
You can combine these directives in different ways to achieve different caching behaviors, however `no-cache/no-store` and `public/private` are mutually exclusive. |
||||
|
||||
If you specify both `no-store` and `no-cache`, `no-store` will be given precedence over `no-cache`. |
||||
|
||||
```html |
||||
; If specified both |
||||
Cache-Control: no-store, no-cache |
||||
|
||||
; Below will be considered |
||||
Cache-Control: no-store |
||||
``` |
||||
|
||||
For `private/public`, for any unauthenticated requests cache is considered `public` and for any authenticated ones cache is considered `private`. |
||||
|
||||
### Validators |
||||
|
||||
Up until now we only discussed how the content is cached and how long the cached content is to be considered fresh but we did not discuss how the client does the validation from the server. Below we discuss the headers used for this purpose. |
||||
|
||||
#### ETag |
||||
|
||||
Etag or "entity tag" was introduced in HTTP/1.1 specs. Etag is just a unique identifier that the server attaches with some resource. This ETag is later on used by the client to make conditional HTTP requests stating `"give me this resource if ETag is not same as the ETag that I have"` and the content is downloaded only if the etags do not match. |
||||
|
||||
Method by which ETag is generated is not specified in the HTTP docs and usually some collision-resistant hash function is used to assign etags to each version of a resource. There could be two types of etags i.e. strong and weak |
||||
|
||||
```html |
||||
ETag: "j82j8232ha7sdh0q2882" - Strong Etag |
||||
ETag: W/"j82j8232ha7sdh0q2882" - Weak Etag (prefixed with `W/`) |
||||
``` |
||||
|
||||
A strong validating ETag means that two resources are **exactly** same and there is no difference between them at all. While a weak ETag means that two resources are although not strictly same but could be considered same. Weak etags might be useful for dynamic content, for example. |
||||
|
||||
Now you know what etags are but how does the browser make this request? by making a request to server while sending the available Etag in `If-None-Match` header. |
||||
|
||||
Consider the scenario, you opened a web page which loaded a logo image with caching period of 60 seconds and ETag of `abc123xyz`. After about 30 minutes you reload the page, browser will notice that the logo which was fresh for 60 seconds is now stale; it will trigger a request to server, sending the ETag of the stale logo image in `if-none-match` header |
||||
|
||||
```html |
||||
If-None-Match: "abc123xyz" |
||||
``` |
||||
|
||||
Server will then compare this ETag with the ETag of the current version of resource. If both etags are matched, server will send back the response of `304 Not Modified` which will tell the client that the copy that it has is still good and it will be considered fresh for another 60 seconds. If both the etags do not match i.e. the logo has likely changed and client will be sent the new logo which it will use to replace the stale logo that it has. |
||||
|
||||
#### Last-Modified |
||||
|
||||
Server might include the `Last-Modified` header indicating the date and time at which some content was last modified on. |
||||
|
||||
```html |
||||
Last-Modified: Wed, 15 Mar 2017 12:30:26 GMT |
||||
``` |
||||
|
||||
When the content gets stale, client will make a conditional request including the last modified date that it has inside the header called `If-Modified-Since` to server to get the updated `Last-Modified` date; if it matches the date that the client has, `Last-Modified` date for the content is updated to be considered fresh for another `n` seconds. If the received `Last-Modified` date does not match the one that the client has, content is reloaded from the server and replaced with the content that client has. |
||||
|
||||
```html |
||||
If-Modified-Since: Wed, 15 Mar 2017 12:30:26 GMT |
||||
``` |
||||
|
||||
You might be questioning now, what if the cached content has both the `Last-Modified` and `ETag` assigned to it? Well, in that case both are to be used i.e. there will not be any re-downloading of the resource if and only if `ETag` matches the newly retrieved one and so does the `Last-Modified` date. If either the `ETag` does not match or the `Last-Modified` is greater than the one from the server, content has to be downloaded again. |
||||
|
||||
### Where do I start? |
||||
|
||||
Now that we have got *everything* covered, let us put everything in perspective and see how you can use this information. |
||||
|
||||
#### Utilizing Server |
||||
|
||||
Before we get into the possible caching strategies , let me add the fact that most of the servers including Apache and Nginx allow you to implement your caching policy through the server so that you don't have to juggle with headers in your code. |
||||
|
||||
**For example**, if you are using Apache and you have your static content placed at `/static`, you can put below `.htaccess` file in the directory to make all the content in it be cached for an year using below |
||||
|
||||
```html |
||||
# Cache everything for an year |
||||
Header set Cache-Control "max-age=31536000, public" |
||||
``` |
||||
|
||||
You can further use `filesMatch` directive to add conditionals and use different caching strategy for different kinds of files e.g. |
||||
|
||||
```html |
||||
# Cache any images for one year |
||||
<filesMatch ".(png|jpg|jpeg|gif)$"> |
||||
Header set Cache-Control "max-age=31536000, public" |
||||
</filesMatch> |
||||
|
||||
# Cache any CSS and JS files for a month |
||||
<filesMatch ".(css|js)$"> |
||||
Header set Cache-Control "max-age=2628000, public" |
||||
</filesMatch> |
||||
``` |
||||
|
||||
Or if you don't want to use the `.htaccess` file you can modify Apache's configuration file `http.conf`. Same goes for Nginx, you can add the caching information in the location or server block. |
||||
|
||||
#### Caching Recommendations |
||||
|
||||
There is no golden rule or set standards about how your caching policy should look like, each of the application is different and you have to look and find what suits your application the best. However, just to give you a rough idea |
||||
|
||||
- You can have aggressive caching (e.g. cache for an year) on any static content and use fingerprinted filenames (e.g. `style.ju2i90.css`) so that the cache is automatically rejected whenever the files are updated. |
||||
Also it should be noted that you should not cross the upper limit of one year as it [might not be honored](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9) |
||||
- Look and decide do you even need caching for any dynamic content, if yes how long it should be. For example, in case of some RSS feed of a blog there could be the caching of a few hours but there couldn't be any caching for inventory items in an ERP. |
||||
- Always add the validators (preferably ETags) in your response. |
||||
- Pay attention while choosing the visibility (private or public) of the cached content. Make sure that you do not accidentally cache any user-specific or sensitive content in any public proxies. When in doubt, do not use cache at all. |
||||
- Separate the content that changes often from the content that doesn't change that often (e.g. in javascript bundles) so that when it is updated it doesn't need to make the whole cached content stale. |
||||
- Test and monitor the caching headers being served by your site. You can use the browser console or `curl -I http://some-url.com` for that purpose. |
||||
|
||||
And that about wraps it up. Stay tuned for more! |
||||
@ -0,0 +1,195 @@ |
||||
HTTP is the protocol that every web developer should know as it powers the whole web and knowing it is definitely going to help you develop better applications. In this guide, I am going to be discussing what HTTP is, how it came to be, where it is today and how did we get here. |
||||
|
||||
### What is HTTP? |
||||
|
||||
First things first, what is HTTP? HTTP is the `TCP/IP` based application layer communication protocol which standardizes how the client and server communicate with each other. It defines how the content is requested and transmitted across the internet. By application layer protocol, I mean it's just an abstraction layer that standardizes how the hosts (clients and servers) communicate and itself it depends upon `TCP/IP` to get request and response between the client and server. By default TCP port `80` is used but other ports can be used as well. HTTPS, however, uses port `443`. |
||||
|
||||
### HTTP/0.9 – The One Liner (1991) |
||||
|
||||
The first documented version of HTTP was [`HTTP/0.9`](https://www.w3.org/Protocols/HTTP/AsImplemented.html) which was put forward in 1991. It was the simplest protocol ever; having a single method called `GET`. If a client had to access some webpage on the server, it would have made the simple request like below |
||||
|
||||
```html |
||||
GET /index.html |
||||
``` |
||||
And the response from server would have looked as follows |
||||
|
||||
```html |
||||
(response body) |
||||
(connection closed) |
||||
``` |
||||
|
||||
That is, the server would get the request, reply with the HTML in response and as soon as the content has been transferred, the connection will be closed. There were |
||||
|
||||
- No headers |
||||
- `GET` was the only allowed method |
||||
- Response had to be HTML |
||||
|
||||
As you can see, the protocol really had nothing more than being a stepping stone for what was to come. |
||||
|
||||
### HTTP/1.0 - 1996 |
||||
|
||||
In 1996, the next version of HTTP i.e. `HTTP/1.0` evolved that vastly improved over the original version. |
||||
|
||||
Unlike `HTTP/0.9` which was only designed for HTML response, `HTTP/1.0` could now deal with other response formats i.e. images, video files, plain text or any other content type as well. It added more methods (i.e. `POST` and `HEAD`), request/response formats got changed, HTTP headers got added to both the request and responses, status codes were added to identify the response, character set support was introduced, multi-part types, authorization, caching, content encoding and more was included. |
||||
|
||||
Here is how a sample `HTTP/1.0` request and response might have looked like: |
||||
|
||||
```html |
||||
GET / HTTP/1.0 |
||||
Host: kamranahmed.info |
||||
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) |
||||
Accept: */* |
||||
``` |
||||
|
||||
As you can see, alongside the request, client has also sent its personal information, required response type etc. While in `HTTP/0.9` client could never send such information because there were no headers. |
||||
|
||||
Example response to the request above may have looked like below |
||||
|
||||
```html |
||||
HTTP/1.0 200 OK |
||||
Content-Type: text/plain |
||||
Content-Length: 137582 |
||||
Expires: Thu, 05 Dec 1997 16:00:00 GMT |
||||
Last-Modified: Wed, 5 August 1996 15:55:28 GMT |
||||
Server: Apache 0.84 |
||||
|
||||
(response body) |
||||
(connection closed) |
||||
``` |
||||
|
||||
In the very beginning of the response there is `HTTP/1.0` (HTTP followed by the version number), then there is the status code `200` followed by the reason phrase (or description of the status code, if you will). |
||||
|
||||
In this newer version, request and response headers were still kept as `ASCII` encoded, but the response body could have been of any type i.e. image, video, HTML, plain text or any other content type. So, now that server could send any content type to the client; not so long after the introduction, the term "Hyper Text" in `HTTP` became misnomer. `HMTP` or Hypermedia transfer protocol might have made more sense but, I guess, we are stuck with the name for life. |
||||
|
||||
One of the major drawbacks of `HTTP/1.0` were you couldn't have multiple requests per connection. That is, whenever a client will need something from the server, it will have to open a new TCP connection and after that single request has been fulfilled, connection will be closed. And for any next requirement, it will have to be on a new connection. Why is it bad? Well, let's assume that you visit a webpage having `10` images, `5` stylesheets and `5` javascript files, totalling to `20` items that needs to fetched when request to that webpage is made. Since the server closes the connection as soon as the request has been fulfilled, there will be a series of `20` separate connections where each of the items will be served one by one on their separate connections. This large number of connections results in a serious performance hit as requiring a new `TCP` connection imposes a significant performance penalty because of three-way handshake followed by slow-start. |
||||
|
||||
#### Three-way Handshake |
||||
|
||||
Three-way handshake in its simplest form is that all the `TCP` connections begin with a three-way handshake in which the client and the server share a series of packets before starting to share the application data. |
||||
|
||||
- `SYN` - Client picks up a random number, let's say `x`, and sends it to the server. |
||||
- `SYN ACK` - Server acknowledges the request by sending an `ACK` packet back to the client which is made up of a random number, let's say `y` picked up by server and the number `x+1` where `x` is the number that was sent by the client |
||||
- `ACK` - Client increments the number `y` received from the server and sends an `ACK` packet back with the number `y+1` |
||||
|
||||
Once the three-way handshake is completed, the data sharing between the client and server may begin. It should be noted that the client may start sending the application data as soon as it dispatches the last `ACK` packet but the server will still have to wait for the `ACK` packet to be recieved in order to fulfill the request. |
||||
|
||||
 |
||||
|
||||
> Please note that there is a minor issue with the image, the last `ACK` packet sent by the client to end the handshake contains only `y+1` i.e. it should have been `ACK:y+1` instead of `ACK: x+1, y+1` |
||||
|
||||
However, some implementations of `HTTP/1.0` tried to overcome this issue by introducing a new header called `Connection: keep-alive` which was meant to tell the server "Hey server, do not close this connection, I need it again". But still, it wasn't that widely supported and the problem still persisted. |
||||
|
||||
Apart from being connectionless, `HTTP` also is a stateless protocol i.e. server doesn't maintain the information about the client and so each of the requests has to have the information necessary for the server to fulfill the request on its own without any association with any old requests. And so this adds fuel to the fire i.e. apart from the large number of connections that the client has to open, it also has to send some redundant data on the wire causing increased bandwidth usage. |
||||
|
||||
### HTTP/1.1 - 1999 |
||||
|
||||
After merely 3 years of `HTTP/1.0`, the next version i.e. `HTTP/1.1` was released in 1999; which made alot of improvements over its predecessor. The major improvements over `HTTP/1.0` included |
||||
|
||||
- **New HTTP methods** were added, which introduced `PUT`, `PATCH`, `OPTIONS`, `DELETE` |
||||
|
||||
- **Hostname Identification** In `HTTP/1.0` `Host` header wasn't required but `HTTP/1.1` made it required. |
||||
|
||||
- **Persistent Connections** As discussed above, in `HTTP/1.0` there was only one request per connection and the connection was closed as soon as the request was fulfilled which resulted in accute performance hit and latency problems. `HTTP/1.1` introduced the persistent connections i.e. **connections weren't closed by default** and were kept open which allowed multiple sequential requests. To close the connections, the header `Connection: close` had to be available on the request. Clients usually send this header in the last request to safely close the connection. |
||||
|
||||
- **Pipelining** It also introduced the support for pipelining, where the client could send multiple requests to the server without waiting for the response from server on the same connection and server had to send the response in the same sequence in which requests were received. But how does the client know that this is the point where first response download completes and the content for next response starts, you may ask! Well, to solve this, there must be `Content-Length` header present which clients can use to identify where the response ends and it can start waiting for the next response. |
||||
|
||||
> It should be noted that in order to benefit from persistent connections or pipelining, `Content-Length` header must be available on the response, because this would let the client know when the transmission completes and it can send the next request (in normal sequential way of sending requests) or start waiting for the the next response (when pipelining is enabled). |
||||
|
||||
> But there was still an issue with this approach. And that is, what if the data is dynamic and server cannot find the content length before hand? Well in that case, you really can't benefit from persistent connections, could you?! In order to solve this `HTTP/1.1` introduced chunked encoding. In such cases server may omit content-Length in favor of chunked encoding (more to it in a moment). However, if none of them are available, then the connection must be closed at the end of request. |
||||
|
||||
- **Chunked Transfers** In case of dynamic content, when the server cannot really find out the `Content-Length` when the transmission starts, it may start sending the content in pieces (chunk by chunk) and add the `Content-Length` for each chunk when it is sent. And when all of the chunks are sent i.e. whole transmission has completed, it sends an empty chunk i.e. the one with `Content-Length` set to zero in order to identify the client that transmission has completed. In order to notify the client about the chunked transfer, server includes the header `Transfer-Encoding: chunked` |
||||
|
||||
- Unlike `HTTP/1.0` which had Basic authentication only, `HTTP/1.1` included digest and proxy authentication |
||||
- Caching |
||||
- Byte Ranges |
||||
- Character sets |
||||
- Language negotiation |
||||
- Client cookies |
||||
- Enhanced compression support |
||||
- New status codes |
||||
- ..and more |
||||
|
||||
I am not going to dwell about all the `HTTP/1.1` features in this post as it is a topic in itself and you can already find a lot about it. The one such document that I would recommend you to read is [Key differences between `HTTP/1.0` and HTTP/1.1](http://www.ra.ethz.ch/cdstore/www8/data/2136/pdf/pd1.pdf) and here is the link to [original RFC](https://tools.ietf.org/html/rfc2616) for the overachievers. |
||||
|
||||
`HTTP/1.1` was introduced in 1999 and it had been a standard for many years. Although, it improved alot over its predecessor; with the web changing everyday, it started to show its age. Loading a web page these days is more resource-intensive than it ever was. A simple webpage these days has to open more than 30 connections. Well `HTTP/1.1` has persistent connections, then why so many connections? you say! The reason is, in `HTTP/1.1` it can only have one outstanding connection at any moment of time. `HTTP/1.1` tried to fix this by introducing pipelining but it didn't completely address the issue because of the **head-of-line blocking** where a slow or heavy request may block the requests behind and once a request gets stuck in a pipeline, it will have to wait for the next requests to be fulfilled. To overcome these shortcomings of `HTTP/1.1`, the developers started implementing the workarounds, for example use of spritesheets, encoded images in CSS, single humungous CSS/Javascript files, [domain sharding](https://www.maxcdn.com/one/visual-glossary/domain-sharding-2/) etc. |
||||
|
||||
### SPDY - 2009 |
||||
|
||||
Google went ahead and started experimenting with alternative protocols to make the web faster and improving web security while reducing the latency of web pages. In 2009, they announced `SPDY`. |
||||
|
||||
> `SPDY` is a trademark of Google and isn't an acronym. |
||||
|
||||
It was seen that if we keep increasing the bandwidth, the network performance increases in the beginning but a point comes when there is not much of a performance gain. But if you do the same with latency i.e. if we keep dropping the latency, there is a constant performance gain. This was the core idea for performance gain behind `SPDY`, decrease the latency to increase the network performance. |
||||
|
||||
> For those who don't know the difference, latency is the delay i.e. how long it takes for data to travel between the source and destination (measured in milliseconds) and bandwidth is the amount of data transfered per second (bits per second). |
||||
|
||||
The features of `SPDY` included, multiplexing, compression, prioritization, security etc. I am not going to get into the details of SPDY, as you will get the idea when we get into the nitty gritty of `HTTP/2` in the next section as I said `HTTP/2` is mostly inspired from SPDY. |
||||
|
||||
`SPDY` didn't really try to replace HTTP; it was a translation layer over HTTP which existed at the application layer and modified the request before sending it over to the wire. It started to become a defacto standards and majority of browsers started implementing it. |
||||
|
||||
In 2015, at Google, they didn't want to have two competing standards and so they decided to merge it into HTTP while giving birth to `HTTP/2` and deprecating SPDY. |
||||
|
||||
### HTTP/2 - 2015 |
||||
|
||||
By now, you must be convinced that why we needed another revision of the HTTP protocol. `HTTP/2` was designed for low latency transport of content. The key features or differences from the old version of `HTTP/1.1` include |
||||
|
||||
- Binary instead of Textual |
||||
- Multiplexing - Multiple asynchronous HTTP requests over a single connection |
||||
- Header compression using HPACK |
||||
- Server Push - Multiple responses for single request |
||||
- Request Prioritization |
||||
- Security |
||||
|
||||
 |
||||
|
||||
|
||||
#### 1. Binary Protocol |
||||
|
||||
`HTTP/2` tends to address the issue of increased latency that existed in HTTP/1.x by making it a binary protocol. Being a binary protocol, it easier to parse but unlike `HTTP/1.x` it is no longer readable by the human eye. The major building blocks of `HTTP/2` are Frames and Streams |
||||
|
||||
##### Frames and Streams |
||||
|
||||
HTTP messages are now composed of one or more frames. There is a `HEADERS` frame for the meta data and `DATA` frame for the payload and there exist several other types of frames (`HEADERS`, `DATA`, `RST_STREAM`, `SETTINGS`, `PRIORITY` etc) that you can check through [the `HTTP/2` specs](https://http2.github.io/http2-spec/#FrameTypes). |
||||
|
||||
Every `HTTP/2` request and response is given a unique stream ID and it is divided into frames. Frames are nothing but binary pieces of data. A collection of frames is called a Stream. Each frame has a stream id that identifies the stream to which it belongs and each frame has a common header. Also, apart from stream ID being unique, it is worth mentioning that, any request initiated by client uses odd numbers and the response from server has even numbers stream IDs. |
||||
|
||||
Apart from the `HEADERS` and `DATA`, another frame type that I think worth mentioning here is `RST_STREAM` which is a special frame type that is used to abort some stream i.e. client may send this frame to let the server know that I don't need this stream anymore. In `HTTP/1.1` the only way to make the server stop sending the response to client was closing the connection which resulted in increased latency because a new connection had to be opened for any consecutive requests. While in HTTP/2, client can use `RST_STREAM` and stop receiving a specific stream while the connection will still be open and the other streams will still be in play. |
||||
|
||||
|
||||
#### 2. Multiplexing |
||||
|
||||
Since `HTTP/2` is now a binary protocol and as I said above that it uses frames and streams for requests and responses, once a TCP connection is opened, all the streams are sent asynchronously through the same connection without opening any additional connections. And in turn, the server responds in the same asynchronous way i.e. the response has no order and the client uses the assigned stream id to identify the stream to which a specific packet belongs. This also solves the **head-of-line blocking** issue that existed in HTTP/1.x i.e. the client will not have to wait for the request that is taking time and other requests will still be getting processed. |
||||
|
||||
|
||||
#### 3. HPACK Header Compression |
||||
|
||||
It was part of a separate RFC which was specifically aimed at optimizing the sent headers. The essence of it is that when we are constantly accessing the server from a same client there is alot of redundant data that we are sending in the headers over and over, and sometimes there might be cookies increasing the headers size which results in bandwidth usage and increased latency. To overcome this, `HTTP/2` introduced header compression. |
||||
|
||||
 |
||||
|
||||
Unlike request and response, headers are not compressed in `gzip` or `compress` etc formats but there is a different mechanism in place for header compression which is literal values are encoded using Huffman code and a headers table is maintained by the client and server and both the client and server omit any repetitive headers (e.g. user agent etc) in the subsequent requests and reference them using the headers table maintained by both. |
||||
|
||||
While we are talking headers, let me add here that the headers are still the same as in HTTP/1.1, except for the addition of some pseudo headers i.e. `:method`, `:scheme`, `:host` and `:path` |
||||
|
||||
|
||||
#### 4. Server Push |
||||
|
||||
Server push is another tremendous feature of `HTTP/2` where the server, knowing that the client is going to ask for a certain resource, can push it to the client without even client asking for it. For example, let's say a browser loads a web page, it parses the whole page to find out the remote content that it has to load from the server and then sends consequent requests to the server to get that content. |
||||
|
||||
Server push allows the server to decrease the roundtrips by pushing the data that it knows that client is going to demand. How it is done is, server sends a special frame called `PUSH_PROMISE` notifying the client that, "Hey, I am about to send this resource to you! Do not ask me for it." The `PUSH_PROMISE` frame is associated with the stream that caused the push to happen and it contains the promised stream ID i.e. the stream on which the server will send the resource to be pushed. |
||||
|
||||
#### 5. Request Prioritization |
||||
|
||||
A client can assign a priority to a stream by including the prioritization information in the `HEADERS` frame by which a stream is opened. At any other time, client can send a `PRIORITY` frame to change the priority of a stream. |
||||
|
||||
Without any priority information, server processes the requests asynchronously i.e. without any order. If there is priority assigned to a stream, then based on this prioritization information, server decides how much of the resources need to be given to process which request. |
||||
|
||||
#### 6. Security |
||||
|
||||
There was extensive discussion on whether security (through `TLS`) should be made mandatory for `HTTP/2` or not. In the end, it was decided not to make it mandatory. However, most vendors stated that they will only support `HTTP/2` when it is used over `TLS`. So, although `HTTP/2` doesn't require encryption by specs but it has kind of become mandatory by default anyway. With that out of the way, `HTTP/2` when implemented over `TLS` does impose some requirementsi.e. `TLS` version `1.2` or higher must be used, there must be a certain level of minimum keysizes, ephemeral keys are required etc. |
||||
|
||||
`HTTP/2` is here and it has already [surpassed SPDY in adaption](http://caniuse.com/#search=http2) which is gradually increasing. `HTTP/2` has alot to offer in terms of performance gain and it is about time we should start using it. |
||||
|
||||
For anyone interested in further details here is the [link to specs](https://http2.github.io/http2-spec) and a link [demonstrating the performance benefits of `HTTP/2`](http://www.http2demo.io/). |
||||
|
||||
And that about wraps it up. Until next time! stay tuned. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/jwt-authentication.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1273375903511465990) where this image was posted. |
||||
@ -0,0 +1,72 @@ |
||||
I have been working on redoing the [roadmaps](https://roadmap.sh) – splitting the skillset based on the seniority levels to make them easier to follow and not scare the new developers away. Since the roadmaps are going to be just about the technical knowledge, I thought it would be a good idea to reiterate and have an article on what I think of different seniority roles. |
||||
|
||||
I have seen many organizations decide the seniority of developers by giving more significance to the years of experience than they should. I have seen developers labeled "Junior" doing the work of Senior Developers and I have seen "Lead" developers who weren't even qualified to be called "Senior". The seniority of a developer cannot just be decided by their age, years of experience or technical knowledge that they have got. There are other factors in play here -- their perception of work, how they interact with their peers and how they approach problems. We discuss these three key factors in detail for each of the seniority levels below. |
||||
|
||||
### Different Seniority Titles |
||||
Different organizations might have different seniority titles but they mainly fall into three categories: |
||||
|
||||
* Junior Developer |
||||
* Mid Level Developer |
||||
* Senior Developer |
||||
|
||||
### Junior Developer |
||||
Junior developers are normally fresh graduates and it's either they don't have or they have minimal industry experience. Not only they have weak coding skills but there are also a few other things that give Junior developers away: |
||||
|
||||
* Their main mantra is "making it work" without giving much attention to how the solution is achieved. To them, a working software and good software are equivalent. |
||||
* They usually require very specific and structured directions to achieve something. They suffer from tunnel vision, need supervision and continuous guidance to be effective team members. |
||||
* Most of the Junior developers just try to live up to the role and, when stuck, they might leave work for a senior developer instead of at least trying to take a stab at something. |
||||
* They don't know about the business side of the company and don't realize how management/sales/marketing/etc think and they don't realize how much rework, wasted effort, and end-user aggravation could be saved by getting to know the business domain. |
||||
* Over-engineering is a major problem, often leading to fragility and bugs. |
||||
* When given a problem, they often try to fix just the current problem a.k.a. fixing the symptoms instead of fixing the root problem. |
||||
* You might notice the "[Somebody Else's Problem](https://en.wikipedia.org/wiki/Somebody_else%27s_problem)" behavior from them. |
||||
* They don't know what or how much they don't know, thanks to the [Dunning–Kruger effect](https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect). |
||||
* They don't take initiatives and they might be afraid to work on an unfamiliar codebase. |
||||
* They don't participate in team discussions. |
||||
|
||||
Being a Junior developer in the team is not necessarily a bad thing; since you are just starting out, you are not expected to be a know-it-all person. However, it is your responsibility to learn, gain experience, not get stuck with the "Junior" title and improve yourself. Here are a few tips for Junior developers to help move up the ladder of seniority: |
||||
|
||||
* All sorts of problems can be solved if you work on them long enough. Do not give up if Stack Overflow or an issue on GitHub doesn't have an answer. Saying "I am stuck, but I have tried X, Y, and Z. Do you have any pointers?" to your lead is much better than saying "This is beyond me." |
||||
* Read a lot of code, not just code in the projects that you are working on, but reference/framework source code, open-source. Ask your fellow developers, perhaps on Reddit too, about the good open-source examples for the language/tools of your choice. |
||||
* Do personal side-projects, share them with people, contribute to the open-source community. Reach out to people for help. You will be surprised how much support you can get from the community. I still remember my first open-source project on GitHub from around 6 years ago which was a small PHP script (a library) that fetched details for a given address from Google's Geocoding API. The codebase was super messy, it did not have any tests, did not have any linters or sniffers, and it did not have any CI because I didn't know about any of this at that time. I am not sure how but one kind soul somehow found the project, forked it, refactored it, "modernized" it, added linting, code sniffing, added CI and opened the pull request. This one pull request taught me so many things that I might have never learned that fast on my own because I was still in college, working for a small service-based company and doing just small websites all on my own without knowing what is right and what is not. This one PR on GitHub was my introduction to open-source and I owe everything to that. |
||||
* Avoid what is known as ["Somebody Else's Problem Field"](https://en.wikipedia.org/wiki/Somebody_else%27s_problem) behavior. |
||||
* When given a problem to solve, try to identify the root cause and fix that instead of fixing the symptoms. And remember, not being able to reproduce means not solved. It is solved when you understand why it occurred and why it no longer does. |
||||
* Have respect for the code that was written before you. Be generous when passing judgment on the architecture or the design decisions made in the codebase. Understand that code is often ugly and weird for a reason other than incompetence. Learning to live with and thrive with legacy code is a great skill. Never assume anybody is stupid. Instead, figure out how these intelligent, well-intentioned and experienced people have come to a decision that is stupid now. Approach inheriting legacy code with an "opportunity mindset" rather than a complaining one. |
||||
* It's okay to not know things. You don't need to be ashamed of not knowing things already. There are no stupid questions, ask however many questions that would allow you to work effectively. |
||||
* Don't let yourself be limited by the job title that you have. Keep working on your self-improvement. |
||||
* Do your homework. Predict what’s coming down the pipe. Be involved in the team discussions. Even if you are wrong, you will learn something. |
||||
* Learn about the domain that you are working with. Understand the product end-to-end as an end-user. Do not assume things, ask questions and get things cleared when in doubt. |
||||
* Learn to communicate effectively - soft skills matter. Learn how to write good emails, how to present your work, how to phrase your questions in a thoughtful manner. |
||||
* Sit with the senior developers, watch them work, find a mentor. No one likes a know-it-all. Get hold of your ego and be humble enough to take lessons from experienced people. |
||||
* Don't just blindly follow the advice of "experts", take it with a grain of salt. |
||||
* If you are asked to provide an estimate for some work, do not give an answer unless you have all the details to make a reasonable estimate. If you are forced to do that, pad it 2x or more depending on how much you don't know about what needs to be done for the task to be marked 'done'. |
||||
* Take some time to learn how to use a debugger. Debuggers are quite beneficial when navigating new, undocumented or poorly documented codebase, or to debug weird issues. |
||||
* Avoid saying "it works on my machine" -- yes, I have heard that a lot. |
||||
* Try to turn any feelings of inadequacy or imposter syndrome into energy to push yourself forward and increase your skills and knowledge. |
||||
|
||||
### Mid Level Developers |
||||
The next level after the Junior developers is Mid Level developers. They are technically stronger than the Junior developers and can work with minimal supervision. They still have some issues to address in order to jump to Senior level. |
||||
|
||||
Intermediate developers are more competent than the Junior developer. They start to see the flaws in their old codebase. They gain the knowledge but they get trapped into the next chain i.e. messing things up while trying to do them "the right way" e.g. hasty abstractions, overuse or unnecessary usage of Design Patterns -- they may be able to provide solution faster than the Junior developers but the solution might put you into another rabbit-hole in the long run. Without supervision, they might delay the execution while trying to "do things properly". They don't know when to make tradeoffs and they still don't know when to be dogmatic and when to be pragmatic. They can easily become attached to their solution, become myopic, and be unable to take feedback. |
||||
|
||||
Mid-level developers are quite common. Most of the organizations wrongly label them as "Senior Developers". However, they need further mentoring in order to become Senior Developers. The next section describes the responsibilities of a senior developer and how you can become one. |
||||
|
||||
### Senior Developers |
||||
Senior developers are the next level after the Mid-level developers. They are the people who can get things done on their own without any supervision and without creating any issues down the road. They are more mature, have gained experience by delivering both good and bad software in the past and have learned from it — they know how to be pragmatic. Here is the list of things that are normally expected of a Senior Developer: |
||||
|
||||
* With their past experiences, mistakes made, issues faced by over-designed or under-designed software, they can foresee the problems and persuade the direction of the codebase or the architecture. |
||||
* They don't have a "Shiny-Toy" syndrome. They are pragmatic in the execution. They can make the tradeoffs when required, and they know why. They know where to be dogmatic and where to be pragmatic. |
||||
* They have a good picture of the field, know what the best tool for the job is in most cases (even if they don't know the tool). They have the innate ability to pick up a new tool/language/paradigm/etc in order to solve a problem that requires it. |
||||
* They are aware they're on a team. They view it as a part of their responsibility to mentor others. This can range from pair programming with junior devs to taking un-glorious tasks of writing docs or tests or whatever else needs to be done. |
||||
* They have a deep understanding of the domain - they know about the business side of the company and realize how management/sales/marketing/etc think and benefit from their knowledge of the business domain during the development. |
||||
* They don't make empty complaints, they make judgments based on the empirical evidence and they have suggestions for solutions. |
||||
* They think much more than just code - they know that their job is to provide solutions to the problems and not just to write code. |
||||
* They have the ability to take on large ill-defined problems, define them, break them up, and execute the pieces. A senior developer can take something big and abstract, and run with it. They will come up with a few options, discuss them with the team and implement them. |
||||
* They have respect for the code that was written before them. They are generous when passing judgment on the architecture or the design decisions made in the codebase. They approach inheriting legacy code with an "opportunity mindset" rather than a complaining one. |
||||
* They know how to give feedback without hurting anyone. |
||||
|
||||
### Conclusion |
||||
All teams are made up of a mix of all these seniority roles. Being content with your role is a bad thing and you should always strive to improve yourself for the next step. This article is based on my beliefs and observations in the industry. Lots of companies care more for the years of experience to decide the seniority which is a crappy metric -- you don't gain experience just by spending years. You gain it by continuously solving different sorts of problems, irrespective of the number of years you spend in the industry. I have seen fresh graduates having no industry experience get up to speed quickly and producing work of a Senior Engineer and I have seen Senior developers labeled "senior" merely because of their age and "years of experience". |
||||
|
||||
The most important traits that you need to have in order to step up in your career are: not settling with mediocrity, having an open mindset, being humble, learning from your mistakes, working on the challenging problems and having an opportunity mindset rather than a complaining one. |
||||
|
||||
With that said, this post comes to an end. What are your thoughts on the levels of seniority of developers? Feel free to send improvements to this guide. Until next time, stay tuned! |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/oauth.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1276994010423361540) where this image was posted. |
||||
@ -0,0 +1,5 @@ |
||||
One of my favorite pastimes is going through the history of my favorite projects to learn how they grew over time or how certain features were implemented. |
||||
|
||||
The image below describes how I do that in WebStorm. |
||||
|
||||
[](/guides/project-history.png) |
||||
@ -0,0 +1,47 @@ |
||||
Internet has connected people across the world using social media and audio/video calling features along with providing an overabundance of knowledge and tools. All this comes with an inherent danger of security and privacy breaches. In this guide we will talk about **proxies** which play a vital role in mitigating these risks. We will cover the following topics in this guide: |
||||
|
||||
- [Proxy Server](#proxy-server) |
||||
- [Forward Proxy Server](#forward-proxy-server) |
||||
- [Reverse Proxy Server](#reverse-proxy-server) |
||||
- [Summary](#summary) |
||||
|
||||
## Proxy Server |
||||
|
||||
***Every web request which is sent from the client to a web server goes through some type of proxy server.*** A proxy server acts as a gateway between client *(you)* and the internet and separates end-users from the websites you browse. It replaces the source IP address of the web request with the proxy server's IP address and then forwards it to the web server. The web server is unaware of the client, it only sees the proxy server. |
||||
|
||||
 |
||||
> NOTE: This is not an accurate description rather just an illustration. |
||||
|
||||
Proxy servers serve as a single point of control making it easier to enforce security policies. It also provides caching mechanism which stores the requested web pages on the proxy server to improve performance. If the requested web-page is available in cache memory then instead of forwarding the request to the web-server it will send the cached webpage back to the client. This **saves big companies thousands of dollars** by reducing load on their servers as their website is visited by millions of users every day. |
||||
|
||||
## Forward Proxy Server |
||||
|
||||
A forward proxy is generally implemented on the client side and **sits in front of multiple clients** or client sources. Forward proxy servers are mainly used by companies to **manage internet usage** of their employees and **restrict content**. It is also used as a **firewall** to secure company's network by blocking any request which would pose threat to the companies's network. Proxy servers are also used to **bypass geo-restriction** and browse content which might be blocked in user's country. It enables users to **browse anonymously**, as the proxy server masks their details from the website's servers. |
||||
|
||||
 |
||||
> NOTE: This is not an accurate description rather just an illustration |
||||
|
||||
## Reverse Proxy Server |
||||
|
||||
Reverse proxy servers are implemented on the **server side** instead of the client side. It **sits in front of multiple webservers** and manages the incoming requests by forwarding them to the web servers. It provides anonymity for the **back-end web servers and not the client**. Reverse proxy servers are generally used to perform tasks such as **authentication, content caching, and encryption/decryption** on behalf of the web server. These tasks would **hog CPU cycles** on the web server and degrade performance of the website by introducing high amount of delay in loading the webpage. Reverse proxies are also used as **load balancers** to distribute the incoming traffic efficiently among the web servers but it is **not optimized** for this task. In essence, reverse proxy server is a gateway to a web-server or group of web-servers. |
||||
|
||||
 |
||||
> NOTE: This is not an accurate description rather just an illustration. Red lines represent server's response and black lines represent initial request from client(s). |
||||
|
||||
## Summary |
||||
|
||||
A proxy server acts as a gateway between client *(you)* and the internet and separates end-users from the websites you browse. ***The position of the proxy server on the network determines whether it is a forward or a reverse proxy server***. Forward proxy is implemented on the client side and **sits in front of multiple clients** or client sources and forwards requests to the web server. Reverse proxy servers are implemented on the **server side** it **sits in front of multiple webservers** and manages the incoming requests by forwarding them to the web servers. |
||||
|
||||
If all this was too much to take in, I have a simple analogy for you. |
||||
|
||||
At a restaurant the waiter/waitress takes your order and gives it to the kitchen head chef. The head chef then calls out the order and assigns tasks to everyone in the kitchen. |
||||
|
||||
In this analogy: |
||||
|
||||
* You are the client |
||||
* Your order is the web request |
||||
* Waiter/Waitress is your forward proxy server |
||||
* Kitchen head chef is the reverse proxy server |
||||
* Other chefs working in the kitchen are the web servers |
||||
|
||||
With that said our guide comes to an end. Thank you for reading and feel free to submit any updates to the guide using the links below. |
||||
@ -0,0 +1,5 @@ |
||||
Random numbers are everywhere from computer games to lottery systems, graphics software, statistical sampling, computer simulation and cryptography. Graphic below is a quick explanation to how the random numbers are generated and why they may not be truly random. |
||||
|
||||
[](/guides/random-numbers.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1237851549302312962) where this image was posted. |
||||
@ -0,0 +1,5 @@ |
||||
The chart below aims to give you a really basic understanding of how the capability of a DBMS is increased to handle a growing amount of load. |
||||
|
||||
[](/guides/scaling-databases.svg) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1234209674003611650) where this image was posted. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/session-authentication.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1264113498520465410) where this image was posted. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/ssl-tls-https-ssh.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1252717722724642822) where this image was posted. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/sso.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1280266408434302979) where this image was posted. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/token-authentication.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1266832006782103552) where this image was posted. |
||||
@ -0,0 +1,3 @@ |
||||
[](/guides/unfamiliar-codebase.png) |
||||
|
||||
Here is the [original tweet](https://twitter.com/kamranahmedse/status/1256340163573231616) where this image was posted. |
||||
@ -0,0 +1,11 @@ |
||||
> **Roadmap is not ready yet**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the roadmap, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,62 @@ |
||||
Since the explosive growth of web-based applications, every developer could stand to benefit from understanding how the Internet works. In this article, accompanied with an introductory series of short videos about the Internet from [code.org](https://code.org), you will learn the basics of the Internet and how it works. After going through this article, you will be able to answer the below questions: |
||||
|
||||
* What is the Internet? |
||||
* How does the information move on the internet? |
||||
* How do the networks talk to each other and the protocols involved? |
||||
* What's the relationship between packets, routers, and reliability? |
||||
* HTTP and the HTML – How are you viewing this webpage in your browser? |
||||
* How is the information transfer on the internet made secure? |
||||
* What is cybersecurity and what are some common internet crimes? |
||||
|
||||
## What is the Internet? |
||||
|
||||
The Internet is a global network of computers connected to each other which communicate through a standardized set of protocols. |
||||
|
||||
In the video below, Vint Cerf, one of the "fathers of the internet," explains the history of how the Internet works and how no one person or organization is really in charge of it. |
||||
|
||||
<iframe width="100%" height="400" src="https://www.youtube.com/embed/Dxcc6ycZ73M" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
||||
|
||||
|
||||
## Wires, Cables, and Wi-Fi |
||||
|
||||
Information on the Internet moves from computer to another in the form of bits over various mediums, including Ethernet cables, fiber optic cables, and wireless signals (i.e., radio waves). |
||||
|
||||
In the video linked below, you will learn about the different mediums for data transfer on the Internet and the pros and cons for each. |
||||
|
||||
<iframe width="100%" height="400" src="https://www.youtube.com/embed/ZhEf7e4kopM" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
||||
|
||||
## IP Addresses and DNS |
||||
|
||||
Now that you know about the physical medium for the data transfer over the internet, it's time to learn about the protocols involved. How does the information traverse from one computer to another in this massive global network of computers? |
||||
|
||||
In the video below, you will get a brief introduction to IP, DNS, and how these protocols make the Internet work. |
||||
|
||||
<iframe width="100%" height="400" src="https://www.youtube.com/embed/5o8CwafCxnU" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
||||
|
||||
## Packets, Routing, and Reliability |
||||
|
||||
Information transfer on the Internet from one computer to another does not need to follow a fixed path; in fact, it may change paths during the transfer. This information transfer is done in the form of packets and these packets may follow different routes depending on certain factors. |
||||
|
||||
In this video, you will learn about how the packets of information are routed from one computer to another to reach the destination. |
||||
|
||||
<iframe width="100%" height="400" src="https://www.youtube.com/embed/AYdF7b3nMto" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
||||
|
||||
## HTTP and HTML |
||||
|
||||
HTTP is the standard protocol by which webpages are transferred over the Internet. The video below is a brief introduction to HTTP and how web browsers load websites for you. |
||||
|
||||
<iframe width="100%" height="400" src="https://www.youtube.com/embed/kBXQZMmiA4s" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
||||
|
||||
## Encryption and Public Keys |
||||
|
||||
Cryptography is what keeps our communication secure on the Internet. In this short video, you will learn the basics of cryptograpy, SSL/TLS, and how they help make the communication on the Internet secure. |
||||
|
||||
<iframe width="100%" height="400" src="https://www.youtube.com/embed/ZghMPWGXexs" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
||||
|
||||
## Cybersecurity and Crime |
||||
|
||||
In this video, you will learn about the basics of cybersecurity and common cybercrimes |
||||
|
||||
<iframe width="100%" height="400" src="https://www.youtube.com/embed/AuYNXgO_f3Y" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
||||
|
||||
And that wraps it up for this article. To learn more about the Internet, [Kamran Ahmed](https://twitter.com/kamranahmedse) has a nice little guide on [DNS: How a website is found on the Internet](/guides/dns-in-one-picture). Also, go through the episodes of [howdns.works](https://howdns.works/) and read this [cartoon intro to DNS over HTTPS](https://hacks.mozilla.org/2018/05/a-cartoon-intro-to-dns-over-https/). |
||||
@ -0,0 +1,69 @@ |
||||
We all have heard the mantra *"build it and they will come"* many times. Stories of people building a startup or project and seemingly stumbling upon a goldmine aren't few, but they aren't the rule. These stories are still the exception in the mass of launched projects and startups. |
||||
|
||||
Before the [Wright brothers](https://en.wikipedia.org/wiki/Wright_brothers) built their Kitty Hawk, people generally believed heavy objects could not fly - physics simply forbade it. The idea to regularly board airplanes as we do it these days was unthinkable. It was considered an unrealistic daydream for humans to ever claim the sky. When the first airplanes took off, people were fascinated, of course. It was a topic people continued to talk about for ages. Technology had made something impossible possible. While the wording "build it and they will come" originated from the movie [Field of Dreams](https://en.wikipedia.org/wiki/Field_of_Dreams), this and similar historic events gave birth to the idea behind it. |
||||
|
||||
The engineers' and inventors' dreams came true: spend time doing what you love while the success follows magically. The internet and web-standards democratized access to this dream. But with it, the idea behind it faded and became less and less powerful. In 2020, there are very strong signs the popular saying isn't correct anymore. |
||||
|
||||
|
||||
Why doesn't "build it and they will come" work anymore? |
||||
------------------------------------------------------- |
||||
|
||||
There are a few reasons working hard to make "build it and they will come" a thing of the past. This being said, it doesn't mean you can't succeed building a side-project anymore. You've just got to adjust the way you are building it. |
||||
|
||||
### Building got much easier |
||||
|
||||
As a software engineer, some websites are a blessing. Most of us couldn't work without GitHub, Stackoverflow and of course Google, ahem, DuckDuckGo. These powerful sites help us to solve problems, learn new techniques and find the right libraries to make building projects easier. If any of these sites are down, most engineers take a break and go for a coffee instead of trying to continue working. Combine this with more sophisticated web-standards and easier access to tooling, and you arrive at a world where building projects isn't just a job for highly specialist developers anymore. Powerful frameworks such as [Laravel](https://laravel.com/) and [Quasar Framework](https://quasar.dev/) are available for anyone to build projects on - for free. |
||||
|
||||
In fact, building projects got to a point where some people simply build them as an exercise or hobby. If you spend some time browsing GitHub you will be surprised by the open source projects people built without any commercial goals. "Low code" and "No code" are the next wave of people building projects with less technological background. |
||||
|
||||
### Too much going on: information overload |
||||
|
||||
We are living in a world with information overload. In the online sphere, you can find a lot of useful information. But there is also a lot of noise. For each piece of information or advice you can find a number of opposing statements. This is partly due to the fact that the internet made it much easier to publish and share information. Everyone has been given a voice - for good or bad. This makes it much harder to reach potential users. Your new project probably just drowns amongst kitten videos, opinions, and news. Never has the average lifetime of published content been so low. You've got to come up with a marketing plan before setting out on the journey. |
||||
|
||||
### Smaller Problems |
||||
|
||||
Besides building being easier than ever before and attention being in short supply, there is another issue making the life of makers, inventors and engineers harder: today's problems are much smaller. Back when the previously mentioned Wright Brothers set out, they fascinated people with the problem they were aiming to address: flying. Unless your name is Elon, your problem is unlikely to attract many people naturally. As a solo developer or indie hacker, the chances are higher for having a much smaller problem in a niche (of a niche). With the information overload mentioned before, niches are pretty much the only way to build a side-project or startup and succeed. |
||||
|
||||
Does sound pretty grim for inventors, developers and engineers? Well, yes and no. We've got to tweak the approach to get in front of the eye of potential users and customers. |
||||
|
||||
|
||||
How to market your project nowadays? |
||||
------------------------------------ |
||||
|
||||
The very first step to improving the odds of success is [idea validation](https://peterthaleikis.com/business-idea-validation/). While this sounds fairly obvious, many engineers and developers still don't validate their ideas before starting to build the MVP. The result is another stale project and wasted effort. To succeed you need to work on marketing before you start building anything. In the link mentioned before, I describe my approach to validation and collecting useful marketing information at the same time. |
||||
|
||||
### Build your Audience first and the project after. |
||||
|
||||
Build your audience before you build your project. Spend your time connecting with potential users, learn from their needs and talk about their problems. This will help you market your project later on. Audience first, project second. There are numerous ways to build an audience. One of the simplest and easiest is to start with a personal or [project blog](https://startupnamecheck.com/blog/how-to-start-a-small-business-blog). |
||||
|
||||
Don't use Medium or a similar service - opt for a self-hosted blog as it allows you to build the blog freely to your needs and have decent links back to your project later on. Don't forget to add a newsletter. Newsletters are a key to reconnect in our world of short attention spans. |
||||
|
||||
### Tool by Tool |
||||
|
||||
Another approach is the "Tool by Tool" approach. I've first noticed this approach being used by Shopify. The team at Shopify are providing little tools such as a [logo generator](https://hatchful.shopify.com/) and release these tools free for anyone to use. This not just builds goodwill with people; it also allows Shopify to attract powerful backlinks to their projects. As developers we are in the perfect position to build such mini-tools. It boosts morale and drives attention at the same time. |
||||
|
||||
Spend some time evaluating where your project or product will deliver value to the end-user. Look at options to split off small, independent tools. Build these and launch them before launching the whole product. This allows you to practice launching and promoting your part-projects at the same time. With each backlink to your part-projects you will enhance your ranking in Google. An example for a maker following this approach is [Kamban](https://kambanthemaker.com/) with [FlatGA](https://flatga.io/). He built FlatGA as phase one of a bigger project currently in development. |
||||
|
||||
### Join a Maker community |
||||
|
||||
While you are building your part-projects, don't forget to discuss the progress publicly. This helps to attract an audience around your work and makes the launches easier. You can use Twitter threads and Reddit posts to share updates. A maker community such as [makerlog](https://getmakerlog.com/) or [WIP.chat](https://wip.chat) can also extend your reach. These allow you to get instant feedback, keep yourself accountable and they will enhance your reach at the same time. |
||||
|
||||
### Getting ready to Launch |
||||
|
||||
Launching seems like this special moment when you release your project into the wide world. Often this moment is combined with high expectations and developers consider launching their project the key - if not only - part of their approach to marketing. While launching can help to attract some initial customers, it shouldn't be your only idea when it comes to marketing. You should also know that launching isn't a single event. You can (and should) launch again and again. Every time you launch you are increasing the chance to reach more and new customers. After the launch is before the launch. |
||||
|
||||
### Marketing Is an On-going Fight |
||||
|
||||
Many developers plan to launch their product on a few sites and see where it takes their project from there on. This works well, if your product goes viral by luck. A much more sustainable approach is constantly working a little on it. Marketing is most effective, if done consistently. That holds true for blogging as well as most other forms of marketing. A simple approach to keep you on the path to market your project regularly is subscribing to a free [newsletter with small marketing opportunities](https://wheretopost.email). This way, you are regularly reminded and given bite-sized tasks to complete. |
||||
|
||||
|
||||
Closing Words |
||||
------------- |
||||
|
||||
I hope the article helped you to wrap your head around the idea that building side-projects alone doesn't solve any issues anymore. If you like what you've just read and want to read more, please consider subscribing to [my newsletter](https://peterthaleikis.com/newsletter). I'll send out the occasional email about interesting new articles or side-projects. |
||||
|
||||
|
||||
About the author |
||||
---------------- |
||||
|
||||
[Peter Thaleikis](https://peterthaleikis.com/) a software engineer and business owner. He has been developing web applications since around 2000. Before he started his own software development company [Bring Your Own Ideas Ltd.](https://bringyourownideas.com/), he has been Lead Developer for multiple organisations. |
||||
@ -0,0 +1,67 @@ |
||||
## What is roadmap.sh? |
||||
|
||||
Roadmap.sh is the place containing community curated roadmaps, study plans, paths and resources for the budding |
||||
developers. It started as a [set of charts to guide the developers](https://github.com/kamranahmedse/developer-roadmap) |
||||
who are confused about what should they learn next but that alone wasn't enough so I expanded it into the website to get |
||||
more contributors involved. |
||||
|
||||
## What are the plans for roadmap.sh? |
||||
|
||||
The website started off as |
||||
a [simple repository containing a few charts](https://github.com/kamranahmedse/developer-roadmap) for developers and |
||||
based on my personal opinions but it could have been much more than that so I decided to expand it to a website where |
||||
people can contribute to study plans with their areas of expertise as well, add more roadmaps, write guides etc. |
||||
|
||||
We haven't opened up the sign ups for now but we will be doing. My long term plans for this website are to turn it into |
||||
a goto place for the developers to seek guidance about their careers, help others, share their journeys, incentivize the |
||||
learnings, get feedbacks on their projects etc. |
||||
|
||||
## How did you build roadmap.sh? |
||||
|
||||
The basic version of the website has been built with [Next.js](https://github.com/zeit/next.js/), is opensource and can |
||||
be found on [github](https://github.com/kamranahmedse/roadmap.sh). It was hastily done to get it out in front of the |
||||
people and get people to start contributing so it might be rough on the edges, but that is where we need your help. |
||||
|
||||
## How does it make money? |
||||
|
||||
It doesn't make any money. I have been using my personal time and budget to build it. I did not create this website with |
||||
any intentions of monetization but as a good will, to help the people get out of the frustration that I was once in. |
||||
|
||||
Having said that, I love teaching and my future plans are to be able to work full-time on roadmap.sh for which it has to |
||||
make enough money to pay for my rent, groceries, bills, travel expenses, etc but even if it doesn't it's likely I'll |
||||
continue growing the site however I can. My focus at the moment is not making money from it and just add content that |
||||
creates value for the people. |
||||
|
||||
> Sponsor the efforts by [paying as little as 5$ per month](https://github.com/sponsors/kamranahmedse) or with [one time payment via paypal](https://paypal.me/kamranahmedse). Alternatively, reach out to me at [kamranahmed.se@gmail.com](mailto:kamranahmed.se@gmail.com). |
||||
|
||||
## Can I contribute? |
||||
|
||||
You definitely can, infact you are encouraged to do that. Even your minor contributions such as typo fixes count. The |
||||
source code of the website can be [found on Github](https://github.com/kamranahmedse/roadmap.sh). Your contributions can |
||||
be: |
||||
|
||||
* Adding a new roadmap |
||||
* Updating existing roadmap |
||||
* Suggesting changes to the existing roadmaps |
||||
* Writing a Guide |
||||
* Updating an existing guide |
||||
* Fixing grammar mistakes, typos on the website or the content |
||||
* Updating the UI of the website |
||||
* Refactoring the codebase |
||||
* Becoming a sponsor |
||||
|
||||
Just make sure |
||||
to [follow the contribution guidelines](https://github.com/kamranahmedse/roadmap.sh/tree/master/contributing) when you |
||||
decide to contribute. |
||||
|
||||
## Can I redistribute the content? |
||||
|
||||
No, the license of the content on this website does not allow you to redistribute any of the content on this website |
||||
anywhere. You can use it for personal use or share the link to the content if you have to but redistribution is not |
||||
allowed. |
||||
|
||||
## What is the best way to contact you? |
||||
|
||||
Tweet or send me a message [@kamranahmedse](https://twitter.com/kamranahmedse) or email me |
||||
at [kamranahmed.se@gmail.com](mailto:kamranahmed.se@gmail.com). I get lots of messages so apologies in advance if you don't hear back |
||||
from me soon but I do reply to everyone. |
||||
@ -0,0 +1,78 @@ |
||||
# Privacy Policy |
||||
|
||||
By using or accessing the Services in any manner, you acknowledge that you accept the practices and policies outlined in this Privacy Policy, and you hereby consent that we will collect, use, and share your information in the following ways. Remember that your use of roadmap.sh’s Services is at all times subject to the [Terms of Use](/terms), which incorporates this Privacy Policy. Any terms we use in this Policy without defining them have the definitions given to them in the Terms of Use. |
||||
|
||||
## What does this Privacy Policy cover? |
||||
|
||||
This Privacy Policy covers our treatment of personally identifiable information ("Personal Information") that we gather when you are accessing or using our Services, but not to the practices of companies we don’t own or control, or people that we don’t manage. We gather various types of Personal Information from our users, as explained in more detail below, and we use this Personal Information internally in connection with our Services, including to personalize, provide, and improve our services, to allow you to set up a user account and profile, to contact you and allow other users to contact you, to fulfill your requests for certain products and services, and to analyze how you use the Services. In certain cases, we may also share some Personal Information with third parties, but only as described below. |
||||
|
||||
As noted in the Terms of Use, we do not knowingly collect or solicit personal information from anyone under the age of 13. If you are under 13, please do not attempt to register for the Services or send any personal information about yourself to us. If we learn that we have collected personal information from a child under age 13, we will delete that information as quickly as possible. If you believe that a child under 13 may have provided us personal information, please contact us at kamranahmed.se@gmail.com. |
||||
|
||||
## Will roadmap.sh ever change this Privacy Policy? |
||||
|
||||
We’re constantly trying to improve our Services, so we may need to change this Privacy Policy from time to time as well, but we will alert you to changes by updating the services on the website, placing a notice on the Services, by sending you an email, and/or by some other means. Please note that if you’ve opted not to receive legal notice emails from us (or you haven’t provided us with your email address), those legal notices will still govern your use of the Services, and you are still responsible for reading and understanding them. If you use the Services after any changes to the Privacy Policy have been posted, that means you agree to all of the changes. Use of information we collect now is subject to the Privacy Policy in effect at the time such information is used or collected. |
||||
|
||||
## What Information does roadmap.sh Collect? |
||||
|
||||
Information You Provide to Us: |
||||
|
||||
We receive and store any information you knowingly provide to us. For example, through the registration process and/or through your account settings, we may collect Personal Information such as your name, title, email address, phone number, and third-party account credentials (for example, your log-in credentials for Twitter or other third party sites. If you provide your third-party account credentials to us or otherwise sign in to the Services through a third party site or service, you understand some content and/or information in those accounts (“Third Party Account Information”) may be transmitted into your account with us if you authorize such transmissions], and that Third Party Account Information transmitted to our Services is covered by this Privacy Policy. Certain information may be required to register with us or to take advantage of some of our features. |
||||
|
||||
We may communicate with you if you’ve provided us the means to do so. For example, if you’ve given us your email address, we may send you promotional email offers on behalf of other businesses, or email you about your use of the Services. Also, we may receive a confirmation when you open an email from us. This confirmation helps us make our communications with you more interesting and improve our services. If you do not want to receive communications from us, please email us at kamranahmed.se@gmail.com. |
||||
|
||||
## Information Collected Automatically |
||||
|
||||
Whenever you interact with our Services, we automatically receive and record information on our server logs from your browser or device, which may include your IP address, geolocation data, device identification, “cookie” information, the type of browser and/or device you’re using to access our Services, and the page or feature you requested. “Cookies” are identifiers we transfer to your browser or device that allow us to recognize your browser or device and tell us how and when pages and features in our Services are visited and by how many people. You may be able to change the preferences on your browser or device to prevent or limit your device’s acceptance of cookies, but this may prevent you from taking advantage of some of our features. Our advertising partners may also transmit cookies to your browser or device, when you click on ads that appear on the Services. Also if you click on a link to a third party website or service, such third party may also transmit cookies to you. Again, this Privacy Policy does not cover the use of cookies by any third parties, and we aren’t responsible for their privacy policies and practices. |
||||
|
||||
When we collect the usage information described above, we only use this data in aggregate form, and not in a manner that would identify you personally. For example, this aggregate data can tell us how often users use a particular feature of the Services, and we can use that knowledge to make the Services interesting to as many users as possible. |
||||
|
||||
## Will roadmap.sh Share Any of the Personal Information it Receives? |
||||
|
||||
We may share your Personal Information with third parties as described in this section: |
||||
|
||||
Information that’s no longer personally identifiable. We may anonymize your Personal Information so that you are not individually identified, and provide that information to our partners. We may also provide aggregate usage information to our partners, who may use such information to understand how often and in what ways people use our Services, so that they, too, can provide you with an optimal online experience. However, we never disclose aggregate information to a partner in a manner that would identify you personally, as an individual. |
||||
|
||||
Advertisers: We may allow advertisers and/or merchant partners (“Advertisers”) to choose the demographic information of users who will see their advertisements and/or promotional offers and you agree that we may provide any of the information we have collected from you in non-personally identifiable form to an Advertiser, in order for that Advertiser to select the appropriate audience for those advertisements and/or offers. For example, we might use the fact you are located in San Francisco to show you ads or offers for San Francisco businesses, but we will not tell such businesses who you are. Note that if an advertiser asks us to show an ad to a certain audience or audience segment and you respond to that ad, the advertiser may conclude that you fit the description of the audience they were trying to reach. |
||||
|
||||
We may deliver a file to you through the Services (known as a “web beacon”) from an ad network. Web beacons allow ad networks to provide anonymized, aggregated auditing, research and reporting for us and for advertisers. Web beacons also enable ad networks to serve targeted advertisements to you when you visit other websites. Because your web browser must request these advertisements and web beacons from the ad network’s servers, these companies can view, edit, or set their own cookies, just as if you had requested a web page from their site. You may be able to opt-out of web beacon tracking by adjusting the settings on your browser. |
||||
|
||||
Affiliated Businesses: In certain situations, businesses or third party websites we’re affiliated with may sell or provide products or services to you through or in connection with the Services (either alone or jointly with us). You can recognize when an affiliated business is associated with such a transaction or service, and we will share your Personal Information with that affiliated business only to the extent that it is related to such transaction or service. One such service may include the ability for you to automatically transmit Third Party Account Information to your Services profile or to automatically transmit information in your Services profile to your third party account; for example, you may sign into your roadmap.sh account using your Twitter account. We have no control over the policies and practices of third party websites or businesses as to privacy or anything else, so if you choose to take part in any transaction or service relating to an affiliated website or business, please review all such business’ or websites’ policies. |
||||
|
||||
Our Agents: We employ other companies and people to perform tasks on our behalf and need to share your information with them to provide products or services to you. Unless we tell you differently, our agents do not have any right to use the Personal Information we share with them beyond what is necessary to assist us. |
||||
|
||||
User Profiles and Submissions: Certain user profile information, including your name, location, and any video or image content that such user has uploaded to the Services, may be displayed to other users to facilitate user interaction within the Services or address your request for our services. Please remember that any content you upload to your public user profile, along with any Personal Information or content that you voluntarily disclose online in a manner other users can view (on discussion boards, in messages and chat areas, etc.) becomes publicly available, and can be collected and used by anyone. Your user name may also be displayed to other users if and when you send messages or comments or upload images or videos through the Services and other users can contact you through messages and comments. Additionally, if you sign into the Services through a third party social networking site or service, your list of “friends” from that site or service may be automatically imported to the Services, and such “friends,” if they are also registered users of the Services, may be able to access certain non-public information you have entered in your Services user profile. Again, we do not control the policies and practices of any other third party site or service. |
||||
|
||||
Business Transfers: We may choose to buy or sell assets. In these types of transactions, customer information is typically one of the business assets that would be transferred. Also, if we (or our assets) are acquired, or if we go out of business, enter bankruptcy, or go through some other change of control, Personal Information could be one of the assets transferred to or acquired by a third party. |
||||
|
||||
Protection of roadmap.sh and Others: We reserve the right to access, read, preserve, and disclose any information that we reasonably believe is necessary to comply with law or court order; enforce or apply our terms of use and other agreements; or protect the rights, property, or safety of roadmap.sh, our employees, our users, or others. |
||||
|
||||
## Is Personal Information about me secure? |
||||
|
||||
Your account is protected by a password for your privacy and security. If you access your account via a third party site or service, you may have additional or different sign-on protections via that third party site or service. You must prevent unauthorized access to your account and Personal Information by selecting and protecting your password and/or other sign-on mechanism appropriately and limiting access to your computer or device and browser by signing off after you have finished accessing your account. We endeavor to protect the privacy of your account and other Personal Information we hold in our records, but unfortunately, we cannot guarantee complete security. Unauthorized entry or use, hardware or software failure, and other factors, may compromise the security of user information at any time. |
||||
|
||||
## What Personal Information can I access? |
||||
|
||||
Through your account settings, you may access, and, in some cases, edit or delete the following information you’ve provided to us: |
||||
|
||||
- first and last name |
||||
- location of residence |
||||
- age or birthday |
||||
- username |
||||
|
||||
The information you can view, update, and delete may change as the Services change. If you have any questions about viewing or updating information we have on file about you, please contact us at kamranahmed.se@gmail.com. |
||||
|
||||
Under California Civil Code Sections 1798.83-1798.84, California residents are entitled to ask us for a notice identifying the categories of Personal Information which we share with our affiliates and/or third parties for marketing purposes, and providing contact information for such affiliates and/or third parties. If you are a California resident and would like a copy of this notice, please submit a written request to: kamranahmed.se@gmail.com. |
||||
|
||||
## What choices do I have? |
||||
|
||||
You can always opt not to disclose information to us, but keep in mind some information may be needed to register with us or to take advantage of some of our features. |
||||
|
||||
You may be able to add, update, or delete information as explained above. When you update information, however, we may maintain a copy of the unrevised information in our records. You may request deletion of your account by contacting us at kamranahmed.se@gmail.com and we will disassociate our email address and Twitter account from any content or other information provided to us. Some information may remain in our records after your deletion of such information from your account. We may use any aggregated data derived from or incorporating your Personal Information after you update or delete it, but not in a manner that would identify you personally. |
||||
|
||||
## What if I have questions about this policy? |
||||
|
||||
If you have any questions or concerns regarding our privacy policies, please send us a detailed message to kamranahmed.se@gmail.com, and we will try to resolve your concerns. |
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,125 @@ |
||||
# Terms of Service |
||||
|
||||
PLEASE NOTE THAT YOUR USE OF AND ACCESS TO OUR SERVICES (DEFINED BELOW) ARE SUBJECT TO THE FOLLOWING TERMS; IF YOU DO NOT AGREE TO ALL OF THE FOLLOWING, YOU MAY NOT USE OR ACCESS THE SERVICES IN ANY MANNER. |
||||
|
||||
Welcome to roadmap.sh. Please read on to learn the rules and restrictions that govern your use of our website(s), products, services and applications (the “Services”). If you have any questions, comments, or concerns regarding these terms or the Services, please contact us at kamranahmed.se@gmail.com. |
||||
|
||||
These Terms of Use (the “Terms”) are a binding contract between you and roadmap.sh (“roadmap.sh,” “we”, and “us”). You must agree to and accept all of the Terms, or you don’t have the right to use the Services. Your using the Services in any way means that you agree to all of these Terms, and these Terms will remain in effect while you use the Services. These Terms include the provisions in this document, as well as those in the Privacy Policy and Copyright Dispute Policy. |
||||
|
||||
## Will these Terms ever change? |
||||
|
||||
We are constantly trying to improve our Services, so these Terms may need to change along with the Services. We reserve the right to change the Terms at any time, but if we do, we will bring it to your attention by updating the terms on the roadmap.sh website, by sending you an email, and/or by some other means. |
||||
|
||||
If you don’t agree with the new Terms, you are free to reject them, however it means you will no longer be able to use the Services. If you use the Services in any way after a change to the Terms is effective, that means you agree to all of the changes. |
||||
|
||||
Except for changes by us as described here, no other amendment or modification of these Terms will be effective unless in writing and signed by both you and us. |
||||
|
||||
## Do these terms cover privacy? |
||||
|
||||
You can view the current roadmap.sh Privacy Policy [here](/privacy). |
||||
|
||||
The Children’s Online Privacy Protection Act (“COPPA”) requires that online service providers obtain parental consent before they knowingly collect personally identifiable information online from children who are under 13. We do not knowingly collect or solicit personally identifiable information from children under 13. If you are a child under 13, please do not attempt to register for the Services or send any personal information about yourself to us. If we learn we have collected personal information from a child under 13, we will delete that information as quickly as possible. If you believe that a child under 13 may have provided us personal information, please contact us at kamranahmed.se@gmail.com. |
||||
|
||||
## What are the basics of using roadmap.sh? |
||||
|
||||
You may be required to sign up for an account, and select a password and username. You agree to provide us with accurate, complete, and up-to-date registration information about yourself. You may not select as your username a name that you don’t have the right to use, or another person’s name with the intent to impersonate that person. You may not transfer your account to anyone else without our prior written permission. |
||||
|
||||
You represent and warrant that you are an individual of legal age to form a binding contract, or if not, you’ve received your parent’s or guardian’s permission to use the Services and gotten your parent or guardian to agree to these Terms on your behalf. |
||||
|
||||
You will only use the Services for your own internal, personal, non-commercial use, and not on behalf of or for the benefit of any third party, and only in a manner that complies with all laws that apply to you. If your use of the Services is prohibited by applicable laws, then you aren’t authorized to use the Services. We can’t and won’t be responsible for your using the Services in a way that breaks the law. |
||||
|
||||
You will not share your account or password with anyone, and you must protect the security of your account and your password. You’re responsible for any activity associated with your account. |
||||
|
||||
## Your use of the Services is subject to the following additional restrictions: |
||||
|
||||
You represent, warrant, and agree that you will not contribute any Content or User Submission (each of those terms is defined below) or otherwise use the Services or interact with the Services in a manner that: |
||||
|
||||
(a) Infringes or violates the intellectual property rights or any other rights of anyone else (including roadmap.sh); (b) Violates any law or regulation, including any applicable export control laws; (c) Is harmful, fraudulent, deceptive, threatening, harassing, defamatory, obscene, or otherwise objectionable; (d) Jeopardizes the security of your roadmap.sh account or anyone else’s (such as allowing someone else to log in to the Services as you); (e) Attempts, in any manner, to obtain the password, account, or other security information from any other user; (f) Violates the security of any computer network, or cracks any passwords or security encryption codes; (g) Runs Maillist, Listserv, any form of auto-responder or “spam” on the Services, or any processes that run or are activated while you are not logged into the Services, or that otherwise interfere with the proper working of the Services (including by placing an unreasonable load on the Services’ infrastructure); (h) “Crawls,” “scrapes,” or “spiders” any page, data, or portion of or relating to the Services or Content (through use of manual or automated means); (i) Copies or stores any significant portion of the Content; (j) Decompiles, reverse engineers, or otherwise attempts to obtain the source code or underlying ideas or information of or relating to the Services. |
||||
|
||||
A violation of any of the foregoing is grounds for termination of your right to use or access the Services. |
||||
|
||||
## What are my rights in roadmap.sh? |
||||
|
||||
The materials displayed or performed or available on or through the Services, including, but not limited to, text, graphics, data, articles, photos, images, illustrations, User Submissions, and so forth (all of the foregoing, the “Content”) are protected by copyright and/or other intellectual property laws. You promise to abide by all copyright notices, trademark rules, information, and restrictions contained in any Content you access through the Services, and you won’t use, copy, reproduce, modify, translate, publish, broadcast, transmit, distribute, perform, upload, display, license, sell or otherwise exploit for any purpose any Content not owned by you, (i) without the prior consent of the owner of that Content or (ii) in a way that violates someone else’s (including roadmap.sh’s) rights. |
||||
|
||||
You understand that roadmap.sh owns the Services. You won’t modify, publish, transmit, participate in the transfer or sale of, reproduce (except as expressly provided in this Section), create derivative works based on, or otherwise exploit any of the Services. |
||||
|
||||
The Services may allow you to copy or download certain Content; please remember that just because this functionality exists, doesn’t mean that all the restrictions above don’t apply – they do! |
||||
|
||||
## Do I have to grant any licenses to roadmap.sh or to other users? |
||||
|
||||
Anything you post, upload, share, store, or otherwise provide through the Services is your “User Submission.” Some User Submissions are viewable by other users. In order to display your User Submissions on the Services, and to allow other users to enjoy them (where applicable), you grant us certain rights in those User Submissions. Please note that all of the following licenses are subject to our Privacy Policy to the extent they relate to User Submissions that are also your personally-identifiable information. |
||||
|
||||
For all User Submissions, you hereby grant roadmap.sh a license to translate, modify (for technical purposes, for example making sure your content is viewable on an iPhone as well as a computer) and reproduce and otherwise act with respect to such User Submissions, in each case to enable us to operate the Services, as described in more detail below. This is a license only – your ownership in User Submissions is not affected. |
||||
|
||||
If you store a User Submission in your own personal roadmap.sh account, in a manner that is not viewable by any other user except you (a “Personal User Submission”), you grant roadmap.sh the license above, as well as a license to display, perform, and distribute your Personal User Submission for the sole purpose of making that Personal User Submission accessible to you and providing the Services necessary to do so. |
||||
|
||||
If you share a User Submission only in a manner that only certain specified users can view (for example, a private message to one or more other users) (a “Limited Audience User Submission”), then you grant roadmap.sh the licenses above, as well as a license to display, perform, and distribute your Limited Audience User Submission for the sole purpose of making that Limited Audience User Submission accessible to such other specified users, and providing the Services necessary to do so. Also, you grant such other specified users a license to access that Limited Audience User Submission, and to use and exercise all rights in it, as permitted by the functionality of the Services. |
||||
|
||||
If you share a User Submission publicly on the Services and/or in a manner that more than just you or certain specified users can view, or if you provide us (in a direct email or otherwise) with any feedback, suggestions, improvements, enhancements, and/or feature requests relating to the Services] (each of the foregoing, a “Public User Submission”), then you grant roadmap.sh the licenses above, as well as a license to display, perform, and distribute your Public User Submission for the purpose of making that Public User Submission accessible to all roadmap.sh users and providing the Services necessary to do so, as well as all other rights necessary to use and exercise all rights in that Public User Submission in connection with the Services and/or otherwise in connection with roadmap.sh’s business for any purpose, provided that roadmap.sh will try to notify you if it uses your Public User Submission for any reason other than displaying it on the Services. Also, you grant all other users of the Services a license to access that Public User Submission, and to use and exercise all rights in it, as permitted by the functionality of the Services. |
||||
|
||||
You agree that the licenses you grant are royalty-free, perpetual, sublicenseable, irrevocable, and worldwide, provided that when you delete your roadmap.sh account, we will stop displaying your User Submissions (other than Public User Submissions, which may remain fully available)] to other users (if applicable), but you understand and agree that it may not be possible to completely delete that content from roadmap.sh’s records, and that your User Submissions may remain viewable elsewhere to the extent that they were copied or stored by other users. |
||||
|
||||
Finally, you understand and agree that roadmap.sh, in performing the required technical steps to provide the Services to our users (including you), may need to make changes to your User Submissions to conform and adapt those User Submissions to the technical requirements of connection networks, devices, services, or media, and the foregoing licenses include the rights to do so. |
||||
|
||||
## What if I see something on the Services that infringes my copyright? |
||||
|
||||
You may have heard of the Digital Millennium Copyright Act (the “DMCA”), as it relates to online service providers, like roadmap.sh, being asked to remove material that allegedly violates someone’s copyright. We respect others’ intellectual property rights, and we reserve the right to delete or disable Content alleged to be infringing, and to terminate the accounts of repeat alleged infringers. |
||||
|
||||
## Who is responsible for what I see and do on the Services? |
||||
|
||||
Any information or content publicly posted or privately transmitted through the Services is the sole responsibility of the person from whom such content originated, and you access all such information and content at your own risk, and we aren’t liable for any errors or omissions in that information or content or for any damages or loss you might suffer in connection with it. We cannot control and have no duty to take any action regarding how you may interpret and use the Content or what actions you may take as a result of having been exposed to the Content, and you hereby release us from all liability for you having acquired or not acquired Content through the Services. We can’t guarantee the identity of any users with whom you interact in using the Services and are not responsible for which users gain access to the Services. |
||||
|
||||
You are responsible for all Content you contribute, in any manner, to the Services, and you represent and warrant you have all rights necessary to do so, in the manner in which you contribute it. You will keep all your registration information accurate and current. You are responsible for all your activity in connection with the Services. |
||||
|
||||
The Services may contain links or connections to third party websites or services that are not owned or controlled by roadmap.sh. When you access third party websites or use third party services, you accept that there are risks in doing so, and that roadmap.sh is not responsible for such risks. We encourage you to be aware when you leave the Services and to read the terms and conditions and privacy policy of each third party website or service that you visit or utilize. |
||||
|
||||
roadmap.sh has no control over, and assumes no responsibility for, the content, accuracy, privacy policies, or practices of or opinions expressed in any third party websites or by any third party that you interact with through the Services. In addition, roadmap.sh will not and cannot monitor, verify, censor or edit the content of any third party site or service. By using the Services, you release and hold us harmless from any and all liability arising from your use of any third party website or service. |
||||
|
||||
Your interactions with organizations and/or individuals found on or through the Services, including payment and delivery of goods or services, and any other terms, conditions, warranties or representations associated with such dealings, are solely between you and such organizations and/or individuals. You should make whatever investigation you feel necessary or appropriate before proceeding with any online or offline transaction with any of these third parties. You agree that roadmap.sh shall not be responsible or liable for any loss or damage of any sort incurred as the result of any such dealings. |
||||
|
||||
If there is a dispute between participants on this site, or between users and any third party, you agree that roadmap.sh is under no obligation to become involved. In the event that you have a dispute with one or more other users, you release roadmap.sh, its officers, employees, agents, and successors from claims, demands, and damages of every kind or nature, known or unknown, suspected or unsuspected, disclosed or undisclosed, arising out of or in any way related to such disputes and/or our Services. If you are a California resident, you shall and hereby do waive California Civil Code Section 1542, which says: "A general release does not extend to claims which the creditor does not know or suspect to exist in his or her favor at the time of executing the release, which, if known by him or her must have materially affected his or her settlement with the debtor." |
||||
|
||||
## Will roadmap.sh ever change the Services? |
||||
|
||||
We’re always trying to improve the Services, so they may change over time. We may suspend or discontinue any part of the Services, or we may introduce new features or impose limits on certain features or restrict access to parts or all of the Services. We’ll try to give you notice when we make a material change to the Services that would adversely affect you, but this isn’t always practical. Similarly, we reserve the right to remove any Content from the Services at any time, for any reason (including, but not limited to, if someone alleges you contributed that Content in violation of these Terms), in our sole discretion, and without notice. |
||||
|
||||
## Does roadmap.sh cost anything? |
||||
|
||||
The roadmap.sh Services are currently free, but we reserve the right to charge for certain or all Services in the future. We will notify you before any Services you are then using begin carrying a fee, and if you wish to continue using such Services, you must pay all applicable fees for such Services. |
||||
|
||||
## What if I want to stop using roadmap.sh? |
||||
|
||||
You’re free to do that at any time, by contacting us at kamranahmed.se@gmail.com; please refer to our Privacy Policy, as well as the licenses above, to understand how we treat information you provide to us after you have stopped using our Services. roadmap.sh is also free to terminate (or suspend access to) your use of the Services or your account, for any reason in our discretion, including your breach of these Terms. roadmap.sh has the sole right to decide whether you are in violation of any of the restrictions set forth in these Terms. |
||||
|
||||
Account termination may result in destruction of any Content associated with your account, so keep that in mind before you decide to terminate your account. We will try to provide advance notice to you prior to our terminating your account so that you are able to retrieve any important User Submissions you may have stored in your account (to the extent allowed by law and these Terms), but we may not do so if we determine it would be impractical, illegal, not in the interest of someone’s safety or security, or otherwise harmful to the rights or property of roadmap.sh. |
||||
|
||||
Provisions that, by their nature, should survive termination of these Terms shall survive termination. By way of example, all of the following will survive termination: any obligation you have to pay us or indemnify us, any limitations on our liability, any terms regarding ownership or intellectual property rights, and terms regarding disputes between us. |
||||
|
||||
## What if I use roadmap.sh via an app available on the Apple App Store? |
||||
|
||||
These Terms apply to your use of all the Services, including the iOS applications available via the Apple, Inc. (“Apple”) App Store (the “Application”), but the following additional terms also apply to the Application: |
||||
|
||||
(a) Both you and roadmap.sh acknowledge that the Terms are concluded between you and roadmap.sh only, and not with Apple, and that Apple is not responsible for the Application or the Content; (b) The Application is licensed to you on a limited, non-exclusive, non-transferrable, non-sublicensable basis, solely to be used in connection with the Services for your private, personal, non-commercial use, subject to all the terms and conditions of these Terms as they are applicable to the Services; (c) You will only use the Application in connection with an Apple device that you own or control; (d) You acknowledge and agree that Apple has no obligation whatsoever to furnish any maintenance and support services with respect to the Application; (e) In the event of any failure of the Application to conform to any applicable warranty, including those implied by law, you may notify Apple of such failure; upon notification, Apple’s sole warranty obligation to you will be to refund to you the purchase price, if any, of the Application; (f) You acknowledge and agree that roadmap.sh, and not Apple, is responsible for addressing any claims you or any third party may have in relation to the Application; (g) You acknowledge and agree that, in the event of any third party claim that the Application or your possession and use of the Application infringes that third party’s intellectual property rights, roadmap.sh, and not Apple, will be responsible for the investigation, defense, settlement and discharge of any such infringement claim; (h) You represent and warrant that you are not located in a country subject to a U.S. Government embargo, or that has been designated by the U.S. Government as a “terrorist supporting” country, and that you are not listed on any U.S. Government list of prohibited or restricted parties; (i) Both you and roadmap.sh acknowledge and agree that, in your use of the Application, you will comply with any applicable third party terms of agreement which may affect or be affected by such use; and (j) Both you and roadmap.sh acknowledge and agree that Apple and Apple’s subsidiaries are third party beneficiaries of these Terms, and that upon your acceptance of these Terms, Apple will have the right (and will be deemed to have accepted the right) to enforce these Terms against you as the third party beneficiary hereof. |
||||
|
||||
|
||||
## What are roadmap.sh's Terms of Sale? |
||||
|
||||
If you purchase any goods or services or license any software through the site whether or not in connection with an Offer or Discount, in addition to agreeing to these Terms of Use, you are agreeing to the Terms of Sale, available here. |
||||
|
||||
## What else do I need to know? |
||||
|
||||
Warranty Disclaimer. Neither roadmap.sh nor its licensors or suppliers makes any representations or warranties concerning any content contained in or accessed through the Services, and we will not be responsible or liable for the accuracy, copyright compliance, legality, or decency of material contained in or accessed through the Services. We (and our licensors and suppliers) make no representations or warranties regarding suggestions or recommendations of services or products offered or purchased through the Services. Products and services purchased or offered (whether or not following such recommendations and suggestions) through the Services are provided “AS IS” and without any warranty of any kind from roadmap.sh or others (unless, with respect to such others only, provided expressly and unambiguously in writing by a designated third party for a specific product). THE SERVICES AND CONTENT ARE PROVIDED BY ROADMAP.SH (AND ITS LICENSORS AND SUPPLIERS) ON AN “AS-IS” BASIS, WITHOUT WARRANTIES OR ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR THAT USE OF THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE. SOME STATES DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. |
||||
|
||||
Limitation of Liability. TO THE FULLEST EXTENT ALLOWED BY APPLICABLE LAW, UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, TORT, CONTRACT, STRICT LIABILITY, OR OTHERWISE) SHALL ROADMAP.SH (OR ITS LICENSORS OR SUPPLIERS) BE LIABLE TO YOU OR TO ANY OTHER PERSON FOR (A) ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND, INCLUDING DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE, ACCURACY OF RESULTS, OR COMPUTER FAILURE OR MALFUNCTION, OR (B) ANY AMOUNT, IN THE AGGREGATE, IN EXCESS OF THE GREATER OF (I) $100 OR (II) THE AMOUNTS PAID BY YOU TO ROADMAP.SH IN CONNECTION WITH THE SERVICES IN THE TWELVE (12) MONTH PERIOD PRECEDING THIS APPLICABLE CLAIM, OR (III) ANY MATTER BEYOND OUR REASONABLE CONTROL. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES, SO THE ABOVE LIMITATION AND EXCLUSIONS MAY NOT APPLY TO YOU. |
||||
|
||||
Indemnity. To the fullest extent allowed by applicable law, You agree to indemnify and hold roadmap.sh, its affiliates, officers, agents, employees, and partners harmless from and against any and all claims, liabilities, damages (actual and consequential), losses and expenses (including attorneys’ fees) arising from or in any way related to any third party claims relating to (a) your use of the Services (including any actions taken by a third party using your account), and (b) your violation of these Terms. In the event of such a claim, suit, or action (“Claim”), we will attempt to provide notice of the Claim to the contact information we have for your account (provided that failure to deliver such notice shall not eliminate or reduce your indemnification obligations hereunder). |
||||
|
||||
Assignment. You may not assign, delegate or transfer these Terms or your rights or obligations hereunder, or your Services account, in any way (by operation of law or otherwise) without roadmap.sh’s prior written consent. We may transfer, assign, or delegate these Terms and our rights and obligations without consent. |
||||
|
||||
Choice of Law; Arbitration. These Terms are governed by and will be construed under the laws of the State of California, without regard to the conflicts of laws provisions thereof. Any dispute arising from or relating to the subject matter of these Terms shall be finally settled in San Francisco County, California, in English, in accordance with the Streamlined Arbitration Rules and Procedures of Judicial Arbitration and Mediation Services, Inc. ("JAMS") then in effect, by one commercial arbitrator with substantial experience in resolving intellectual property and commercial contract disputes, who shall be selected from the appropriate list of JAMS arbitrators in accordance with such Rules. Judgment upon the award rendered by such arbitrator may be entered in any court of competent jurisdiction. Notwithstanding the foregoing obligation to arbitrate disputes, each party shall have the right to pursue injunctive or other equitable relief at any time, from any court of competent jurisdiction. For all purposes of this Agreement, the parties consent to exclusive jurisdiction and venue in the state or federal courts located in, respectively, San Francisco County, California, or the Northern District of California. Any arbitration under this Agreement will take place on an individual basis: class arbitrations and class actions are not permitted. YOU UNDERSTAND AND AGREE THAT BY ENTERING INTO THIS AGREEMENT, YOU AND ROADMAP.SH ARE EACH WAIVING THE RIGHT TO TRIAL BY JURY OR TO PARTICIPATE IN A CLASS ACTION. |
||||
|
||||
Miscellaneous. You will be responsible for paying, withholding, filing, and reporting all taxes, duties, and other governmental assessments associated with your activity in connection with the Services, provided that roadmap.sh may, in its sole discretion, do any of the foregoing on your behalf or for itself as it sees fit. The failure of either you or us to exercise, in any way, any right herein shall not be deemed a waiver of any further rights hereunder. If any provision of these Terms is found to be unenforceable or invalid, that provision will be limited or eliminated, to the minimum extent necessary, so that these Terms shall otherwise remain in full force and effect and enforceable. You and roadmap.sh agree that these Terms are the complete and exclusive statement of the mutual understanding between you and roadmap.sh, and that it supersedes and cancels all previous written and oral agreements, communications and other understandings relating to the subject matter of these Terms. You hereby acknowledge and agree that you are not an employee, agent, partner, or joint venture of roadmap.sh, and you do not have any authority of any kind to bind roadmap.sh in any respect whatsoever. Except as expressly set forth in the section above regarding the Apple Application, you and roadmap.sh agree there are no third party beneficiaries intended under these Terms. |
||||
|
||||
|
||||
|
||||
@ -0,0 +1,284 @@ |
||||
[ |
||||
{ |
||||
"seo": { |
||||
"title": "Learn to become a modern frontend developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for modern frontend development. Learn to become a modern frontend developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a developer", |
||||
"guide to becoming a frontend developer", |
||||
"frontend developer", |
||||
"frontend engineer", |
||||
"frontend skills", |
||||
"frontend development", |
||||
"javascript developer", |
||||
"frontend development skills", |
||||
"frontend development skills test", |
||||
"frontend engineer roadmap", |
||||
"frontend developer roadmap", |
||||
"become a frontend developer", |
||||
"frontend developer career path", |
||||
"javascript developer", |
||||
"modern javascript developer", |
||||
"node developer", |
||||
"skills for frontend development", |
||||
"learn frontend development", |
||||
"what is frontend development", |
||||
"frontend developer quiz", |
||||
"frontend developer interview questions" |
||||
] |
||||
}, |
||||
"title": "Frontend Developer", |
||||
"description": "Step by step guide to becoming a modern frontend developer in 2021", |
||||
"featuredTitle": "Frontend", |
||||
"featuredDescription": "Step by step guide to becoming a frontend developer in 2021", |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"featured": true, |
||||
"imagePath": "/roadmaps/frontend.png", |
||||
"resourcesPath": "/roadmaps/1-frontend/resources.md", |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/frontend-roadmap", |
||||
"id": "frontend", |
||||
"isUpcoming": false |
||||
}, |
||||
{ |
||||
"seo": { |
||||
"title": "Learn to become a modern backend developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for modern backend development. Learn to become a modern backend developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a developer", |
||||
"guide to becoming a backend developer", |
||||
"backend developer", |
||||
"backend engineer", |
||||
"backend skills", |
||||
"backend development", |
||||
"javascript developer", |
||||
"backend development skills", |
||||
"backend development skills test", |
||||
"backend engineer roadmap", |
||||
"backend developer roadmap", |
||||
"become a backend developer", |
||||
"backend developer career path", |
||||
"javascript developer", |
||||
"modern javascript developer", |
||||
"node developer", |
||||
"skills for backend development", |
||||
"learn backend development", |
||||
"what is backend development", |
||||
"backend developer quiz", |
||||
"backend developer interview questions" |
||||
] |
||||
}, |
||||
"title": "Backend Developer", |
||||
"description": "Step by step guide to becoming a modern backend developer in 2021", |
||||
"featuredTitle": "Backend", |
||||
"featuredDescription": "Step by step guide to becoming a backend developer in 2021", |
||||
"featured": true, |
||||
"imagePath": "/roadmaps/backend.png", |
||||
"resourcesPath": "/roadmaps/2-backend/resources.md", |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/backend-roadmap", |
||||
"id": "backend", |
||||
"isUpcoming": false |
||||
}, |
||||
{ |
||||
"seo": { |
||||
"title": "DevOps Roadmap: Learn to become a DevOps Engineer or SRE", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for DevOps. Learn to become a modern DevOps engineer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a devops enginer", |
||||
"devops roadmap", |
||||
"sre roadmap", |
||||
"site reliability engineer roadmap", |
||||
"operations roles", |
||||
"become devops", |
||||
"devops skills", |
||||
"modern devops skills", |
||||
"devops skills test", |
||||
"skills for devops", |
||||
"learn devops", |
||||
"what is devops", |
||||
"what is sre", |
||||
"devops quiz", |
||||
"devops interview questions" |
||||
] |
||||
}, |
||||
"title": "DevOps Roadmap", |
||||
"description": "Step by step guide for DevOps, SRE or any other Operations Role in 2021", |
||||
"featuredTitle": "DevOps", |
||||
"featuredDescription": "Step by step guide for DevOps or operations role in 2021", |
||||
"featured": true, |
||||
"imagePath": "/roadmaps/devops.png", |
||||
"resourcesPath": "/roadmaps/3-devops/resources.md", |
||||
"versions": [ |
||||
"latest", |
||||
"2018", |
||||
"2017" |
||||
], |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/devops-roadmap", |
||||
"id": "devops", |
||||
"isUpcoming": false |
||||
}, |
||||
{ |
||||
"seo": { |
||||
"title": "React Developer Roadmap: Learn to become a React developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for react development. Learn to become a modern React developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a react developer", |
||||
"react developer roadmap", |
||||
"react roadmap", |
||||
"become react developer", |
||||
"react developer skills", |
||||
"react skills test", |
||||
"skills for react development", |
||||
"learn react development", |
||||
"what is react", |
||||
"react quiz", |
||||
"react interview questions" |
||||
] |
||||
}, |
||||
"title": "React Developer", |
||||
"description": "Everything that is there to learn about React and the ecosystem in 2021.", |
||||
"featuredTitle": "React", |
||||
"featuredDescription": "Step by step guide to become a React Developer in 2021", |
||||
"isTextHeavy": false, |
||||
"isCommunity": false, |
||||
"featured": true, |
||||
"contentPath": "/roadmaps/4-react/landscape.md", |
||||
"resourcesPath": "/roadmaps/4-react/resources.md", |
||||
"versions": [ |
||||
"latest", |
||||
"2018", |
||||
"2017" |
||||
], |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/react-roadmap", |
||||
"id": "react", |
||||
"isUpcoming": false |
||||
}, |
||||
{ |
||||
"seo": { |
||||
"title": "DBA Roadmap: Learn to become a database administrator with PostgreSQL", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for DevOps. Learn to become a modern DevOps engineer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a database administrator", |
||||
"guide to becoming a DBA", |
||||
"dba roadmap", |
||||
"db administrator roadmap", |
||||
"database administrator roadmap", |
||||
"postgresql roadmap", |
||||
"dba skills", |
||||
"db administrator skills", |
||||
"become dba", |
||||
"postgresql skills", |
||||
"modern dba skills", |
||||
"dba skills test", |
||||
"skills for dba", |
||||
"skills for database administrator", |
||||
"learn dba", |
||||
"what is dba", |
||||
"database administrator quiz", |
||||
"dba interview questions" |
||||
] |
||||
}, |
||||
"title": "PostgreSQL DBA", |
||||
"description": "Step by step guide to becoming a modern PostgreSQL DB Administrator in 2021", |
||||
"featuredTitle": "DBA", |
||||
"featuredDescription": "Step by step guide to become a PostgreSQL DBA in 2021", |
||||
"contentPath": "/roadmaps/5-postgresql-dba/landscape.md", |
||||
"resourcesPath": "/roadmaps/5-postgresql-dba/resources.md", |
||||
"author": { |
||||
"name": "Alexey Lesovsky", |
||||
"url": "https://github.com/lesovsky" |
||||
}, |
||||
"isCommunity": true, |
||||
"isTextHeavy": true, |
||||
"featured": true, |
||||
"detailed": false, |
||||
"versions": [], |
||||
"id": "postgresql-dba", |
||||
"isUpcoming": false |
||||
}, |
||||
{ |
||||
"seo": { |
||||
"title": "Android Developer Roadmap: Learn to become an Android developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for android development. Learn to become a modern Android developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming an android developer", |
||||
"android developer roadmap", |
||||
"android roadmap", |
||||
"become android developer", |
||||
"android developer skills", |
||||
"android skills test", |
||||
"skills for android development", |
||||
"learn android development", |
||||
"what is android", |
||||
"android quiz", |
||||
"android interview questions" |
||||
] |
||||
}, |
||||
"title": "Android Developer", |
||||
"description": "Step by step guide to becoming an Android developer in 2021", |
||||
"featuredTitle": "Android", |
||||
"featuredDescription": "Step by step guide to becoming an Android Developer in 2021", |
||||
"isTextHeavy": true, |
||||
"isCommunity": true, |
||||
"featured": true, |
||||
"contentPath": "/roadmaps/6-android/landscape.md", |
||||
"resourcesPath": "/roadmaps/6-android/resources.md", |
||||
"versions": [ |
||||
"latest", |
||||
"2018", |
||||
"2017" |
||||
], |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"id": "android", |
||||
"isUpcoming": false |
||||
}, |
||||
{ |
||||
"seo": { |
||||
"title": "QA Roadmap: Learn to become a modern QA engineer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for modern QA development. Learn to become a modern QA engineer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a QA engineer", |
||||
"QA engineer", |
||||
"QA skills", |
||||
"QA development skills", |
||||
"QA development skills test", |
||||
"QA engineer roadmap", |
||||
"become a QA engineer", |
||||
"QA engineer career path", |
||||
"skills for QA development", |
||||
"what is QA engineer", |
||||
"QA engineer quiz", |
||||
"QA engineer interview questions" |
||||
] |
||||
}, |
||||
"title": "QA Engineer", |
||||
"description": "Steps to follow in order to become a modern QA Engineer in 2021", |
||||
"featuredTitle": "QA", |
||||
"featuredDescription": "Step by step guide to becoming a modern QA Engineer in 2021", |
||||
"isUpcoming": true, |
||||
"contentPath": "/roadmaps/7-qa/landscape.md", |
||||
"resourcesPath": "/roadmaps/7-qa/resources.md", |
||||
"author": { |
||||
"name": "Anas Fitiani", |
||||
"url": "https://github.com/anas-qa" |
||||
}, |
||||
"id": "qa" |
||||
} |
||||
] |
||||
@ -0,0 +1,41 @@ |
||||
{ |
||||
"seo": { |
||||
"title": "Learn to become a modern frontend developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for modern frontend development. Learn to become a modern frontend developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a developer", |
||||
"guide to becoming a frontend developer", |
||||
"frontend developer", |
||||
"frontend engineer", |
||||
"frontend skills", |
||||
"frontend development", |
||||
"javascript developer", |
||||
"frontend development skills", |
||||
"frontend development skills test", |
||||
"frontend engineer roadmap", |
||||
"frontend developer roadmap", |
||||
"become a frontend developer", |
||||
"frontend developer career path", |
||||
"javascript developer", |
||||
"modern javascript developer", |
||||
"node developer", |
||||
"skills for frontend development", |
||||
"learn frontend development", |
||||
"what is frontend development", |
||||
"frontend developer quiz", |
||||
"frontend developer interview questions" |
||||
] |
||||
}, |
||||
"title": "Frontend Developer", |
||||
"description": "Step by step guide to becoming a modern frontend developer in 2021", |
||||
"featuredTitle": "Frontend", |
||||
"featuredDescription": "Step by step guide to becoming a frontend developer in 2021", |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"featured": true, |
||||
"imagePath": "/roadmaps/frontend.png", |
||||
"resourcesPath": "./resources.md", |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/frontend-roadmap" |
||||
} |
||||
@ -0,0 +1,76 @@ |
||||
<div className='alert alert-primary' style={{ marginBottom: '-10px'}}> |
||||
This page is incomplete and is being worked upon. Please check back later or <a href='/signup'>subscribe</a> / <a href='https://twitter.com/kamranahmedse'>follow me on twitter</a> to get notified. Also, feel free to contribute by suggesting the resources in <a href='https://github.com/kamranahmedse/developer-roadmap'>the issues</a>. |
||||
</div> |
||||
|
||||
# Become a Frontend Developer |
||||
Before I go ahead and list down the resources, please know that the roadmap and the list below is exhaustive and you don't need to know it all from the get go. For frontend development, all you need to get started with is learn some basic HTML, CSS and JavaScript and start working on projects; everything else you will learn along the way. |
||||
|
||||
## Internet and how it works? |
||||
|
||||
Get the basic understanding of internet, browsers, networks and other relevant knowledge. |
||||
|
||||
* <BadgeLink badgeText='Read' href='/guides/what-is-internet'>What is Internet?</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=7_LPdttKXPc'>How the internet works in 5 minutes</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://kamranahmed.info/blog/2016/08/13/http-in-depth/'>What is HTTP and how it evolved?</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://blog.cloudflare.com/http3-the-past-present-and-future/'>HTTP/3: the past, the present, and the future</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://kinsta.com/blog/http3/'>What Is HTTP/3 – Lowdown on the Fast New UDP-Based Protocol</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://www.html5rocks.com/en/tutorials/internals/howbrowserswork/'>How Browsers Work: Behind the scenes of modern web browsers</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=Rck3BALhI5c'>DNS as Fast As Possible</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://howdns.works/'>How DNS works?</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='/guides/dns-in-one-picture'>DNS in One Picture</BadgeLink> |
||||
|
||||
## Learn HTML |
||||
HTML provides the skeleton of a webpage. Learn the basics of HTML; learn the basic tags, learn how to write semantic HTML, understand basic SEO, learn how to divide your pages into sections that will help you style them. |
||||
|
||||
Please know that I have put multiple links for each resource. While you may pick something new while going through each, you don't need to go through all of them - if you feel like you have understood the concepts and are just repeating what you learnt, you may skip the resource and move to exercises section. |
||||
|
||||
|
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=UB1O30fR-EE'>HTML Crash Course For Absolute Beginners</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://www.w3schools.com/html/default.asp'>W3Schools – HTML Tutorial</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=pQN-pnXPaVg'>HTML Full Course - Build a Website Tutorial</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://hacks.mozilla.org/2016/08/a-few-html-tips/'>A few HTML tips</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://hackernoon.com/six-tips-to-set-up-a-better-html-document-ud1033z3z'>Six tips to set up a better HTML document</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://www.w3schools.com/html/html5_semantic_elements.asp'>HTML Semantic Elements</BadgeLink> |
||||
* <BadgeLink badgeText='Read' href='https://developer.mozilla.org/en-US/docs/Web/HTML/Element'>HTML elements reference</BadgeLink> |
||||
|
||||
## Style your pages with CSS |
||||
With the help of HTML, you create structure for your pages. CSS allows you to style your pages and make them pretty. If you take the analogy of human body, the skeleton would be the HTML, skin would be the CSS and muscles that help us move would be JavaScript - we will learn more about JavaScript in the coming sections. |
||||
|
||||
* <BadgeLink badgeText='Read' href='https://www.w3schools.com/css/'>W3Schools – CSS Tutorial</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=yfoY53QXEnI'>CSS Crash Course For Absolute Beginners</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=Wm6CUkswsNw'>Build An HTML5 Website With A Responsive Layout</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://youtu.be/JJSoEo8JSnc?t=46'>Flexbox CSS In 20 Minutes</BadgeLink> |
||||
|
||||
## Basics of JavaScript |
||||
JavaScript allows you to add interactivity to your pages. Common examples that you may have seen on the websites are sliders, click interactions, popups and so on. In this section, you will learn the basics of JavaScript. |
||||
|
||||
* <BadgeLink badgeText='Read' href='https://www.w3schools.com/js/'>W3Schools – JavaScript Tutorial</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://youtu.be/hdI2bqOjy3c?t=2'>JavaScript Crash Course for Beginners</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://youtu.be/P7t13SGytRk?t=22'>Build a Netflix Landing Page Clone with HTML, CSS & JS</BadgeLink> |
||||
|
||||
## Version Control Systems and Git |
||||
|
||||
Version control systems allow you to track changes to your codebase/files over time. They allow you to go back to some previous version of the codebase without any issues. Also, they help in collaborating with people working on the same code – if you’ve ever collaborated with other people on a project, you might already know the frustration of copying and merging the changes from someone else into your codebase; version control systems allow you to get rid of this issue. |
||||
|
||||
In this section, you will learn what version control systems are and understand how to use Git which is the de facto VCS. |
||||
|
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=zbKdDsNNOhg'>Version Control System Introduction</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=SWYqp7iY_Tc'>Git & GitHub Crash Course For Beginners</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://youtu.be/Y9XZQO1n_7c?t=21'>Learn Git in 20 Minutes</BadgeLink> |
||||
|
||||
Now that you know what git is go ahead and create an account on [GitHub](https://github.com) and push everything that you do from now on to GitHub so that you can get the practice and get it reviewed from the other people in the community. |
||||
|
||||
## Modern JavaScript |
||||
|
||||
In this section you will learn how to use package managers and get started with the "modern JavaScript". |
||||
|
||||
* <BadgeLink badgeText='Read' href='https://medium.com/the-node-js-collection/modern-javascript-explained-for-dinosaurs-f695e9747b70'>Modern JavaScript for Dinosaurs (Don't worry if you don't understand some parts of it)</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=8Rmj5UY5mJk'>What is NPM and how to use it</BadgeLink> |
||||
* <BadgeLink variant='primary' badgeText='Watch' href='https://www.youtube.com/watch?v=jHDhaSSKmB0'>NPM Crash Course</BadgeLink> |
||||
|
||||
<br /> |
||||
<br /> |
||||
<br /> |
||||
<br /> |
||||
<br /> |
||||
<br /> |
||||
@ -0,0 +1,41 @@ |
||||
{ |
||||
"seo": { |
||||
"title": "Learn to become a modern backend developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for modern backend development. Learn to become a modern backend developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a developer", |
||||
"guide to becoming a backend developer", |
||||
"backend developer", |
||||
"backend engineer", |
||||
"backend skills", |
||||
"backend development", |
||||
"javascript developer", |
||||
"backend development skills", |
||||
"backend development skills test", |
||||
"backend engineer roadmap", |
||||
"backend developer roadmap", |
||||
"become a backend developer", |
||||
"backend developer career path", |
||||
"javascript developer", |
||||
"modern javascript developer", |
||||
"node developer", |
||||
"skills for backend development", |
||||
"learn backend development", |
||||
"what is backend development", |
||||
"backend developer quiz", |
||||
"backend developer interview questions" |
||||
] |
||||
}, |
||||
"title": "Backend Developer", |
||||
"description": "Step by step guide to becoming a modern backend developer in 2021", |
||||
"featuredTitle": "Backend", |
||||
"featuredDescription": "Step by step guide to becoming a backend developer in 2021", |
||||
"featured": true, |
||||
"imagePath": "/roadmaps/backend.png", |
||||
"resourcesPath": "./resources.md", |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/backend-roadmap" |
||||
} |
||||
@ -0,0 +1,7 @@ |
||||
> **We are still preparing the resources**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the list, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
@ -0,0 +1,40 @@ |
||||
{ |
||||
"seo": { |
||||
"title": "DevOps Roadmap: Learn to become a DevOps Engineer or SRE", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for DevOps. Learn to become a modern DevOps engineer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a devops enginer", |
||||
"devops roadmap", |
||||
"sre roadmap", |
||||
"site reliability engineer roadmap", |
||||
"operations roles", |
||||
"become devops", |
||||
"devops skills", |
||||
"modern devops skills", |
||||
"devops skills test", |
||||
"skills for devops", |
||||
"learn devops", |
||||
"what is devops", |
||||
"what is sre", |
||||
"devops quiz", |
||||
"devops interview questions" |
||||
] |
||||
}, |
||||
"title": "DevOps Roadmap", |
||||
"description": "Step by step guide for DevOps, SRE or any other Operations Role in 2021", |
||||
"featuredTitle": "DevOps", |
||||
"featuredDescription": "Step by step guide for DevOps or operations role in 2021", |
||||
"featured": true, |
||||
"imagePath": "/roadmaps/devops.png", |
||||
"resourcesPath": "./resources.md", |
||||
"versions": [ |
||||
"latest", |
||||
"2018", |
||||
"2017" |
||||
], |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/devops-roadmap" |
||||
} |
||||
@ -0,0 +1,7 @@ |
||||
> **We are still preparing the resources**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the list, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
@ -0,0 +1,7 @@ |
||||
The intent of this guide is to give you an idea about the React ecosystem and to help guide your learning if you are confused. We have another [roadmap on the Frontend Development](/frontend) that focuses on the frontend development if you are interested in that. |
||||
|
||||
Also, please note that the list below is exhaustive, and the items are listed in no particular order. You don't need to learn everything listed in the picture, however knowing what you don't know is as important as knowing things. |
||||
|
||||
 |
||||
|
||||
Please note that the list is opinionated, and you might have different opinions than those of the author. Having said that, [we would love to hear your opinions](https://github.com/kamranahmedse/roadmap.sh/issues/new) and incorporate them in the picture if suitable. |
||||
@ -0,0 +1,38 @@ |
||||
{ |
||||
"seo": { |
||||
"title": "React Developer Roadmap: Learn to become a React developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for react development. Learn to become a modern React developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a react developer", |
||||
"react developer roadmap", |
||||
"react roadmap", |
||||
"become react developer", |
||||
"react developer skills", |
||||
"react skills test", |
||||
"skills for react development", |
||||
"learn react development", |
||||
"what is react", |
||||
"react quiz", |
||||
"react interview questions" |
||||
] |
||||
}, |
||||
"title": "React Developer", |
||||
"description": "Everything that is there to learn about React and the ecosystem in 2021.", |
||||
"featuredTitle": "React", |
||||
"featuredDescription": "Step by step guide to become a React Developer in 2021", |
||||
"isTextHeavy": false, |
||||
"isCommunity": false, |
||||
"featured": true, |
||||
"contentPath": "./landscape.md", |
||||
"resourcesPath": "./resources.md", |
||||
"versions": [ |
||||
"latest", |
||||
"2018", |
||||
"2017" |
||||
], |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
}, |
||||
"pdfUrl": "https://kamranahmedse.gumroad.com/l/react-roadmap" |
||||
} |
||||
@ -0,0 +1,7 @@ |
||||
> **We are still preparing the resources**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the list, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
@ -0,0 +1,180 @@ |
||||
The intent of this guide is to give you an idea about the DBA landscape and to help guide your learning if you are confused. The roadmap is highly opinionated — neither, knowing everything listed in the roadmap, nor the order of items given in the roadmap is required to be followed in order to be a DBA. |
||||
|
||||
## Learn basic RDBMS terms and concepts |
||||
Get basic understanding of Postgres key terms and basic RDBMS concepts. |
||||
|
||||
- **Object model**: data types, columns, rows, tables, schemas, databases, queries. |
||||
- **Relational model**: domains, attributes, tuples, relations, constraints, NULL. |
||||
- **Databases high-level concepts**: ACID, MVCC, transactions, write-ahead log, query processing. |
||||
- **Links**: |
||||
- [Postgres Glossary](https://www.postgresql.org/docs/13/glossary.html) |
||||
- SQL and Relational Theory - Christopher J. Date, 2009 |
||||
- Database Design and Relational Theory - Christopher J. Date, 2012 |
||||
|
||||
## Learn how to install and run PostgreSQL |
||||
Get practical skills of how to set up and run Postgres to get a working environment for further learning. |
||||
|
||||
- Using package managers (APT, YUM, etc.) |
||||
- Using `docker`. |
||||
- Managing Postgres service using `systemd` (start, stop, restart, reload). |
||||
- Managing Postgres service using `pg_ctl`, or OS-specific tools (like `pg_ctlcluster`). |
||||
- Connect to Postgres using `psql`. |
||||
- Deploy database service in cloud environment (AWS, GCE, Azure, Heroku, DigitalOcean, etc...). |
||||
- **Links**: |
||||
- [Official download and install instructions](https://www.postgresql.org/download/) |
||||
- [Official Docker images](https://hub.docker.com/_/postgres) |
||||
|
||||
## Learn SQL concepts |
||||
Get practical skills of how to create and manipulate database objects and how to execute queries using `psql` client. |
||||
- Understand basic data types. |
||||
- **DML queries**: querying data, modifying data, filtering data, joining tables. |
||||
- **Advanced topics**: transactions, CTE, subqueries, lateral join, grouping, set operations. |
||||
- **DDL queries**: managing tables and schemas (create, alter, drop). |
||||
- Import and export data using `COPY`. |
||||
- **Links**: |
||||
- [DB Fiddle](https://www.db-fiddle.com/) |
||||
- [PostgreSQL Tutorial](https://www.postgresqltutorial.com/) |
||||
- [PostgreSQL SQL Getting Started](https://www.postgresql.org/docs/current/tutorial-sql.html) |
||||
- [The SQL Language](https://www.postgresql.org/docs/current/sql.html) |
||||
|
||||
## Learn how to configure Postgres |
||||
Get understanding of the main aspects of how Postgres could be configured. Deep understanding of Postgres internals is not yet necessary here. |
||||
|
||||
- postgresql.conf: |
||||
- Resources usage |
||||
- Write-ahead Log |
||||
- Checkpoints and Background Writer |
||||
- Cost-based vacuum and auto-vacuum |
||||
- Replication |
||||
- Query planner |
||||
- Reporting, logging and statistics |
||||
- Adding extra extensions |
||||
- ...keep exploring other configuration options |
||||
- **Links**: |
||||
- [Postgresqlco.nf](http://postgresqlco.nf/) |
||||
|
||||
## Learn Postgres security concepts |
||||
Get understanding about basic security concepts and common ways of how to deploy secure configurations. |
||||
- Authentication models, roles, pg_hba.conf, SSL settings. |
||||
- **Objects privileges**: grant/revoke, default privileges. |
||||
- **Advanced topics** - row-level security, selinux. |
||||
- **Links**: |
||||
- [Client authentication](https://www.postgresql.org/docs/current/client-authentication.html) |
||||
- [Roles and users managements](https://www.postgresql.org/docs/current/user-manag.html) |
||||
|
||||
## Develop infrastructure DBA skills |
||||
Get practical skills of how to deploy, extend, maintain and support Postgres installations and 3rd-party Postgres ecosystem software. |
||||
- **Replication**: streaming replication, logical replication |
||||
- **Backup/recovery tools**: |
||||
- Built-in: `pg_dump`, `pg_dumpall`, `pg_restore`, `pg_basebackup` |
||||
- 3rd-party: `barman`, `pgbackrest`, `pg_probackup`, `WAL-G` |
||||
- Backup validation procedures |
||||
- **Upgrading procedures** |
||||
- Minor and major upgrades using `pg_upgrade` |
||||
- Upgrades using logical replication |
||||
- **Connection pooling**: |
||||
- `Pgbouncer` |
||||
- Alternatives: `Pgpool-II`, `Odyssey`, `Pgagroal` |
||||
- **Infrastructure monitoring**: `Prometheus`, `Zabbix`, other favourite monitoring solution |
||||
- **High availability and cluster management tools**: |
||||
- `Patroni` |
||||
- **Alternatives**: `Repmgr`, `Stolon`, `pg_auto_failover`, `PAF` |
||||
- **Applications Load Balancing and Service Discovery**: `Haproxy`, `Keepalived`, `Consul`, `Etcd` |
||||
- **Deploy Postgres on `Kubernetes`**: Simple `StatefulSet` setup, `HELM`, operators |
||||
- Resource usage and provisioning, capacity planning |
||||
|
||||
## Learn how to automate routines |
||||
Get practical skills, learn automation tools and automate existing routine tasks. |
||||
- Automation using shell scripts or any other favourite language (`Bash`, `Python`, `Perl`, etc) |
||||
- Configuration management: `Ansible`, `Salt`, `Chef`, `Puppet` |
||||
|
||||
## Develop application DBA skills |
||||
Learn theory and get practical skills of how applications should work with Postgres |
||||
- **Migrations**: |
||||
- practical patterns and antipatterns |
||||
- tools: `liquibase`, `sqitch`, language-specific tools |
||||
- Data import/export, bulk loading and processing |
||||
- **Queues**: |
||||
- practical patterns and anti-patterns |
||||
- `Skytools PGQ` |
||||
- Data partitioning and sharding patterns. |
||||
- Database normalization and normal forms. |
||||
- Books: |
||||
- The Art of PostgreSQL - Dimitri Fontaine, 2020 |
||||
|
||||
## Learn Postgres advanced topics |
||||
Here is important to continuously extend and develop existing knowledge about Postgres. |
||||
- **Low level internals**: |
||||
- Processes and memory architecture |
||||
- Vacuum processing |
||||
- Buffer management |
||||
- Lock management |
||||
- [Physical storage and file layout](https://www.postgresql.org/docs/current/storage.html) |
||||
- [System catalog](https://www.postgresql.org/docs/current/catalogs.html) |
||||
- **Fine-grained tuning**: |
||||
- Per-user, per-database settings |
||||
- [Storage parameters](https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS) |
||||
- Workload-dependant tuning: OLTP, OLAP, HTAP |
||||
- **Advanced SQL topics**: |
||||
- PL/pgSQL, procedures and functions, triggers |
||||
- Aggregate and window functions |
||||
- Recursive CTE |
||||
- **Links**: |
||||
- [The Internals of PostgreSQL](http://www.interdb.jp/pg/index.html) for database administrators and system developers |
||||
- [PL/pgSQL Guide](https://www.postgresql.org/docs/current/plpgsql.html) |
||||
|
||||
## Learn Postgres troubleshooting techniques |
||||
Get basic understanding about troubleshooting tools and get practical skills of how to detect and resolve problems. |
||||
- **Operating system tools** |
||||
- `top` (`htop`, `atop`) |
||||
- `sysstat` |
||||
- `iotop` |
||||
- **Postgres system views** |
||||
- `pg_stat_activity` |
||||
- `pg_stat_statements` |
||||
- **Postgres tools** |
||||
- `pgcenter` - *personal recommendation* |
||||
- **Query analyzing**: |
||||
- [EXPLAIN](https://www.postgresql.org/docs/current/sql-explain.html) |
||||
- [Depesz](https://explain.depesz.com/) online EXPLAIN visualization tool |
||||
- [PEV](https://tatiyants.com/pev/#/plans) online EXPLAIN visualization tool |
||||
- [Tensor](https://explain.tensor.ru/) online EXPLAIN visualization tool, RU language only |
||||
- **Log analyzing**: |
||||
- `pgBadger` |
||||
- Ad-hoc analyzing using `grep`, `awk`, `sed`, etc. |
||||
- **External tracing/profiling tools**: `gdb`, `strace`, `perf-tools`, `ebpf`, core dumps |
||||
- **Troubleshooting methods**: USE, RED, Golden signals |
||||
- **Links**: |
||||
- [Linux Performance](http://www.brendangregg.com/linuxperf.html) by Brendan Gregg |
||||
- [USE Method](http://www.brendangregg.com/usemethod.html) |
||||
|
||||
## Learn SQL optimization technics |
||||
Get understanding and practical skills of how to optimize SQL queries. |
||||
- **Indexes, and their use cases**: B-tree, Hash, GiST, SP-GiST, GIN, BRIN |
||||
- SQL queries patterns and anti-patterns |
||||
- SQL schema design patterns and anti-patterns |
||||
- **Links**: |
||||
- [Use the Index, Luke](https://use-the-index-luke.com/) - a Guide to Database Performance for Developers |
||||
- **Books**: |
||||
- SQL Antipatterns: Avoiding the Pitfalls of Database Programming - Bill Karwin, 2010 |
||||
|
||||
## Develop architect skills |
||||
Get deeper understanding of Postgres use cases and where Postgres is suitable and where is not. |
||||
- **Postgres forks and extensions**: `Greenplum`, `Timescaledb`, `Citus`, `Postgres-XL`, etc. |
||||
- RDBMS in general, benefits and limitations |
||||
- Differences between Postgres and other RDBMS and NoSQL databases |
||||
|
||||
## Develop Postgres hacker skills |
||||
Get involved to Postgres community and contribute to Postgres; be a useful member of Postgres, and the open source community; use personal experience to help other people. |
||||
- Daily reading and answering in [mailing lists](https://www.postgresql.org/list/) |
||||
- pgsql-general |
||||
- pgsql-admin |
||||
- pgsql-performance |
||||
- pgsql-hackers |
||||
- pgsql-bugs |
||||
- Reviewing patches |
||||
- Writing patches, attending in [Commitfests](https://commitfest.postgresql.org/) |
||||
|
||||
<br /> |
||||
<br /> |
||||
<br /> |
||||
@ -0,0 +1,41 @@ |
||||
{ |
||||
"seo": { |
||||
"title": "DBA Roadmap: Learn to become a database administrator with PostgreSQL", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for DevOps. Learn to become a modern DevOps engineer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a database administrator", |
||||
"guide to becoming a DBA", |
||||
"dba roadmap", |
||||
"db administrator roadmap", |
||||
"database administrator roadmap", |
||||
"postgresql roadmap", |
||||
"dba skills", |
||||
"db administrator skills", |
||||
"become dba", |
||||
"postgresql skills", |
||||
"modern dba skills", |
||||
"dba skills test", |
||||
"skills for dba", |
||||
"skills for database administrator", |
||||
"learn dba", |
||||
"what is dba", |
||||
"database administrator quiz", |
||||
"dba interview questions" |
||||
] |
||||
}, |
||||
"title": "PostgreSQL DBA", |
||||
"description": "Step by step guide to becoming a modern PostgreSQL DB Administrator in 2021", |
||||
"featuredTitle": "DBA", |
||||
"featuredDescription": "Step by step guide to become a PostgreSQL DBA in 2021", |
||||
"contentPath": "./landscape.md", |
||||
"resourcesPath": "./resources.md", |
||||
"author": { |
||||
"name": "Alexey Lesovsky", |
||||
"url": "https://github.com/lesovsky" |
||||
}, |
||||
"isCommunity": true, |
||||
"isTextHeavy": true, |
||||
"featured": true, |
||||
"detailed": false, |
||||
"versions": [] |
||||
} |
||||
@ -0,0 +1,7 @@ |
||||
> **We are still preparing the resources**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the list, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
@ -0,0 +1,82 @@ |
||||
The intent of this guide is to give you an idea about the Android development landscape and to help guide your learning if you are confused. Before we start, please note that the roadmap is opinionated, and you might have different opinions than those of the author. Having said that, [we would love to hear your opinions](https://github.com/kamranahmedse/roadmap.sh/issues/new) and incorporate them in the roadmap if suitable. |
||||
|
||||
There are multiple ways to develop applications for the android; you can go down the path of hybrid application development where [flutter](https://flutter.dev/), [react-native](https://reactnative.dev/), or [NativeScript](https://www.nativescript.org/) are the most common contenders. Flutter uses Dart, whereas React Native and Native Script rely on JavaScript. Answering the question of hybrid vs native is out of the scope of this roadmap. This roadmap is focused on the native Android apps development but if you are interested in learning any hybrid framework, my personal preference is [react-native](https://reactnative.dev) and I would recommend you to checkout the [Frontend Developer Roadmap](/frontend). |
||||
|
||||
## Complete Roadmap |
||||
|
||||
Here is the full version of the roadmap in a single image and after that we have the broken down version with the resources and links to learn more about each of the boxes. |
||||
|
||||
[](/roadmaps/android/roadmap.png) |
||||
|
||||
## Broken Down Version |
||||
Below is the broken down version of the roadmap with links and resources to learn more about each of the items listed in the complete roadmap above. |
||||
|
||||
## Pick a Language |
||||
For the languages, you can develop android apps either by using Kotlin or Java. |
||||
|
||||
[](/roadmaps/android/pick-language.svg) |
||||
|
||||
Although, you can use both [Kotlin](https://en.wikipedia.org/wiki/Kotlin_(programming_language)) and [Java](https://en.wikipedia.org/wiki/Java_(programming_language)) to develop native android apps, [Google announced in 2019](https://android-developers.googleblog.com/2019/05/google-io-2019-empowering-developers-to-build-experiences-on-Android-Play.html) to make Kotlin the preferred way of developing android applications. If you were to start learning android development today, Kotlin should be your language of choice. |
||||
|
||||
## The Fundamentals |
||||
Install the [Android Studio](https://developer.android.com/studio) and learn the basics of Kotlin to get started. |
||||
|
||||
[](/roadmaps/android/the-fundamentals.png) |
||||
|
||||
We have also listed down some free resources which you can use for the items listed in the image above. If you have some better ones, please do suggest. Also, you don't need to go through all of them, just go through them and pick what you like. |
||||
|
||||
* [Learn the basics of Kotlin](https://blog.teamtreehouse.com/absolute-beginners-guide-kotlin) |
||||
* [Kotlin Docs](https://kotlinlang.org/docs/reference/basic-syntax.html) and [Official Kotlin Tutorials](https://kotlinlang.org/docs/tutorials/) |
||||
* [Data Structures and Algorithms](https://www.studytonight.com/data-structures/introduction-to-data-structures). Also [check this](https://www.tutorialspoint.com/data_structures_algorithms/index.htm). |
||||
* [Kotlin DataStructures](https://kotlinlang.org/docs/reference/collections-overview.html) |
||||
* [Algorithms and DataStructures in Kotlin](https://github.com/bmaslakov/kotlin-algorithm-club) |
||||
|
||||
## Version Control Systems |
||||
Version control systems record your changes to the codebase and allow you to recall specific versions later. There are multiple Version Control Systems available but [Git](https://git-scm.com/) is the most common one these days. |
||||
|
||||
[](/roadmaps/android/git-github.png) |
||||
|
||||
Here are some of the resources to get you started. Feel free to google and find something else that you find easier. |
||||
|
||||
* [Udacity — Version Control with Git](https://www.udacity.com/course/version-control-with-git--ud123) |
||||
* [GitHub Hello World](https://guides.github.com/activities/hello-world/) |
||||
|
||||
## Building an Application |
||||
|
||||
Here is the list of items that you are going to need when developing Android applications. Please note that, this is an exhaustive list, and you don't need to know it all from the get-go. Get an idea of the items listed, and just start building some apps and keep the items listed in the back of your mind and have a deep dive when using them. |
||||
|
||||
[](/roadmaps/android/build-an-application.png) |
||||
|
||||
To learn more about the items listed in the image above, here are the links to the relevant docs |
||||
|
||||
* [Using Activities and Activity Life Cycles](https://developer.android.com/guide/components/activities/intro-activities) |
||||
* Building Flexible Interfaces using [Fragments](https://developer.android.com/guide/components/fragments) |
||||
* [Debugging using Android Studio Debugger](https://developer.android.com/studio/debug) |
||||
* [Handling App Configurations](https://developer.android.com/work/managed-configurations) |
||||
* [Using Intents and Intent Filters](https://developer.android.com/guide/components/intents-filters) |
||||
* [Understand Context](https://guides.codepath.com/android/Using-Context) |
||||
* [Learn about Multithreading](https://developer.android.com/training/multiple-threads) |
||||
* [Data Privacy](https://www.raywenderlich.com/6901838-data-privacy-for-android) |
||||
* [Securing Network Data](https://www.raywenderlich.com/5634-securing-network-data-tutorial-for-android) |
||||
* [Dependency Injection](https://developer.android.com/training/dependency-injection) |
||||
* [Content Providers](https://developer.android.com/guide/topics/providers/content-providers) |
||||
* [Glide](https://github.com/bumptech/glide), [Retrofit](https://square.github.io/retrofit/), [Crashlytics](https://firebase.google.com/docs/crashlytics/get-started), [GSON](https://github.com/google/gson) |
||||
* [Room](https://developer.android.com/topic/libraries/architecture/room), [Navigation](https://developer.android.com/guide/navigation/navigation-getting-started), [Work Manager](https://developer.android.com/topic/libraries/architecture/workmanager), [LiveData](https://developer.android.com/topic/libraries/architecture/livedata), [Data Binding](https://developer.android.com/topic/libraries/data-binding) |
||||
* [RxJava](https://github.com/ReactiveX/RxJava), [RxKotlin](https://github.com/ReactiveX/RxKotlin) |
||||
* [Memory Management Overview](https://developer.android.com/topic/performance/memory-overview) |
||||
* [Diving deeper into context-oriented programming in Kotlin](https://proandroiddev.com/diving-deeper-into-context-oriented-programming-in-kotlin-3ecb4ec38814) |
||||
|
||||
I would highly recommend watching [this free course](https://www.udacity.com/course/developing-android-apps-with-kotlin--ud9012) from google on Developing Android Apps with Kotlin. Also, here are some of the resources to learn more about the topics listed above. |
||||
|
||||
* [Developing Android Apps with Kotlin](https://www.udacity.com/course/developing-android-apps-with-kotlin--ud9012) |
||||
* [Android Developer Guides](https://developer.android.com/guide) |
||||
* [Raywenderlich](https://www.raywenderlich.com) |
||||
|
||||
## Wrap Up |
||||
|
||||
That wraps it up for the android developer roadmap. Again, remember to not be exhausted by the list; just learn the basics and start working on some project, rest of the learnings will come along the way. Good luck! |
||||
|
||||
For any suggestions, improvements and feedback, feel free to [submit an issue](https://github.com/kamranahmedse/roadmap.sh) or reach out to me on twitter [@kamranahmedse](https://twitter.com/kamranahmedse). |
||||
|
||||
<!-- @fixme add padding to the container --> |
||||
<br /><br /><br /> |
||||
@ -0,0 +1,37 @@ |
||||
{ |
||||
"seo": { |
||||
"title": "Android Developer Roadmap: Learn to become an Android developer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for android development. Learn to become a modern Android developer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming an android developer", |
||||
"android developer roadmap", |
||||
"android roadmap", |
||||
"become android developer", |
||||
"android developer skills", |
||||
"android skills test", |
||||
"skills for android development", |
||||
"learn android development", |
||||
"what is android", |
||||
"android quiz", |
||||
"android interview questions" |
||||
] |
||||
}, |
||||
"title": "Android Developer", |
||||
"description": "Step by step guide to becoming an Android developer in 2021", |
||||
"featuredTitle": "Android", |
||||
"featuredDescription": "Step by step guide to becoming an Android Developer in 2021", |
||||
"isTextHeavy": true, |
||||
"isCommunity": true, |
||||
"featured": true, |
||||
"contentPath": "./landscape.md", |
||||
"resourcesPath": "./resources.md", |
||||
"versions": [ |
||||
"latest", |
||||
"2018", |
||||
"2017" |
||||
], |
||||
"author": { |
||||
"name": "Kamran Ahmed", |
||||
"url": "https://twitter.com/kamranahmedse" |
||||
} |
||||
} |
||||
@ -0,0 +1,7 @@ |
||||
> **We are still preparing the resources**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the list, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
@ -0,0 +1,11 @@ |
||||
> **Roadmap is not ready yet**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the roadmap, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,31 @@ |
||||
{ |
||||
"seo": { |
||||
"title": "QA Roadmap: Learn to become a modern QA engineer", |
||||
"description": "Community driven, articles, resources, guides, interview questions, quizzes for modern QA development. Learn to become a modern QA engineer by following the steps, skills, resources and guides listed in this roadmap.", |
||||
"keywords": [ |
||||
"guide to becoming a QA engineer", |
||||
"QA engineer", |
||||
"QA skills", |
||||
"QA development skills", |
||||
"QA development skills test", |
||||
"QA engineer roadmap", |
||||
"become a QA engineer", |
||||
"QA engineer career path", |
||||
"skills for QA development", |
||||
"what is QA engineer", |
||||
"QA engineer quiz", |
||||
"QA engineer interview questions" |
||||
] |
||||
}, |
||||
"title": "QA Engineer", |
||||
"description": "Steps to follow in order to become a modern QA Engineer in 2021", |
||||
"featuredTitle": "QA", |
||||
"featuredDescription": "Step by step guide to becoming a modern QA Engineer in 2021", |
||||
"isUpcoming": true, |
||||
"contentPath": "./landscape.md", |
||||
"resourcesPath": "./resources.md", |
||||
"author": { |
||||
"name": "Anas Fitiani", |
||||
"url": "https://github.com/anas-qa" |
||||
} |
||||
} |
||||
@ -0,0 +1,7 @@ |
||||
> **We are still preparing the resources**. Please check back later or [subscribe to get notified](/signup). |
||||
|
||||
While we prepare the list, follow this simple advice to learn anything |
||||
|
||||
> Just **pick a project and start working on it**, you will learn all that you need along the way. |
||||
|
||||
**→** [All Roadmaps](/roadmaps) • [Programming guides](/guides) • [Subscribe](/signup) |
||||
@ -0,0 +1,49 @@ |
||||
{ |
||||
"author": "Kamran Ahmed", |
||||
"title": "Roadmaps to becoming a modern developer", |
||||
"name": "roadmap.sh", |
||||
"description": "Community driven roadmaps, articles, guides, quizzes, tips and resources for developers to learn from, identify their career paths, know what they don't know, find out the knowledge gaps, learn and improve.", |
||||
"twitter": "kamranahmedse", |
||||
"facebook": "kamranahmedse", |
||||
"logo": "/brand.png", |
||||
"logoSquare": "/brand-square.png", |
||||
"url": { |
||||
"web": "https://roadmap.sh", |
||||
"twitter": "https://twitter.com/kamranahmedse", |
||||
"youtube": "https://youtube.com/theroadmap?sub_confirmation=1", |
||||
"repo": "https://github.com/kamranahmedse/roadmap.sh", |
||||
"sponsor": "https://github.com/sponsors/kamranahmedse", |
||||
"repoData": "https://github.com/kamranahmedse/roadmap.sh/tree/master/content", |
||||
"addGuide": "https://github.com/kamranahmedse/roadmap.sh/tree/master/contributing/guide.md", |
||||
"addRoadmap": "https://github.com/kamranahmedse/roadmap.sh/tree/master/contributing/roadmap.md", |
||||
"addResources": "https://github.com/kamranahmedse/roadmap.sh/tree/master/contributing/resources.md", |
||||
"contribute": "https://github.com/kamranahmedse/roadmap.sh/tree/master/contributing", |
||||
"issue": "https://github.com/kamranahmedse/roadmap.sh/issues/new" |
||||
}, |
||||
"keywords": [ |
||||
"roadmap", |
||||
"developer roadmaps", |
||||
"developer roadmap", |
||||
"frontend developer", |
||||
"frontend developer roadmap", |
||||
"frontend", |
||||
"frontend roadmap", |
||||
"backend", |
||||
"backend developer", |
||||
"backend developer roadmap", |
||||
"devops", |
||||
"devops roadmap", |
||||
"fullstack developer roadmap", |
||||
"guide to becoming a developer", |
||||
"sre roadmap", |
||||
"sre", |
||||
"operations roadmap", |
||||
"qa roadmap", |
||||
"android roadmap", |
||||
"android developer roadmap", |
||||
"react roadmap", |
||||
"react developer roadmap", |
||||
"dba roadmap", |
||||
"postgresql dba roadmap" |
||||
] |
||||
} |
||||
@ -0,0 +1,211 @@ |
||||
[ |
||||
{ |
||||
"id": "transport-protocols-tcp-vs-udp", |
||||
"title": "Transport Protocols: TCP vs UDP", |
||||
"description": "Learn about the Transport Layer of the TCP/IP model and different transport protocols.", |
||||
"isPro": false, |
||||
"youtubeLink": "https://www.youtube.com/watch?v=37AFBZv4_6Y", |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "10 minutes", |
||||
"updatedAt": "2020-11-21T19:59:14.191Z", |
||||
"createdAt": "2020-11-21T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "tcp-ip-model", |
||||
"title": "TCP/IP Model Explained", |
||||
"description": "Learn what is TCP/IP Model and the different layers involved.", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=F5rni9fr1yE", |
||||
"duration": "5 minutes", |
||||
"updatedAt": "2020-11-06T19:59:14.191Z", |
||||
"createdAt": "2020-11-06T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "osi-model", |
||||
"title": "OSI Model Explained", |
||||
"description": "Learn what is OSI Model and the different layers involved.", |
||||
"isPro": false, |
||||
"youtubeLink": "https://www.youtube.com/watch?v=dV8mjZd1OtU", |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "7 minutes", |
||||
"updatedAt": "2020-10-24T19:59:14.191Z", |
||||
"createdAt": "2020-10-24T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "freeze-and-seal-objects-in-javascript", |
||||
"title": "Freeze and Seal in JavaScript", |
||||
"description": "Learn what is OSI Model and the different layers involved.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=O3uT2l6vgZ8", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "6 minutes", |
||||
"updatedAt": "2020-10-16T19:59:14.191Z", |
||||
"createdAt": "2020-10-16T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "all-about-http-caching", |
||||
"title": "All about HTTP Caching", |
||||
"description": "Learn what is HTTP caching, places for caching and different caching headers.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=HiBDZgTNpXY", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "13 minutes", |
||||
"updatedAt": "2020-10-04T19:59:14.191Z", |
||||
"createdAt": "2020-10-04T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "content-delivery-networks", |
||||
"title": "Content Delivery Networks", |
||||
"description": "Learn what the CDNs are and the difference between push CDN vs pull CDN.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=6DXEPcXKQNY", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "4 minutes", |
||||
"updatedAt": "2020-09-26T19:59:14.191Z", |
||||
"createdAt": "2020-09-26T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "load-balancers-101", |
||||
"title": "Load Balancers 101", |
||||
"description": "Learn the basics of load balancers, types and different algorithms.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=galcDRNd5Ow", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "9 minutes", |
||||
"updatedAt": "2020-09-18T19:59:14.191Z", |
||||
"createdAt": "2020-09-18T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "dns-records", |
||||
"title": "DNS Records", |
||||
"description": "Learn what the DNS is and how a website is found on the internet.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=7lxgpKh_fRY", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "6 minutes", |
||||
"updatedAt": "2020-08-31T19:59:14.191Z", |
||||
"createdAt": "2020-08-31T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "dns-explained", |
||||
"title": "DNS and how does it work?", |
||||
"description": "Learn what the DNS is and how a website is found on the internet.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=Wj0od2ag5sk", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "5 minutes", |
||||
"updatedAt": "2020-08-17T19:59:14.191Z", |
||||
"createdAt": "2020-08-17T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "system-design-101", |
||||
"title": "System Design 101", |
||||
"description": "Learn about all the bits and pieces of system design.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=Y-Gl4HEyeUQ", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "7 minutes", |
||||
"updatedAt": "2020-08-08T19:59:14.191Z", |
||||
"createdAt": "2020-08-08T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "javascript-fetch-api", |
||||
"title": "JavaScript Fetch API", |
||||
"description": "Learn how to use JavaScript's Fetch API to interact with remote API.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=-ZI0ea5O2oA", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "3 minutes", |
||||
"updatedAt": "2020-08-02T19:59:14.191Z", |
||||
"createdAt": "2020-08-02T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "scaling-the-unscalable", |
||||
"title": "Scaling the Unscalable", |
||||
"description": "Learn the basics of System Design and understand how to build a scalable application.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=a2rcgzludDU", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "10 minutes", |
||||
"updatedAt": "2020-07-26T19:59:14.191Z", |
||||
"createdAt": "2020-07-26T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "promises-in-javascript", |
||||
"title": "All about Promises in JavaScript", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=BvrkobaCVVE", |
||||
"description": "Learn how to write asynchronous code in JavaScript using promises.", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "8 minutes", |
||||
"updatedAt": "2020-07-20T19:59:14.191Z", |
||||
"createdAt": "2020-07-20T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "how-to-use-github-actions", |
||||
"title": "Automate with GitHub Actions", |
||||
"description": "Learn how to implement CI/CD with GitHub Actions", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=nyKZTKQS_EQ", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "6 minutes", |
||||
"updatedAt": "2020-07-13T19:59:14.191Z", |
||||
"createdAt": "2020-07-13T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "what-is-dependency-injection", |
||||
"title": "What is Dependency Injection?", |
||||
"description": "Learn what is dependency injection and how to write better code with the help of it.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=0yc2UANSDiw", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "3 minutes", |
||||
"updatedAt": "2020-07-04T19:59:14.191Z", |
||||
"createdAt": "2020-07-04T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "how-to-use-css-variables", |
||||
"title": "How to use CSS Variables?", |
||||
"description": "Learn how to write scalable CSS using CSS Variables.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=lgaxU7CRmxU", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "5 minutes", |
||||
"updatedAt": "2020-07-03T19:59:14.191Z", |
||||
"createdAt": "2020-07-03T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "what-is-dom-shadow-dom-virtual-dom", |
||||
"title": "DOM, Shadow DOM, Virtual DOM", |
||||
"description": "Learn what is DOM, Shadow DOM and Virtual DOM and how they work.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=7Tok22qxPzQ", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "6 minutes", |
||||
"updatedAt": "2020-07-20T19:59:14.191Z", |
||||
"createdAt": "2020-07-20T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "practical-intro-to-react", |
||||
"title": "Practical Introduction to React", |
||||
"description": "Learn how to create a React Application with practical example.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=NyG7YJWJd6s&list=PLkZYeFmDuaN3NDLnBG01-sH2-nwn43mYu", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "40 minutes", |
||||
"updatedAt": "2020-07-09T19:59:14.191Z", |
||||
"createdAt": "2020-07-09T19:59:14.191Z" |
||||
}, |
||||
{ |
||||
"id": "arrays-and-objects-in-javascript", |
||||
"title": "Arrays and Objects in JavaScript", |
||||
"description": "Learn how to manipulate arrays and objects in JavaScript.", |
||||
"youtubeLink": "https://www.youtube.com/watch?v=n3NKGsM3iEw", |
||||
"isPro": false, |
||||
"authorUsername": "kamranahmedse", |
||||
"duration": "12 minutes", |
||||
"updatedAt": "2020-05-09T19:59:14.191Z", |
||||
"createdAt": "2020-05-09T19:59:14.191Z" |
||||
} |
||||
] |
||||
@ -0,0 +1 @@ |
||||
<iframe src="https://www.youtube.com/embed/HiBDZgTNpXY" title="All about HTTP Caching" /> |
||||
@ -0,0 +1 @@ |
||||
<iframe src="https://www.youtube.com/embed/n3NKGsM3iEw" title="Arrays and Objects in JavaScript" /> |
||||
@ -0,0 +1 @@ |
||||
<iframe src="https://www.youtube.com/embed/6DXEPcXKQNY" title="Content Delivery Networks" /> |
||||
@ -0,0 +1 @@ |
||||
<iframe src="https://www.youtube.com/embed/Wj0od2ag5sk" title="DNS and how does it work?" /> |
||||
@ -0,0 +1 @@ |
||||
<iframe src="https://www.youtube.com/embed/7lxgpKh_fRY" title="DNS Records" /> |
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in new issue