Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Pretty much correct — I built it in plain HTML/CSS to get it working, then retired to Photoshop to build how it would essentially look (which I took a lot from the existing weddingtype.com design, so that helped with the speed), then threw in CSS at the end. None of the extraneous pages, like "About", were built either until the CSS point, so it wasn't all design.

Thank you!



Did you do wireframes or page description diagrams?

I always need something to help me conceptualize what it is that I want to build, more than just a few bullet points or flowcharts. As a designer/developer, I find it easiest to just dive into photoshop and mock a few things up, even if they're not what I would consider final designs. It helps me think about how things will work, and what the user experience will be like.


If I'm working on client work, then I always do wireframes first (giving a choice of three different layout/UX concepts). But for WIL, because I was working for myself and under a self imposed time constraint, I went straight from sketches --> PSDs --> CSS.

I'm going to be revamping the profile pages in the near future, and that process will almost certainly include wireframing, since I have more time to do it "right".


I do both design and development so I'm not really sure what side of the fence I fall under, but in the last year or so I've actually transitioned to writing the HTML first and then designing in photoshop as well. I actually find this method to be far superior to skin first, but then again I am a good enough developer that it makes sense to me to think in this way easily. I'm surprised that this method comes as such a surprise to HN, I thought it was a much more common practice.

The best part is that this leads to very clean and well structured HTML, and a better design because you know exactly what your content is.


Gorgeous design! If I'm allowed a nitpick, the two buttons on the About page are nearly but not exactly aligned vertically, probably as an oversight.


Definitely allowed to nitpick — in Firefox they were aligned but I can see now that in Chrome they aren't. Thanks for passing along!


A nitpick on the linked bio page:

WeddingType, the invitation typography generator, is for non-designer couples looking for a save some money by creating their own invitations.

"...looking for a save..." should probably be "...looking to save..."


Im really impressed to see a person who wont give up and try even if it means to learn something new and not being in the part that they like the most. sidenote: you have inspired me to keep going. I hope you have a bright future in your road.


Hey Tracy, congrats on finally launching! You probably don't remember me, but I was hoping to see a YC11 on that app. Anyway, if you ever need any Django advice, feel free to contact me!


I recognize the name, and due to the power of Gmail, found our convo way back in August. ;)

Alas, not YC but that's not the end of the world. I'm sure the YC folks won't be surprised to see me applying again soon. :P


You definitely should. I was hoping to meet you in this batch but I guess our days were different (I was on the last one). Regardless, good luck!




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: