Skip to content
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.

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

Blog Creation Feature #204

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Blog Creation Feature #204

wants to merge 4 commits into from

Conversation

CodePokeX
Copy link
Contributor

Description

Added the feature for creating new Blogs. Each exec member has a different dashboard for creating/editing/approving the blogs. This is mostly similar to the virtual_expo reports. Each user has to get the blogs approved before being published. The approver is being assigned manually by the admin for now and each user can approve only those blogs assigned to them by the admin. There is a separate dashboard for the admins to see all the status of all the blogs. I have also added a filter option by author and blog_tag for ease of searching the blogs. There is also a separate form for managing the blog separately for the admin.
image

image

image

image

image
image

image

Screencast_20250215_120131.webm

Fixes #

Dependencies

List any dependencies that are required for this change.

Type of Change

What types of changes does your code introduce?
Put an x in the boxes that apply

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration. (for bug fix / breaking change)
Put an x in the boxes that apply

  • Test A
  • Test B

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Copy link

sentry-io bot commented Feb 15, 2025

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: corpus/blog/views.py

Function Unhandled Issue
tagged_blog Tag.DoesNotExist: Tag matching query does not exist. /blog/tags/{specific_...
Event Count: 8

Did you find this useful? React with a 👍 or 👎

@yukitya-1811
Copy link
Contributor

A few points -

  1. The content of the blog must be a ckeditor field and we should support rich-text typing here (image uploading functionality etc)
  2. I'm assuming all permissions are being handled by group checks here?
  3. @VarshiniAdurti28 is working on the frontend redesign for blog so it's better you wait a little bit until her PR is merged. There may be small conflicts which you might have to resolve

@CodePokeX
Copy link
Contributor Author

Yes all permissions are being handled by group checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants