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: Images and Comments #55

Open
calo1 opened this issue Jul 26, 2016 · 9 comments
Open

Blog: Images and Comments #55

calo1 opened this issue Jul 26, 2016 · 9 comments
Assignees

Comments

@calo1
Copy link
Collaborator

calo1 commented Jul 26, 2016

The blog feature is integrated , but we need images to go to a database. Also fix bugs in the commenting feature

@calo1
Copy link
Collaborator Author

calo1 commented Jul 26, 2016

There are also some formatting issues in the blog itself
screen shot 2016-07-25 at 8 50 27 pm

@stlim0730
Copy link
Owner

The time has come: it's time to talk about database. The current version of Farmview is using PostgreSQL running on Heroku; free plan for now. @kbourque, you can find the database credentials on Heroku dashboard.

@stlim0730
Copy link
Owner

stlim0730 commented Jul 27, 2016

@kbourque, I have a question. Where is the text content and comments currently stored when you create a blog post?

@calo1
Copy link
Collaborator Author

calo1 commented Aug 3, 2016

@kbourque I'm working a bit on blogs today.

Here are some minor things I think could use polishing:

  1. Readme file ( indicate the required textism formatting) and provide a link to textism documentation resources

  2. The CSS for the sidebar looked great on your demo, but got lost when it was merged.

  3. What do the SITE(s) option and example url options intended to do on the admin panel

  4. What is the best way to provide images? Either we do farmview-supported image hosting or we do image source referencing in the text?

@kbourque
Copy link
Collaborator

kbourque commented Aug 3, 2016

Hey Taek,

I'll update the readme file and look into the other issues. I will let you
know what I have in the next few hours.

Thanks,
Kim

On Wednesday, August 3, 2016, calo1 [email protected] wrote:

@kbourque https://github.com/kbourque I'm working a bit on blogs today.

Here are some minor things I think could use polishing:

  1. Readme file ( indicate the required textism formatting) and provide a
    link to textism documentation resources

  2. The CSS for the sidebar looked great on your demo, but got lost when it
    was merged.

  3. What do the SITE(s) option and example url options intended to do on
    the admin panel

  4. What is the best way to provide images? Either we do farmview-supported
    image hosting or we do image source referencing in the text?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#55 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANQB7fyfZPKgJs8tPg7EZ8RE3FK1lMIgks5qcNC3gaJpZM4JUsCc
.

Kimberly Bourque
Computer Science
University of California, Berkeley
Degree to be Awarded May 2018
619-988-2006

@kbourque
Copy link
Collaborator

kbourque commented Aug 3, 2016

Also, are you talking about this in regards to the sidebar?

screenshot 2016-08-03 14 19 25

I can change that easily. Working on comments and image upload now.

@calo1
Copy link
Collaborator Author

calo1 commented Aug 3, 2016

@kbourque yes, the CSS for the sidebar

@kbourque
Copy link
Collaborator

kbourque commented Aug 3, 2016

In regards to the comments, I was thinking we could just use Disqus for the commenting system as I would have to set up e-mail configurations for Zinnia's comment system; that was the issue earlier. I have successfully integrated Disqus, but let me know if that is not the route you want to go.

@calo1
Copy link
Collaborator Author

calo1 commented Aug 3, 2016

Let's discuss (haha) tomorrow! I think DIsqus is very reasonable.

@karingoh karingoh assigned karingoh and unassigned kbourque Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants