Import docs #787
Import docs #787
Conversation
Added link to lektor-htmlmin
typo fix in flow block models documentation
Add 'Taiga.io Support' to Showcase
…idbaumgold.com Showcase davidbaumgold.com
…eploy Update docs for Travis CI deploy
Now that Lektor supports Python 3, we need to document this support. This change is perhaps a bit extreme: it replaces all explicit references to Python 2.7 with explicit references to Python 3.5. However, it's a good start, and it can and should be reviewed before being merged.
added code to install python dependencies for Ubuntu
updated installation doc
Add lektor-creative-commons plugin to plugin list
So that mistune can parse it correctly. Fixes lektor-website/106
…art-video-iframe Add quotations marks around HTML attribute
Because valid HTML is better than invalid HTML
Fix typo "net" → "next"
Added documentation about video FFmpeg support. Fixes lektor-website/264.
Update documentation of Guides:Portfolio size to width on some of the fields
Deleted _where_ following _anywhere_.
Fix grammatical mistake in /urls/contents.lr
Set my_image correctly
Fix 'comes in handy' phrase
Update Website.lektorproject
Update project file documentation to include `output_path`
|
Guys, please help with a checklist for getting things done? Please also commit to this branch liberally and help with related issues? First thing that comes to mind is lektor/lektor-website#219. |
xlotlu
force-pushed
the
import-docs
branch
2 times, most recently
from
500bbaa
to
a98bcee
Compare
|
Unfortunately I never thought about the original #PR / #issue references in the imported commits, which polluted lots of local issues with wrong references. See for example #304 (yey for another spurious reference). Force-pushing only made things worse, as the commits are preserved in the reflog and github doesn't remove the links. |
|
You could probably rework the script that imports the old repo to regex replace all #$bug_id references with absolute links to the original repo. But to be fair: If it was just for me, I would be ok with just importing the current status without transporting all the history. It would be nice to get the history, but going forward it will probably not be super neccessary. |
@dwt this is already there, it's just that I decided to use the
Well, it's true that from a practical standpoint the commit history is not as relevant as code history, more so due to them not being in sync, but... It's history. Even if it would be entirely irrelevant (which it isn't, diffs are useful information, for docs too), I personally think the commit history should be preserved because it snapshots people's contributions. It's a good homage to their efforts to preserve this info. |
|
@xlotlu More power to you - as long as it doesn't prevent getting this merged. |
This merges the docs from
lektor-websiteas a stand-alone site, along with the needed models, templates etc.Closes #756
Blocks lektor/lektor-website#226
The script generating this branch is available at https://gist.github.com/xlotlu/1dd9076e4886faa77797f1b3720f20a3. It uses https://github.com/newren/git-filter-repo/.