What's the best way for my client to add pictures to website - html

I am working with an artist to make her personal website. She would like to sell her artwork from the website. The issue is, she would like to be able to add, remove and price the artwork herself. She would also like to use paypal as the payment method.
Obviously design and coding is easy for me, that's all static. I am not sure however, what the best method would be to set up a way for her to add artwork herself.
I know there are some open source e-commerce sites (magento, zencart ect.) but I have never used these and feel they might be a bit overkill for a simple art site. Is there something else really simple I should use?
Any general thoughts or suggestions are greatly appreciated.
Thanks!

Use a ecommerce site, its the obvious choice if she wants to sell stuff.
Zencart isn't as overkill as you think - it allows you to remove all the bits you don't want from the site using its admin gui; so you keep just the categories and the cart sections.
It also has options (IIRC, but I may be thinking of a different one, like CRELoaded) that provide for pay-and-download links.
Certainly, reusing ecommerce code will be a lot easier than writing your own.

Always use an existing framework for commercial sites. It's just too easy to make a silly mistake which allows hackers to take over control of the server.

I recently found a really cool (and free) method of using php and javascript to upload, resize thumbnails, and display all uploaded content from the folder.
Taking this code from a free tutorial and pairing it with a customized javascript gallery looks really slick (used it for my own photography site as well as a few clients who loved it).
Very soon I will be combining it with a site for a historical golf course architect... a gentleman has come to me with hundreds of pictures he would like to store on the web, but he wants the capability to upload himself at any time. The trick is this: If your client artist wants to price it herself, the gallery use would require her to be able to navigate the basic html framework enough to change the descriptions which appear beneath all of the pictures as she adds/changes them.
If you want to get started on your own check out some of the tutorials here:
http://net.tutsplus.com/category/videos/screencasts/page/3/
as well as finding a gallery that you both like for displaying the photos in an attractive way... Let me know if you want anything else from me :)

Why don't you create a simple administration panel where s/he can add, remove and price the artwork? Do you know any programming languages? PHP?

Virtuemart is based Joomla CMS , very easy to set up, an Open Source eCommerce solution. You might find a lot of free extensions of Joomla for photo gallery and other things.

Gallery2 is an excellent web-gallery software, suitable for presenting images, videos, and audio.
It has a "CheckOut with PayPal" plugin.
Gallery2 will require some time to configure, it is unlikely that you will use it "as is" after install.
Gallery2 is easily embeddable - provided minimal PHP skills, and good HTML/CSS skills, one can make it fit inside any design (maybe except for the grid-like thumbnails layout, which I guess is possible but harder than average).

Related

How do I build the "To add content" page of a responsive website

