on 04-04-201704:02 AM - last edited on 04-04-201708:33 AM by Adam
just had an idea that might be worth considering in order to boost contributions to the community.
The administrators of this community page could reward members who post useful or insightful responses, positive behavior, solutions to problems, educational comments, etc, with credit/points that can be spent on Apps (from the Weebly App section) for their websites.
I think it should be admin controlled rather than being tied to Kudos or post numbers.
on 06-18-201611:47 AM - last edited on 05-19-201707:25 PM by Queso
It would be so cool if we can share each other's website names so we can find more inspiration from each other as well as take ideas and comment on what looks good and what doesn't. It is important to get feedback from people so we can improve and enhance our websites' look and feel. So for instance, I place my website's name and people vote on who has the highest ranking for their site's visual appeal. I think that will leverage our ways of how to create great-looking websites that are attracting for visitors . Vote if you find this topic interesting!
on 02-17-201712:45 PM - last edited on 02-19-201708:11 AM by Adam
It's actually kind of useless as it is because the purpose of quoting as it pertains to forums is to shift the context from the main idea. Quoting the main idea is an extremely rare necesity, grammatically speaking.
The function should targe other users within the thread so that we can add to it or refernce it to help describe our own thought.
People with use this to repond directly to another user in conjunction with @Mention which is considered improper use but tolerated on most forums. Strict discouragement goes .a long way especially on Weebly.
byAngelXAces02-12-201701:12 AM - edited 02-17-201712:17 PM
We need some more options here in the community editor. It's difficult to write in the community which is in large part why I haven't done so as often. I like to post here, it's a good community. Writing with the current options is just so limiting. Maybe the solution is to have a markdown
I propose that an advanced option be to enable markdown.
some things are missing with what we have already as well
"Spoiler" should be editable because this is useful for more than just spoilers
<--line numbers are nice to have for code. Also, it would make a lot more sense if this had the same styles as Edit HTML/CSS with the JS that text elements change color for easy reading.
EDIT: Syntax Highlighting! that's what I was looking for. I must admit, Monokai was an awesome choice. I never changed highlight options from default until post-weebly.
Tool Tips would also be nice. They sort of happen on links but that's barely a cheap knock off.
Fonts! You have the whole Google Font API at your disposal. I don't understand why we have such a limited range. Sure. fonts increase load time among other things. We don't need the entire library. Since the API lets you make a specific selection, a few extra choices would be nice.
EDIT: Why not add the entire library? We'll pick the font's that will be used on our site from a menu (preferably a dropdow with the font applied to the name, that last part is obnoxious when it's not done) and the rest won' be loaded in the production.
Color: Color wheel instead of swatches
ABC Check. This thing locks you in. If you make a manual correction it doesn't register and will still show as incorrect. Difficult to make manual corrections when the correct option isn't listed.
on 05-02-201704:23 AM - last edited on 05-02-201706:42 AM by Adam
It seems to me that a LOT of the suggestions relate to ecommerce.
Would it not be a good idea - and more efficient and effdective for developers and consumers alike - to seperate out ideas about how to improve the ecommerce / store operation from notions about how to improve other aspects of the website webware?
on 01-09-201707:25 AM - last edited on 01-09-201708:07 AM by Adam
I did my pre-search using what's in my idea labels
Weebly prides itself on it's ability to facilitate e Commerce business in a relatively simple, user friendly environment, does it not? Well, as they should, in my opinion, but there's always more work to be done and opportunity to grow. I think this is something that will be be an inevitability. For some, business owners are the target market.
I'm not suggesting turning the community into a shopping mall. You'll see a post here and there of someone who need some, "I don't want a walk through just do it for me," kind of help help and they offer compensation. Though it's not really encouraged to do that, if it's discouraged its hardly noticeable and really shouldn't be. I think a section for something similar to a classified section for help wanted or who's available.
Weebly would be in a good place because of all the options it's created. Make dev/designer (writers and other freelance can should be able to work with one or the other) accounts the only ones that can respond to these and then block their ability to accept real payment leaving only the testing capabilities intact. Make a big notice that It is against weebly policy to facilitate payment between members for services rendered as well as some of the dangers that come with it Yes, people will jump on another account to take the payments or use a donation box to collect. At that point they're showing they are fully aware of the policy and actively trying to get around it. Most people with just get a paypal real quick (if they don't have one already for their checkout) and do it there but this way since the compensation wasn't exchanged on Weebly, the only thing they could be blamed for is owning the environment in which two people met.
Or they could extend their liability insurance to include potential hazards that come along with something like this which they may not have to do because there's a good chance that it already does.
Honestly, if your contribution to ideas is, "can't, liability issues" Then don't bother. The fact is...
that you don't know what kind of coverage a business has or if an idea supports others currently in question making coverage extension a viable option. The, "Liability," response is only valid from a member of the company who holds a position to know the policy AND can speak on the company's behalf (and the only people I want to hear that from). Anyone else just thinks they look smarter than the person with the idea because they found a theory as to why it won't work and they state it as fact (hey, I was guilty of it too before I put some thought into it). Most people know when there's risk, they ask because it might be worth finding a cost effective safety net.
Every rough draft falls short. You look smart when you find a way to make things work
on 01-03-201704:12 PM - last edited on 01-04-201708:59 AM by Adam
display production stage of upcoming features
display each function it provides
Forum for allowing discussion: This doesn't make it a democracy and I'm not suggesting that we necessarily get to vote on different things during the process. I recognize that once it's already in production its little late to start editing the game plan. But in production, I also know that things don't always go as expected and keeping an eye on things that we discuss will give you a pool of ideas to draw from when mid-production decisions have to be made and you don't know off the top of your head what directionis going to have the best reaction. If the Community chatter regarding some unfortunate customer service experiences have shown anything it's that the community is quite vocal. If you gave us this forum section We’ll probably answer a lot of questions without you even having to ask much less create surveys/questionnaires or take a voted if it ever came to it.
on 01-03-201703:49 PM - last edited on 01-04-201709:00 AM by Adam
This is something just for moderators but would help us on our side of the screen. It would help us see what is going on so when we search for suggestions, we don't suggest things that might be in the works as an option in a feature currently under production,
This is somewhat self explainatory. Instead of deleting duplicate requests it would be really sleak to have a system to merge multiple requests. Comments made in response to a different request than the one featured would have a link added to show a lightbox with the text of the request they responded to.
It would also help in cases like my previous suggest, where if accepted, would cater to a few other requests so they could be merged together as a batch of feature being accepted and satisfied while keeping it under a single project. This way everything wil still show up in searches to cut down on duplicate requests but it would also show that the project is being considered and give a clue as to the direction it's headed in.