On 05/13/2012 09:42 AM, Dave Fisher wrote:
On May 13, 2012, at 8:50 AM, Kay Schenk wrote:On 05/12/2012 08:49 PM, Joe Schaefer wrote:While I don't quite grok what you are having issue with regarding mdtext pages, I can give you an example of how to link to some named element within the current page: [Link text](#name) where "name" is the id or name of the element you want to link to. More generally I've explained a few more of the UI design elements just now at http://www.apache.org/dev/cmsref#organizationWell I wasn't as clear as I could have been either. :/ When I use the CMS bookmarklet to edit one of the mdtext pages, I am presented with a very limited set of "functions" I can use vis a vis the toolbar presented to me. And the WMD link presented, http://www.wmd-editor.com/, doesn't seem to work -- I was going to use this to get to more information. So thanks for the info you provided above. Because I couldn't get anywhere with the WMD link, I wasn't sure what to do. Maybe I put more thought into this then was needed, though...I guess i could have just entered markdown directly.The CMS build scripts really don't need much explaining as they don't actually contain very much rendering logic themselves, all that information is in the per-project site's trunk/lib/path.pm and trunk/lib/view.pm.OK, well then, something that was suggested to me vis a vis using the build scripts to generate some dynamic elements in a page, might not work. This is a "down the road" project and something that would be nice for us but not absolutely needed now. I will get back on some options regarding this type of thing later. Higher priority items right now...I've been modifying the path.pm and view.pm all along. What dynamic elements do you have in mind? It is totally possible to have certain pages auto-update every hour (like www.apache.org) and contain elements like twitter feeds. Also, there is another thread where the site design is being discussed.
well it...it concerned culling the native language lists that had been setup and automatically inserting this info into:
http://incubator.apache.org/openofficeorg/native-lang.htmlWe can start a new thread...and I'm starting a page on "web site enhancements" in the planning wiki to include items like this for further discussion. Might be easier/cleaner to do a wiki "whiteboard" approach rather than e-mail.
more later...
Regards, DaveHTH ----- Original Message -----From: Kay Schenk<[email protected]> To: [email protected] Cc: Sent: Saturday, May 12, 2012 11:56 AM Subject: Re: Feedback on the CMS Hi Joe -- On 05/11/2012 11:18 AM, Joe Schaefer wrote:With 1100 builds so far the ooo-site CMS instance is only 350 builds behind www.apache.org as the most-used CMS tree so far.� I monitor the CMS logs daily to evaluate usage and this project publishes about as often as all our other projects combined, which really makes me wonder where we'd be here if the org had never created the CMS in the first place. The ooo-site is far and away the largest instance at over 9GB total.� The reason I'm writing here is to ask general questions about user satisfaction with the CMS:WOW!1) Is there any aspect of the CMS that needs immediate �� improvement?Oddly, the area I seem to have problems with in the current environment is the editing of the mdtext files. I can't see to find, on the toolbar provided, editing features such as adding a link name for local in-page links for example. And I don't think I'm provided with direct access to mdtext from the CMS (I could be wrong about this, but I didn't see a way), so that's my only immediate suggestion. I rarely use it for direct editing of www.openoffice.org, but it works great for that too.2) Are you satisfied with the workflow, or are there areas �� that could stand improvement?It's very good as far as I'm concerned. I've gotten into the habit of checking the buildbot to ascertain buld completion to staging, but the comments about notification BACK to the user would be a wonderful addition.3) Is there anything that should be done to encourage more �� users who are not committers to use the CMS to submit patches �� to the list?Comments here about automatically submitting to BZ would be super!4) Are there any UI features you'd like to see implemented, �� either in the web interface or the publication script?I can't think of any UI features right now except for the mdtext editing I mentioned in 1). But more information/instructions on items like where our build scripts are, what can be done with them as for as additional customizations would be helpful. Again, maybe this information is out there and I just haven't found it yet.Thanks in advance for taking the time to answer a few of these!I think it goes without saying that Apache OpenOffice greatly appreciates the effort infra has put into the CMS over the last few months to serve the project's huge needs. Thank you! -- ------------------------------------------------------------------------
MzK
"Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out." -- "Ironic", Alanis Morissette-- ------------------------------------------------------------------------
MzK
"Well, life has a funny way of sneaking up on you And life has a funny way of helping you out Helping you out." -- "Ironic", Alanis Morissette
--
------------------------------------------------------------------------
MzK
"Well, life has a funny way of sneaking up on you
And life has a funny way of helping you out
Helping you out."
-- "Ironic", Alanis Morissette
