I'm new to Pelican and am trying to modify the default theme (called simple) so suit my tastes. So I started by trying to get rid of the footer that says "Proudly powered by Pelican, which takes great advantage of Python".
So I looked things up online and went through the following steps:
Uncommented the footer section from the file ./venv/lib/python3.6/site-packages/pelican/themes/simple/templates/base.html.
Ran the command pelican content -s pelicanconf.py -t venv/lib/python3.6/site-packages/pelican/themes/simple
Tried make html as well
Viewed the site using pelican --autoreload --listen and reloaded the page
Also viewed the site using make devserver abd reloaded the page.
However, the footer stays. Yes, I can just hide it through CSS, but that's not my goal; my goal is to learn how to modify Pelican themes.
Not sure what else I need to do!
Related
I'm making a Docusaurus site with two separate sets of documentation. One set of documents is for our website content creators and the other is for site development documentation.
I followed instructions on the Docusaurus site for implementing Docs Multi-instance: https://docusaurus.io/docs/docs-multi-instance
I already have a /docs folder. I created a new /dev folder on the same level. Screenshot: two documentation directories
I installed the docs plugin according to instructions here: https://docusaurus.io/docs/api/plugins/#docusaurus/plugin-content-docs
I have the original docs instance from preset-classic. Screenshot: preset-classic code
I added a line for the additional docs by adding plugin info to the docusaurus.config.js file. Screenshot: plugin code
Both /docs and /dev have a markdown file called intro.md. The site loads but the two nav items both point to the intro.md file that's in /docs.
I changed the name of the intro.md file in /dev to devintro.md. After that change, I don't get an error in terminal, but the content isn't visible on the docusaurus site anymore. I just see the favicon and nothing else.
Here's a screenshot from inspector: inspector view of nav links
Has anyone else successfully gotten a multidocs instance running in Docusaurus? How can I have my nav items point to the landing page within each directory? Am I missing a step?
I have followed tutorial by Yihui and created a website using blowdown, github and netlify. Now, I want to change theme of my website. The issue is that I have several posts that produces many plots. As a result when I create a new website locally and add my posts, git push fails. I suspect it is because I have too many files.
I tried adding posts piece by piece as if I am writing a new post, which worked. But it will take too much time. I suspect others have the same problem. Is there a way to change theme of my website easier?
Two ways of changing themes in blogdown, which are documented here:
install the theme via blogdown::install_theme(), or just create a new site under another new directory and pass the GitHub repository name to the theme argument of new_site(). We recommend that you use the second approach, because Hugo themes could be very complicated and the usage of each theme can be very different and highly dependent on config.toml
In your use case, you can
1. blogdown::new_site(theme = "gcushen/hugo-academic") to build a new site
2. Copy your *.Rmd|*.md|*.Rmarkdown files into content/post
3. blogdown::serve_site(), if local preview is ok
4. setup github repo, push your new site to it ,and connects to netlify
It's strange that git push failed, it would be of great help to share the error message.
So here's a question. I'm new to Sylius, and am working on some simple CSS updates. I have a local copy of Sylius running with the built-in webserver: server:run. I also have a development server on Digital Ocean, which runs an (almost) identical copy of Sylius, aside from the configs of course.
Something strange is happening with my CSS update, however. I made a change to .navbar-brand within web/assets/compiled/backend_backend_4.css.
This change showed up immediately on my local. On the development server, however, when pulling down the change (git), and verifying that it now exists in that file, the change doesn't seem to propegate. It's effects aren't shown, inspecting the stylesheet doesn't show them, and furthermore viewing the css file sourcecode directly in the browser does not show the change. But on the filesystem it's definitely there.
I've tried clearing the cache, to no avail.
I also checked the assetic value in both config_dev.yml files, and verified they are both set to use_controller: true
Even still, I tried dumping assetic, to no avail.
So I'm wondering what's going on. Additionally, I realize that I probably shouldn't edit CSS files within a folder called 'compiled'. I'm sure there's a way to do that using a compiler, but I'm not yet familiar with the process and am just making minor changes and learning about caching so far.
Yes you are right you shouldn't be editing the compiled files.
You should edit the source files, then run gulp
or on my system i have to explicitly run npm run gulp
I've documented the solution that worked for me here. It didn't involve Gulp at all, but instead uses Assetic:
Assets need to be installed as hard copies first (I'm not quite sure
what this does exactly, but it seems like an important step because
it copies a lot of assets to places. Documentation was unhelpful but
it was suggested on Stack Overflow somewhere.):
app/console assets:install web
Assets should be edited in web/bundles/[bundle-here]/css or js. This
is frequently within syliusweb if it has to do with page styles /
layouts.
Hint: These assets are referred to in files such as
src/Sylius/Bundle/Resources/views/Backend/layout.html.twig (see the
opening:
(% stylesheets
tag, or search universally for this tag).
Within this tag, you'll see that stylesheets have an output to the compiled folder, but also list the
bundles where they pull their original css from. You should edit one of the source css files, if you'd like your changes to end up in the destination css.
After editing assets, dump assetic:
php app/console assetic:dump
Note - it is also possible to set an assetic watcher on these assets
(google to find out how, think it's a -w flag somewhere), but this is
said to only work in development mode, as it should.
After dumping assetic, the assets from the source bundles compile into their assets/compiled versions, usually combining multiple stylesheets. You should now see your asset refresh!
I've installed a fresh skeleton-navigation with typescript and tried to follow the instructions here:
http://aurelia-ui-toolkits.github.io/demo-materialize/#/installation
When checking the network tabs and console windows, there are no errors however the styles do not seem to apply to the controls.
Be sure that when you're setting up the skeleton, you follow either the Aurelia tutorial or the Materialize Bridge tutorial. They outline how to do manual bootstrapping in different ways which don't play well with one another.
In a nutshell, you either want to include the bootstrap script in your index.html file or you want to move that logic to your "main.js" file, not both. If you choose to go in the latter direction, you'll need to make sure that your HTML contains an import for "aurelia-bootstrappper" or the configure method of Main won't be run.
I've followed the instructions here:
https://developers.arcgis.com/web-appbuilder/guide/create-a-theme.htm
Created the correct scaffold, placed in stemapp/themes but I just can't get it to show up. Also, when I edit the DemoTheme, my changes aren't displaying. I've cleared my cache, using incognito but it's just not working. I've also used the yo generator to scaffold the theme, but no dice. https://github.com/Esri/generator-esri-appbuilder-js
What am I doing wrong?
Two possibilities:
If using Demo Theme, by default, it is disabled. To enable it, open the .repoignore file in client\stemapp\themes, remove DemoTheme from the file, and restart the node server.
During development, use "http://your host/webappbuilder/?id=stemapp" to access your theme directly.
If it doesn't appear here, you are not following the instructions correctly. Make sure all your theme names are well placed. There must be instances where you still have names from your copied theme(e.g DemoTheme), replace all of them with your theme's name. It should appear.
Restarting the ArcGISWebAppBuider service worked for me