Context: Ok so I am building a website for a friend. Hes a designer with a high need to daily include his projects (images and text).
Problem:
Ok so I know pretty much how to code in html/css/javascript a front end responsive website, that is the easy part for me, the hard one is the content page. I've never done it so I don't know the best way.
A page that he goes daily put a new project, new images, formatted text (A like a blog). But since he doesn't know anything about coding and front end, it has to be simple enough for him to understand.
Resources: I made several searches and found some websites that allow custom templates with content, one of them standing is wordPress (haven't used it for years). I am currently abusing tumblr for that matter, but their support is quite bad. Should I use one, should I buy a host like bluehost and create my self one, what you guys recommend? I tried google it but perhaps I am not doing it the right way since I am not finding any answer to my problem.
Look, you've come to a programming website, so the most common suggestion you'll get here, and the option I myself recommend is:
MAKE IT YOURSELF!
It really is a fun and very educational experience.
There are many, many ways to do this. In general you'll want to have a front end that communicates with a back end API.
For the front end, there are a lot of options. From templating engines like Jekyll, to MVC frameworks like Laravel, to full fledged high level abstractions like Angular and React, which are admitedly harder to learn but so, so robust, and useful once you've figured them out.
The selection of tools you can use to make the API that supports the website is just as rich. There is ASP.NET for C# (which some people use for the front end as well but I wouldn't), there is Node.JS for JavaScript, with a myriad of libraries and packages to get you started. Flask is a popular option for Python. The list goes on and on.
Oh and dont forget about Ruby on Rails.
As for the interface which your friend will use to add their work, turning all that complicated back end into a simple, easy to use interface is a fundamental part of UX design and, IMHO, quite satisfying once you get it right. Make it sleek and, most of all, intuitive. One shouldn't have to be taught how to use it. It should be apparent from the first time they open the page. You should always ask for their feedback as you are developing it. Some even opt to create mock ups of the interface, in order to get feedback on both its aesthetics and its intuitiveness before a single line of code has been written.
Now, regarding how you'll actually do it, the answer really depends on the tools you opt to use. In general, you'll want to read up on things like the MVC pattern, or React's component architecture. The former is something you'll come across on a wide variety of platforms. The latter is mostly React specific, but in my opinion, understanding how to properly build a website using component architecture means you're in the right mindset, something that will help you no matter how you choose to build it.
All that being said...
Web development is complicated. Creating dynamic websites is a much larger undertaking that designing a static page, or even making an SPA. Though I do wholeheartedly recommend you do it at some point, starting with your friend's website might not be the best idea. Or, you may simply not have the time to sift through all your options, figure out which is best for you, begin the learning process etc.
In that case, there are plenty of publishing frameworks and tool sets to choose from. Wordpress has become very popular in the recent years, and templates and plugins for it are abundant. Alternatives like Medium and Ghost have also gained some traction.
There are plenty of commercial CMS type frameworks. One I have heard good things about is ExpressionEngine. However, I cannot speak for it with certainty.
If you are looking for a website builder, there are also plenty of options out there such as Weebly, Wix, as well as Squarespace. Google sites is a relative newcomer in that department, but seems promising.
So, in summary,
I wholeheartedly recommend building it from scratch. There are many, many languages, frameworks, and tools out there you can choose from, each with its own patterns, best practices and idiosyncrasies. If you lack the time, or simply don't feel like going through that process of building a dynamic website from scratch, you can use one of many tools available. However, that wouldn't be nearly as much fun, and would likely produce an inferior result.

How to allow clients to manage their website?

I do small websites for local companies. All I know is HTML5 and CSS3, no JavaScript, no PHP.
I have this client who wants me to make a website for his coffee shop. All good so far. I have an idea for a beautiful responsive design which will get his coffee shop a lot of fame.
The problem:
The guy wants to be able to manage his website, meaning: he wants to add a photo if he needs to, or even some text on a particular page. He doesn't want to depend on me so he wants to do it by himself. The problem is that I can't teach him HTML so he would download the HTML file and write the code for the desired thing.. I need to do beautiful websites for my portfolio.
No Wordpress: I don't like Wordpress because it's limited so I can't be creative with the design. I thought of that as being the only solution requiring his needs.
I'm willing to learn more: if there is a solution that I could implement in one month or two, I will do this and learn what is needed, but can't learn PHP in two months.
Any advice?
You might find that CushyCMS does what you want. From the site:
Allow clients to safely edit content
No software to install, no programming required
Takes just a few minutes to setup
Define exactly which parts of the page can be changed
Produces standards compliant, search engine friendly content
From experience, a couple of downsides:
No choice of editor
You have to add pages that can be edited - the client cannot create new pages.

Website Update Tool for a Non-Programmer

I work with my professor to implement web-based decision support tools. I am a seasoned programmer, and am at ease with the various web technologies we use. However, my professor isn't, and he usually has to rely upon me to do even the most basic tasks like adding publications and presentations to an existing list. However, he now wants to be able to do these basic tasks by himself since we both feel it will be more efficient that way, and to leave the hard-core tool implementation for me.
He suggested that we purchase Dreamweaver to achieve this. However, I do not have much experience with Dreamweaver since I prefer to work with bare HTML, CSS etc., and Emacs and Eclipse have filled these needs very well for me.
What do you think we should do? Do you think Dreamweaver will be a good tool for this? If not, is there something else we should look at? How far will he be able to get along without knowing much HTML? Do you think I should give him a crash course in HTML? Feel free to opine!
NOTE: The website is not based on any CMS; it is completely bred in-house. We use HTML, CSS, PHP, and JavaScript. However, my professor will most likely dealing only with HTML (no CSS etc.)
For these types, I often (while cringing) reach for WordPress.
If your customers can make a Facebook post, they can edit content in WordPress. Just stay on top of the updates for it, as exploits for WordPress are found with very high frequency. Even with this maintenance, it will still be easier than doing updates for them.
It shouldn't be too hard to convert your site over to a template that you can use within WordPress. If you can't, you can easily embed content from WordPress into your site via feeds, but there is a performance penalty for this.
If you build the site with Dreamweaver, Adobe Contribute is a good option that is pretty much WYSIWYG (what you see is what you get), and it is designed to work with Dreamweaver templates.
Basically, it helps prevent novices from screwing up the site too badly by locking users out of template areas (the areas that are supposed to stay the same from page to page, such as navigation).

help for beginner at web dev/design

I was wondering, how does a web designer/developer start out in his buisness with nothing to show (in the sense of a portfolio,) and only his word to show he does good work? How are those people supposed to get buisness?
If you don't have a portfolio and want business, it is best to make your own site look incredible. Show people what you can do with your own site. Once your site is incredible, network with companies in your area, friends, family and offer your services cheap if they'll let you use their site as a portfolio example.
Once your portfolio is up, referrals should be coming in and folks seeing your site should be even more interested.
EDIT Per Martin's request, when you build your own site, please don't grab a run of the mill template like every other web developer out there. If you do take a template, make it yours, modify the heck out of it.
The best thing you can do for an empty portfolio is personal projects. I was hired for my first job out of college because I had created a website for my personal business. I was able to show that I had talent because I was in charge the entire site. You shouldn't ever rely on "your word" to get you jobs.
If you need ideas for a personal project, you can see if any friends/family need help, but that can be limiting. Still, it's another project to put in your portfolio to help you get more professional work.
I'd also recommend reading up on online articles dealing with starting a business. Some recommended reading:
alistapart.com/articles/startingabusiness/
alistapart.com/articles/business1/
freelanceswitch.com/general/101-essential-freelancing-resources/
Start by doing projects for people you know and work to create a small selection of work that reflects your current skill set. At the beginning, you may find that your talents are evolving so rapidly that your previous work doesn't reflect your current abilities — that's fine. Try to create a narrative on your portfolio site that shows people your progress and how each piece of work has built on the next.
Your portfolio site should demonstrate both technical and aesthetic skills. If you're an artist or industrial designer, you want your site to fade to the background and push your work forwards. Being a web designer means that your actual site is as important as the work featured on it. Your code should be clean and organized (you don't need to be a standardista, but be tidy).
If there's one skill you should really have before you start to work for clients, it's a sense of typography. You don't want to contribute to the ever-expanding world of poorly set websites.
Good luck.
I completely agree with all of the above - if you can demonstrate your capabilities with some sample work, that will count for far more than a resume in the end. Most of my work has come through people seeing my other work, not knowing my employment history.
Get yourself a domain, build a bunch of sample home pages, create a bunch of sub directories on your site. Make one for a small business, then maybe e-commerce, then maybe a blog, make a few different example scenarios of the types of sites that you would likely be asked to do, I have seen some people design mock home pages in Photoshop and just show them all as clickable JPEGS, that can be quick yes, although I recommend using all live pages on your site to show what interactive things you can do. Up to you, depending how quick you want it up and how important it is to you. I was paid $2500 to make this blog by a guy who was just completely web illiterate. I didn't quote that price mind you, he offered it to me out of nowhere after looking at a gallery of WP templates I had up as "possible" themes for a customer's blog. Sometimes, you are just in the right place at the right time. Best of luck to you.
Do side projects and see if you can build friends' websites (for free, or if they'll pay you, cool). Do whatever you can to demonstrate your abilities. Building a personal site doesn't hurt either.
I'd recommend making an online portfolio, if not to display past projects at least to post your resume and basically a cover letter. You can get a lot of free css templates if you're not comfortable with designing your own.
I'm building a site for my wife and a friend of mine from high school. If you're not getting work, its just the economy. I've been looking for work since March. It's tough.
Just keep at it, and it'll pay off.
You need to create a professional looking site. If you are a developer I also suggest that you start a small open source project (or a big one if you are so inclinded). It doesn't have to be any thing major...a widget or library. Something useful for people to play with. On your website show examples of your work. If you have no examples then sign up for accounts on getafreelancer.com, elance.com, scriptlance.com, guru.com, rentacoder.com and any of the other freelance style sites. Build up your portfolio by doing cheap work...but not work that is cheap! Create a resume and post it somewhere for google to find. Create a linkedin, facebook, and myspace account. Make it easy for people to find you and for people to find your work. Write about the things that you are interested in either by way of a personal blog or by posting articles to a site that already gets lots of traffic. Speak at small user groups or conferences to get your name out.
There is a lot you can do it is just a matter of how badly you want to succeed. Programming or designing is just as much a business as selling physical products. It is all about how much you saturate a given space with good words about your services. Marketing!

