{"action":"created","issue":{"url":"https://api.github.com/repos/ElektraInitiative/libelektra/issues/1030","repository_url":"https://api.github.com/repos/ElektraInitiative/libelektra","labels_url":"https://api.github.com/repos/ElektraInitiative/libelektra/issues/1030/labels{/name}","comments_url":"https://api.github.com/repos/ElektraInitiative/libelektra/issues/1030/comments","events_url":"https://api.github.com/repos/ElektraInitiative/libelektra/issues/1030/events","html_url":"https://github.com/ElektraInitiative/libelektra/issues/1030","id":183977453,"number":1030,"title":"Web Page Issues","user":{"login":"markus2330","id":7949075,"avatar_url":"https://avatars.githubusercontent.com/u/7949075?v=3","gravatar_id":"","url":"https://api.github.com/users/markus2330","html_url":"https://github.com/markus2330","followers_url":"https://api.github.com/users/markus2330/followers","following_url":"https://api.github.com/users/markus2330/following{/other_user}","gists_url":"https://api.github.com/users/markus2330/gists{/gist_id}","starred_url":"https://api.github.com/users/markus2330/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/markus2330/subscriptions","organizations_url":"https://api.github.com/users/markus2330/orgs","repos_url":"https://api.github.com/users/markus2330/repos","events_url":"https://api.github.com/users/markus2330/events{/privacy}","received_events_url":"https://api.github.com/users/markus2330/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2016-10-19T14:26:51Z","updated_at":"2016-10-23T07:28:49Z","closed_at":null,"body":"- [x] When going to Documentation -> Plugins you see the resolver README.md not the intro to plugins. (for decisions it works fine, the name \"README\" in the top left should be changed though)\r\n- [x] the left menu for plugins and man pages is much too long. Can we make the left menu more compact?\r\n- [x] is there an URL for pages in the left menu?\r\n- [x] markdown converter: is this CAPITALIZATION for headers really necessary?\r\n- [x] C-Code and ini files look funny. (no newlines,...)\r\n- [x] cryptograhic_key_h.. goes across its box (decisions)\r\n- [x] Libraries empty (README.md missing)\r\n- [x] left menu: cursor does not change (as it usually does over links)?\r\n- [x] external links in menus not recognisable (put some sign before them?)\r\n- [x] breadcrumbs need i18n keys in the language file\r\n- [x] plugin readmes look stupid, maybe we should reformat the info block at the top to a code-block?\r\n- [x] images and links in the documentation texts cause trouble\r\n- [x] maybe add a button to \"jump to top\"?\r\n- [x] function `makePrettyName(name)` that is used to format the file name for the menu needs improvements\r\n- [x] markdown for tables doesn't seem to work, although it is explicitely turned on\r\n- [x] some headlines don't look good, maybe change font\r\n- [ ] plugin sections expandable\r\n- [ ] `no-referrer` in links\r\n- [ ] sitemap\r\n\r\n## Docu issues\r\n\r\n### Plugins\r\n- [x] `src/plugins/*/README.md`\r\n - should always have a short-description in the same line as `infos/description` and a more comprehensive description starting on a new line\r\n - headlines should have a uniform style, e.g. first-capitalize and not all-upper-case, and also no h1 headlines\r\n- [x] `src/plugins/hosts/README.md` has unparsable headers (seems to be a missing space after #)\r\n- [x] `src/plugins/resolver/README.md`\r\n - the description headline should start in a new line (only short description inline)\r\n - the macros at the bottom are considered markdown by github and should be formatted as codeblock maybe\r\n- [x] `src/plugins/wresolver/README.md` the macro causes format problems\r\n- [x] `src/plugins/tcl/README.md` could be improved, almost no info there\r\n- [x] `src/plugins/ini/README.md` has unnecessary indentation in the multiline example?\r\n- [x] `src/plugins/yajl/README.md` has unnecessary indentation in the examples?\r\n- [x] `src/plugins/fstab/README.md` could use code-blocks for inline code\r\n- [x] `src/plugins/regexstore/README.md` either give a list of TODOs at the bottom or remove the hint; plugin status is `unfinished` anyway\r\n- [x] `src/plugins/simpleini/README.md` reformat HEADER (add space after #)\r\n- [x] `src/plugins/cachefilter/README.md` put description with a headline into new line\r\n- [x] `src/plugins/keytometa/README.md`\r\n - indentation of examples\r\n - code blocks for elektra keys?\r\n- [x] `src/plugins/struct/README.md` indentation of example code like `src/plugins/glob/README.md`\r\n\r\n### Libraries\r\n- [x] `src/libs/README.md` uses absolute paths\r\n\r\n### Other\r\n- [x] `doc/COMPILE.md` could need some improvements too (e.g. `CMAKE_INSTALL_PREFIX/include/elektra` formatted as code block for better readability)\r\n\r\n## Snippets\r\n\r\n- [ ] Scope/Slug is not explained. And is it a good idea to make it required entries?\r\n- [x] edit entry does not work after only changing \"Configuration:\"\r\n- [x] Rank in account information without explanation?"},"comment":{"url":"https://api.github.com/repos/ElektraInitiative/libelektra/issues/comments/255573894","html_url":"https://github.com/ElektraInitiative/libelektra/issues/1030#issuecomment-255573894","issue_url":"https://api.github.com/repos/ElektraInitiative/libelektra/issues/1030","id":255573894,"user":{"login":"Namoshek","id":8877609,"avatar_url":"https://avatars.githubusercontent.com/u/8877609?v=3","gravatar_id":"","url":"https://api.github.com/users/Namoshek","html_url":"https://github.com/Namoshek","followers_url":"https://api.github.com/users/Namoshek/followers","following_url":"https://api.github.com/users/Namoshek/following{/other_user}","gists_url":"https://api.github.com/users/Namoshek/gists{/gist_id}","starred_url":"https://api.github.com/users/Namoshek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Namoshek/subscriptions","organizations_url":"https://api.github.com/users/Namoshek/orgs","repos_url":"https://api.github.com/users/Namoshek/repos","events_url":"https://api.github.com/users/Namoshek/events{/privacy}","received_events_url":"https://api.github.com/users/Namoshek/received_events","type":"User","site_admin":false},"created_at":"2016-10-23T07:28:49Z","updated_at":"2016-10-23T07:28:49Z","body":"> Do you mean implementing both or only a global tag? The global tag should be enough if it is non-trivial to add it to every link.\r\n\r\nI mean to only add a global tag instead of tagging every link, which is not so easy, because I'm using links in quite some places already (and not all are HTML links, the Report on GitHub button for example is implemented code-based, which makes it even more difficult).\r\n\r\n> Thanks, smaller search engines might still heavily rely on it. Supporting changefreq and priority seems to be not so important.\r\n\r\nYeah, you are right.\r\n\r\n> Do you mean you also cannot add the snippets in the sitemap?\r\n\r\nSorry, I guess what I wrote was a bit misleading. I can certainly add dynamic pages like the docu from the structure file (because that basically is already a sitemap), but I don't think I can add pages for the content of the backend. Other pages with big databases create the sitemap by appending, but that won't work here because backend and frontend are split apart. I can try to add sitemap creation also for dynamic pages during website-content creation, but I can't promise anything.\r\n\r\nBtw. you are talking about a sitemap.xml, right? Not one visible for the users in the frontend?"}}
{"actor":{"display_login":"Namoshek"}}