First, I would like to thank Web Quick Start support team. This is the most active forums I have ever seen. All questions were/are answered in very timely way.
Thank you. We try to be helpful
1). How WQS handles the qlobal collection which is not section-related. For instance, I have footer shared by every page. Currently you get the collection by specifying the section name and collection name. If you want inherit or share the same results for every page, you just need to hard-code the same section name and collection name without creating new collection. Any other better idea without hard-code section name and collection name;
I would have expected "global" asset collections to live under the root section of the site. This is always easy to obtain:
webSite.rootSection.getAssetCollection("my-global-asset-collection")
2). I have list page including around one thousand of articles. I would like to have dynamic query to pull out the articles but don't like to see the list from metadata details since it is huge list. Also it is good idea to use dynamic query for this case since it will create association in alfresco based on the query.I'm not 100% certain of your meaning here, but of course you could carry out queries against the repo dynamically if you want to. Be aware of potential performance issues - a dynamic asset collection would be safer in this respect, since it is intelligently cached by the asset collection factory in the latest version of the code. If you want to carry out a query at request time then perhaps investigate using the OpenCMIS interface that is embedded in the WQS API. There is a thread-local Session object available via the static operation CmisSessionHelper.getSession(). You can see this being used in the class SectionFactoryCmisImpl, for example.
3). I would like to preview, publish functions showing in alfresco explorer instead of share.It's relatively unlikely that this will be done by Alfresco, but it should be quite simple for you to expose a custom action to do it. For the preview there is a class in the repo tier named "SiteHelper" (an instance of which is created with a bean id of "org_alfresco_module_wcmquickstart_siteHelper") that has a method called getWebAssetURL. Basically the preview action simply redirects the browser to the URL returned by that method. For the publish there is actually already an action defined with the name "webqs_publish". Invoking that action on a given node will place the node on the publish queue, so it's just a case of including that action in the appropriate action group(s).