REALLY Simple Website--How Basic Can You Go?

Although I've done programming, I'm not a programmer. I've recently agreed to coordinate getting a Website up for a club. The resources are--me, who has done Web content maintenance (putting content into HTML and ColdFusion templates via a gatekeeper to the site itself; doing simple HTML and XML coding); a serious Web developer who does database programming, ColdFusion, etc., and talks way over the heads of the rest of us; two designers who use Dreamweaver; the guy who created the original (and now badly broken) site in Front Page and wants to use Expression Web; and assorted other club members who are even less technically inclined.
What we need up first is some text and graphics (a gorgeous design has been created in Dreamweaver), some links (including to existing PDF newsletters for download), and maybe hooking up an existing Blogspot blog. Later (or earlier if it's not hard), we may add mouseover menus to the links, a gallery, a calendar, a few Mapquest hotlinks, and so on.
My question--First, is there any real problem with sticking with HTML and jpegs for the initial site? Second, for the "later" part of the site development, what's the simplest we can go with? Third, are there costs in doing this the simple way that will make us regret it down the road? Also, is there a good site/resource where I can learn more about this from a newbie perspective?
­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­
If you don't require any dynamic content, heck, if you don't plan on editing the content more than once a week, I'd say stick to basic HTML.
Later, you'd probably want a basic, no-fuss and easily installable CMS. The brand really depends on the platform (most likely PHP/Rails/ASP), but most of them can be found by typing " CMS" into Google. Try prefixing it with "free" or "open source" if you want.
I'm pretty sure you can do all this for absolutely free. Most PHP and Ruby CMS's are free and web hosting is free/extremely cheap if you're not demanding.
And last/best tip: Find someone who has done this before, preferably more than once. He'll probably set you up so you never have to look at anything more complicated than a WYSIWYG editor.
Plain old HTML is fine, just as long as you don't use tags like blink and marquee.
I personally love tools like CityDesk.
And I'm not just plugging Joel. (There are others out there in this class I'm sure.) The point is they make making a static website very easy:
The structure is just a filesystem structure
pages have templates to consolidate formatting
all resources are contained in one file
easy and fast Preview and Publish functions
For a dynamic collaborative site, I would just install one of many open source CMSs available on shared hosting sites.
If you're familiar with html/javascript basics I'd look into a CMS - wordpress, drupal, joomla, nuke, etc. All of these are free. Very often your web hosting company will install one of these by default which takes all of the hard part out of your hands. Next is just learning to customize the system and there's tons of docs out there for any of those systems.
All that being said there is noting wrong with good old fashioned html.
In addition to some of the great content management systems already mentioned, consider cms made simple.
It makes it very easy to turn a static site into a content managed site (which sounds like exactly what you might need to do in the future), and the admin area is very easy to use. Our clients have found it much simpler to use than the likes of Joomla.
It's also free and open source.
Good luck!
There's no reason to not go with plain old HTML and JPGs if you don't know any server side scripting languages. Also, once you want to get more advanced, most cheap hosting services have tools that can be installed with one click, and provide things like blogs, photo galleries, bulletin boards (PHPBB), and even content management tools like Joomla.
I had the same problem myself, I was just looking for something really easy to smash together a website quickly. First I went with just plain old HTML, but then I realised a simple CMS would be better.
I went for Wordpress. Wordpress is mostly known as a blogging platform, but in my opinion it is really great as a deadly simple CMS as well.
why not simply use Google pages?
Here is an example of a website I did, takes about 2 hours, easy to maintain (not that I do (-: ) and FREE.
I think that suggesting you mess with HTML for what you need is crazy!
Plain HTML is great, gives you the most control. If you want to make updating a bit easier though, you could use SSI. Most servers have this enabled. It basically let's you attach one file to many pages.
For example, you could have your menu in navigation.html and every page would include this file. That way you wouldn't have to update this one file on every page each time you need to update.
<!--#include virtual="navigation.html" -->
I agree with the other commenters that a CMS might be useful to you, however as I see it, probably a solution like Webby might do it for you. It generates plain HTML pages based on Templates. Think about it as a "webpage preprocessor" which outputs plain HTML files. It has most of the advantages of using a server-based CMS, but without a lot of load on the server, and making it easy for you to change stuff on any of the templates you might use.
It's fine
Rails (or purchase / use a CMS)
Not unless you start becoming crazy-popular
It really depends on what you go with for 2. Rails has a plethora of tutorials on the net and any product you go with will have its own community etc.
To be perfectly honest though, if the dynamic part is someone elses blog and you move the gallery out into flikr you may find that you can actually live with large parts of it being static HTML for a very long time.
If a to Implement a website With User Profiles/Logins, Extensions, Gallery's etc s a Newbi then a CMS like Joomla, Etc are good , but Else if you presently have only Static Content then Its good to go with Good Old HTML, About JPEG , I though Presently Its better to use PNG or GIF as its Less Bulky.
Also About you Query About Shifting to Server Scripts , When you have Database Driven Material or When you have Other Things that Require Advanced Prog Languages , Just use PHP Scripts inside PHP , and Rename teh File as a PHP, Thats IT, No Loss to you HTML Data.....
Do Go Ahead and Launch you Site ......
Dude, you're talking about HTML, obviously you'll be styling your content with CSS. Wait till you run into IE issues and god forbid your client wants ie6 compatibility.
Go with the HTML for now, I'm sure you guys will hack it through. Our prayers are with you.
Personally, I'd never use JPEG images on a website, mainly because of three reasons:
JPEGs often contains artifacts.
Quality is often proportional
with filesize.
Does not support
alpha transparency.
That said, I'd recommend you to use PNGs for images since it's lossless and a 24-bit palette (meaning full colors + alpha transparency). The only quirk is that IE6 and below does not support native alpha for PNGs, however this could be resolved by running a javascript which would fix this issue.
As for designing a website, there's both pros and cons for this. I suggest you read through:
37 Signal's Why We Skip Photoshop
Jeff Croft's Why We Don't Skip Photoshop
As for newbie resources, I'd recommend you flip through the pages at W3 Schools.