always open to more feedback on the dark skin so i can dev on it until its fixed. i have an important appointment soonish but ill fix the mobile version of dark when i get home. sorry again for not testing as well as i should have.
No worries ur doin great
thanks, always appreciate hearing that 
take care!
oh and alightsoul go check out site development, give some feedback if youd like
Seems Dark-Old stopped working? It’s now got all the new stuff on it, same as the new Dark branch
Still working for me
It shouldn’t I deleted all the custom css for that.
Honestly the easiest way to be able to get things out in a smooth process is to make prs via github. Wouldn’t mind making and merging branches of changes so that things can be handled in a more incremental fashion. Also works well for prototyping over Dev discourse, instead of doing css like I have been doing through the sites admin panel.
But yeah, I’m probably doing a little too much too fast. I think I’m gonna take a couple days to run through the plugin tutorial myself so I can begin tackling some of the stuff I’ve got in my todo.
If you want to make a pull request against discourse go for it. But I mostly feel some of things we want are plugins. User post coubt, mafia editing abilities.
We can’t manually update the core because discourse is still under huge development. They commit almost every other day to master…
im still a rails dev and its a rails app, so im doing something ive done plenty of times before. Theres ways to add styling so there is virtually 0 conflict. for the record im NOT merging anything to “master” that isn’t styling unless its a plugin and those will introduce tests of course so there’s that.
I plan to just creating a folder in the stylesheets folder called namafia. so unless they put down a folder like that, it will never conflict. rails will automatically gather whatevers added to that styles folder automagically and itll show up here.
also FTR, the only styling that would be added would be universal. defining custom colors, mixins, sass garb that will help reduce skin-specific duplicated code. it would be a bad idea to merge any spreadsheet specific-styling to that, as i’ve learned from past and today (again my bad lol) so yeah only incrementally introducing things is what im down to do.
the stylesheet-editing portal can still be used in the event of a style-merge that has weird fringe effects, but as theres only 2 skins i should be able to catch everything and i plan on extracting piecewise since theres some functions i can introduce to make the code dryer.
ill still be using the CSS editing portal on dev in order to work on new versions of skins but that way ill almost never have to do use the portal here, in production, and ill spare everyone the consequences of my code lol
I know css doesnt conflict. Was talking about other things
yeah everything regarding plugins written for ember can be handled through the plugin interface…i dont wanna bother doing any merges giving me a difficult, error-prone time when i be using the plugin api to do my job for me. i dont know what discourse looks like post-plugin install but if the merge request was just to like, document progress and simulate me merging to master then im for that too.
PR’s are just good stuff. I dunno hwo cogs is but i can link that skelly PR to the real repo that the plugin is in. that’s how i want to do it, nice n safe so we figure out hwo to do it right
tell you what, ill do a little research about how other discourse communities handle their custom styling and get back to you with what i think is right. no changes on dark until then
I’m just confused what you are trying to pr against. I would LoVe for css to be a plugin we can add and revision it somewhere.
I stood this up the other day git.roragok.com
twitch emotes when?
i added plenty (see the emoticon thread) but whats missing?
yeah if this is what they do ill do it. wont look till tomorrow tho
goddamnit i love this site
1 Like
Discord ist honestly so good but its advertised as “Chat for gamers” sad
