109 | We are dedicated to building a positive environment that inculcates
110 | open learning and high respect for one another. So we expect our
111 | members to maintain a certain decorum.
112 |
113 |
114 |
115 |
116 | No trolling of members on the group. We are here to learn and help
117 | each other grow.
118 |
119 |
120 | No spamming off topic stuff. Time is the most important resource.
121 | Lets save it in manifolds by reducing off topic content.
122 |
123 |
124 | Avoid Direct Messages. Do not hesitate to ask your queries on the
125 | #support discord channel. Aids in quicker response.
126 |
127 |
128 | Avoid using tags @everyone and @here until it is very important.
129 |
130 |
131 | Google your queries before you seek help.
132 |
133 |
134 | When seeking help, submit the code in an easy-to-evaluate fashion.
135 | Share a
136 | Codepen link instead of a
139 | Github link.
142 |
143 |
144 | Overall challenge yourself. Take up tasks proactively and update
145 | your progress
146 |
147 |
148 | It helps to have a picture of yourself on your Discord & Github
149 | profiles.
150 |
151 |
152 |
153 |
154 |
155 |
167 |
168 |
169 |
170 |
171 |
172 |
173 |
--------------------------------------------------------------------------------
/css/discord.css:
--------------------------------------------------------------------------------
1 | :root {
2 | --color-bg: #fff;
3 | --color-text: #000;
4 | --color-bg-card: #fff;
5 | --color-links: #1d1283;
6 | --color-events: #e30162;
7 | }
8 |
9 | .dark-theme {
10 | --color-bg: #1c1b22;
11 | --color-text: #e1e1ec;
12 | --color-bg-card: #312f3b;
13 | --color-links: #0080ff;
14 | --color-events: #ff0090;
15 | }
16 | * {
17 | margin: 0;
18 | padding: 0;
19 | box-sizing: border-box;
20 | }
21 |
22 | body {
23 | font: 16px 'Roboto', sans-serif;
24 | background-color: var(--color-bg);
25 | }
26 | .dropdown {
27 | top: 56px;
28 | }
29 |
30 | a {
31 | text-decoration: none;
32 | color: var(--color-links);
33 | }
34 |
35 | .animation-container .animation-heading-container {
36 | align-items: center;
37 | justify-content: center;
38 | display: flex;
39 | flex-wrap: wrap;
40 | position: relative;
41 | z-index: 2;
42 | height: 100%;
43 | }
44 |
45 | .animation-container {
46 | position: relative;
47 | height: 300px;
48 | background: url(../img/discord-page/bg-top-inner.png) no-repeat center center;
49 | background-size: cover;
50 | color: #ffffff;
51 | overflow: hidden;
52 | padding: 3.5rem 0;
53 | }
54 |
55 | .animation-heading-container {
56 | display: flex;
57 | flex-direction: column;
58 | justify-content: center;
59 | align-items: center;
60 | }
61 |
62 | .new-heading {
63 | font-weight: 400;
64 | color: var(--color-text);
65 | font-size: 2.125rem;
66 | margin-top: 3.5rem;
67 | width: 95%;
68 | }
69 |
70 | .rds-name {
71 | color: #e30062;
72 | }
73 |
74 | .discord-info-para {
75 | margin-top: 2rem;
76 | width: 80%;
77 | }
78 |
79 | .discord-info-para p {
80 | font-size: 1.25rem;
81 | color: var(--color-text);
82 | }
83 |
84 | .center-block {
85 | display: flex;
86 | justify-content: center;
87 | align-items: center;
88 | flex-direction: column;
89 | text-align: center;
90 | }
91 |
92 | .get-started-heading {
93 | font-weight: 400;
94 | color: var(--color-links);
95 | font-size: 2.125rem;
96 | margin: 2rem 0;
97 | display: flex;
98 | align-items: center;
99 | justify-content: center;
100 | width: 97%;
101 | }
102 |
103 | .rds-channels-list {
104 | padding: 0;
105 | margin: 0;
106 | list-style: none;
107 | }
108 |
109 | .rds-channels-list li {
110 | margin: 0 0 0.75rem 0;
111 | }
112 |
113 | .end-block {
114 | background-color: var(--color-bg);
115 | margin-top: 3rem;
116 | display: flex;
117 | align-items: center;
118 | justify-content: center;
119 | color: var(--color-text);
120 | }
121 |
122 | .discord-image {
123 | margin-top: 4rem;
124 | object-fit: cover;
125 | width: 90%;
126 | margin: 20px auto;
127 | }
128 |
129 | .image-div {
130 | width: 40%;
131 | }
132 |
133 | .rds-info-block {
134 | width: 35%;
135 | }
136 |
137 | footer {
138 | position: relative;
139 | margin-top: 40px;
140 | bottom: 0;
141 | width: 100%;
142 | padding: 15px;
143 | text-align: center;
144 | color: var(--color-text);
145 | }
146 |
147 | @keyframes moveLeftBounce {
148 | 0% {
149 | transform: translateX(0);
150 | }
151 | 50% {
152 | transform: translateX(5px);
153 | }
154 | 100% {
155 | transform: translateX(0);
156 | }
157 | }
158 | @keyframes animationFramesOne {
159 | 0% {
160 | transform: translate(0px, 0px) rotate(0deg);
161 | }
162 | 20% {
163 | transform: translate(73px, -1px) rotate(36deg);
164 | }
165 | 40% {
166 | transform: translate(141px, 72px) rotate(72deg);
167 | }
168 | 60% {
169 | transform: translate(83px, 122px) rotate(108deg);
170 | }
171 | 80% {
172 | transform: translate(-40px, 72px) rotate(144deg);
173 | }
174 | 100% {
175 | transform: translate(0px, 0px) rotate(0deg);
176 | }
177 | }
178 | @keyframes rotateme {
179 | from {
180 | transform: rotate(0deg);
181 | }
182 | to {
183 | transform: rotate(360deg);
184 | }
185 | }
186 |
187 | .animation-heading {
188 | font-size: 2.5rem;
189 | margin: 0;
190 | text-align: center;
191 | }
192 |
193 | .animation-shapes {
194 | position: absolute;
195 | }
196 |
197 | .animation-shape-1 {
198 | top: 40px;
199 | right: 84px;
200 | max-width: 40px;
201 | z-index: 1;
202 | animation: rotateme 25s linear infinite;
203 | }
204 |
205 | .animation-shape-2 {
206 | top: 55px;
207 | right: 95px;
208 | max-width: 25px;
209 | animation: rotateme 25s linear infinite;
210 | }
211 |
212 | .animation-shape-3 {
213 | top: 160px;
214 | left: 350px;
215 | animation: animationFramesOne 15s infinite linear;
216 | }
217 |
218 | .animation-shape-4 {
219 | top: 50%;
220 | left: 50%;
221 | -webkit-animation: animationFramesOne 25s infinite linear;
222 | animation: animationFramesOne 25s infinite linear;
223 | }
224 |
225 | .animation-shape-5 {
226 | top: 70px;
227 | right: 50px;
228 | animation: animationFramesOne 25s infinite linear;
229 | }
230 |
231 | .animation-shape-6 {
232 | left: 20px;
233 | bottom: 30px;
234 | animation: rotateme 25s linear infinite;
235 | max-width: 50px;
236 | }
237 |
238 | .animation-shape-7 {
239 | bottom: 1rem;
240 | right: 1rem;
241 | animation: moveLeftBounce 3s linear infinite;
242 | }
243 |
244 | .animation-shape-8 {
245 | top: 10px;
246 | left: 10px;
247 | animation: animationFramesOne 25s infinite linear;
248 | }
249 |
250 | @media (max-width: 768px) {
251 | .end-block {
252 | display: flex;
253 | flex-direction: column;
254 | }
255 | .image-div {
256 | width: 60%;
257 | }
258 | .rds-info-block {
259 | flex: 0 0 100%;
260 | min-width: 80%;
261 | }
262 | }
263 |
264 | @media (max-width: 625px) {
265 | .get-started-heading {
266 | font-size: 20px;
267 | font-weight: 700;
268 | }
269 | .new-heading {
270 | font-size: 1.75rem;
271 | font-weight: 700;
272 | margin-left: 0.6rem;
273 | }
274 | .help-heading {
275 | font-size: 20px;
276 | margin-right: 0.4rem;
277 | }
278 | .animation-heading {
279 | font-size: 2rem;
280 | }
281 | .server-heading {
282 | display: block;
283 | }
284 | }
285 |
286 | @media (max-width: 375px) {
287 | .discord-info-para {
288 | font-size: 1rem;
289 | }
290 |
291 | .new-heading {
292 | width: 97%;
293 | margin-bottom: 2rem;
294 | font-size: 1.5rem;
295 | font-weight: 700;
296 | margin-left: 0.6rem;
297 | }
298 |
299 | .help-heading {
300 | font-size: 20px;
301 | margin-right: 0.4rem;
302 | }
303 |
304 | .animation-heading {
305 | font-size: 2rem;
306 | }
307 |
308 | .end-block {
309 | display: flex;
310 | flex-direction: column;
311 | }
312 |
313 | .rds-info-block {
314 | min-width: 75%;
315 | }
316 |
317 | .image-div {
318 | width: 80%;
319 | margin-top: 1rem;
320 | }
321 |
322 | .get-started-heading {
323 | font-size: 20px;
324 | font-weight: 700;
325 | }
326 |
327 | .server-heading {
328 | display: block;
329 | }
330 | }
331 |
--------------------------------------------------------------------------------
/jest.config.js:
--------------------------------------------------------------------------------
1 | /*
2 | * For a detailed explanation regarding each configuration property, visit:
3 | * https://jestjs.io/docs/configuration
4 | */
5 |
6 | export default {
7 | // testEnvironment: 'jest-environment-node',
8 | transform: {},
9 | // "testEnvironment": "jest-environment-jsdom-sixteen",
10 | verbose: true,
11 | transformIgnorePatterns: ['node_modules/(?!@ngrx|(?!deck.gl)|ng-dynamic)'],
12 | // All imported modules in your tests should be mocked automatically
13 | // automock: false,
14 |
15 | // Stop running tests after `n` failures
16 | // bail: 0,
17 |
18 | // The directory where Jest should store its cached dependency information
19 | // cacheDirectory: "C:\\Users\\mgnat\\AppData\\Local\\Temp\\jest",
20 |
21 | // Automatically clear mock calls, instances, contexts and results before every test
22 | clearMocks: true,
23 |
24 | // Indicates whether the coverage information should be collected while executing the test
25 | collectCoverage: true,
26 |
27 | // An array of glob patterns indicating a set of files for which coverage information should be collected
28 | // collectCoverageFrom: undefined,
29 |
30 | // The directory where Jest should output its coverage files
31 | coverageDirectory: 'coverage',
32 |
33 | // An array of regexp pattern strings used to skip coverage collection
34 | // coveragePathIgnorePatterns: [
35 | // "\\\\node_modules\\\\"
36 | // ],
37 |
38 | // Indicates which provider should be used to instrument code for coverage
39 | coverageProvider: 'v8',
40 |
41 | // A list of reporter names that Jest uses when writing coverage reports
42 | // coverageReporters: [
43 | // "json",
44 | // "text",
45 | // "lcov",
46 | // "clover"
47 | // ],
48 |
49 | // An object that configures minimum threshold enforcement for coverage results
50 | // coverageThreshold: undefined,
51 |
52 | // A path to a custom dependency extractor
53 | // dependencyExtractor: undefined,
54 |
55 | // Make calling deprecated APIs throw helpful error messages
56 | // errorOnDeprecated: false,
57 |
58 | // The default configuration for fake timers
59 | // fakeTimers: {
60 | // "enableGlobally": false
61 | // },
62 |
63 | // Force coverage collection from ignored files using an array of glob patterns
64 | // forceCoverageMatch: [],
65 |
66 | // A path to a module which exports an async function that is triggered once before all test suites
67 | // globalSetup: undefined,
68 |
69 | // A path to a module which exports an async function that is triggered once after all test suites
70 | // globalTeardown: undefined,
71 |
72 | // A set of global variables that need to be available in all test environments
73 | // globals: {},
74 |
75 | // The maximum amount of workers used to run your tests. Can be specified as % or a number. E.g. maxWorkers: 10% will use 10% of your CPU amount + 1 as the maximum worker number. maxWorkers: 2 will use a maximum of 2 workers.
76 | // maxWorkers: "50%",
77 |
78 | // An array of directory names to be searched recursively up from the requiring module's location
79 | // moduleDirectories: [
80 | // "node_modules"
81 | // ],
82 |
83 | // An array of file extensions your modules use
84 | // moduleFileExtensions: [
85 | // "js",
86 | // "mjs",
87 | // "cjs",
88 | // "jsx",
89 | // "ts",
90 | // "tsx",
91 | // "json",
92 | // "node"
93 | // ],
94 |
95 | // A map from regular expressions to module names or to arrays of module names that allow to stub out resources with a single module
96 | // moduleNameMapper: {},
97 |
98 | // An array of regexp pattern strings, matched against all module paths before considered 'visible' to the module loader
99 | // modulePathIgnorePatterns: [],
100 |
101 | // Activates notifications for test results
102 | // notify: false,
103 |
104 | // An enum that specifies notification mode. Requires { notify: true }
105 | // notifyMode: "failure-change",
106 |
107 | // A preset that is used as a base for Jest's configuration
108 | // preset: undefined,
109 |
110 | // Run tests from one or more projects
111 | // projects: undefined,
112 |
113 | // Use this configuration option to add custom reporters to Jest
114 | // reporters: undefined,
115 |
116 | // Automatically reset mock state before every test
117 | // resetMocks: false,
118 |
119 | // Reset the module registry before running each individual test
120 | // resetModules: false,
121 |
122 | // A path to a custom resolver
123 | // resolver: undefined,
124 |
125 | // Automatically restore mock state and implementation before every test
126 | // restoreMocks: false,
127 |
128 | // The root directory that Jest should scan for tests and modules within
129 | // rootDir: undefined,
130 |
131 | // A list of paths to directories that Jest should use to search for files in
132 | // roots: [
133 | // ""
134 | // ],
135 |
136 | // Allows you to use a custom runner instead of Jest's default test runner
137 | // runner: "jest-runner",
138 |
139 | // The paths to modules that run some code to configure or set up the testing environment before each test
140 | // setupFiles: [],
141 |
142 | // A list of paths to modules that run some code to configure or set up the testing framework before each test
143 | // setupFilesAfterEnv: [],
144 |
145 | // The number of seconds after which a test is considered as slow and reported as such in the results.
146 | // slowTestThreshold: 5,
147 |
148 | // A list of paths to snapshot serializer modules Jest should use for snapshot testing
149 | // snapshotSerializers: [],
150 |
151 | // The test environment that will be used for testing
152 | testEnvironment: 'jsdom',
153 |
154 | // Options that will be passed to the testEnvironment
155 | // testEnvironmentOptions: {},
156 |
157 | // Adds a location field to test results
158 | // testLocationInResults: false,
159 |
160 | // The glob patterns Jest uses to detect test files
161 | // testMatch: [
162 | // "**/__tests__/**/*.[jt]s?(x)",
163 | // "**/?(*.)+(spec|test).[tj]s?(x)"
164 | // ],
165 |
166 | // An array of regexp pattern strings that are matched against all test paths, matched tests are skipped
167 | // testPathIgnorePatterns: [
168 | // "\\\\node_modules\\\\"
169 | // ],
170 |
171 | // The regexp pattern or array of patterns that Jest uses to detect test files
172 | // testRegex: [],
173 |
174 | // This option allows the use of a custom results processor
175 | // testResultsProcessor: undefined,
176 |
177 | // This option allows use of a custom test runner
178 | // testRunner: "jest-circus/runner",
179 |
180 | // A map from regular expressions to paths to transformers
181 | // transform: undefined,
182 |
183 | // An array of regexp pattern strings that are matched against all source file paths, matched files will skip transformation
184 | // transformIgnorePatterns: [
185 | // "\\\\node_modules\\\\",
186 | // "\\.pnp\\.[^\\\\]+$"
187 | // ],
188 |
189 | // An array of regexp pattern strings that are matched against all modules before the module loader will automatically return a mock for them
190 | // unmockedModulePathPatterns: undefined,
191 |
192 | // Indicates whether each individual test should be reported during the run
193 | // verbose: undefined,
194 |
195 | // An array of regexp patterns that are matched against all source file paths before re-running tests in watch mode
196 | // watchPathIgnorePatterns: [],
197 |
198 | // Whether to use watchman for file crawling
199 | // watchman: true,
200 | };
201 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # How can I contribute?
2 |
3 | - You can add questions and answers in FAQ.
4 | - You can style the pages using CSS.
5 | - If you find a bug anywhere, you can fix it.
6 | - You can add a feature once you get approval from the community.
7 |
8 | # File Structure
9 |
10 | ```
11 | ├── index.html For homepage HTML page
12 | ├── css All the styling goes here
13 | ├── img All the images go here
14 | │ ├── discord-page
15 | | ├── icons
16 | | ...
17 | ├── js All JavaScript goes here
18 | ├──.prettierrc.json For formatting code
19 | ├── code-of-conduct.html For code of conduct HTML page
20 | ├── discord.html For the discord help HTML page
21 | ├── faq.html For FAQs HTML page
22 | ├── CONTRIBUTING.md Contribution file
23 | ├── README.md README file for the repository
24 | ├── package-lock.json For storing an exact versioned dependency tree
25 | ├── package.json For installing dependencies
26 | ```
27 |
28 | # How can you make your first **Pull Request**
29 |
30 | **Note**: Steps 1, 2 and 3 are **one-time** steps required for setup. If you have already cloned the repo and added upstream, consider following this documentation from step 4.
31 |
32 | 1. **Forking repository**
33 |
34 | Fork this repository using the **Fork** option at the top-right corner of this page. This will create your own copy of this repository. You'll be redirected to your forked repository. Copy the link of this repository (which will look like `https://github.com//website-welcome/`) as you'll need it in the step 2.
35 |
36 | 
37 |
38 | 2. **Cloning repository**
39 |
40 | Clone your forked repository, this will download your copy of repository in your computer. To do this, open your terminal (command prompt/bash/git bash) and enter the following command, paste your link after the word **clone** without the **<>**.
41 |
42 | ```
43 | git clone
44 | ```
45 |
46 | Once you have cloned the repository, now you should go into the folder containing the repository. You can do that with:
47 |
48 | ```
49 | cd website-welcome
50 | ```
51 |
52 | 3. **Adding remote repository**
53 |
54 | Add the Real Dev Squad repository as a remote repository, so that you can anytime pull the latest changes from the Real Dev Squad repository which is being deployed. This needs to be done only for the first time.
55 |
56 | ```
57 | git remote add upstream https://github.com/Real-Dev-Squad/website-welcome/
58 | ```
59 |
60 | 4. **Getting the latest code from the develop branch** (Can be skipped if you've cloned the repo just now)
61 |
62 | If it's been quite a while after you have cloned the repo/made the last pull request, it's recommended to take a pull from the develop branch. Reason being, there may be some changes which could have merged after you had cloned the repo/made the last pull request.
63 |
64 | To do so, make sure you're in the develop branch by checking out to the **develop** branch:
65 |
66 | ```
67 | git checkout develop
68 | ```
69 |
70 | Once you're in the **develop** branch, it's time to take a pull:
71 |
72 | ```
73 | git pull upstream develop
74 | ```
75 |
76 | Now that you've made sure that you've got latest changes, we can proceed to creating our branch
77 |
78 | 5. **Creating a new branch**
79 |
80 | Let's create a new branch to work on. We require a different branch so that we always have a stable, working version in the default (develop) branch. We're not supposed to touch the **main** branch as it is the one getting deployed on production.
81 |
82 | ```
83 | git checkout -b
84 | ```
85 |
86 | We will try to name the branch according to the task we are going to perform in it. If it is going to be a `feature`, the branch name should begin with `feat` or `feature`. If it is going to be a `fix`, the branch name should begin with `fix` or `bugfix`. The branch name should be self-explanatory.
87 | For example, if I want to work on a `feature` called `login-form`, the branch name will be **feature/login-form**. If it is going to be a `fix` in `navbar`, the branch name will be `fix/navbar`.
88 | Command example:
89 |
90 | ```
91 | git checkout -b feature/login-form
92 | ```
93 |
94 | 6. **Just do it!**
95 |
96 | Perform the tasks you wanted to, can be anything, ranging from fixing simple typo to re-designing the whole page!
97 |
98 | 7. **Committing your changes**
99 |
100 | Now you have made the changes, though they are saved in your system, Git doesn't know what changes you've done. So you have to **commit** your changes. First step is to add the files which you want to add to the staging area, the dot after **add** in the first command tells Git to check for changes in all the files. The second step is about committing your changes. The message part is short description of your commit, like "adds a login form on homepage". Please make sure NOT to have commit messages like "fix issue#34". When we look at the commit history, we should understand what a particular commit is supposed to do based on the commit message.
101 |
102 | ```
103 | git add .
104 | git commit -m "Write message about your commit"
105 | ```
106 |
107 | 8. **Making sure you have the latest changes from the develop branch**
108 |
109 | It may so happen that since the last time you cloned the repo/took a pull from develop, some changes may be merged in the develop branch. So to be on the safer side, we should have those changes as well.
110 |
111 | In order to do that, we first checkout to **develop** branch by:
112 |
113 | ```
114 | git checkout develop
115 | ```
116 |
117 | Once we're in develop, it's time to take a pull:
118 |
119 | ```
120 | git pull upstream develop
121 | ```
122 |
123 | Now that our **local** develop branch is in sync with **remote** develop branch (of the Real Dev Squad Repository), we should let our branch know about the changes from the develop branch (if any). To do so we first checkout to our branch:
124 |
125 | ```
126 | git checkout
127 | ```
128 |
129 | Once we're in our branch, we **rebase** our branch on top of the current develop branch (we change the base of our branch, so that it appears as if we have worked from the time the latest changes were merged in the develop branch). To do so:
130 |
131 | ```
132 | git rebase develop
133 | ```
134 |
135 | You should solve the merge conflicts, if any.
136 |
137 | 9. **Pushing the code**
138 |
139 | Now that we have made our changes plus we have the latest changes made by other contributors, we should push our code from **local** branch to the same branch on our **GitHub fork**. We do so by:
140 |
141 | ```
142 | git push origin
143 | ```
144 |
145 | For example, if the branch name is `feat/login-form`, we enter `git push origin feat/login-form`
146 |
147 | The **origin** refers to your GitHub fork. You can check it by entering `git remote -v`, you should see the link to your fork against **origin**.
148 |
149 | 10. **Making a pull request**
150 |
151 | Your GitHub fork now has the changes, but you want those changes to be merged in the Real Dev Squad repository, right? There's a twist, you can't directly merge your code in the Real Dev Squad. Imagine you own a company whose code is open sourced, would you like if anyone could code make changes in the directly without asking you? For the same reason, **Pull Requests** exist. You `request` the repository maintainers/admins to `pull` your code in their repository.
152 |
153 | To make a pull request, go to your **forked repository** and you'll see ** had recent pushes less than a minute ago** . Right next to it will be an option to **Compare & pull request**. Click on it, submit your pull request (also known as _PR_) explaining what you've done. Again, the PR title should be self-explanatory but concise. If you want to write details, you can add it in the description. If you're making some UI (User Interface) changes, please make sure to add a short screen recording. If that's not possible, at least add some screenshots.
154 |
155 | 
156 |
157 | 11. **Review stage**
158 |
159 | Now the maintainers/admins will review your pull request. They might suggest some changes if required. You should then make the required changes in the **same branch**, commit them and push your changes to the **same branch** (follow the steps 7, 8 and 9 for the same).
160 |
161 | 12. **Congratulations on your first Pull Request in Real Dev Squad! 🎉**
162 |
--------------------------------------------------------------------------------
/discord.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 | Discord
8 |
9 |
10 |
11 |
12 |
13 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
26 |
27 |
28 |
29 |
32 |
33 |
34 |
35 |
107 |
108 |
109 |
110 |
111 |
112 |
113 |
114 |
115 |
116 |
117 |
118 |
119 |
120 |
121 |
122 |
123 |
124 |
125 |
126 |
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 | Real Dev Squad Server on Discord
137 |
138 |
139 |
140 |
141 |
142 | New to Real Dev Squad ?
143 |
Don't worry we are here to help you.
144 |
145 |
146 |
147 | Discord is a chat app, similar
148 | to apps such as Skype, or app widely used for professional
149 | communications like Slack.
150 |
151 |
152 | It’s geared towards multiple users, providing them with ways to find
153 | each other, coordinate and talk while using it.
154 |
155 |
156 | It supports video calls, voice chat, and text, allowing users to get
157 | in touch however they please.
158 |
159 |
160 | We have created different channels based on the
161 | task making things much easier to keep information straight &
162 | segregated.
163 |
164 |
165 |
166 |
167 |
168 |
173 |
174 |
175 |
Let's get started with Discord
176 |
177 |
Discord has the server named Real Dev Squad.
178 |
There are multiple categories inside it
179 |
180 |
181 | Live: Which lets you connect with the
182 | members.You can seperatly get connected on call with members of
183 | specific channel.
184 |
185 |
186 |
Admin: All Channels related to admin.
187 |
188 |
189 | Main: It has channels for general
190 | disussion,progress-updates ,newcomers & Support.
191 |
192 |
193 | #general: It carries general discussions.
194 |
195 |
196 | #newcomers: All info related to newcomers are floated
197 | in it.
198 |
199 |
200 | #progress-updates: All info related to current
201 | ongoing task,discussions are posted here.
202 |
203 |
204 | #support: In case you are stuck on need some help
205 | everyone is there to help you keep running.
206 |
207 |
208 |
209 |
210 |
211 | Text Channels: Contains multiple other channels
212 | in it.
213 |
214 |
215 |
216 | Learning: It contains different technology
217 | related channels plus channel for interview preparation.
218 |
219 |
220 |
221 | Dev groups: It contains channels for different
222 | projects.
223 |
145 | Real Dev Squad is a community of developers, where we come
146 | together to learn, use that in building projects, prepare for
147 | interviews, help each-other, put those projects online and try
148 | to help the set of new developers or freshers, helping them get
149 | better jobs and higher salaries with quality work. We come from
150 | all walks of lives and all kinds of background, with one thing
151 | in common: Wanting to work with others and improve ourselves.
152 |
199 | We communicate over a Discord channel. If you wish to join the
200 | Discord channel, please contact any of our
201 | members
204 | to get invitation link.
205 |
230 | Learning Git is highly recommended, but if you do not know it
231 | yet, please follow
232 | this
236 |
237 | guide to get started with Git.
238 |
280 |
281 | Ready to level up your dev skills?
282 | Join
287 | the Real Dev Squad - head over to for an epic coding adventure! or
288 | check our FAQ section.
289 |
290 |
291 |
296 |
297 |