I posted this discussion topic, and have received loads of viewing but no comments:
When I looked at the discussion just now, it was saying Read Only, but I don't understand why. Can anyone help me the original query, or why the discussion has changed to RO.
If you need more information, or I'm posting in the wrong place, perhaps someone could let me know.
Adobe announced a few days ago that it plans to stop developing Spry. That's probably why the Spry Forum is locked.
Do you still want to keep using Spry?
GitHub is a repository for scripts. Adobe moved the Spry scripts and sample files to GitHub for people who want to keep using/developing it.
You can keep using the Spry menus in your web site. Nothing has changed in that regard unless you previously linked to Spry's CSS and JS files on Adobe Labs server. If so, you'll need to download those support files from GitHub and save them in your site folder.
As to your other questions, can you post a link to your site and explain what you need help with?
Thanks, I understand GitHub a little better now. I didn't link to the CSS and JS files on the Adobe Labs server so I'm glad to know my website will be ok.
My site isn't live at the moment as I've taken it down whilst working on it. However, my question was more about tring to understand how to do something' in principle'.
I currently have around four templates and one individual screen. When I add/remove/edit the Spry drop down menu, I currently go to each of the four templates + the screen and make the adjustments to each one. It works fine, but is there a more efficient way of making changes so that I only have to do it once?
The second question is linked to the first - having made the changes to the Spry menus, when I make the site live, the majority of users see the 'old' version of the website. Am I doing something wrong, or is this just the way it works (presumably something to do with the pages being cached??)? I advise them to use Refresh, but not all of them are happy with this especially as they have to do it for each page.
Why so many templates? Even for complex sites, one Template is all you really need. Changes to layout should be contained in your CSS code.
Anyway, I use Server-Side Includes for site wide menus, headers and footers. In this way you only need to edit & upload one file. Changes are automatically populated to pages by the server. It's much more efficient than Templates or Library Items.
Server-Side Include basics
More on Server-Side Includes
Hope this helps,
I've been rationalising the templates over the last few days and I'm down to two + 1 individual page. I have one template for a 'plain' page of just an image and text, and a second template for a banner image, some text and a gallery of images. Does that sound ok? The odd page contains a script for the Contact Form which I'm loathe to tamper with, but am going to give it a go.
I've had a quick look at the SSI stuff and felt a little overwhelmed! I'm going to be away for a couple of weeks, so will read it properly when I get back. I'm sure I'll be back here!
Thanks for you help.
Europe, Middle East and Africa