Interesting read but I was hoping for a bit more insight. I would have liked to see a few low-level examples of their file structure, how they build certain components, or how they utilise certain Sass features.
I was also hoping he would talk more about his thoughts on CSS methodologies, like BEM or OOCSS. The methodology itself is more interesting than the application of it.
I'm working on this browser-based interaction prototyping tool. The goal is to provide a a simple workspace where you can brainstorm and build clickable prototypes quickly and easily.
I agree with most of that. I was actually planning to write a much longer post but ran out of time. Perhaps I'll elaborate with another post next week.
Thanks for the feedback. A lot of people seem to be getting hung up on the sass thing. I'm all for sass, I don't think using 15 CSS classes for margins is the best way to handle this. I just wanted to use a watered down illustration for those who don't yet understand sass. Ideally, this should al be abstracted into variables/mixins/extends.
My main point though, is that I'd like to see us working together to decide what the best approach is, then apply that across the board. I don't see any reason for us to continue doing things slightly differently.
Whether you use CSS, SASS, LESS or any other preprocessor, we should be writing reusable CSS. At the moment, that is not happening across the web.
Seems like a pretty smart idea. Good work. I'm impressed by the speed. I like the tour too. I think the UI is very text-heavy right now, it might benefit from swapping some text for icons.
I'd like to see more of a pitch by way of how this app can help me and why I should be using it. Other than that, good job. Hope it does well.
There is currently no internal way to import your own color scheme. You can always override the CSS with your own colors.
We have lots of extra features planned for the future including extra color schemes, custom color schemes, extra Modulz, web fonts, more customization options etc.
If lots of people start using it, we will add new customization options very soon.
It wouldn't take much work to override the base styles with your own colors. Shoot me an email at colm@modulz.co and I'll walk you through how to do it.
We've decided to drop the prices based on feedback. Thew new prices are $49 and $79. Everyone who has purchased Modulz already will be refunded the difference.
Beautiful design, and with the pricing change it is a great buy. One quick note -- when you click the eye buttons to see details, the old prices still show up.
A landing page is a marketing site. When startups want to launch their products, they build marketing sites to help advertise. Modulz is a collection of HTML website sections that you can customize and piece together to build your marketing site.
What does a landing page have to
do with the Web site? Is
the landing page
one of the pages at the site
with the domain name of the site?
Is the hosting the same as for
the site?
Does the landing page first exist
before the site does,
at the same time the site does,
or only after the site does?
Why isn't a landing page
just one more page I could
have at my site with the
same domain name of my site?
Does the landing page have links
to the other pages of the site?
In what sense is the landing page
"marketing", keywords for
search engines or search engine
optimization (SEO) or something else?
I understand the Web site I'm building
but not landing pages --
trying to learn. I might need
a landing page.
So, if one reason someone
might use my site is to learn
about cooking, then maybe
I will have a landing page
intended just to attract
(via search engines and keywords
about cooking) users interested
in cooking and from that landing
page have a link to my site? In this
case the landing page for cooking
doesn't really tell the user much
about cooking but just directs them
to my site where they can learn more
about cooking?
And if my site is also of interest
to people interested in classical
music, then I might have a
landing page just for
users with that interest?
Is that the idea?
If so, then such a landing page
might have difficulty doing well
in page rank?
The term 'landing page' is overloaded with two different meanings.
Meaning 1, the 'startup community' angle and the one being used for this product, is effectively a "one page website that sells a product". This can be a simple test (put a page up for a product that doesn't exist and see if it converts well), a page about a mobile app, or simply a page to promote a company with no released or conventional products yet. Often this'd be the only page on the site, and the root page at that domain.
Examples: anything from LaunchRock, Hipster's launch.
These landing pages often grow beyond their initial "onepager" design and become gateways into the product itself, blurring with the second interpretation of the term:
The 'marketing community' angle for landing pages is as you describe above. A page that's effectively targeted at an audience to convert them to a sale, sign-up, etc. This can be anything from a page that's keyword optimised for a specific feature-slice of a product, to a splash page that's used in certain campaigns, and the general point is to replace the "first contact" experience with the site with one that's more tailored to the specific user. (So that's why they're used in marketing, when the campaigns have some 'specific user' connotation.)
It's more of a very simple website that you are going to use before you have your actual website built, to gauge interest from potential users.
Usually a 'landing page' consists of a big title / catchphrase, a few points of information about your upcoming product, and a box where you can fill in your email address if you want to subscribe to the mailing list to have more info later. Kind of like what http://launchrock.co/, but less minimalistic I guess.
I was also hoping he would talk more about his thoughts on CSS methodologies, like BEM or OOCSS. The methodology itself is more interesting than the application of it.