Second version of iit-techambit frontend.
npm install
npm start
NOTE: Please use only npm as package manager not any other to avoid dependency clashes
- We do not commit to
master
branch directly. We open pull requests and merge them in master after review. - Create the issue as necessary.
- If you lack the technical knowhow, feel free ask in the slack workspace.
- Create a Branch and Commit your changes.
- Name the branch carefully. For example
feature-card-component
,bugfix-overlay
. Do not use generic names such asdevelop
,work
, your username etc. - Name the commits meaningfully. For help read How to Write a Git Commit Message.
- Name the branch carefully. For example
- Check if the solution works by testing it locally.
- Submit a PR with an appropriate name including the term
Fixes #{issue number}
if it fixes that particular issue. - Be attentive and respond to comments and suggestions in the opened PR.
- We will merge your PR after reviewing and testing it.
- Use prettier extension for code linting
Note that the master
branch is deployed to server through Midgard. Any commits pushed to master
will be deployed to server instantly
A manual deployment can be triggered by going to the midgard dashboard.
The documentation for the Material Kit React is hosted at our website.
{
"files.trimTrailingWhitespace": true,
"editor.formatOnSave": true,
"eslint.autoFixOnSave": true,
"eslint.alwaysShowStatus": true,
"javascript.updateImportsOnFileMove.enabled": "always",
"prettier.jsxSingleQuote": true,
"prettier.singleQuote": true
}
- Use Pascal case naming convention for naming files, variables meaningfully.
- Usage of ES6 Features when compared to vanilla JS is highly recommended.
All the routes are present in src/index.js
- Navbar is present in
src/views/Components/Navbar.js
- And navbar items are present in
src/components/Header/HeaderLinks.js
- The frontpage is present in
src/views/Components/Components.js
/stories
route- The component that is rendered in the page is
src/views/Archive/Archive.js
which renders Article cards.Here only data is being fetched from the Drupal CMS API - Each Article card is present is present in
src/views/Archive/ArticleCard.js
- On clicking on each card, leads to ReadingPage of each article which is the component
src/views/ReadingPage/ReadingPage.js
,Here also the data is fetched from Drupal CMS API
/archive
route- The component that is rendered is in the page
src/views/Stories/Stories.js
which displays Stories Card(Bad naming) ,this renders from the Flask API. **Fetching from Flask API is done using functiongetData
present insrc/integrate.js
and the endpoints are present insrc/config.js
** - Each Story card is present in
src/views/Stories/StoriesCard.js
/newsletter
route- The component being rendered is in
src/views/Newsletter/Newsletter.js
- It fetches the HTML from Flask API using similar manner as described in the
/archive
route in bold. The HTML is rendered using a parser,which is a npm package. Other component isSubscriptInput
which is the subscribe box present at the right bottom of the page
/team
route- The component that is being rendered is in
src/views/Team/Team.js
which displays TeamMemberCard. Each team members details are present in the array namedTeamList
insrc/views/Team/TeamList.js
- The team member card is present in
src/views/TeamMemberCard.js
- For stylings we are using
SASS
, Don't worry, just write plain CSS in thescss
file too. It works perfectly fine - Mostly, we have tried naming to be in such a way that the name of the
.js
file and.scss
file match. Keep up the practice please !
-
Copyright 2019 Creative Tim (https://www.creative-tim.com/)
-
Licensed under MIT (https://github.com/creativetimofficial/material-kit/blob/master/LICENSE.md)
- Tutorials
- Affiliate Program (earn money)
- Blog Creative Tim
- Free Products from Creative Tim
- Premium Products from Creative Tim
- React Products from Creative Tim
- Angular Products from Creative Tim
- VueJS Products from Creative Tim
- More products from Creative Tim
- Check our Bundles here