I am new to Adobe cq5. Went through many online blogs and tutorials but could not get much. Can any one describe a way how I can create an HTML page from Adobe Illustrator (.ai) file containing images and font, required for web page.
I have installed CQ5 instance on my system but don't know how to work with AI files.
Thanks in advance.
Simply put you can't. For starters CQ5 is a modular CMS in that you drag in various components to build a page up. You have page templates that contain the basics of a page such as the header and footer but you don't create entire pages in one go so to speak. You build them up from reusable components.
Second you can't automatically convert an illustrator file to a webpage, you need a web developer to translate it into HTML, Javascript, JSP's and CSS. Also CQ5 can require quite a bit of back end coding in Java so that is something to keep in mind.
CQ5 is really an enterprise CMS so depending on your needs it might be worth taking a look at something like Wordpress although you still wont be able to simply upload an AI file.
You can use Adobe Illustrator (.ai) to build graphics for use within an AEM web site. You place those graphics in the the AEM DAM (Digial Asset Manager). You can then use those assets. For example:
1 - reference them in web pages.
2 - build components that use them. See http://scottsdigitalcommunity.blogspot.ca/2013/04/creating-gallery-components-that.html
As a new user, I recommend that you read this: http://helpx.adobe.com/experience-manager/using/onboardAEM.html.
From that link - you will find a section about creating your first AEM site. Its a must to walk through to learn AEM.
You will also find other articles that will show you how to perform tasks - like creating OSGi services.
Related
We have several Drupal 6 sites. On most of the sites we will have some content editors, who will optimally log into a dev/test site and create content. Mostly just plain vanilla pages. What is the best method for migrating these newly created pages to the live server? I know there is the Deploy module and also Backup and Migrate. Are these the de facto standards? I was wondering if there is anything else I might be overlooking or if there is a better/easier solution. I am ONLY interested in moving content. We will be using GIT to move code and the Features module to migrate admin changes.
THANKS
In the past I've used node_export and recently I've found (in drupal 7) that the uuid module is invaluable. It means you can keep a track of content even if the nid's change as you move it over.
There are some legacy modules hanging around too that did an okay job but their functionality has really been surpassed by the modules you mention and the ones above.
If you're creating all your content using fields added with cck, you shouldn't have a problem. I personally use node_export along with features to allow easy importing and updating.
One gotcha you might want to look for on node_export is when importing on the new site, if a node is found with the same uuid (i.e. you're doing and update), the default is to create a new node. I prefer to create a new revision. Worth tracking down that setting (it's there in d7 so likely in d6 too).
EDIT: node_export doesn't currently export panels very well if at all - just in case.
It depends on the structure and diversity of the nodes (how many fields of which type, how many node types). My first try would be to generate a view with XML output (views_datasource.module or views_data_export) on the dev site and use the feeds.module for XML import on the live site.
The above XML export modules are avalable for D6 and D7. In Drupal 6 I used views_bonus.module for the XML export.
I'm working in a web application that has several areas of bussiness work. With time it's size has became a problem to develop on and to maintain.
I would like to break the web project into several sub-projects or libraries depending on a main root web project that has the common files to share (Masterpages, Resources, Css, etc...)
Ideally I would like to have some kind of injection that allows me to optionally publish that "components" or simply publish a customized variation, although it's configuration depended on after deploy DB setup.
I searched all over the web, reading all the pages related to multiple projects, dependency injection and composite apps that I could find, 'till I soften my head, but couldn't find anything really useful.
Major part of the writings where a theoretical approaches or unit testing applications (well, you can't make your desired app, but you still can unit test something else)
Other approaches simply don't work in VS2010 .Net 4.0
Can someone address me on a COMPLETE solution or an example? Or simply lets discuss.
We say that the solution has the following structure, with module contents already separated into directories:
Solution
L_ Datalayer library project
L_ Bussiness logic /common utils library project
L_ Web project
L_ Controls
L_ Images
L_ Css....
L_ Warehouse
L_ Sales
Masterpages
...
Warehouse and Sales contains pages related to the "module"
Thanks,
I post my progress in the subject.
As per suggestion of Steven I experimented further more using MEF. Due to the lack of documentation, specially for webforms, that was a pain in*. So far I managed to implement MEF in my solution and sucessfully inserted a plugin project visible for the main app.
Then loads the available plugins, through an interface that has the plugin name, the default page url and its order, picks all this data and render a menu tab. That part it's easy.
Clicking on a menu element must redirect to the main page of the plugin, which will render several menus for its pages contained (from another export interface)
I finally got an aspx page embedded as a resource in the plugin project. Where I'm currently stuck.
¿Is there any way to render a page embedded as a resorce on a libray using MEF or I'm forced to also use a VirtualPathProvider? ¿Hows specifically the statement to redirect to that page? I've tried several ways but no-one works (MEF and VirtualPathProvider)
I looked at zillion of articles that talk about it but all them end doing control rendering, not page. So frustrating.
Though it is not an answer to your question, I am adding it as answer due to length of my suggestion.
I suggest you look into the approach NopCommerce is following where they have extended over .net with their own framework, which supports Plugins and extensions to existing solutions. Though I definitely know that nopcommerce is an ecommerce solution but if you study it, you can modify it according to your business needs or at least it can give you a heads on for what you should adopt while designing your solution. Hope it helps.
I have been doing dynamic PDF creation via ASP.net for some time -- in the form of HTML to PDF conversion. It works well for us, but we have accessibility requirements from the State to make everything is accessible. For static PDFs, we simply "tag" the files manually using Adobe's accessibility tools. Of course this does not work for dynamically created files. PDFs that I create dynamically fail the Acrobat Pro Accessibility test.
Does anyone have any ideas about create PDFs dynamically in ASP.net, but producing PDFs that are tagged and can pass the Adobe Accessiblity test? I have researched many components, but none that I have found support tagging.
Thanks.
I would look seriously at iText. AFAIK, this is the definitive library for creating dynamic PDF's, for Java and .NET.
You will need the book iText in Action.
Here's a quote from iText in Action on accessibility:
"You can use iText to create a document that passes all the criteria that are listed in Section 508."
I was curious how in the typical ASP.NET MVC mentality one could build a platform that others could develop plugins for. I mean, how would those plugins look like?
Like exiting user controls for WebForms, encapsulating all layers in themselves, or three different files representing the model the view and the controller. I should develop the core of a CMS, that I'd like others to build plugins for later on. Which mentality is better for that, classic Web Forms or ASP.NET MVC?
I need developers to be able to separately build components for that. Is it possible to encapsulate the MVC directory structure in a component DLL file and then when I reference the DLL file, to be able to directly access the component's model, view, or controller as part of the general MVC structure?
The most promising component techniques have come from the guys over at lostechies.com and Mvccontrib in the form of Portable Areas. Portable Areas allows an entire MVC app to be appended onto an existing application. So its not just a UI component but also provides all the work flow and screen integration as well.
Open Forum does something like this as well. I don't know how, but it is very plug and play.
For straight up plugin architecture there is an interesting screencast and source code for Rob Connery's link text. He takes advantage of the App-Code directory to slide new plugins into place without having to edit the main site.
I need to add a gallery to my website, to show screen shots of websites and applications.
I run IIS.
I'm looking for something that is fairly self-contained and ready to integrate without a lot of work. I'd like to through a bunch of images in a directory and let it go.
I would love some nice effects for browsing the gallery.
What would you suggest?
You might want to look at nGallery for ASP.NET 2.0. I've support an application that uses an older version of this. No experience with this particular version, though.
Consider Gallery Server Pro (www.galleryserverpro.com). It is a free open source web gallery based on ASP.NET and has been around for several years. It is easy to integrate into an existing site by using the self-contained ascx user control.
Disclaimer: I am the Creator and Lead Developer.