Skip to content

New Design and layout #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Abinash-Anand wants to merge 2 commits into
base: main
Choose a base branch
from
Open

New Design and layout #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c7ec6cf
New Design and layout
Abinash-Anand Jul 24, 2023
9cca9e0
Add files via upload
Abinash-Anand May 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
template.html
portfolio-details.html
template.html
portfolio-details.html
838 changes: 419 additions & 419 deletions 404.html
View file
Open in desktop

Large diffs are not rendered by default.

10 changes: 5 additions & 5 deletions CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Lines starting with '#' are comments.
# Each line is a file pattern followed by one or more owners.

# These owners will be the default owners for everything in the repo.
* @Anindyadeep @AneeshBose @Ash-29
# Lines starting with '#' are comments.
# Each line is a file pattern followed by one or more owners.
# These owners will be the default owners for everything in the repo.
* @Anindyadeep @AneeshBose @Ash-29
166 changes: 83 additions & 83 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,84 +1,84 @@
# Contributing

When contributing to this repository, please first discuss the change you wish to make via issue,
email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

## Pull Request Process

1. Ensure any install or build dependencies are removed before the end of the layer when doing a
build.
2. Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
3. Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent.
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.

## Code of Conduct

### Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.

### Our Standards

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

### Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.

### Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

### Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at [email protected]. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
# Contributing
When contributing to this repository, please first discuss the change you wish to make via issue,
email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
## Pull Request Process
1. Ensure any install or build dependencies are removed before the end of the layer when doing a
build.
2. Update the README.md with details of changes to the interface, this includes new environment
variables, exposed ports, useful file locations and container parameters.
3. Increase the version numbers in any examples files and the README.md to the new version that this
Pull Request would represent.
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
do not have permission to do that, you may request the second reviewer to merge it for you.
## Code of Conduct
### Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.
### Our Standards
Examples of behavior that contributes to creating a positive environment
include:
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
### Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
### Scope
This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
### Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at [email protected]. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
84 changes: 42 additions & 42 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,42 +1,42 @@
# **CORD.ai Website**

![alt text](assets/img/portfolio/cordai.png)

This is the official website of CORD.ai. Please contribute to the website by solving the issues posted by the team.

## **Contributing**

Please head over to the issues tab to get started with contributing to the website. This is how we expect you to contribute to the website.

1. Clone the website.
2. Go to the issues tab and take one issue at a time and discuss that issue with the repo maintainers.
3. Maintainers will be assigning those issues to you.
4. Clone the repo and create your branch. The format must be `<your Name>/<feature name>`. For e.g. Suppose a person named Sam is trying to create dark mode to the website then the branch name must be: `Sam/Website-darkmode`.

5. Commit your changes. We have hosted our website in netlify. So once your PR gets merged to our main branch, you will be seeing the changes to the main site. Netlify automatically has its own CI/CD pipeline. So no need to worry about the deployment.

---

## **Website Roadmap**
### **Phase 0**

1. [x] Completed the initial website.

### **Phase 1**

1. [x] Add a CORD.ai icon.
2. [x] Add the required names, credentials and socials links of each of the core team members.
3. [x] Add new projects and group them based on `projects`, `blogs` and `sessions`.
4. [x] Have a initial maling services done using EmailJS.
5. [x] Adding a form in the `join community` button that will redirect to slack community once form submitted successfully.
6. [x] Deployed the initial repo to Netlify with custom domain.

### **Phase 2**

1. [ ] Solve the left over issues.
2. [ ] Completely change the backend to either `jekyll` or `react`.
3. [ ] Have a proper database of the members and the works that have been done on the community.
4. [ ] Smoothen the experience of users with front end and backend changes. (Specific issues to be added soon.)

---

# **CORD.ai Website**
![alt text](assets/img/portfolio/cordai.png)
This is the official website of CORD.ai. Please contribute to the website by solving the issues posted by the team.
## **Contributing**
Please head over to the issues tab to get started with contributing to the website. This is how we expect you to contribute to the website.
1. Clone the website.
2. Go to the issues tab and take one issue at a time and discuss that issue with the repo maintainers.
3. Maintainers will be assigning those issues to you.
4. Clone the repo and create your branch. The format must be `<your Name>/<feature name>`. For e.g. Suppose a person named Sam is trying to create dark mode to the website then the branch name must be: `Sam/Website-darkmode`.
5. Commit your changes. We have hosted our website in netlify. So once your PR gets merged to our main branch, you will be seeing the changes to the main site. Netlify automatically has its own CI/CD pipeline. So no need to worry about the deployment.
---
## **Website Roadmap**
### **Phase 0**
1. [x] Completed the initial website.
### **Phase 1**
1. [x] Add a CORD.ai icon.
2. [x] Add the required names, credentials and socials links of each of the core team members.
3. [x] Add new projects and group them based on `projects`, `blogs` and `sessions`.
4. [x] Have a initial maling services done using EmailJS.
5. [x] Adding a form in the `join community` button that will redirect to slack community once form submitted successfully.
6. [x] Deployed the initial repo to Netlify with custom domain.
### **Phase 2**
1. [ ] Solve the left over issues.
2. [ ] Completely change the backend to either `jekyll` or `react`.
3. [ ] Have a proper database of the members and the works that have been done on the community.
4. [ ] Smoothen the experience of users with front end and backend changes. (Specific issues to be added soon.)
---
Loading