XSite
  1. XSite
  2. XSITE-15

XSite is not WYSIWYG friendly - would love to see images (etc) work while editing

    Details

    • Type: Wish Wish
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      meaning site/content and site/resources/images/ are too far removed to be useful.

      Better would be

      src/site/
      index.html
      foo.html
      sitemap.xml
      images/
      logo.png

        Activity

        Hide
        Paul Hammant added a comment -

        Lets try again -

        . src/site/
        . index.html
        . foo.html
        . sitemap.xml
        . images/
        . logo.png

        Show
        Paul Hammant added a comment - Lets try again - . src/site/ . index.html . foo.html . sitemap.xml . images/ . logo.png
        Hide
        Paul Hammant added a comment -

        Jeez

        src/site/
        ____index.html
        ____foo.html
        ____sitemap.xml
        ____images/
        ________logo.png

        Show
        Paul Hammant added a comment - Jeez src/site/ ____index.html ____foo.html ____sitemap.xml ____images/ ________logo.png
        Hide
        Mauro Talevi added a comment -

        That does not play well with L10N and use cases in which resources are re-used.

        The WYSIWYG is likely to work better on a non-templatable approach. It's not just the images that are needed, but the style and the templates as well.

        I think the advantages of separation (eg L10N support) outweigh the disadvantages. Ultimately it just requires a copy of the modified resources to the output directory (ie without regeneration site).

        Alternatively, you can use WYSIWYG on the output directory and copy back to scm the resources once you're happy with them.

        Show
        Mauro Talevi added a comment - That does not play well with L10N and use cases in which resources are re-used. The WYSIWYG is likely to work better on a non-templatable approach. It's not just the images that are needed, but the style and the templates as well. I think the advantages of separation (eg L10N support) outweigh the disadvantages. Ultimately it just requires a copy of the modified resources to the output directory (ie without regeneration site). Alternatively, you can use WYSIWYG on the output directory and copy back to scm the resources once you're happy with them.
        Mauro Talevi made changes -
        Field Original Value New Value
        Resolution Won't Fix [ 2 ]
        Status Open [ 1 ] Resolved [ 5 ]

          People

          • Assignee:
            Mauro Talevi
            Reporter:
            Paul Hammant
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: