Compare commits

...

3 Commits

Author SHA1 Message Date
ray 92acacbba9 update draft 2020-02-15 15:46:52 +00:00
ray 41403c759a update draft 2020-02-15 15:46:47 +00:00
ray 3b12d3f6e0 add plugin links 2020-02-15 14:17:37 +00:00
2 changed files with 55 additions and 32 deletions

View File

@ -11,36 +11,50 @@ externalLink = ""
series = []
+++
Giana Boutique is an online ecommerce store.
Now, this site, is one of the earliest I ever worked upon.
It was my first time using WooCommerce and second time using WordPress to build a site.
It is the site of Giana Boutique, an online ecommerce store.
Done quite some time ago.
Their [website](https://giana.rayelliott.dev/).
First time using WooCommerce and second time using WordPress to build a site.
Uses pre-existing theme.
Nothing special required.
Main customisations were little bits of CSS to tidy some things up -- created child theme based on a theme from ModernThemes called Exchange.
Main customisations were little bits of CSS to tidy some things up -- created child theme based on a theme from [ModernThemes](https://modernthemes.net/) called Exchange.
Now, onto why I used the Exchange theme?
Well, it was pretty much entirely because it was free and I thought it looked okay.
It was free and I felt it was a reasonable looking theme that I could use to get started with setting up a WordPress site to use WooCommerce.
Would I use it again?
Certainly not.
I felt it was difficult to customise, although this may have been at least partly due to my inexperience.
Doesn't really offer much over Storefront, the WooCommerce theme from Automattic???
Doesn't do much to set it above all the other similar looking WooCommerce sites around.
I feel it is perfectly fine for someone wishing to set up a WooCommerce with an acceptable theme quickly with little effort.
Not so good for developers.
Plugins used:
* Contact Form 7.
* Cookie Notice.
* Display Posts.
* [Contact Form 7](https://wordpress.org/plugins/contact-form-7/).
* [Cookie Notice](https://wordpress.org/plugins/cookie-notice/).
* [Display Posts](https://wordpress.org/plugins/display-posts-shortcode/).
Would most likely write own plugin for this now.
* Hustle.
* iThemes Security.
* MC4WP:Mailchimp for WordPress.
* QuickView WooCommerce.
* UpdraftPlus - Backup/Restore
* WooCommerce.
* WP Super Cache.
* [Hustle](https://wordpress.org/plugins/wordpress-popup/).
* [iThemes Security](https://wordpress.org/plugins/better-wp-security/).
* [MC4WP:Mailchimp for WordPress](https://wordpress.org/plugins/mailchimp-for-wp/).
* [QuickView WooCommerce](https://wordpress.org/plugins/quick-view-woocommerce/).
* [UpdraftPlus - Backup/Restore](https://wordpress.org/plugins/updraftplus/).
* [WooCommerce](https://wordpress.org/plugins/woocommerce/).
* [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/).
Would reassess the best plugins available currently, if doing this site now.
Would certainly reassess the best plugins available currently, if doing this site now.
Would definitely use a better theme.
Main reason using this is that it was free.
Would now almost certainly develop a child theme based on Storefront.
Would now almost certainly develop a child theme based on [Storefront](https://woocommerce.com/storefront/#).

View File

@ -17,30 +17,39 @@ Done a while ago.
Their [website](https://stanthams.rayelliott.dev/).
Uses Elementor.
Uses [Elementor](https://elementor.com/).
Was before Gutenberg update.
Nothing particularly special.
Some bits of minor customisation via CSS required and so a child theme, based on OceanWP, is used.
Some bits of minor customisation via CSS required and so a child theme, based on [OceanWP](https://oceanwp.org/), is used.
Reasons for choosing OceanWP:
Reasons for choosing Elementor and OceanWP:
* one
* two
* at least three good reasons
* Cuts development time considerably.
* Flexible.
* Free version can be enough for a lot of sites -- if need additional stuff can either purchase addon plugins or code manually.
* Relatively lightweight compared to other page builders.
Disadvantage is bloat required to cover many use cases, in which not many may be used.
Purpose built design elements will always be leaner and more efficient with cleaner code (if coded correctly of course).
This especially true if using very few components of the chosen parent theme / page builder.
Performance may not be so much of an issue for small sites with few users -- will become much more of an issue the bigger the site.
Can be harder to customise in ways that are not available in the interface -- e.g., CSS specificity problems.
Plugins used (with reasons, and what I would probably use now):
* Contact Form 7.
* Elementor.
* Elementor Addon Elements.
* GDPR Cookie Compliance.
* iThemes Security.
* Ocean Extra.
* UpdraftPlus - Backup/Restore
* WP Fastest Cache.
* WP Mail SMTP.
* [Contact Form 7](https://wordpress.org/plugins/contact-form-7/).
* [Elementor](https://wordpress.org/plugins/elementor/).
* [Elementor Addon Elements](https://wordpress.org/plugins/addon-elements-for-elementor-page-builder/).
For Google Maps integration.
* [GDPR Cookie Compliance](https://wordpress.org/plugins/gdpr-cookie-compliance/).
* [iThemes Security](https://wordpress.org/plugins/better-wp-security/).
* [Ocean Extra](https://wordpress.org/plugins/ocean-extra/).
* [UpdraftPlus - Backup/Restore](https://wordpress.org/plugins/updraftplus/).
* [WP Fastest Cache](https://wordpress.org/plugins/wp-fastest-cache/).
* [WP Mail SMTP](https://wordpress.org/plugins/wp-mail-smtp/).
Always a good idea to test speed of site after adding a plugin, especially if not used before.
Not much to say - a pretty basic brochure site.
The primary purpose is to allow users to discover/get more information about the firm.