这是indexloc提供的服务,不要输入任何密码
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion .eslintrc.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,4 @@
"@next/next/no-img-element": 0,
"react-hooks/exhaustive-deps": 0
}
}
}
40 changes: 18 additions & 22 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,34 +1,30 @@
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
<div style="text-align: center;">
<img src="public/logo.png" />
<h1>NUESA FUNAAB</h1>
</div>

## Getting Started
This is the project repository for the Nigerian Society of Engineers FUNAAB chapter website[^1].

First, run the development server:

```bash
npm run dev
# or
yarn dev
# or
pnpm dev
```
### Contacts

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
Contact us at any of our social media handles:

You can start editing the page by modifying `app/page.js`. The page auto-updates as you edit the file.
<a href="https://instagram.com/nuesafunaab?igshid=NTc4MTIwNjQ2YQ==" target="_blank" style="text-decoration: none">
<img loading="lazy" height="15" width="15" title="NUESA FUNAAB Instagram" src="https://cdn.simpleicons.org/instagram/E1306C" alt="Instagram icon" /> Instagram</a><br />

This project uses [`next/font`](https://nextjs.org/docs/basic-features/font-optimization) to automatically optimize and load Inter, a custom Google Font.
<a href="https://www.linkedin.com/company/nuesa-funaab/" target="_blank">
<img loading="lazy" height="15" width="15" title="NUESA FUNAAB LinkedIn" src="https://cdn.simpleicons.org/linkedin/0A66C2" alt="LinkedIn icon" /> LinkedIn</a><br />

## Learn More
<a href="https://www.nuesafunaab.com.ng/contact" target="_blank">
<img loading="lazy" height="15" width="15" title="NUESA FUNAAB Website" src="public/logo.png" alt="website icon" /> Website</a><br />

To learn more about Next.js, take a look at the following resources:
<a href="https://x.com/nuesafunaab?s=11" target="_blank">
<img loading="lazy" height="15" width="15" title="NUESA FUNAAB Twitter" src="https://cdn.simpleicons.org/twitter/1DA1F2" alt="Twitter icon" /> Twitter</a><br />

- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.

You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!
---

## Deploy on Vercel
Developer Documentation [&rarr;](docs/README.md)

The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.
[^1]: https://www.nuesafunaab.com.ng/
49 changes: 49 additions & 0 deletions docs/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
<div style="text-align: center;">
<img src="../public/logo.png" />
<h1>NUESA FUNAAB</h1>
<h2>Contributor Code of Conduct</h2>
</div>

---

### Our Pledge

Here, we are committed to fostering an open and welcoming environment. We pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, level of experience, nationality, personal appearance, race and religion.

### Our Standards

To create a positive environment, we expect the following behaviors from all contributors:

* Use welcoming language.
* Show respect for differing viewpoints and experiences.
* Accept constructive criticism gracefully.
* Focus on what is best for the community.
* Demonstrate empathy towards other community members.

Examples of unacceptable behavior include:

* Usage of sexualized language or imagery, as well as unwelcome sexual attention or advances.
* Trolling, insulting or derogatory comments, personal or political attacks.
* Harassment, whether public or private.
* Publishing others' private information, such as physical or electronic addresses, without explicit permission.
* Any other conduct that could reasonably be considered inappropriate in a professional setting.

### Our Responsibilities

As project maintainers, we are responsible for establishing and enforcing acceptable standards of behavior. We are committed to taking 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 do not align with this Code of Conduct. They may also temporarily or permanently ban any contributor for other behaviors they deem inappropriate, threatening, offensive, or harmful.

### Scope

This Code of Conduct applies to all spaces associated with this project, both online and offline. This includes project spaces and public spaces where an individual is representing the project or its community. Examples of representation include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Project maintainers may further define and clarify the representation of a project.

### Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project [team](mailto:nuesafunaab01gmail.com?subject=NUESA%20FUNAAB%20%5BIMPORTANT%5D%3A%20Complaint&cc=jesulayomy@gmail.com,eolaosebikan60@gmail.com,victoryicha2@gmail.com). All complaints will be reviewed and investigated promptly. The project team is committed to maintaining confidentiality regarding the reporter of any incident. Further details on specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce this Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

### Attribution

This Code of Conduct is adapted (rewritten) from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at [Contribution Convenant](http://contributor-covenant.org/version/1/4/).
22 changes: 22 additions & 0 deletions docs/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
<div style="text-align: center;">
<img src="../public/logo.png" />
<h1>NUESA FUNAAB</h1>
<h2>Contributing</h2>
</div>

---

Thank you for considering contributing to NUESA FUNAAB! Before you proceed, we kindly request that you first discuss the changes you wish to make with the owners of this repository. You can reach out to us via the discussions page, or for urgent issues through [email](mailto:nuesafunaab01gmail.com?subject=NUESA%20FUNAAB%20Security%20Vulneraility%20-%20Description&cc=jesulayomy@gmail.com,eolaosebikan60@gmail.com,victoryicha2@gmail.com). This initial discussion will help ensure that your contribution aligns with the project's goals and prevents any duplication of efforts.

As a contributor to NUESA FUNAAB, please adhere to our code of conduct in all your interactions with the project. We strive to maintain an inclusive and respectful environment for everyone involved.

### Pull Request Process

To streamline the process of merging your changes into the main repository, please follow these steps:

1. Before initiating a build, make sure to remove any unnecessary install or build dependencies.
2. Update the README.md file to include clear details of the changes you've made to the interface. This includes documenting new environment variables, exposed ports, useful file locations, and any relevant container parameters.
3. Increment the version numbers in any example files and the README.md to reflect the new version that your Pull Request represents. We adhere to the [SemVer](http://semver.org/) versioning scheme.
4. Once you are ready to merge your Pull Request, kindly obtain the sign-off of at least one developers. If you don't have the necessary permissions, you can request a reviewer to merge it on your behalf.

We appreciate your cooperation in following this process, as it helps maintain the quality and integrity of the NUESA FUNAAB codebase.
Loading