This page showcases the various products or services offered by our company. You can find details about each product, such as features, pricing, and customer reviews.
72 |
73 |
74 |
75 |
76 |
77 |
Product 1
78 |
Description of Product 1. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Description of Product 2. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
87 |
Price: $XX.XX
88 | Learn More
89 |
90 |
91 |
92 |
93 |
94 |
95 |
96 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make 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, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6 |
7 | ## Our Standards
8 |
9 | Examples of behavior that contributes to creating a positive environment include:
10 |
11 | - Using welcoming and inclusive language
12 | - Being respectful of differing viewpoints and experiences
13 | - Gracefully accepting constructive criticism
14 | - Focusing on what is best for the community
15 | - Showing empathy towards other community members
16 |
17 | Examples of unacceptable behavior by participants include:
18 |
19 | - The use of sexualized language or imagery and unwelcome sexual attention or advances
20 | - Trolling, insulting/derogatory comments, and personal or political attacks
21 | - Public or private harassment
22 | - Publishing others' private information, such as a physical or electronic address, without explicit permission
23 | - Other conduct which could reasonably be considered inappropriate in a professional setting
24 |
25 | ## Our Responsibilities
26 |
27 | 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.
28 |
29 | 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.
30 |
31 | ## Scope
32 |
33 | 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.
34 |
35 |
36 | ## Attribution
37 |
38 | This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
39 |
40 | For answers to common questions about this code of conduct, see [FAQ](https://www.contributor-covenant.org/faq).
41 |
--------------------------------------------------------------------------------
/assets/asset 29.svg:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | ### Welcome to Job-Portal 🚀
3 |
4 |
5 | ---
6 | **About Job-Portal**
7 |
8 | Welcome to our Job Portal Project! This project aims to create a user-friendly platform for job seekers to find employment opportunities and for employers to post job listings. Below you'll find information on how to set up and run the project, as well as an overview of its features.
9 |
10 | **Features:**
11 |
12 | 1.**User Registration and Authentication:** Job seekers and employers can register and log in securely to access the portal's features.
13 |
14 | 2.**Job Listings:** Employers can post job listings, including job titles, descriptions, requirements, and contact information.
15 |
16 | 3.**Job Search:** Job seekers can search for job listings based on various criteria such as job title, location, and keywords.
17 |
18 | 4.**Filters and Sorting:** Users can filter and sort job listings based on different parameters to find relevant opportunities efficiently.
19 |
20 | 5.**Application Management:** Job seekers can apply to job listings directly through the portal, and employers can manage received applications.
21 |
22 | 6.**User Profiles:** Both job seekers and employers have profiles where they can manage their information, including resumes, job preferences, and company details.
23 |
24 | 7.**Notifications:** Users receive notifications for important events such as new job listings, application status updates, and messages from employers.
25 | ***
26 | **Getting Started**
27 |
28 | Contributing Contributions are always welcome!
29 |
30 | 1. Fork this repository.
31 | 2. Clone your forked copy of the project.
32 | ``` git clone https://github.com/your-username/jobproject.git```
33 | 3. Add reference to original repository,use the following command
34 | ``` git remote add upstream https://github.com/your-username/jobproject.git ```
35 | 4. Check the remotes for this repository,use following command.
36 | ```git remote -v```
37 |
38 | 5. Always take a pull from the upstream repository to your main branch
39 | to keep it up-to-date with the main
40 | ```git pull upstream main```
41 | 6. Create a new branch.
42 | ``` git checkout -b ```
43 |
44 | 7. You are all set ! Perform your desired changes to the code base.
45 | 8. Track your changes.
46 | ```git add .```
47 | 9. Commit your changes.
48 | ```git commit -m "relevant commit message"```
49 | 10. Push the committed changes in your feature branch to your remote
50 | repo.
51 | ``` git push -u origin ```
52 | 11. To create a pull request, click on "Compare and pull requests".
53 | Please ensure you compare your feature branch to the desired branch
54 | of the repo you are suppose to make a PR to.
55 | ***
56 |
57 | **Feedback:**
58 |
59 | We value your feedback! If you encounter any issues, have suggestions for improvements, or want to contribute ideas for new features, please open an issue on the project's GitHub repository or reach out to us directly.
60 |
61 |
--------------------------------------------------------------------------------
/pricing.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Pricing
7 |
58 |
59 |
60 |
61 |
Pricing
62 |
This page outlines the pricing plans or packages offered by our company. You can find details about different tiers, features included in each plan, and pricing information.
96 |
97 |
98 |
99 |
100 |
101 |
102 |
--------------------------------------------------------------------------------
/Learn.md:
--------------------------------------------------------------------------------
1 |
2 | # Contributing to Job-Portal 🚀
3 |
4 | Welcome to our Job Portal Project! This project aims to create a user-friendly platform for job seekers to find employment opportunities and for employers to post job listings. Below you'll find information on how to set up and run the project, as well as an overview of its features.
5 |
6 | ## Features:
7 |
8 | 1. **User Registration and Authentication**: Job seekers and employers can register and log in securely to access the portal's features.
9 |
10 | 2. **Job Listings**: Employers can post job listings, including job titles, descriptions, requirements, and contact information.
11 |
12 | 3. **Job Search**: Job seekers can search for job listings based on various criteria such as job title, location, and keywords.
13 |
14 | 4. **Filters and Sorting**: Users can filter and sort job listings based on different parameters to find relevant opportunities efficiently.
15 |
16 | 5. **Application Management**: Job seekers can apply to job listings directly through the portal, and employers can manage received applications.
17 |
18 | 6. **User Profiles**: Both job seekers and employers have profiles where they can manage their information, including resumes, job preferences, and company details.
19 |
20 | 7. **Notifications**: Users receive notifications for important events such as new job listings, application status updates, and messages from employers.
21 |
22 | ## Getting Started
23 |
24 | ### Contributing
25 |
26 | Contributions are always welcome!
27 |
28 | 1. **Fork this repository**: Click the "Fork" button in the top-right corner of this repository's page to create your own copy of the project.
29 |
30 | 2. **Clone your forked copy**: Clone the repository to your local machine using the following command:
31 | ```bash
32 | git clone https://github.com/your-username/jobproject.git
33 | ```
34 |
35 | 3. **Add reference to original repository**: Connect your fork to the original repository to stay updated with its changes:
36 | ```bash
37 | git remote add upstream https://github.com/your-username/jobproject.git
38 | ```
39 |
40 | 4. **Create a new branch**: Before making any changes, create a new branch to work on your feature or bug fix:
41 | ```bash
42 | git checkout -b
43 | ```
44 |
45 | 5. **Make Changes**: Now you're ready to make your changes! Feel free to modify existing code, add new features, or fix bugs.
46 |
47 | 6. **Commit Your Changes**: Once you've made your changes, commit them with a descriptive message:
48 | ```bash
49 | git add .
50 | git commit -m "relevant commit message"
51 | ```
52 |
53 | 7. **Push Changes to Your Fork**: Push your changes to your fork on GitHub:
54 | ```bash
55 | git push -u origin
56 | ```
57 |
58 | 8. **Submit a Pull Request**: Go to your fork on GitHub and click on the "Compare and pull requests" button. Provide a descriptive title and detailed description of your changes. Then, submit the pull request for review.
59 |
60 | ## Feedback
61 |
62 | We value your feedback! If you encounter any issues, have suggestions for improvements, or want to contribute ideas for new features, please let us know by [creating an issue](https://github.com/your-username/jobproject/issues).
63 |
64 | We appreciate your contributions!
65 | ```
66 |
--------------------------------------------------------------------------------
/assets/asset 8.svg:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/.github/contributing.md:
--------------------------------------------------------------------------------
1 | # Contributing Guidelines
2 |
3 | *Pull requests, bug reports, and all other forms of contribution are welcomed and highly encouraged!* :octocat:
4 |
5 | ### Contents
6 |
7 | - [Code of Conduct](#book-code-of-conduct)
8 | - [Asking Questions](#bulb-asking-questions)
9 | - [Opening an Issue](#inbox_tray-opening-an-issue)
10 | - [Feature Requests](#love_letter-feature-requests)
11 | - [Triaging Issues](#mag-triaging-issues)
12 | - [Submitting Pull Requests](#repeat-submitting-pull-requests)
13 | - [Writing Commit Messages](#memo-writing-commit-messages)
14 | - [Code Review](#white_check_mark-code-review)
15 | - [Coding Style](#nail_care-coding-style)
16 | - [Certificate of Origin](#medal_sports-certificate-of-origin)
17 | - [Credits](#pray-credits)
18 |
19 | > **This guide serves to set clear expectations for everyone involved with the project so that we can improve it together while also creating a welcoming space for everyone to participate. Following these guidelines will help ensure a positive experience for contributors and maintainers.**
20 |
21 | ## :book: Code of Conduct
22 |
23 | Please review our [Code of Conduct](https://github.com/jessesquires/.github/blob/main/CODE_OF_CONDUCT.md). It is in effect at all times. We expect it to be honored by everyone who contributes to this project. Acting like an asshole will not be tolerated.
24 |
25 | ## :bulb: Asking Questions
26 |
27 | See our [Support Guide](https://github.com/jessesquires/.github/blob/main/SUPPORT.md). In short, GitHub issues are not the appropriate place to debug your specific project, but should be reserved for filing bugs and feature requests.
28 |
29 | ## :inbox_tray: Opening an Issue
30 |
31 | Before [creating an issue](https://help.github.com/en/github/managing-your-work-on-github/creating-an-issue), check if you are using the latest version of the project. If you are not up-to-date, see if updating fixes your issue first.
32 |
33 | ### :lock: Reporting Security Issues
34 |
35 | Review our [Security Policy](https://github.com/jessesquires/.github/blob/main/SECURITY.md). **Do not** file a public issue for security vulnerabilities.
36 |
37 | ### :beetle: Bug Reports and Other Issues
38 |
39 | A great way to contribute to the project is to send a detailed issue when you encounter a problem. We always appreciate a well-written, thorough bug report. :v:
40 |
41 | In short, since you are most likely a developer, **provide a ticket that you would like to receive**.
42 |
43 | - **Review the documentation and [Support Guide](https://github.com/jessesquires/.github/blob/main/SUPPORT.md)** before opening a new issue.
44 |
45 | - **Do not open a duplicate issue!** Search through existing issues to see if your issue has previously been reported. If your issue exists, comment with any additional information you have. You may simply note "I have this problem too", which helps prioritize the most common problems and requests.
46 |
47 | - **Prefer using [reactions](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)**, not comments, if you simply want to "+1" an existing issue.
48 |
49 | - **Fully complete the provided issue template.** The bug report template requests all the information we need to quickly and efficiently address your issue. Be clear, concise, and descriptive. Provide as much information as you can, including steps to reproduce, stack traces, compiler errors, library versions, OS versions, and screenshots (if applicable).
50 |
51 | - **Use [GitHub-flavored Markdown](https://help.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax).** Especially put code blocks and console outputs in backticks (```). This improves readability.
52 |
53 | ## :love_letter: Feature Requests
54 |
55 | Feature requests are welcome! While we will consider all requests, we cannot guarantee your request will be accepted. We want to avoid [feature creep](https://en.wikipedia.org/wiki/Feature_creep). Your idea may be great, but also out-of-scope for the project. If accepted, we cannot make any commitments regarding the timeline for implementation and release. However, you are welcome to submit a pull request to help!
56 |
57 | - **Do not open a duplicate feature request.** Search for existing feature requests first. If you find your feature (or one very similar) previously requested, comment on that issue.
58 |
59 | - **Fully complete the provided issue template.** The feature request template asks for all necessary information for us to begin a productive conversation.
60 |
61 | - Be precise about the proposed outcome of the feature and how it relates to existing features. Include implementation details if possible.
62 |
63 | ## :mag: Triaging Issues
64 |
65 | You can triage issues which may include reproducing bug reports or asking for additional information, such as version numbers or reproduction instructions. Any help you can provide to quickly resolve an issue is very much appreciated!
66 |
67 | ## :repeat: Submitting Pull Requests
68 |
69 | We **love** pull requests! Before [forking the repo](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) and [creating a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests) for non-trivial changes, it is usually best to first open an issue to discuss the changes, or discuss your intended approach for solving the problem in the comments for an existing issue.
70 |
71 | For most contributions, after your first pull request is accepted and merged, you will be [invited to the project](https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) and given **push access**. :tada:
72 |
73 | *Note: All contributions will be licensed under the project's license.*
74 |
75 | - **Smaller is better.** Submit **one** pull request per bug fix or feature. A pull request should contain isolated changes pertaining to a single bug fix or feature implementation. **Do not** refactor or reformat code that is unrelated to your change. It is better to **submit many small pull requests** rather than a single large one. Enormous pull requests will take enormous amounts of time to review, or may be rejected altogether.
76 |
77 | - **Coordinate bigger changes.** For large and non-trivial changes, open an issue to discuss a strategy with the maintainers. Otherwise, you risk doing a lot of work for nothing!
78 |
79 | - **Prioritize understanding over cleverness.** Write code clearly and concisely. Remember that source code usually gets written once and read often. Ensure the code is clear to the reader. The purpose and logic should be obvious to a reasonably skilled developer, otherwise you should add a comment that explains it.
80 |
81 | - **Follow existing coding style and conventions.** Keep your code consistent with the style, formatting, and conventions in the rest of the code base. When possible, these will be enforced with a linter. Consistency makes it easier to review and modify in the future.
82 |
83 | - **Include test coverage.** Add unit tests or UI tests when possible. Follow existing patterns for implementing tests.
84 |
85 | - **Update the example project** if one exists to exercise any new functionality you have added.
86 |
87 | - **Add documentation.** Document your changes with code doc comments or in existing guides.
88 |
89 | - **Update the CHANGELOG** for all enhancements and bug fixes. Include the corresponding issue number if one exists, and your GitHub username. (example: "- Fixed crash in profile view. #123 @jessesquires")
90 |
91 | - **Use the repo's default branch.** Branch from and [submit your pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) to the repo's default branch. Usually this is `main`, but it could be `dev`, `develop`, or `master`.
92 |
93 | - **[Resolve any merge conflicts](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)** that occur.
94 |
95 | - **Promptly address any CI failures**. If your pull request fails to build or pass tests, please push another commit to fix it.
96 |
97 | - When writing comments, use properly constructed sentences, including punctuation.
98 |
99 | - Use spaces, not tabs.
100 |
101 | ## :memo: Writing Commit Messages
102 |
103 | Please [write a great commit message](https://chris.beams.io/posts/git-commit/).
104 |
105 | 1. Separate subject from body with a blank line
106 | 1. Limit the subject line to 50 characters
107 | 1. Capitalize the subject line
108 | 1. Do not end the subject line with a period
109 | 1. Use the imperative mood in the subject line (example: "Fix networking issue")
110 | 1. Wrap the body at about 72 characters
111 | 1. Use the body to explain **why**, *not what and how* (the code shows that!)
112 | 1. If applicable, prefix the title with the relevant component name. (examples: "[Docs] Fix typo", "[Profile] Fix missing avatar")
113 |
114 | ```
115 | [TAG] Short summary of changes in 50 chars or less
116 |
117 | Add a more detailed explanation here, if necessary. Possibly give
118 | some background about the issue being fixed, etc. The body of the
119 | commit message can be several paragraphs. Further paragraphs come
120 | after blank lines and please do proper word-wrap.
121 |
122 | Wrap it to about 72 characters or so. In some contexts,
123 | the first line is treated as the subject of the commit and the
124 | rest of the text as the body. The blank line separating the summary
125 | from the body is critical (unless you omit the body entirely);
126 | various tools like `log`, `shortlog` and `rebase` can get confused
127 | if you run the two together.
128 |
129 | Explain the problem that this commit is solving. Focus on why you
130 | are making this change as opposed to how or what. The code explains
131 | how or what. Reviewers and your future self can read the patch,
132 | but might not understand why a particular solution was implemented.
133 | Are there side effects or other unintuitive consequences of this
134 | change? Here's the place to explain them.
135 |
136 | - Bullet points are okay, too
137 |
138 | - A hyphen or asterisk should be used for the bullet, preceded
139 | by a single space, with blank lines in between
140 |
141 | Note the fixed or relevant GitHub issues at the end:
142 |
143 | Resolves: #123
144 | See also: #456, #789
145 | ```
146 |
147 | ## :white_check_mark: Code Review
148 |
149 | - **Review the code, not the author.** Look for and suggest improvements without disparaging or insulting the author. Provide actionable feedback and explain your reasoning.
150 |
151 | - **You are not your code.** When your code is critiqued, questioned, or constructively criticized, remember that you are not your code. Do not take code review personally.
152 |
153 | - **Always do your best.** No one writes bugs on purpose. Do your best, and learn from your mistakes.
154 |
155 | - Kindly note any violations to the guidelines specified in this document.
156 |
157 | ## :nail_care: Coding Style
158 |
159 | Consistency is the most important. Following the existing style, formatting, and naming conventions of the file you are modifying and of the overall project. Failure to do so will result in a prolonged review process that has to focus on updating the superficial aspects of your code, rather than improving its functionality and performance.
160 |
161 | For example, if all private properties are prefixed with an underscore `_`, then new ones you add should be prefixed in the same way. Or, if methods are named using camelcase, like `thisIsMyNewMethod`, then do not diverge from that by writing `this_is_my_new_method`. You get the idea. If in doubt, please ask or search the codebase for something similar.
162 |
163 | When possible, style and format will be enforced with a linter.
164 |
165 | ## :medal_sports: Certificate of Origin
166 |
167 | *Developer's Certificate of Origin 1.1*
168 |
169 | By making a contribution to this project, I certify that:
170 |
171 | > 1. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
172 | > 1. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
173 | > 1. The contribution was provided directly to me by some other person who certified (1), (2) or (3) and I have not modified it.
174 | > 1. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
175 |
176 | ## [No Brown M&M's](https://en.wikipedia.org/wiki/Van_Halen#Contract_riders)
177 |
178 | If you are reading this, bravo dear user and (hopefully) contributor for making it this far! You are awesome. :100:
179 |
180 | To confirm that you have read this guide and are following it as best as possible, **include this emoji at the top** of your issue or pull request: :black_heart: `:black_heart:`
181 |
182 | ## :pray: Credits
183 |
184 | Written by [@jessesquires](https://github.com/jessesquires).
185 |
186 | **Please feel free to adopt this guide in your own projects. Fork it wholesale or remix it for your needs.**
187 |
188 | *Many of the ideas and prose for the statements in this document were based on or inspired by work from the following communities:*
189 |
190 | - [Alamofire](https://github.com/Alamofire/Alamofire/blob/master/CONTRIBUTING.md)
191 | - [CocoaPods](https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md)
192 | - [Docker](https://github.com/moby/moby/blob/master/CONTRIBUTING.md)
193 | - [Linux](https://elinux.org/Developer_Certificate_Of_Origin)
194 |
195 | *We commend them for their efforts to facilitate collaboration in their projects.*
196 |
--------------------------------------------------------------------------------
/assets/asset 27.svg:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
22 |
23 | My Website
24 |
25 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 | 🥳 New to Usability Hub: Open and Closed card sorting
41 |
42 |
43 |
44 |
45 |
46 |
76 |
77 |
78 |
79 |
80 |
81 |
Design Confidently
82 |
83 | UsabilityHub is a remote user research platform that takes the
84 | guesswork out of design decisions by validating them with real
85 | users.
86 |