Apostrophe Widget with a horizontal CSS Layout for an Area
I am making a widget with an area that is horizontally aligned using flexbox and I'd like to have all the "Add New Content" buttons and lines of the Apostrophe UI become vertical instead of horizontal.
While I can override the built-in styles, I'd have to use the dreaded !Important to make them even think about working, and even then, I don't really want to reach my dirty fingers in other folk's code if I don't have to. Plus, it appears that the actual position of some of these elements is decided by javascript... somewhere...
Is there a way to make this happen using the existing API? Where should I look?
css flexbox apostrophe-cms
asked Nov 27 '18 at 20:56
fogfog
187
add a comment |
I am making a widget with an area that is horizontally aligned using flexbox and I'd like to have all the "Add New Content" buttons and lines of the Apostrophe UI become vertical instead of horizontal.
While I can override the built-in styles, I'd have to use the dreaded !Important to make them even think about working, and even then, I don't really want to reach my dirty fingers in other folk's code if I don't have to. Plus, it appears that the actual position of some of these elements is decided by javascript... somewhere...
Is there a way to make this happen using the existing API? Where should I look?
css flexbox apostrophe-cms
asked Nov 27 '18 at 20:56
fogfog
187
Unfortunately the best way is to bash through the CSS. I would scope all yourapos-*overrides to a specific wrapper class to keep things separated. You'll have to really flesh out the user experience for editors (add content ui / dropzones, etc) in order for it to be any good. If you manage it in a clean way, the apostrophe team might be interested in incorporating the styles into core and adding an option to switch modes. Good luck!
– Stuart Romanek
Nov 29 '18 at 16:53
add a comment |
I am making a widget with an area that is horizontally aligned using flexbox and I'd like to have all the "Add New Content" buttons and lines of the Apostrophe UI become vertical instead of horizontal.
While I can override the built-in styles, I'd have to use the dreaded !Important to make them even think about working, and even then, I don't really want to reach my dirty fingers in other folk's code if I don't have to. Plus, it appears that the actual position of some of these elements is decided by javascript... somewhere...
Is there a way to make this happen using the existing API? Where should I look?
css flexbox apostrophe-cms
asked Nov 27 '18 at 20:56
fogfog
187
I am making a widget with an area that is horizontally aligned using flexbox and I'd like to have all the "Add New Content" buttons and lines of the Apostrophe UI become vertical instead of horizontal.
While I can override the built-in styles, I'd have to use the dreaded !Important to make them even think about working, and even then, I don't really want to reach my dirty fingers in other folk's code if I don't have to. Plus, it appears that the actual position of some of these elements is decided by javascript... somewhere...
Is there a way to make this happen using the existing API? Where should I look?
css flexbox apostrophe-cms
css flexbox apostrophe-cms
asked Nov 27 '18 at 20:56
fogfog
187
asked Nov 27 '18 at 20:56
fogfog
187
asked Nov 27 '18 at 20:56
fogfog
187
asked Nov 27 '18 at 20:56
fogfog
187
asked Nov 27 '18 at 20:56
fogfog
187
187
Unfortunately the best way is to bash through the CSS. I would scope all yourapos-*overrides to a specific wrapper class to keep things separated. You'll have to really flesh out the user experience for editors (add content ui / dropzones, etc) in order for it to be any good. If you manage it in a clean way, the apostrophe team might be interested in incorporating the styles into core and adding an option to switch modes. Good luck!
– Stuart Romanek
Nov 29 '18 at 16:53
add a comment |
Unfortunately the best way is to bash through the CSS. I would scope all yourapos-*overrides to a specific wrapper class to keep things separated. You'll have to really flesh out the user experience for editors (add content ui / dropzones, etc) in order for it to be any good. If you manage it in a clean way, the apostrophe team might be interested in incorporating the styles into core and adding an option to switch modes. Good luck!
– Stuart Romanek
Nov 29 '18 at 16:53
Unfortunately the best way is to bash through the CSS. I would scope all your
apos-* overrides to a specific wrapper class to keep things separated. You'll have to really flesh out the user experience for editors (add content ui / dropzones, etc) in order for it to be any good. If you manage it in a clean way, the apostrophe team might be interested in incorporating the styles into core and adding an option to switch modes. Good luck!– Stuart Romanek
Nov 29 '18 at 16:53
Unfortunately the best way is to bash through the CSS. I would scope all your
apos-* overrides to a specific wrapper class to keep things separated. You'll have to really flesh out the user experience for editors (add content ui / dropzones, etc) in order for it to be any good. If you manage it in a clean way, the apostrophe team might be interested in incorporating the styles into core and adding an option to switch modes. Good luck!– Stuart Romanek
Nov 29 '18 at 16:53
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53508021%2fapostrophe-widget-with-a-horizontal-css-layout-for-an-area%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53508021%2fapostrophe-widget-with-a-horizontal-css-layout-for-an-area%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Unfortunately the best way is to bash through the CSS. I would scope all your
apos-*overrides to a specific wrapper class to keep things separated. You'll have to really flesh out the user experience for editors (add content ui / dropzones, etc) in order for it to be any good. If you manage it in a clean way, the apostrophe team might be interested in incorporating the styles into core and adding an option to switch modes. Good luck!– Stuart Romanek
Nov 29 '18 at 16:53