I know what you are saying. Booki is the editing platform, where we edit books. It's not the reading platform where we read them.<br><br>I guess the confusion crept in because <a href="http://en.flossmanuals.net/civicrm" target="_blank">http://en.flossmanuals.net/civicrm</a> is still being fed from the old editing platform (and hence still has the old URLs in).<br>
<br>Following form that (sorry if you have answered these questions already :) ...<br><br>* Can we publish to <a href="http://en.flossmanuals.net/civicrm" target="_blank">http://en.flossmanuals.net/civicrm</a> from booki at the moment? <br>
<br>* Agree that it is confusing to have two read only versions.<br><br>Am I right in saying that 2 is a read only version of 'trunk' and 3 is the latest stable release. A read only version of trunk is useful when you are editing to see what your changes will look like before publishing, but perhaps this could be acheived by just hitting a preview / publish button and getting a copy located in a preview-like URL, kind of like a release candidate? So the workflow would be to go from TOC to edit without a view stage between?<br>
<br>I could live without 2, but it is kind of useful. how about styling 2 so it is obviously 'unpublished'?<br><br><br><br><br><br><br><div class="gmail_quote">On Fri, Dec 17, 2010 at 12:11 PM, adam <span dir="ltr"><<a href="mailto:adam@xs4all.nl" target="_blank">adam@xs4all.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
ok...so i think we might have a issue here with confusion over the 'read<br>
only' version of the manual in the editing section<br>
(<a href="http://booki.flossmanuals.net" target="_blank">booki.flossmanuals.net</a>) AND the 'read' version of the manual located<br>
here:<br>
<a href="http://en.flossmanuals.net" target="_blank">http://en.flossmanuals.net</a><br>
<br>
as i am seeing it...we do need to resolve the issue of duplicate url<br>
name for chapters...however, i am also considering the possibility to<br>
turn off the 'read only' display in <a href="http://booki.flossmanuals.net" target="_blank">booki.flossmanuals.net</a><br>
<br>
for example...<br>
<br>
1. we have the edit interface for civicrm:<br>
<a href="http://booki.flossmanuals.net/civicrm/edit/" target="_blank">http://booki.flossmanuals.net/civicrm/edit/</a><br>
<br>
2. and then the 'read only' version:<br>
<div><a href="http://booki.flossmanuals.net/civicrm/" target="_blank">http://booki.flossmanuals.net/civicrm/</a><br>
<br>
</div>3. and then the manual for users:<br>
<a href="http://en.flossmanuals.net/civicrm" target="_blank">http://en.flossmanuals.net/civicrm</a><br>
<br>
<br>
My feeling is that we have a big potential problem with people confusing<br>
2+3 ie. thinking that option 2 *is* option 3<br>
<br>
My feeling that this is happening is enhanced when I see some bugs being<br>
tracked which see to also share this confusion:<br>
<a href="http://booki-dev.flossmanuals.net/ticket/326" target="_blank">http://booki-dev.flossmanuals.net/ticket/326</a><br>
<br>
So...while we need to fix the duplicate url issue, i think we can also<br>
shut down option 2 since the edit interface now also has a 'view' button<br>
so you can read chapters without needing to edit them<br>
<br>
i know this is a lot to digest but if anyone can follow this and comment<br>
on it i would appreciate any thoughts on this<br>
<font color="#888888"><br>
adam<br>
</font><div><div></div><div><br>
<br>
On Fri, 2010-12-17 at 00:29 +0000, Michael McAndrew wrote:<br>
> sooo... you want to switch between full chapter name and<br>
> shorther url<br>
> name in editor (in TOC)? is that what you want? that is so<br>
> crazy that<br>
> it might just work! :)<br>
><br>
> I love it when a plan comes together. yeah, the more i think about<br>
> it, the more i like the section/chapter hierarchy for the civicrm<br>
> book.<br>
><br>
> so we would have<br>
><br>
> fundraising/about<br>
> fundraising/planning<br>
> fundraising/configuring<br>
> membership/about<br>
> membership/planning<br>
> membership/configuring<br>
><br>
> etc.<br>
><br>
> that looks pretty to me (i know, i'm sick).<br>
><br>
> imagine this would look really ugly in other situations though, so if<br>
> we could have the flexibilidad that would be awesome :)<br>
><br>
><br>
> On Thu, Dec 16, 2010 at 11:33 PM, Aleksandar Erkalovic<br>
> <<a href="mailto:aerkalov@gmail.com" target="_blank">aerkalov@gmail.com</a>> wrote:<br>
> On Thu, Dec 16, 2010 at 8:34 PM, Michael McAndrew<br>
> <<a href="mailto:michaelmcandrew@thirdsectordesign.org" target="_blank">michaelmcandrew@thirdsectordesign.org</a>> wrote:<br>
> > one problem - is this reported yet? we get a predictable<br>
> error in civicrm<br>
> > because we repeat a lot of chapter titles on purpose to<br>
> guide people through<br>
> > the book. for example.<br>
> > <a href="http://booki.flossmanuals.net/civicrm/_v/1.0/planning/" target="_blank">http://booki.flossmanuals.net/civicrm/_v/1.0/planning/</a><br>
><br>
><br>
> yes... aware of this. did not implement anything before<br>
> because i knew<br>
> people will get broken links in books. was thinking of maybe<br>
> implementing intelligent rename tool... also, it kind of<br>
> waited for<br>
> permissions. we do have permissions now (at least in code), so<br>
> i guess<br>
> i could implement chapter url_name rename also.<br>
><br>
> > my ideal world enhancement/solution to this would be to have<br>
> the option of<br>
> > overriding chapters names on an adhoc basis and to be able<br>
> to switch between<br>
> > a "section/chapter" and just plain old "chapter" url schema<br>
> for the default<br>
> > chapter titles.<br>
> ><br>
> > thought it might be worth discussing here a bit?<br>
><br>
><br>
> sooo... you want to switch between full chapter name and<br>
> shorther url<br>
> name in editor (in TOC)? is that what you want? that is so<br>
> crazy that<br>
> it might just work! :)<br>
><br>
><br>
> aco<br>
><br>
> --<br>
> <a href="http://www.binarni.net/" target="_blank">http://www.binarni.net/</a><br>
> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.flossmanuals.net" target="_blank">Discuss@lists.flossmanuals.net</a><br>
> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Michael McAndrew<br>
> 07817 802299 (mobile)<br>
><br>
> Third Sector Design Ltd.<br>
> <a href="http://thirdsectordesign.org" target="_blank">http://thirdsectordesign.org</a><br>
><br>
> For support, email <a href="mailto:support@thirdsectordesign.org" target="_blank">support@thirdsectordesign.org</a><br>
> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.flossmanuals.net" target="_blank">Discuss@lists.flossmanuals.net</a><br>
> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
<br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.flossmanuals.net" target="_blank">Discuss@lists.flossmanuals.net</a><br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><font style="color: rgb(102, 102, 102);" size="1"><span style="color: rgb(51, 51, 51);"></span><span style="color: rgb(51, 51, 51);">Michael McAndrew</span><br style="color: rgb(51, 51, 51);">
<span style="color: rgb(51, 51, 51);">07817 802299 (mobile)</span><br style="color: rgb(51, 51, 51);"><br style="color: rgb(51, 51, 51);"><span style="color: rgb(51, 51, 51);">Third Sector Design Ltd.</span><br style="color: rgb(51, 51, 51);">
<a href="http://thirdsectordesign.org" target="_blank"><span style="color: rgb(51, 51, 51);">http://thirdsectordesign.org</span></a><br style="color: rgb(51, 51, 51);"><br style="color: rgb(51, 51, 51);"><span style="color: rgb(51, 51, 51);">For support, email <a href="mailto:support@thirdsectordesign.org" target="_blank">support@thirdsectordesign.org</a></span></font><br>