WordWise is a responsive, user-friendly blogging platform designed to enrich vocabulary and engage readers with insightful articles. Built using HTML, CSS, and JavaScript, the website offers an enjoyable experience with an interactive interface. Whether you're here to read blogs or explore topics, WordWise is for everyone.
| Event Logo | Event Name | Event Description |
|---|---|---|
 |
GirlScript Summer of Code 2024 | GirlScript Summer of Code is a three-month-long Open Source Program conducted every summer by GirlScript Foundation. It is an initiative to bring more beginners to Open-Source Software Development. |
- Key Features
- Technologies Used
- How to Contribute
- Contribution
- Code of conduct
- Contribution Guidelines
- PR Guidelines
- Contribution Points
- GSSoC Guidelines
- Ending Note
- Join Us!
- Contributors
-
📱 Responsive Design
- Thoughtful layout with sections like Home, Leading Blogs, About, and Contact Us for a dedicated navigation experience.
-
📝 Blog Functionality
- Category exploration for easier navigation through organized blogs.
- User Interface designed with appealing graphics to engage viewers.
-
⭐ User Engagement
- Readers can share their thoughts and feedback directly on the Contact Us page.
-
🟦 HTML (HyperText Markup Language)
- Provides structure to the website, organizing content into various elements such as headings, paragraphs, buttons, and images.
-
🟪 CSS (Cascading Style Sheets)
- Responsible for the aesthetics, enhancing visual appeal, and ensuring responsiveness across all devices.
-
⬛ JavaScript
- Adds interactivity and dynamic features, enriching user engagement through blog navigation, comment sections, and form validations.
We’re excited to have you contribute to the WordWise Blogging Website project! Follow these simple steps to get started:
-
🍴 Fork the Repository
- Go to the repository page.
- Click the Fork button (top right) to create a copy in your GitHub account.
-
💻 Clone Your Fork
- Open your terminal and run:
git clone https://github.com/your-username/WordWise.git
- Replace
your-usernamewith your GitHub username.
- Open your terminal and run:
-
🌿 Create a New Branch
- Create a new branch for your work:
git checkout -b your-branch-name
- Create a new branch for your work:
-
🛠️ Make Your Changes
- Open the project files in your code editor and make your changes.
- Contact the project manager ANSHIKA for any queries.
-
✅ Test Your Changes
- Test your changes locally by opening the
index.htmlfile in your browser.
- Test your changes locally by opening the
-
💬 Commit Your Changes
- Once ready, commit them with a descriptive message:
git add . git commit -m "Added feature X or Fixed issue Y"
- Once ready, commit them with a descriptive message:
-
📤 Push Your Changes
- Push your changes to your forked repository:
git push origin your-branch-name
- Push your changes to your forked repository:
-
🔄 Create a Pull Request (PR)
- Go back to the original repository here.
- Click the Compare & pull request button, write a short description of your changes, and submit the PR.
-
🔎 Review Changes
- The project manager will review your PR, and if approved, your request will be merged.
- Open the website and navigate through the articles.
- Use the search bar to find specific topics.
- Click on any article to read in detail.
Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
- If you have any suggestions for the project, such as reporting a bug, improving the UI, or enhancing the README.md file, feel free to open an issue to discuss it or directly create a pull request with the necessary changes.
- Please make sure to check your spelling and grammar.
- Create individual pull requests for each suggestion to keep changes focused and manageable.
Your involvement helps to improve the project and make it better for everyone. Thank you for your contributions!
Kindly go through CONTRIBUTING.md to understand everything from setup to contributing guidelines.
If you would like to contribute to the project, please follow our contribution guidelines.
We are committed to fostering a welcoming and inclusive environment for everyone. All contributors and participants are expected to uphold the following values:
- Be respectful of different viewpoints and experiences.
- Show empathy toward others.
- Use inclusive language.
Please read and follow our Code of Conduct to foster an inclusive community. If anyone violates these standards, they may be banned from the community.
Please follow these guidelines to help maintain the quality and organization of the project. This ensures that contributions and issues are effectively tracked, addressed, and resolved.
- When creating an issue, kindly provide a description of how you plan to implement the solution.
- Make sure the issue has not been raised by someone else!
- If you raise a duplicate issue, it will be closed.
- Review issues raised by other contributors before raising your own to avoid confusion related to duplicate issues. For example, if someone is working on the Navbar UI and you want to add a hover effect to navbar items, understand that this falls under the existing Navbar UI issue.
-
Search for Existing Issues
Before opening a new issue, search the repository to check if the issue already exists. If you find a similar or the same issue, comment on the existing issue and ask to be assigned to it instead of opening a new one. -
Avoid Spamming Multiple Issues
If you have several changes related to the UI, such as footer updates, logo changes, etc., combine them into a single issue. Instead of opening separate issues for each minor adjustment, create one issue and name it appropriately, like "UI Changes". This keeps the issue tracker clean and focused. -
Do Not Ask for a Level Label
Please do not request a level label (e.g., level 1, level 2, level 3). These labels will be assigned based on the issue content and review process.
- Do not work on an issue unless it has been assigned to you!
- Once the issue is assigned, keep us updated on the changes you're making.
- Follow the PR template when raising a Pull Request.
To ensure smooth collaboration and maintain the quality of the project, please follow these guidelines when creating a Pull Request (PR).
- Always create a new branch for your PR and avoid working directly on the
mainormasterbranch. - Use meaningful branch names that reflect the purpose of the changes (e.g.,
feature/add-authentication,bugfix/fix-login-issue).
- Ensure your PR addresses only one issue or feature at a time. Avoid combining unrelated changes in one PR.
- Keep the size of the PR manageable. Large PRs are difficult to review and may cause delays.
Before submitting a PR, ensure that:
- You have synced your branch with the latest version of the main branch.
- You have added necessary screenshots or videos to demonstrate the changes.
- You have written or updated any necessary documentation (if applicable).
- You have tested your changes to ensure they work as expected.
- Use a clear and concise title for the PR that explains the change.
- In the PR description, provide:
- A brief explanation of the problem being solved or the feature being implemented.
- A list of changes made.
- References to any related issues (e.g., "Fixes Does not visible 'Load More Post...' #123").
- Any specific areas where the reviewer should focus.
All tasks will be assigned various levels based on complexity and required skills. Each level provides different points:
- 🥇 Level 1: 10 Points
- 🥈 Level 2: 25 Points
- 🥉 Level 3: 45 Points
It is important to adhere to the guidelines; violations can affect your profile. Review the guidelines here.
Thank you for checking out the WordWise Blogging Website! We hope you find this project enjoyable and informative. Your feedback, contributions, and suggestions are always welcome!
If you have any questions or need assistance, please feel free to reach out through the Issues section of this repository.
We encourage you to explore the website, share your thoughts, and get involved in improving the project. Let’s make this blogging experience even better together!
