-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: Blog #15
Comments
Also, there's still no UI Design from this features, just use your creativity to make it real and usable. |
I wanna try solving this one @algonacci |
Alright, do you have any inspiration of the UI design or you'll go with Plain design? Btw just mention me if you need the sample of a blog post 😄 I'll assign first yaa |
Maybe you can breakdown the field that will be needed for this feature? I'm thinking of like this
|
Yeah i think i can add :
I will try to create the database schema design and post it here |
Alright, just mention me if you need something |
Can i see KawanData website design components? like headers, logo, color, fonts, etc |
Sure, you can access it from here. Btw you'll also do the frontend side too? 😅 https://www.figma.com/file/1N5ODROvOxrar1zv7imjTJ/KawanData?node-id=0%3A1 |
That's my intention, but it would be better if someone else is willing to contribute |
Anyone's interested in doing the frontend side? 😅 @doniwirawan @fadila-amin |
I have few questions:
|
|
|
i'm really interested to contribute on that |
Alright, I'll assign you first yaa. We will collaborate each other @NurfitraPujo @doniwirawan. Both FE to BE or BE to FE is fine, no problem who will done the task first. Any template also definitely fine for this project. Thank you guys, we'll see the result later yaa. |
I am in the middle of designing the UI for the blogs. Here's the link https://www.figma.com/file/QqH7NF7scHAWxUFgW2N8xx/KawanData?node-id=0%3A1 need feedback @algonacci @doniwirawan |
Can you please review or is there any suggestion? @AaEzha |
My concern when i placed the list of articles on the left because if there any changes in the future the layout can stay consistent. What do you think? For what can be placed in the right section:
|
Oohh alright. I like this one, we can continue with this |
how do we use "popularity" column on tags table? |
I think it must be from 'most viewed' blog post? Correct me if I'm wrong @AaEzha @NurfitraPujo |
yep i think so, we probably can increment it each time there is unique viewer accessing the article (by IP Address maybe?). We can also have popular article this month, this week, etc but thats for future i guess |
I ever make this kind of blog feature. There are so many parameters.
I will come back if I found the schema. |
Mas @benben4567 joined the team! Feel free to share our workload because he will help us develop this feature 😄 @NurfitraPujo @doniwirawan |
amazing news! welcome to the club, mas @benben4567 due to holiday vibes, I prefer to relax for a while :) |
Sorry for late reply @algonacci , my email notification doesn't appear.. i just monitoring from discord.. I will do this task ASAP |
How about we discuss about the database schema first? |
i have something about schema that works and proper to Laravel naming conventions, maybe later i will add it. |
That would be nice! Thanks a lot |
I will go with this but still need suggestion from the others |
I think we can start working using that schema, i have some question thought:
I also think we need to add a table to store the most popular tag based on periodic blog views. But i guess this is not priority |
|
How do we divide the task for this epic? |
Any suggestion? Maybe we can open up new issues for this epic into a single backlog? I'll assign later |
The text was updated successfully, but these errors were encountered: