http://purplehazetheme.weebly.com/ http://collectiontheme.weebly.com/
http://purplehazetheme.weebly.com/ http://collectiontheme.weebly.com/
[1]http://www.slate.com/articles/technology/technology/2011/08/...
Here are a few example sites:
We salt and hash all passwords using a variable-cost bcrypt implementation.
But the solution I've favored is hashing the user's password on the client with a hash that provides enough significant bits that your key derivation on the server is not weakened. This way you get the benefit of not needing to deal with differences in transmission size and the user's plaintext password is never exposed to any listener (regardless of whether the connection is secure, or believed to be secure).
1. It's monolingual.
2. It's mono-currency.
3. It has a hidden schedule of fees like ripoff domain name registration with unwanted extra features, support for requisite features like SSL support (duh!) and shipping calculations.
4. It's not clear for which jurisdictions/product types you support tax calculations, or whether multi-party split revenue models are supported (eg. for dropship scenarios, digital product retailing eg. online content). Dynamic pricing also looks like it's not supported .. common digital retailing operations might use this, eg. for Hollywood content.
5. It's unclear to me based in China whether or not I can receive payments through your system.
6. It has no support for communities (eg. hosted forums) which despite not being Web2.0 are actually pretty cool for building customers for ecommerce operations.
7. The actual build bit seems almost completely disconnected from the plan bit, which mostly talks in gross generalities about the build bit without making you do it. The link between the two could be improved.
8. Dogecoin support?
Congrats on getting rich.
I tried your feature request voting website but it didn't seem like my suggestions showed up at all after submitting them.
There are plenty of people using Weebly for personal projects or educational purposes (teachers, professors, students), but our core focus is entrepreneurs.
I don't want to be in the web site or CMS business. I've sufficient metadata from my application to export enough information to generate a single page website for these clients. How can I send them your way?
The app itself is very nice.
Or maybe that just isn't a concern because so far nothing like that exists?
I like the idea of Weebly, I think building web software should be based on components for the programmers and usability for users. But I don't see how a closed platform stays relevant.
I think its just that most web developers still don't understand widgets.
I'd love to know what's your take on third party integrations with Weebly - are you guys working on an App Store or this is only doable through partnerships? If only partnerships, what's the best way reach out?
We're a platform offering customisable widgets, currently rebranding as Widgetic. I played with some widgets here: http://vuzum.weebly.com. Oana Calugar (at Weebly) has reached out to us a while ago and I agree with her, we do fit as a glove. :-)
Went to sign up but sign up page was on a non SSL page. I don't like sending passwords in the clear.
Would love to add some buttons to page and what not.