It rankles me a little that you want to be a trusted voice in journaling, but can't be bothered to proofread or spell-check the very first descriptive paragraph anyone sees.
He's showing his project, it's best to keep condescending comments about the person to yourself. Just focus on what is needed to make the project better.
@Daybooks - Kudos for actually launching something. Done is better than perfect. Now on with comments that actually help the project.
Writing copy is always a pain - I still have issues with grammar and spelling, however my code is flawless :) It's a pain to proofread when you're heavily invested in the code.
The presentation is neat and clean. Until you get buzz that will do the explaining for you, it's best to put something on the front page for those who don't get what you have already. It feels intimate because you have to be in the know to have a good gist of what it does. However, it's all about your audience.
I like UI but for users with IE or older browsers, your dependence on HTML5 and CSS3 might pose a problem with adoption. Always have graceful fallback.
The images you're loading are sized way too large and take time to load. Kill the image sizes at 1080P and let responsive CSS do the rest. Faster load times and better presentation.
On the landing page or about page - show an actual example of what the daybook entry looks like. Is there a link or a screenshot?
It looks promising - is this public or private posting?
Thanks for your suggestions, I have been working on making the images smaller and load faster. In reply to your question if the post is public or private, the answer is up to you. Initially your daybook page is private, this can be changed under settings, a published post is public and a private post is hidden from the site. I get this can be confusing and I'm working on adding clarity throughout.
In response to everyone else who commented, thanks for taking the time to share your thoughts, and I will be sure to update the page accordingly, i.e (copy, landing page, ssl, clearer publish button, demo, etc). I apologize for not commenting earlier, but being HN was not allowing me to comment at my usual speed, that and I was taking a history exam. Anyway, thanks for looking at the site, I hope in the next update will shed more insight as to what daybook can do.
I apologize for any errors made in the copy of the website, please understand that these were made unintentionally and will be corrected promptly. That being said, I do want to clarify that my goal with daybook is not to be a voice in journaling, but to provide consumers with a platform where they can log their lives just as they would with a diary.
Ever considered the possibility that not everyone who writes on the Internet had the fate to be born Anglophone? To some, believe it or not, English might even be their tertiary language. A quick Whois lookup might have made you reconsider your phrasing on that one. And while we're at it, how is your French?
c'est terrible. Mais, je ne producer un anglais web site du journaling pas. If I ever do the converse, I promise I'll make sure my French copy is comprehensible.
@Daybooks - Kudos for actually launching something. Done is better than perfect. Now on with comments that actually help the project.
Writing copy is always a pain - I still have issues with grammar and spelling, however my code is flawless :) It's a pain to proofread when you're heavily invested in the code.
The presentation is neat and clean. Until you get buzz that will do the explaining for you, it's best to put something on the front page for those who don't get what you have already. It feels intimate because you have to be in the know to have a good gist of what it does. However, it's all about your audience.
I like UI but for users with IE or older browsers, your dependence on HTML5 and CSS3 might pose a problem with adoption. Always have graceful fallback.
The images you're loading are sized way too large and take time to load. Kill the image sizes at 1080P and let responsive CSS do the rest. Faster load times and better presentation.
On the landing page or about page - show an actual example of what the daybook entry looks like. Is there a link or a screenshot?
It looks promising - is this public or private posting?