-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example request: DIY WYSIWYG #104
Comments
heavyweight WYSIWYG html editor solutions like TinyMCE still dominate the market even though lighter weight alternatives have sprung up here and there... I think snuggsi is a perfect way to approach creating a light and fast and more importantly, easily customizable, WYSIWYG text / markup / markdown editor |
This is amazing as need to come up with a document editor on a project with @robcole. Timing is perfect actually so i get to really knock this out of the park. @brandondees @pachonk will need your guidance on them as i've avoided them like the plague. Will start as soon as #85 is merged. Can we agree that at minimum a WYSYWIG is nothing more than a glorified Can we PLEASE put the |
@pachonk assigning this one to you to quarterback. I'll run touchdowns if you toss me the ball. Quarterback keeps the cadence. ;-) #FreeJewelry 💍 💎 /cc @albertoponti @cristhiandick |
Let's first start with a name.
That said i think needs to be some re-invention. MUST be something friendlier than an acronym.
First thing we should do is go over this documentation. Then can understand the 140LOC of a stick figure implementation they have. I bet i can trim that down by about 40% @pachonk @brandondees. @halorium may want to keep an eye out on ☝️ this issue/PR. https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Editable_content |
@snuggs why does it break specs? Where does it say that? |
@pachonk must go through #86 thoroughly. Fully documented in description. |
How about |
How about |
#CATAT /cc @tmornini |
CATAT? |
I'm fine with |
I agree, menu should be bottom-anchored by default, preferably, and IMHO should assume a preference for minimalism rather than including everything by default. formatting buttons should probably be designated in some kind of groupings which could be added / omitted easily together, without removing the ability to add / skip individual buttons. I believe the button features themselves probably can / should be nested custom element components of their own, making this a modular and extensible system by default (:unicorn: inside of 🦄 ). the architecture for how a button and text / code editing behavior should be structured to integrate with a parent editor container and menu bar, I don't have much idea about yet but I'll leave that to you who are actively working on it. I believe it should hypothetically be feasible to make this very versatile and flexible.
i don't think it's what we're trying to build here but i can foresee a wysiwyg and text-only variant of any given variation of this concept, so maybe |
@pachonk can even wrap the acronym in a |
@pachonk found this as a great benchmark.#salue @brandondees |
yeah was checking this out @pachonk interesting. |
It looks more snuggsi style already, might be easier. |
No description provided.
The text was updated successfully, but these errors were encountered: