How to auto-upload/sync graphic layouts from Fireworks to wiki?

Question

Data synchronization

As they work, designers often save mockups in a simple graphical format and post them, for example, on a wiki for further use by other team members.
If edits have been made to the layouts, they need to be synchronized with the wiki for relevance, but constantly re-uploading dozens of files is very inconvenient.

Ideally, you want the designer to export files from Fireworks and have them automatically updated in the wiki.

It certainly sounds like magic, but if anyone has solved a similar problem, I will be grateful for the advice.

Answer 1

I understand the problem is like this. A design team is working on a project (not even full-time, remote, sitting on different axes), the results of which everyone should have access to. Designers got sick of constantly uploading files to the project.
WIKi was created as a common medium for the exchange of information, and here you are faced with the fact that any technology equals exactly the same degree of limitation in any situation. Wiki is not user-friendly in this format. There are several solutions that I see:
1) If possible, install the client for everyone to synchronize files from the designer's local folder to a folder on a shared server. Check out bitsync. The designer can simply save the file in his folder and it will appear on the server. Alya dropbox. The wiki needs to be improved a bit. Not Bitrix? It should read files from the shared folder and generate html from them. For me, there is a wiki (well, let it be just a news resource) and the browser is generally an extra link. Why designers need to constantly download layout files from the browser when it comes to file sharing.
2) Connect the server as a network drive and throw layouts there, bypassing the synchronization programs, it may be convenient to set up something with the webdav protocol. Again, the wiki will have to make a page with code that reads all files from the server and generates html for the browser . If you agree on a common file format, then you can also parse the file names and somehow expand the descriptions about them in the html code.
It is not necessary to remake the wiki. You can just throw in there a link to a script for reading files from disk.
3) Use only bitsync without a shared server. All designers are connected in a common folder to each other. everyone sees the layouts of everyone in their folder.
4) Make a plug-in for the browser. which will upload the files in the folder at your direction, for example, "ready to upload" POST request from your cookies to your wiki (you only need to log in to the browser).
This is not at all difficult to do. A couple of times dabbled similar. You can add a window on top of the html of your wiki (no need to touch the wiki code at all) with the display of local designer layout files ready for 1-click lasing. Again, I don’t understand, but what the hell is a wiki when it comes to exchanging files.)
In general, you can do everything and it’s not as difficult as it seems. The question is simply in the theoretical description of the ideal solution. How would you see it? I see it more like 1 option. The user has saved. It became available either on the wiki or via a link on the wiki...

Answer 2

Another option:
1) click in FW send to email, a desktop mailer will open with a ready-made attachment, give what you need in the description of the letter. You can send to your corp mailbox, where the robot will remove the attachment and take the description from the body of the letter. Is a wiki more convenient...
As for the first option, from my first answer, you can describe the layout in FW through the file ctrl+alt+shift+F. And for the wiki, you will make a Bot that once a minute polls folders with files and reads your description from new PNG tags and adds it to the project for everyone.
The only problem here is that the bot can try to start reading a file that has just appeared but has not been downloaded. We ourselves got into such a situation - not the best solution. It is better to immediately give the bot script. And so the second option
2) make an extension for FW. This is probably the most convenient option if comments are required. The application is available as an icon in FW directly in the program, it can send the current file to the bot with the opening of the message window. Extensions are written there in my opinion on flex, or even on javascript. Yes, and maybe the bot does not need to be made on the wiki. The extension can fully emulate both authorization in your wiki and a post request with a file attachment ... well, look. This application will take two weeks of full time for an average developer. It is narrowly specialized because not everyone knows about writing extensions, but it is, in my opinion, the very minimum of actions.
1 click + gave a description + ok went to send.