I am confused re. text linking in RSD, and the association to file/page names.

When linking to a page name, do we need to add the .html extension to the file name? Or are these extensions not used within RSD, and are only added automatically when the software exports out of the Preview folder and into standard HTML code?

This also applies to the software's naming conventions when creating pages. Do we just use a basic text name, or do we need to add the .HTML extension?

And what about the Text Link element in the toolbar? This element presents a # in the URL entry window, implying that this element refers only to links within the existing page (bookmarks), and is not used to link externally from the current page?

My experience is as follows -

1. When adding pages using the pages menu button or Manage Project, the program automatically adds the .html. If one adds it oneself, the file name gets exported as name.html.html.
2. When linking to a page name, the .html (Note) does need to be added by the user.
3. The # entry in the URL entry window needs to be replaced with whatever URL one wishes to link with unless, of course, the link is to an ID within the page.

Frank

Note: or whatever suffix the particular page or file has - it could be on another website altogether.

Thanks Frank. I was sort of getting to this on my own, as I noticed the .html.html extension showing up when testing in an external browser and finding my links non-functional. I have even located the preview folder and experimented with changing the file extensions there to match the extensions on my pages, though this may have made things worse, without understanding the naming convention the software uses in posting to the cache. I also noticed that RSD uses all lower case for file names in the cache. I created some pages while learning, that came from coding I did long ago, and which still had some caps in the file name. Uncertain what effect that may have had, I went back and properly renamed using all lower case, but by then things were a bit of a mess.

CC has done a pretty decent job of explaining the "big picture" in their online tutorials, but it would be helpful if they also included a chart which broke down the functions of each tool in the tool menu, for quick reference by noobs.

I think they should also use the same file-naming convention across the board to avoid confusion, especially since this program hides the true HTML code until dumping it through the export function.

To see the HTML code I often use the 'Preview on ...' button, and then press Ctrl-u on the keyboard to bring up the code in the browser. Within that code one can, of course, click on <link> etc. items in the header code to show also the .css etc. files in the browser.

Frank