You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a planning issue, not yet complete, to eventually be broken up into sub-issues.
Idea
To make editing wikis easier, we're interested in making it possible to edit just one section; sections could be divided as block elements, so any header, paragraph, list, blockquote, or image would become a subsection.
Subsections could have an "edit" link next to them, which opens an inline editor for just that subsection.
DrupalNode would have a "update_subsection" or similar method, which accepts strings A and B; A is what's replaced, B is what replaces it. A new revision is made with the post-swap version of the whole wiki's content.
This architecture could be pretty robust, and might later lead to possible "suggestions" which affect just one block, and aren't yet "run". These could be stored as comments (so they're authored) or as some other new type -- and could apply to both notes and wikis.
However, we'd need to think about authorship; can we efficiently show recent authors for a given subsection separately from for a whole wiki page?
(Alternatively, could we think about per-line changes, rather than per-block changes, making it easier to split wiki pages up? But then list items would be one item per subsection, which doesn't sound right.)
Subsections would require:
Client-side sections method which splits latest revision body up by block element
DrupalNode.update_subsection(old, new) method
DrupalNode.replace(old, new) method which returns false if no replacements can be made
replace controller method in wiki_controller.rb
some view method for inserting "edit" links next to each block element on wiki pages
unit/functional tests for replace!
client-side tests for all that jazz
interface work to integrate new Rich editor inline
The text was updated successfully, but these errors were encountered:
jywarren
added
the
break-me-up
break up for cleaner code separation, discrete tests, and, easier and iterative collaboration
label
Nov 22, 2016
This is a planning issue, not yet complete, to eventually be broken up into sub-issues.
Idea
To make editing wikis easier, we're interested in making it possible to edit just one section; sections could be divided as block elements, so any header, paragraph, list, blockquote, or image would become a subsection.
Subsections could have an "edit" link next to them, which opens an inline editor for just that subsection.
DrupalNode
would have a "update_subsection" or similar method, which accepts strings A and B; A is what's replaced, B is what replaces it. A new revision is made with the post-swap version of the whole wiki's content.This architecture could be pretty robust, and might later lead to possible "suggestions" which affect just one block, and aren't yet "run". These could be stored as comments (so they're authored) or as some other new type -- and could apply to both notes and wikis.
However, we'd need to think about authorship; can we efficiently show recent authors for a given subsection separately from for a whole wiki page?
(Alternatively, could we think about per-line changes, rather than per-block changes, making it easier to split wiki pages up? But then list items would be one item per subsection, which doesn't sound right.)
Subsections would require:
sections
method which splits latest revision body up by block elementDrupalNode.update_subsection(old, new)
methodDrupalNode.replace(old, new)
method which returns false if no replacements can be madereplace
controller method in wiki_controller.rbThe text was updated successfully, but these errors were encountered: