I am trying to change the layout and customize the pre-configured Geometrixx-Gov site in AEM 6. For example, I would like to change the blue color in the header
Also, I would like to change the text of All Applications to something else I want.
Questions
What is the best way to make these changes?
Once I make my changes, is there a way to somehow take/package my changes and deploy them to an instance of AEM not running on my local computer?
When I try to edit things, I can change the text around in the body of the site but can't seem to change the text around in the header
1- To change the menu, I think you have to change the page title or the page navigation title, you probably have a page called "All Applications".
2- To change the color, you have to edit the CSS in the client libs which are somewhere under /etc/clientlibs/{your_app}
3- You can package the application using the package manager, make sure you include the /apps/{your_app}, /etc/clientlibs/{your_app}, /etc/designs/{your_app}, /content/{your_app}, those are basic folders, you may need other files or paths in your filters, make sure all dependencies are respected.
Related
Recently started work on a BigCommerce project and on the homepage I want to have a theme area where normal site admin users can upload their own images based on holidays (Xmas, halloween etc) in the theme editor.
I know how to add in some custom elements in the theme editor using the Schema and Config files (headings, text, font colours etc), and how to reference them in the homepage. I'm also fine with referencing set images in the assets folder which aren't going to change, and manually coding references to them.
However I can't quite seem to work out how to add a custom image upload to the theme editor, or how to reference it in a page. Can't seem to find any answers in the Stencil documentation or usual Google searches etc either.
The Stencil Theme Editor currently only supports the file upload data type in the Optimized One-Page Checkout customization settings, but there are a couple of possible workarounds to allow the user to upload their custom background image and then reference it in Theme Editor settings:
One option would be to have the user upload their image to WebDAV, making sure that their image followed a naming convention that you specified. For example, the Halloween image could be required to have the file name halloween.png. You could map that value to a Theme Editor dropdown setting for Holiday Background>Halloween.
Another solution might be to have the user upload their image to WebDAV as mentioned above, but instead of a dropdown menu, you could have the user type their file's name into a text input setting in the Theme Editor. Keep in mind though that there's a 64 character limit for input values.
Hope this helps!
There are 4 ways to get images into the BigCommerce store.
You can:
Upload into the content folder through webdav. Then the images would be referenced like url.com/content/image.jpg. This does require a webdav connection and while everything does point you to using file managers like cyberduck, you can actually map a drive to a network resource to make this super easy. This mean you can create a z drive that is actually your bigcommerce content upload through webdav. It's pretty easy to set up and for customers to use. The drawback is that these files do not get put on a CDN so there's a little loss of performance.
Upload into the theme's images folders. This is complex and would require your client to figure out the stencil local dev connection and push versions up to their store. This would allow the images to be CDN'd but is super complex and your clients won't figure it out... It could also expose you to some long-term version control issues as they may be overwriting you or vice versa.
You can use the media manager to upload images. If you're referring to them in code, an easy trick is when your clients want to replace an image, to delete it and upload a new one with the exact same name... then the reference doesn't break. This is the easiest way to deal with site-wide issues from the client-side. Images are CDN'd this way as well.
You can consider using the marketing banner function for semi-temporary marketing messages. This is what it is made for, the images will be CDN'd and it's full GUI with no techy connections for your clients to figure out. This is perfect for banners that span a single page, but I don't think there is currently a side-wide setting for locations.
Please I need some guidelines (or link of tutorials) in creating Joomla (3 - 3.5) website with the purchased template design. I wonder how professionals with experience are solving my doubts in practice.
Do you recommend the installation of the purchased blank template with a single installation and configuration of modules and components or installation of template with demo examples (Quickstart)? I know the differences but I was wondering how you are doing.
Till now I've almost always used the Quickstart installation.
I wonder if you clone the main menu (and other navigation and modules) and than you rename a copy for your needs and you change the content or you delete all navigation items except Home and than you are re-creating items according to your needs.
I'm not sure if I can copy the main menu or I copy only his necessary items and than delete overage of template.
It happens to me sometimes if I click on some of category it leads me to the main menu from original item, not to the desired custom copy, even though the path is set (the default items). Therefore, I am not sure which is better... copy main menu and items or to delete all navigation and content of the Quickstart installation and form my own navigation, content and modules.
In short, how to sort out all unnecessary items, and those that I am using should I copy and modify, modify existing, or delete all and make my own needed items.
I believe you will know my concerns.
Thank you and regards,
John
I have created several websites in Joomla with blank template and also with quickstart package.
Advantages with Blank Template
You will get the core theme without any unnecessary content and
basic modules and plugins. You dont have to delete any
contents/articles later.
You will be having authority to place modules at your desired positions. To check the modules position at the frontend simply do this http://example.com/?tp=1.
Disadvantage of Blank Template
There are some module style settings embedded in quickstart package that you wont be able to set yourself without going through full documentation. So sometimes your menu seems distorted.
Disadvantage of Quickstart Package
Deleteing unnecessary articles, removing unnecessary modules is a big headache.
Database size unnecessarily increases.
Steps I follow
I create a quickstart package in localhost and create a blank site with blank template in live site. Whatever settings I need I copy from the local website so that I am saved from removing unnecessary contents from live site. Also sometimes deleting some contents give rise to some other issues. Its better t go with a Blank template.
This is my first project on website development using Joomla. I am trying to make a dashboard implementation. My problem is that whenever I edit my script in article using source tags, the changes are not reflected on my site immediately. I have even tried restarting my Wamp server, but in vain. Any tips that I should follow?
Thanks.
Depending on your Joomla-Version there are different options to check to suppress stripping or filtering of tags like <script> for the frontend. Here are some hints:
First of all your tags could be filtered out client-sided depending on the editor you selected. If you use the standard TinyMCE e.g. go to Extensions - Plugins - TinyMCE where you will find a list of prohibited Elements which may include script. Be exactly sure what you do though, always check who should be allowed to enter script tags in an article, this is almost always a major security risk if anybody else like you as an administrator has the right to use them. So another option could be to just set the editor for your administrator/author accout to plain text and leave TinyMCE untouched.
Another filtering is done server-sided by joomla itself which can be controlled in "Global Configuration" -> "Text filter". After a standard installation all groups will use Default Black List filtering which includes removing script tags. Here you could define "No Filtering" for the Super User group e.g.
Again, all this depends on your Joomla-Version (my examples are referring to 2.5) and are hints to get around the issue but without knowing your security concept.
Plone 4.1.
What would be the easiest way to make TinyMCE image picker dialog point to a site default folder (/image-bank) instead of current folder?
This + folder display as album would provide a rudimentary image bank support for Plone easily.
I'd hope to achieve this feature for
All Plone out of the box content types (ATContentTypes)
My custom AT content types
MY custom Dexterity content types
Portlet editor WYSIWYG (is it zope.formlib?)
If it's difficult to edit Python code all over the places, it's accetable just to a Javascript snippet patching TinyMCE settings on the client side.
Mikko: What a coincidence. I'm just trying to achieve the same thing. I managed to create a more specific adapter than `Products/TinyMCE/adapters/Upload/Upload`.
This new adapter changes the upload folder (by setting self.context) to the central-images-folder and then updates radio button listing (and image preview) with the central-folder images (and just uploaded image). This is done by defining an uploadOk method inside the new adapter.
However, to change the initial folder, I think the only way is to customize ploneimage.html.pt or ploneimage.js inside the skins/tinymce/plugins/ploneimage folder. But changing any of these two large files (which might change in the future), could make new releases of TinyMCE not to work with your changes. So you will be forced to re-customize them again.
My idea (which I already emailed this morning to Four Digits) is to provide this feature with TinyMCE out-of-the-box, via a configuration option. This way the package files would be always aware of this feature and future changes won't harm this new functionality.
I have a piece of software, a winform program developed in c#, that has several different themes. But if one of my team members wants to change the theme they have to ask me, then i have to change it, recompile and send it. Instead I wish for them to be able to freely change the theme. It is like changing the theme in Firefox, etc. Any ideas on how to begin coding such a piece of software?
This seems like a good thing to put into your config file. Have a method that checks the config file for a theme setting. And change the theme based on that. I would also recommend having a default theme in case the config file fails to specify one.
Alternatively, this could go into the admin / settings / options portion of the application. Where you could save it with your other settings. In the registry, or app settings folder, etc.